Share your ideas with us

As a merchant, I allow shoppers to exchange items for different variants during returns, which may have different prices. For example, a Small size costs $30 while a Large size costs $50.   Currently, Shopify allows me to adjust prices manually only after the Return Merchandise Authorization (RMA) is submitted. If aftership could facilitate charging or refunding price differences for variants during the return request process, it would greatly streamline our operations and enhancing the overall efficiency of RMA management.

I am using the API for Zoho Inventory integration with Aftership. I would like the items on the shipping order of Zoho Inventory displayed on the shipment items of the email notifications to my customers. The shipments are created within Zoho Inventory and tracked by Aftership.

The current capability features a static returns approval notification. There are instances where the approval notification should be customized before being sent to the customer. Currently, the only way of doing this is to change the approval notification for all returns, save, go back to the RMA in question, approve it with the new notification, make sure no other returns are approved, go back to the nofication and amend it to how it was prior and save.   Use case: there may be a specific product that is available for exchange in store, this needs to be checked with the store first so cannot be a hard rule. If the approval notification could be amended on an adhoc basis, you could give the customer the option at the point of approval and avoid back and forth via email.

I'd like to log an enhancement request for the Tracking page editor. Currently the section where we add social media connectors is limited in connection options. Specifically for Instagram (which is a really cool feature) the only way to connect is using our own credentials (user name/password login). This is an unacceptable option as it exposes us to being hacked and is a security concern obviously. The better way to do this is via Instagram's API connection: https://developers.facebook.com/docs/instagram-platform. Can you please log that as a high priority enhancement request? Should we decided to stay with AfterShip, this will be a critical branding requirement.

Currently, I can only choose from 3 resolution options in Warranty admin: Repair item, Replace item & Other. At the end of the day, I need to manually export a list of Warranty claims and see how many store credit resolutions were recorded. (By using the “Other” option with a note.) This process is very time-consuming and inefficient.    It would be very helpful if a direct "issue store credit" feature were integrated, potentially automating the process across platforms like Shopify.

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.

Hi, The data when the shipment is created at the carrier is important for shipment analysis. Example:  Info received   Shipment information received DHL Express Mar 25, 2025 at 12:01 pm

I want to fully customize different free shipping thresholds for different currencies/regions.   This would better compensate for my shipping costs in different currencies and may also increase the order value.

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

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.