Share your ideas with us

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. 

Good morning, When viewing notification emails on a mobile device, the background colour only appears at the top as a small strip. As a result, the background colour on the sides and beneath the email is completely lost. I therefore propose hiding the background area entirely on mobile, displaying only what is within the content background, which is the main body of the email. Thank you.

Can we get an option to automatically restock the item based on resolution, not just when received. We still need to process, and inspect the item before we issue the refund, and we can't have our inventory adjusted upon recept. Thanks!

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.

Expose an REST API for creating Warranty Claims.

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.

Is it possible to increase the bulk search limit from 50? We often have to peform bulk search a number of times to retrieve the data that we're looking. 

Hello, We would like to identify the parcels that were delivered by secured delivery methods, and which ones. For example, was the parcel delivered with a Pin Code? With a QR Code? With a signature? This would allow to better measure Exceptions per delivery method, and size the opportunity of such services, on which we are completely blind today.

GM is there a way to close an exception order rather than a total delete?

For the tracking page I am currently using, it would be great to have the Delivery Instructions feature, so that my customers can provide specific instructions to carriers, and ensure successful deliveries.   This feature will also be valuable for drivers who can have all the necessary information at their fingertips, even for dispatchers who can manage delivery more effectively with all that info.   A seamless last-mile delivery experience can create a sense of reliability and convenience that fosters long-term customer relationships and encourages repeat purchases for my brand.