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 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.
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
I don't want to sync my email, so it would be great to be able to add a record for items that I've ordered but haven't shipped yet. I can then edit/update the shipment when the tracking number is available.
The vendor/supplier's email should be copied when sending any type of response to the customer regarding a return. This includes the RMA confirmation of return, tracking label and when it is received, refunded and resolved. We/supplier are getting chargebacks through Shopify from customers stating that their returns are not refunded in a timely manner and we have no way to get the email to show that it was processed in Aftership and to dispute a chargeback with shopify. We have no copies sent to us.
Please fix this issue in Aftership/Shopify immediately.
Thank you.
Related to BOPIS Track - set a Pickup deadline date and use it as a Merge Tag on Notifications.
Ideally, set a date and time expiration date so the end consumer know when they need to pick up their order. If the end consumer doesn't pick up their package before the expiration date, then cancel the order, notify the client and possibly refund the end consumer.