Share your ideas with us

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.

Hello AfterShip Team, We run an e-commerce platform that sells digital licenses and premium accounts (our store is https://accountlicense.ir/). We are looking to use AfterShip to manage our post-purchase experience and customer tracking, but we've run into a limitation because our products are purely digital. Currently, AfterShip is heavily tailored toward physical goods with carrier tracking numbers. Since we deliver license keys and credentials digitally (via email/SMS), we would love to see a dedicated "Digital Delivery Flow" in AfterShip. Specifically, it would be amazing to have: 1. A tracking page layout optimized for digital goods that displays license activation instructions or download links instead of shipping carrier maps. 2. Webhook and API triggers that update the order status to "Delivered" when the digital product is sent to the customer's portal or inbox. 3. Custom post-purchase emails specifically designed to track when a customer reveals or views their digital key. This feature would be incredibly helpful for digital merchants like us. Currently, adapting standard physical tracking for a site like https://accountlicense.ir/ requires confusing workarounds. Are there any plans to support customized tracking portals for digital-only products in your roadmap? Thank you!

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.

Good morning, I kindly ask you to enable the option to change the font, font size, colour, etc., for the “address” field within the footer of notification emails. Currently, this is the only field that cannot be customised, which creates a noticeable contrast between the main text in the body and this field, making the emails aesthetically unappealing. Thank you.

Expose an REST API for creating Warranty Claims.

Scenarios 1. We give a customer a partial refund for a coupon code they forgot to enter. This partial refund is currently stopping the customer and us from being able to request a return in Aftership. Please allow an option to make RMA or override in this scenario. 2. (similar to #1) Customer orders multiple items, gets RMA for one item, returns it and is refunded. Now they want to return the other item, however, because there is a refund in Shopify we are not able to open a RMA for the other item because the order shows as returned. Please allow option to make RMA or override in this scenario.  Thank you

im trying to figure out how to connect my store Discreet Life to shopify to get this app going. Thanks!

Please add the shipping company ACI EXPRESS, which is based in South Korea. They have partnerships with multiple overseas shipping companies, and a lot of merchandise is being shipped through ACI Express to the USA and the Middle East, especially after the implementation of tariffs in the USA.

A notification to give the customer the opportunity to change their requested ship date. This allows wineries to change the date without re-directing.  Using the RSD and sending a notification 3 days or so before. 

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.