Share your ideas with us

Enhance Aftership’s functionality by integrating with Royal Mail, one of the leading postal services in the UK. This integration would allow users to track shipments directly through Aftership, providing seamless tracking updates, improved user experience, and broader carrier support. This feature would be particularly valuable for e-commerce businesses that frequently use Royal Mail for deliveries.

Our warehouse needs to know how many returns were requested on a daily basis so they can plan their resources accordingly. but it is not an option for now. It would be nice if we could build our own reports and schedule it. 

When using the mobile App, currently shipments remain visible in the tracking list even after they have been delivered. Over time, this can make the main tracking screen feel cluttered, especially for users who receive a large number of packages. It would be very helpful to have an option to: - Archive delivered shipments manually, or - Automatically move delivered shipments to an archive after a certain period of time. This would allow users to keep their active tracking list clean and focused on packages that are still in transit, while still retaining access to past deliveries when needed.   Thank you,

The ability to see how much it cost per tracking label for the carrier, alongside all the other analytics would be beneficial to business operations.   Having “cost” as a piece of data collect and display in analytics will help us make larger business decisions when it comes to choice of carrier preferences to know which carrier is best to work with in the long run. I believe this feature will be great value add to Aftership as well!

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

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.

That would be great if Feed could accommodate the listing of "not-for-sale products" on TTS. This feature is newly introduced in TTS, where the product is not for sale to shoppers but will be gifted to them instead.

Is it possible to increase the bulk search limit from 50? We often have to peform bulk search a number of times to retrieve the data that we're looking. 

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.

We would love to be able to see the return comment information our customers provide when returning items within the return reports we download. Our customers are using the comment box to describe the return reason in depth but this information is lost when it comes to dowloading the return reports.