Share your ideas with us

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

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

I want to be able to show values and total value of anything that is currently in transit, out for delivery and delivered so i can manage my insurance process of total value out at a given time 

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.

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.

it would be great to be able to manually add a placeholder delivery in order to keep track of my deliveries.

That would be great if Feed could accommodate the listing of "not-for-sale products" on TTS. This feature is newly introduced in TTS, where the product is not for sale to shoppers but will be gifted to them instead.

Hello, Could you add Vinted Go shipping to the shipping list in the next update, please? It's a very very good app to follow shipping. Thanks's in advance Best regards 

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

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.