Share your ideas with us

As a loyal Aftership customer, I am extremely disappointed to learn that integrating a new carrier requires an additional fee—a neither transparent nor customer-friendly policy. Carrier expansion should be a standard improvement to Aftership’s platform, not an extra cost passed onto paying customers. Why This Needs to Change: Improving Aftership Should Be Your Priority, Not an Upsell Adding new carriers benefits all Aftership users. Expanding carrier integrations should be part of Aftership’s ongoing development efforts, not a hidden fee imposed on individual customers. Hidden Costs Undermine Customer Trust Nowhere in Aftership’s pricing model is it clearly stated that carrier integration comes with additional fees. This lack of transparency frustrates users and creates an unexpected financial burden. Loyal Customers Deserve Better Customers who have trusted Aftership for their business operations should not have to pay extra to access a fundamental feature like carrier support. Proposed Solution: Aftership should eliminate extra fees for new carrier integrations and invest in expanding its platform instead of charging individual users. This would be part of its commitment to improving service for all customers. Clear, upfront disclosure of costs should be required if Aftership maintains this fee structure. If Aftership truly values its customers, this change must ensure a fair, transparent, and customer-centric experience.

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.

I would like to include the RMA number barcode on the returns label. This way, upon receiving the returns label at my warehouse, I can simply scan the barcode to retrieve the RMA number. Subsequently, I can use this number to efficiently locate the corresponding RMA information within the returns system. This process will significantly enhance the operational efficiency of our RMA procedures.

Upload label manually from external source and link (instead of file only) Today its only possible to upload label manually through file via computer.   Hope this will change and we ca upload via external url

Instead of directly integrating Aftership with Gmail, I would like to send my emails with package information to an aftership email address associated with my account, for aftership to parse and automatically show tracking information. 

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.

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.

I work in the furniture industry with thousands of products and continuous new product listings.   Consumers often inquire about variations in materials and sizes between similar pieces of furniture, placing a significant burden on my support team. Generating comparison pages for every query we receive is unfeasible due to the volume of requests.   Given the potential of AI to suggest comparable items, could it also be leveraged to pinpoint disparities among products and present these distinctions to consumers? Such a system can alleviate my workload significantly and potentially reduce bounce rates as well.

Consider leveraging Estimated Delivery Dates for Return Shipments as a column on the Returns Dashboard

I don't want to sync my email, so it would be great to be able to add a record for items that I've ordered but haven't shipped yet. I can then edit/update the shipment when the tracking number is available.