Share your ideas with us

As a business owner, I am seeking a system that can facilitate risk level scoring for each RMA (Return Merchandise Authorization) and enable my staff to input risk assessment findings based on actual RMA inspections. This system will enable us to assess risk levels effectively and respond accordingly. Moreover, the system will allow for the reporting of any detected fraud instances.   Implementing this system is crucial for mitigating fraud occurrences, as well as proactively preventing future fraudulent activities. Such measures are instrumental in safeguarding my business's profitability in the long term.

 I just started using the app today and overall I do like it, but I have a few minor suggestions. 1. A compact mode: right now the list of tracking numbers/packages is very spread out. Consolidating it would make it look cleaner, IMO. 2. Allow me to put tags on them, custom or otherwise. For example I have a few incoming packages and a few outgoing ones. It would be nice to add tags to differentiate them and also filter by them if needed. Hopefully that made sense. Thank you.

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.

If you are working with many different returns in one day, there needs to be a quick way to copy information like in Shopify as example. Please reference the far right side of this image:

the only customization allowed is subject line and preview text for the reminder email, can't change the body copy of the reminder email.    benefit would be to add a secondary reminder of receiving loyalty points/an incentivization 

Can we have a way to export the report of the notifications? So for example, I would love to be able to export the list of people who had bounced emails for our shipping notifications or even to export the list of folks who did not open the message. 

As a business owner, having precise accounting records is essential for tax purposes. It's particularly important to account for returns correctly by adjusting for them and deducting the relevant taxes to prevent overpayment.   I've observed that Shopify currently only accommodates refunds, lacking store credit or exchange options for returns. Therefore, if aftership Return could support all three options and assist in reconciling taxes and producing accurate tax reports for returns, it would greatly benefit our operations.

Some customers enter +1 before their phone number when requesting a return or exchange. This causes the shipping label to fail to generate and creates frustration for the customer and extra work for me. I would like the system to correct the phone number to allow successful label generation.

Most major carriers already provide an estimated delivery date/time as part of their tracking data, but this isn't currently surfaced in the app. Context: Customers tracking a shipment want to know when it will arrive, not just its current status. Right now they have to infer this themselves or check the carrier's own site separately. Issue to address: Add a field that displays the carrier's estimated delivery date (and time window, where the carrier provides one) on the tracking/order page. This would reduce "where is my order" support inquiries and improve the post-purchase experience. Suggestion: Pull the estimated delivery data from carriers that already expose it via their APIs, and display it prominently near the shipment status.

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.