Share your ideas with us

My package is currently reading that it is out for delivery in my area, but is still showing to be located in a totally different country so the tracking needs to be updated and fixed because this has been an ongoing issue that I've contacted them about for support and it's still reading the same way

 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.

When utilizing an HTML email editor, I aim to display and personalize shipment or order items within my tracking notifications.   This feature would allow shoppers to conveniently view their purchases directly in the email, thereby improving customer satisfaction.

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

I want to be able to mask certain words such as 'flight'and ''import'', or ''customs''. As for EU customers this is not relevant infromation and they faster think goods are from china and want to return faster. When they see basic info and a EDD they are assured everything is good. They dont neem more info.

Compared to AfterShip Tracking, Returns currently lacks key customization capabilities: * No page segmentation (by market, country, store, customer type, etc.) * No way to associate a return with a specific store * No configurable notification flows based on return status or parameters The absence of these settings significantly limits customization for clients and prevents them from offering tailored return experiences. Suggestion: Introduce advanced configuration options similar to Tracking, including: * Segmented return pages based on defined parameters * Store-level return association and rules * Conditional notification flows triggered by return events and attributes These improvements would greatly enhance flexibility, customer experience, and alignment across the AfterShip product suite.

Most major carriers already provide an estimated delivery date/time as part of their tracking data, but this isn't currently surfaced in the app. Context: Customers tracking a shipment want to know when it will arrive, not just its current status. Right now they have to infer this themselves or check the carrier's own site separately. Issue to address: Add a field that displays the carrier's estimated delivery date (and time window, where the carrier provides one) on the tracking/order page. This would reduce "where is my order" support inquiries and improve the post-purchase experience. Suggestion: Pull the estimated delivery data from carriers that already expose it via their APIs, and display it prominently near the shipment status.

Add the ability to block a return and direct the customer to the warranty portal. Bonus if you could log the customer in and auto fill information.   Potential Mockup Potential User Experience

I would like to view the chart showing reasons for late shipments in the current on-time report that I am using.

Hi there, We ship wine, which means orders are often held by our fulfilment center when temperatures along the route are above or below certian threshold we have set. I would like to create a flow that automatically notifies the customer that their order has been flagged for a weather hold and ensures them it is still on the way. Is this possible? Thanks