Share your ideas with us

Seems like a basic thing, but when I have an enhancement I'd like to submit, I want to ensure I don't duplicate someone else's submission.  Obviously that's why there is an 'upvote' button.  The only way to determine if there is something worth upvoting is to scroll through the entire list from top to bottom.

1. customer is NOT receiving any email from Aftership when a return has been received, refunded and resolved.  2. We are getting chargebacks from customers claiming they were not notified and advised a refund was on its way. 3. their bank (JPM) has sided with customers even though we have shown the ARP info from the return details.  4. An email advising of a received and pending refund would be quite helpful. 5. ALL other companies send these emails of pending refund, except Aftership/Shopify does not. 6. Its creating a lot of work and loss of revenue for our company. 

Currently OTD report, reports the complete journey so the avereage time can fluctuate based on how long it takes for customers to collect their order.  We need to report on the carrier performance and then the time it takes to collect.  It would be good to have  a PUDO report that breaks down : average transit time to collection point   Average time waiting for collection    If we expand our PUDO options in Europe it would be a good indication 

Can we get an option to automatically restock the item based on resolution, not just when received. We still need to process, and inspect the item before we issue the refund, and we can't have our inventory adjusted upon recept. Thanks!

Add the option to pay online ~ $2 at checkout for free returns and extended warranty later.    Add tags to people / allow different RMA flow for those who optin to this. 

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 

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.

We'd like the ability to restrict which order-editing options are available on a per-country basis, rather than applying the same set of options globally.   Many merchants work with regional checkout or fulfillment partners (e.g. Global-E) that prohibit certain order changes after an order is placed in specific countries. For example, a merchant might need to limit editing to only "apply discount code" and "cancel order" for a subset of countries, while keeping the full set of editing options available everywhere else.   Being able to configure order-editing permissions by country/region would help merchants stay compliant with regional partner restrictions without giving up flexibility in other markets.

For instance, customers can quickly locate reviews based on size, incorporate images and videos, consider age, product characteristics, and the reviewer's recommendation status.

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.