Share your ideas with us

If you are working with many different returns in one day, there needs to be a quick way to copy information like in Shopify as example. Please reference the far right side of this image:

Hi, I hope you can include a column where users can also see "WHEN" the order arrived in customs clearance and "WHEN" it was released. I am referring to ALL orders, not just the delayed orders.

Please let me hide the ad carousel, I am happy to pay subscription or whatever to disable it. Thanks 

 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.

Hello,  We currently use AfterShip Feed to connect our Amazon Seller account to TikTok Shop. But it would be fantastic to be able to also connect with Walmart Seller's MCF. It would allow even greater reach of products on more sales channels.

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.

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.

As a user, I'd like the ability to pull in tracking numbers to my dashboard by parcel account number so that I can view all shipments assigned to a specific or multiple parcel accounts.   For example I have 10 parcel accounts (4 with DHL and 6 with FedEx). I'd like the ability to utilize the parcel account number(s) instead of the API to pull in tracking associated with my parcel accounts.

When I receive tracking from suppliers, I add manually to AfterShip.  Usually there's more than 1 tracking number, for the same courier, so it would be great to able to add multiple tracking numbers at the same time as comma separated.   When clicking Save, it would then use all the information entered, for example; Customer name, order number etc etc.   Below example for tracking number 123456789 and 987654321  

Background: * At the moment, a user with a specific domain can easily create a new organization when creating an account in AfterShip * We don’t indicate to this use that an existing organization is already linked to the same domain This can create confusion when member are trying to get access to an organization proactively (without being added by the current owner) * Hence we end up with support tickets from member not able to get access to their main org. Expectation: * Alert message during new inscription if we identify that the email domain is already used. * Eventually an option to send a request to the owner of the main org. * Possibility to delete the new account to avoid unnecessary org and member creations for our clients. * Could be active only for ENT client if we want to reduce the scope