Share your ideas with us

Requesting to provide an option for the end consumers to edit the review on the AfterShip tracking page after the product is being delivered.    Currently, the customers are able to leave the review but unable to edit them. 

Currently, AfterShip's webhook outgoing IP list is only available on an HTML documentation page (https://www.aftership.com/docs/tracking/webhook/webhook-outgoing-ips). This makes it impossible to automate IP allowlist management in infrastructure-as-code (IaC) workflows.   Problem: Teams that use IP-based firewalls to secure their webhook endpoints must manually monitor the documentation page for any IP changes and update their firewall rules accordingly. If a change is missed, it can cause webhook delivery failures and broken integrations.   Request: Please publish the webhook outgoing IP list as a dedicated plain-text endpoint — similar to how Cloudflare publishes theirs at https://www.cloudflare.com/ips-v4 — where each IP is returned on a separate line.   This would allow teams to: * Fetch the IP list programmatically as part of their CI/CD or IaC pipelines * Keep firewall allowlists automatically in sync without manual intervention * Avoid service disruptions caused by missed IP changes This is a standard practice among major API providers and would significantly improve the developer experience for customers who manage network security programmatically.

To enhance the shipping experience for customers purchasing hair extensions or hair care products, AfterShip could focus on providing real-time tracking updates that are both detailed and easy to understand. For the hair industry, ensuring timely delivery is critical, as customers expect to receive their products in a timely manner, especially for events like weddings, parties, or other special occasions. Additionally, offering automated notifications at each stage of the shipping process — from dispatch to in-transit updates and delivery confirmation — would allow customers to stay informed and reduce anxiety around the arrival of their products. A specific feature that would be beneficial in the hair industry is providing an estimated delivery window based on the type of hair products purchased, considering how delicate and time-sensitive hair products can be. Another improvement could be offering customized delivery options, like express shipping for urgent orders or delivery tracking tailored to customers’ needs based on their location, enhancing convenience and customer experience. By integrating these features, AfterShip could help ensure a seamless experience for customers in the hair industry, driving satisfaction and repeat business.

We are a worldwide dropshipping service catering to e-commerce entrepreneurs. Merchants can design and market personalized products through us, setting prices and choosing their sales platforms from our integrated e-commerce options.   Once merchants place orders, we will handle the manufacturing, fulfillment, and shipping logistics to consumers.   When I am using Aftership for tracking, I want to enable my premium customers (merchants) with the ability to customize white label branded tracking pages and possibly an API to create them (since they won't have access to Aftership admin, and it would be impossible for me to maintain all tracking pages for them).   So that I can add this ability as part of the product & service package for my main customers (merchants), which creates more value for my business.

As online shopping continues to expand, cities and businesses are looking for ways to simplify last-mile delivery. In this shift, automated parcel lockers have become a practical solution, helping reduce missed deliveries and improving convenience for both couriers and customers. Their use is steadily shaping the future of contactless and efficient package management.

I hope to insert a form in the email, allowing customers to fill out the form directly within the email.   For example, if there are some events or new product launches, I would like to invite users to participate and collect information on whether they are interested or not.

That would be great if Feed could accommodate the listing of "not-for-sale products" on TTS. This feature is newly introduced in TTS, where the product is not for sale to shoppers but will be gifted to them instead.

 I just started using the app today and overall I do like it, but I have a few minor suggestions. 1. A compact mode: right now the list of tracking numbers/packages is very spread out. Consolidating it would make it look cleaner, IMO. 2. Allow me to put tags on them, custom or otherwise. For example I have a few incoming packages and a few outgoing ones. It would be nice to add tags to differentiate them and also filter by them if needed. Hopefully that made sense. Thank you.

Goal: To make it easier for customers to accurately select the correct item for return when using the return portal. Preconditions: The customer has placed an order containing multiple items, some of which may have similar or identical titles, colors, or sizes. The SKU numbers for the items exist in the system but are not currently displayed in the return portal. Trigger: The customer initiates a return and accesses the return portal to select the item(s) they wish to return. Basic Flow: The customer logs into the return portal. The portal displays the items from their order, including details such as title, color, size, and now the SKU number for each item. The customer uses the SKU number to cross-reference their order confirmation or invoice, ensuring they select the correct item for return. The customer completes the return process with confidence that the correct item has been selected. Postconditions: The customer successfully returns the correct item without confusion. The support team receives fewer inquiries about mismatched returns. Benefits: For Customers: Improved user experience by reducing confusion when selecting items for return. Greater confidence in completing returns independently. For the Business: Reduced customer support requests related to returns. Increased efficiency in processing returns, minimizing errors caused by incorrect item selection. Priority: Medium – This enhancement has a high potential to improve customer satisfaction with a relatively low implementation effort. Technical Requirements: Modify the front-end display of the return portal to include SKU numbers as part of the product details. Ensure the SKU numbers are fetched and displayed consistently across all customer orders. This use case focuses on enhancing the clarity of the return process for customers while streamlining operational efficiency for the business.

Change the update indicator Dot from the light blue color to the orange color you already use in your iOS app. It is hard to pick out the dot if you have a long list of shipments. If it was the orange color you already use in the app it should be a simple change to make for an updated version. Also so carriers on the list of carriers to pick from are now asking for receiving zip, so those carriers never update now.  Thanks