Share your ideas with us

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.

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.

Currently you can manually refund the shipping fee in the admin manually, but would like the ability for it to be automatic.

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.

leading latin america e commerce platform https://tiendanube.com

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

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

In our business we refund direcly in Shopify for our returns that are made from our online website. It would be nice if the status of Shopify shows refunded or partically refund that Aftership would show the return as resolved. Some of the tracking information has to be put in manaully and we have multiple people on our team and if they do not do it correctly our customers receive emails that their return was not send and is expiring when they have already been refunded. 

Currently, AfterShip's webhook outgoing IP list is only available on an HTML documentation page (https://www.aftership.com/docs/tracking/webhook/webhook-outgoing-ips). This makes it impossible to automate IP allowlist management in infrastructure-as-code (IaC) workflows.   Problem: Teams that use IP-based firewalls to secure their webhook endpoints must manually monitor the documentation page for any IP changes and update their firewall rules accordingly. If a change is missed, it can cause webhook delivery failures and broken integrations.   Request: Please publish the webhook outgoing IP list as a dedicated plain-text endpoint — similar to how Cloudflare publishes theirs at https://www.cloudflare.com/ips-v4 — where each IP is returned on a separate line.   This would allow teams to: * Fetch the IP list programmatically as part of their CI/CD or IaC pipelines * Keep firewall allowlists automatically in sync without manual intervention * Avoid service disruptions caused by missed IP changes This is a standard practice among major API providers and would significantly improve the developer experience for customers who manage network security programmatically.