Share your ideas with us

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.

Hello AfterShip team, We use the AfterShip Post-Purchase connector in Claude to automate our daily delivery follow-up, and it works very well for shipments. However, the connector currently only exposes shipments (trackings) and returns. Orders without a tracking number are not accessible, although they are visible in the AfterShip admin under Tracking > Orders. Our use case: every morning we want to detect orders that are still "Unfulfilled" (or "Partially fulfilled") more than 2 business days after the order date, and that have no tracking yet, so we can follow up with our suppliers. Could you add the following to the MCP connector? 1. A list_orders tool with filters on fulfillment status (unfulfilled, partially fulfilled), order status (open / canceled), order date (placed_at) and order number. 2. For each order: fulfillments with their trackings (to know whether a tracking exists), line items, customer, tags and order notes. 3. Access to the internal comments added on an order (the "Comments" section of the order page), so we can exclude orders already handled by our team. 4. If possible, order-level custom fields (e.g. our "isBackorder" flag, which today only exists on shipments). Is this on your roadmap? In the meantime, is there another supported way (API endpoint, scheduled export or webhook) to get this list of unfulfilled orders automatically? Thank you for your help.

It would be great if you could automate sending out the shipment tracking dashboard, and allow filters for that report, lijke the analysis report.  This enbales us to send the report to customers and others in our team as a live snapshot of their shipments. It consolidates all their shipments into one view so they don't have to track them individually each day. 

Titles should update with count of items in the section so you know it's updating and should be clicked on. 

we provide return shipping label after approving the return request. Our product contains hazarious material, which should be shipped with hazmat label. Aftership doesn't grant the api access of selecting the Hazmat label when auto-generating return shipping label Please fix it

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.

Add the ability to upload a separate images for desktop and mobile header logos. An example of the what the UI could like like is below. Returns > Customizations > Returns page    

Aftership agent is powerful and will be more in the future. In that future, MCP protocol connection is a must. It's a game changer! So customers (us) can connect their agents with Aftership.

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. 

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.