We'd like the ability to restrict which order-editing options are available on a per-country basis, rather than applying the same set of options globally.
Many merchants work with regional checkout or fulfillment partners (e.g. Global-E) that prohibit certain order changes after an order is placed in specific countries. For example, a merchant might need to limit editing to only "apply discount code" and "cancel order" for a subset of countries, while keeping the full set of editing options available everywhere else.
Being able to configure order-editing permissions by country/region would help merchants stay compliant with regional partner restrictions without giving up flexibility in other markets.
Like to set their own “Image not found” image for Products in the Returns Portal. That way, If a Product is not sent to AfterShip with an Image URL, they have an image that looks more branded.
Today, when an item does have an img url, the Return Portal defaults to the missing image icon.
Request - have a function within Return Portal where if any items on my return portal dont have an image URL, it can set to a image that I select instead of defaulting to the standard broken/no image icon.
It would be incredibly helpful if there was a way to export the shipping data from the phone app. It would be extremely simple and improve the apps usefuleness.
It would also be incredibly helpful if there was a way to have the phone app on the computer. I know the browser version is different and designed for merchants while the phone app is designed for recipients. But, it would be easy to create a aftership.com/recipients version of the app on the computer that just syncs the shipments across devices.
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.
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.
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.