Share your ideas with us

When utilizing an HTML email editor, I aim to display and personalize shipment or order items within my tracking notifications.   This feature would allow shoppers to conveniently view their purchases directly in the email, thereby improving customer satisfaction.

Fast and reliable delivery plays a vital role in customer satisfaction for heavy equipment buyers. When products arrive on time and in perfect condition, it builds trust, reduces downtime, and encourages repeat business and brand loyalty.

It would be great if we could allow the discount to carry over to the new order if a customer is just exchanging a size, at the moment our customer is choosing to refund rather then exchange sizing because they have to pay the difference between the original discounted price and the price. 

I am the owner of a fashion company preparing to expand my business operations in the US. I have been utilizing Aftership EDD for some time now and I'm interested in learning how to configure my EDDs to accommodate multiple locations.   Specifically, I have two separate locations in Australia and the US where identical SKUs are stocked. In cases where a particular SKU is out of stock at the US location, I would like orders to be fulfilled using available stock from the AU location as a fallback option. I am seeking guidance on integrating this specific logic into my EDD settings.

I guess for shipping emails sent out to my customers, it would be nice to have dynamic info that updates as the package progresses through the network. I also want all my existing emails to stay current.   The reason is simply that I wanna give my customers a unified experience by delivering consistent messages to them. I believe this will help with my customer satisfaction.

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.

The website is in dutch but then after login, the portal is in english.

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.

Background: * At the moment, a user with a specific domain can easily create a new organization when creating an account in AfterShip * We don’t indicate to this use that an existing organization is already linked to the same domain This can create confusion when member are trying to get access to an organization proactively (without being added by the current owner) * Hence we end up with support tickets from member not able to get access to their main org. Expectation: * Alert message during new inscription if we identify that the email domain is already used. * Eventually an option to send a request to the owner of the main org. * Possibility to delete the new account to avoid unnecessary org and member creations for our clients. * Could be active only for ENT client if we want to reduce the scope

Consider leveraging Estimated Delivery Dates for Return Shipments as a column on the Returns Dashboard