Share your ideas with us

Expose an REST API for creating Warranty Claims.

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.

Would be a great feature if there was a link to the returns status page within the returns dashboard.   And if this link can be easily copied so we can share to the end consumer if they call through the contact center/help, then our agents can quickly copy the link and then email/share to the end consumer

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.

Would you be able to: 1. Add a functionality that restricts order views based on a ship from location or/or login? We have multiple ship from locations and we are 100% manula orders; it creates confusion when one warehouse sees orders from another warehouse.  2. Have a ship to address book and have that be varied based on ship from locations. We have set ship to locations and it doesnt change often. 

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.

Scenarios 1. We give a customer a partial refund for a coupon code they forgot to enter. This partial refund is currently stopping the customer and us from being able to request a return in Aftership. Please allow an option to make RMA or override in this scenario. 2. (similar to #1) Customer orders multiple items, gets RMA for one item, returns it and is refunded. Now they want to return the other item, however, because there is a refund in Shopify we are not able to open a RMA for the other item because the order shows as returned. Please allow option to make RMA or override in this scenario.  Thank you

As a merchant, I would like to break down the shipping volume report by Carrier and Lane. Currently, it can be broken down by only one condition.   This would allow us to understand how a carrier is performing in a specific market.

Enable merchants to customize the duration before an RMA is automatically canceled. Currently, the system only allows for auto-cancellation after 28 days of inactivity. To better suit our company's needs, we would like the option to extend this period.

I have had customers who have accidently unsubscribed themselves from receiving AfterShip emails. I can see them in the Unsubscribe list, but I cannot remove them. Please add a feature that would allow AfterShip administrators to remove emails from the Unsubscribe list. Currently this process has to be done by the AfterShip tech team. By making this a self-service feature, you will reduce the labor required by the AfterShip team and make the product more efficient.