Share your ideas with us

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!

Would like to be able to display any discount received, from the orginal order, on the product selection page in the warranty portal. If possible, the discount code that was used as well. Important: Discount amount and discount code should show in the AfterShip admin portal.  

Currently, when a shipping label is voided and a new label is created for an order, the customer-facing AfterShip tracking dashboard continues to show the tracking information associated with the original, voided label rather than the new, active label. This results in customers seeing outdated or incorrect tracking information, even though a valid replacement label has been generated. We would like AfterShip to automatically update the tracking dashboard to reflect the most recent active shipping label whenever a previous label is voided and replaced, ensuring customers always have access to accurate tracking information for their orders.

We are able to retrieve shipping rates for each carrier, but we would also like customs clearance fees and other charges available through each carrier’s API to be integrated via API as well. This is especially important for DDP shipments. Some information that can be retrieved through the carrier APIs cannot be retrieved through AfterShip, which means we would need to connect to each carrier’s API separately.

It would be nice to be able to open links with the default browser (i.e. Firefox) instead of with the in-app browser. Perhaps with a setting, to allow the in-app browser to stay the default option.   Thanks! 

I work in the furniture industry with thousands of products and continuous new product listings.   Consumers often inquire about variations in materials and sizes between similar pieces of furniture, placing a significant burden on my support team. Generating comparison pages for every query we receive is unfeasible due to the volume of requests.   Given the potential of AI to suggest comparable items, could it also be leveraged to pinpoint disparities among products and present these distinctions to consumers? Such a system can alleviate my workload significantly and potentially reduce bounce rates as well.

I don't want to sync my email, so it would be great to be able to add a record for items that I've ordered but haven't shipped yet. I can then edit/update the shipment when the tracking number is available. 

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.

Title: Feature request: Claude MCP connector for AfterShip Returns AfterShip Returns should offer an official Claude MCP connector. Claude already connects to Shopify, Gmail, Slack, and Google Drive, so many merchants run their daily operations through it. Returns data is the missing piece. Without a connector, teams still have to open the portal, find the return, and copy details into customer replies or reports by hand. A connector would make it possible to ask questions like: “What’s the status of the return on order #1234?” “Which returns from last week haven’t been refunded yet?” “What are the top return reasons this month?” “Which SKUs have the highest return rate?” Why it should be added: Faster customer service. “Where’s my refund?” emails could be answered in seconds using live return data. Fewer errors. Order numbers, tracking, and refund amounts would come straight from AfterShip instead of being copied manually. More accessible reporting. Small teams without a dedicated analyst could get insight from return data in plain language. A connected workflow. Returns would link up with the order, email, and team tools merchants already use with Claude. Keeps AfterShip central. As more operations move through AI assistants, the platforms that connect to them become the ones merchants depend on. Read-only access would be a strong starting point: return lookups, statuses, reasons, and refund/exchange outcomes. Actions like approving or rejecting requests could follow later, with confirmation steps built in.

1. What is the context?  * We are currently a Premium plan subscriber operating a high-volume merchant shipping 68% of our Canadian orders via GLS Canada. We are looking to utilize the Enhanced MPS Visibility feature to improve our customer experience.   * Currently, your documentation lists carriers like FedEx, UPS, and DHL as supported for MPS, but GLS Canada is excluded. When we contacted support, we were told this is due to "carrier limitations.   2. What issue do you want to address? We believe the "carrier limitation" rationale may be outdated or incorrect because AfterShip is already successfully pulling data for GLS child packages. * Evidence: On GLS Canada tracking number P97186751, AfterShip retrieves events for both Package 1 (Delivered Nov 21) and Package 2 (Delivered Nov 19). * The Problem: Because GLS Canada is not on your "Supported Carriers" list for MPS logic, your system aggregates these distinct events into a single "scrambled" timeline instead of separating them into tabs. * The Gap: The data exists in your system; the parsing logic to separate "Master" vs. "Child" is simply missing for this specific carrier. 3. What outcome do you expect? * We request that the product team add GLS Canada to the Enhanced MPS Visibility supported carrier list * We need the system to recognize the child packages it is already detecting and display them in separate tabs (Piece 1, Piece 2), just as it does for FedEx or UPS.   4. Who will benefit from your idea? * Merchants: This allows Canadian merchants to use your Enterprise MPS features for their dominant carrier, reducing support tickets regarding "confusing" status updates. * AfterShip: It improves the value of your Enterprise plan for the Canadian market by supporting the region's major logistics provider.