Share your ideas with us

I guess for shipping emails sent out to my customers, it would be nice to have dynamic info that updates as the package progresses through the network. I also want all my existing emails to stay current.   The reason is simply that I wanna give my customers a unified experience by delivering consistent messages to them. I believe this will help with my customer satisfaction.

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

Background On the Return Summary page, the Return Status section is commonly used to display shipping instructions that guide customers on how to return their items. As part of these instructions, customers are often required to include both their RMA ID and Order ID with the return shipment so that the warehouse and processing teams can identify and process the return correctly. Currently, the RMA ID is only displayed at the top of the page, and the Order ID is not prominently visible within the Return Status section. Requested Enhancement Add configurable fields within the Return Status section of the Return Summary page to display: * Order ID * RMA ID These fields should be displayed alongside the shipping instructions and return status details, making them easily accessible to customers while preparing and packaging their return shipment. We are open to any placement within the Return Summary page that provides clear visibility and easy access to these details. Business Use Case Our client specifically requested this enhancement because their return instructions ask customers to include the RMA ID and Order ID with the return package. Having these details displayed directly within the Return Status section would: * Improve visibility of important return information. * Reduce customer confusion when preparing returns. * Eliminate the need for customers to search for these details elsewhere on the page. * Help ensure return shipments contain the correct identification information. * Improve operational efficiency and reduce return processing delays. Expected Outcome Customers can quickly locate the required Order ID and RMA ID in the same section where they view their shipping instructions, resulting in a smoother and more user-friendly return experience. Thank you for considering this enhancement. We believe it would benefit merchants who require customers to include reference identifiers with returned packages and would improve the overall returns experience.

While using personalization, I want to understand the actual product results generated by these algorithms and the reason behind the chosen product displays for shoppers.   If I can preview the recommendation results in the admin, it would reduce uncertainty, ensure optimal outcomes, and improve my marketing strategies to boost conversions.

We'd like the ability to restrict which order-editing options are available on a per-country basis, rather than applying the same set of options globally.   Many merchants work with regional checkout or fulfillment partners (e.g. Global-E) that prohibit certain order changes after an order is placed in specific countries. For example, a merchant might need to limit editing to only "apply discount code" and "cancel order" for a subset of countries, while keeping the full set of editing options available everywhere else.   Being able to configure order-editing permissions by country/region would help merchants stay compliant with regional partner restrictions without giving up flexibility in other markets.

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

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.

The “Back” button on the RC portal is not obvious or prominent enough. It is too hard to find and blends into the page. 

For the tracking page I am currently using, it would be great to have the Delivery Instructions feature, so that my customers can provide specific instructions to carriers, and ensure successful deliveries.   This feature will also be valuable for drivers who can have all the necessary information at their fingertips, even for dispatchers who can manage delivery more effectively with all that info.   A seamless last-mile delivery experience can create a sense of reliability and convenience that fosters long-term customer relationships and encourages repeat purchases for my brand.

It would be useful to have a Sku column amognst the list when editing the returns dashboard. The image of the item is useful but often the item is enclosed in a boxed which is marked with the sku. Therefore at first glance, the sku is seen before the physical item.