Share your ideas with us

We should be able to update the email address on the returns and warranty pages in case the cx is unable to access the default email.

There should be an option to send at least all email notifications to one email address, such as a shared folder, each time a shipment has an action. Using a webhook should not be the only option. Many companies would like this option in conjuntion with an M365 automation to create MS teams messages etc for internal use.

There's quite a few couriers where the 'View on Carrier Website' doesn't take you directly to the trracking page, and instead requires you to enter the tracking number.  These can be easily fixed by correcting the URL.   For example, for Cainiao the link takes you to; https://global.cainiao.com/   This needs correcting to; https://global.cainiao.com/newDetail.htm?mailNoList=   Please submit any further examples below.

I have loved your app from the start. And improvements made along the way have been spot on. But now you lost me in both content and execution.    First, you put in ads. One of things I loved was no ads. But, hey, that revenues hard to pass up forever, especially after you've built your user base.   Second, I could have dealt with the ads if you had placed in a footer bar. But when you place the ads as large blocks right in the middle of the data, you lost me.   I was a developer for over 30 years on several different platforms. I must say that decision alone makes my top 20 of bad UI choices.   So, I will be unloading your app in favor of one that has no ads and all the functionality I need. It is a shame, because you do beat them out in feature, although not too much.   If you would at least move them to the footer then I would most likely return

I want to be able to mask certain words such as 'flight'and ''import'', or ''customs''. As for EU customers this is not relevant infromation and they faster think goods are from china and want to return faster. When they see basic info and a EDD they are assured everything is good. They dont neem more info.

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.

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.

Hi there,    We’re planning to fully transition to your warranty return platform and would like to see the following improvements: * Dynamic Reference Lines on Return Shipping Labels: We’d like the option to add customizable reference lines on shipping labels. While there are default placeholders available, we need a more flexible solution to include internal notes that will help us organize returns efficiently. * Delayed Replacement Order Processing: We’d prefer the ability to process a replacement order without sending it to Shopify until the carrier marks the warranty return as “en route.” * Regex Validation for Warranty Intake Form: Adding regex validation would help us ensure inputs follow specific formats, such as order numbers or serial numbers, for better accuracy.

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.

I see that Aftership is already having public api end points available for tracking and returns. i would like to have similar one for reviews.