Share your ideas with us

Would you be able to: 1. Add a functionality that restricts order views based on a ship from location or/or login? We have multiple ship from locations and we are 100% manula orders; it creates confusion when one warehouse sees orders from another warehouse.  2. Have a ship to address book and have that be varied based on ship from locations. We have set ship to locations and it doesnt change often. 

What is the context  When using AfterShip Returns with the "Shop Now" / "exchange for anything" option that redirects customers to shop on the merchant's own store, customers can select any product available on the store as their exchange item. What issue do you want to address? There is currently no way to exclude specific products from being selectable as exchange items in this flow. The existing exclusion controls (the block list and excluding products from recommendations via product tags) only apply when AfterShip is recommending products or when "Exchange on AfterShip returns page" is selected. When customers shop directly on the merchant's own website via "Shop Now," these exclusions do not apply, so restricted products remain selectable. This allows customers to exchange low-value items for high-value products, resulting in margin loss and exchange abuse. The only current workaround, switching to "Exchange on AfterShip returns page," removes the on-store shopping experience the merchant wants to keep.   What outcome do you expect? The ability to exclude specific products from being eligible exchange items while still using the "Shop Now" flow where customers shop on the merchant's own website. Ideally the exclusion could be defined by SKU, in addition to collection or product tag, since some merchants do not have the relevant products grouped in a collection and may not have access to create collections in Shopify.   Who will benefit from your idea? Merchants using the "Shop Now" exchange flow who need to prevent certain products from being selected as exchange items, protecting their margins and preventing exchange abuse while preserving the branded on-site shopping experience during exchanges.

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

Items + return reasons are not clearly highlighted/shown as selected, during the Return Request flow on the RC portal.    Request: During the return flow more clearly define that an item/return resolution is selected. i.e. have text say “Selected” or have the box change colour when an item/resolution is selected beyond just the black box. 

We use this to ship to clients it would be nice if we could save clients within the system to send notifications to. 

I have had customers who have accidently unsubscribed themselves from receiving AfterShip emails. I can see them in the Unsubscribe list, but I cannot remove them. Please add a feature that would allow AfterShip administrators to remove emails from the Unsubscribe list. Currently this process has to be done by the AfterShip tech team. By making this a self-service feature, you will reduce the labor required by the AfterShip team and make the product more efficient.

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

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.

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.

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.