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 ability to see how much it cost per tracking label for the carrier, alongside all the other analytics would be beneficial to business operations.
Having “cost” as a piece of data collect and display in analytics will help us make larger business decisions when it comes to choice of carrier preferences to know which carrier is best to work with in the long run. I believe this feature will be great value add to Aftership as well!
Hello,
We currently use AfterShip Feed to connect our Amazon Seller account to TikTok Shop. But it would be fantastic to be able to also connect with Walmart Seller's MCF.
It would allow even greater reach of products on more sales channels.
I would find it very useful if I could pull the SMS communication metadata using an API. Currently it is only available as a download from the portal which makes automation impossible.
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.
As a user, I'd like the ability to pull in tracking numbers to my dashboard by parcel account number so that I can view all shipments assigned to a specific or multiple parcel accounts.
For example I have 10 parcel accounts (4 with DHL and 6 with FedEx). I'd like the ability to utilize the parcel account number(s) instead of the API to pull in tracking associated with my parcel accounts.
When I receive tracking from suppliers, I add manually to AfterShip. Usually there's more than 1 tracking number, for the same courier, so it would be great to able to add multiple tracking numbers at the same time as comma separated.
When clicking Save, it would then use all the information entered, for example; Customer name, order number etc etc.
Below example for tracking number 123456789 and 987654321
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.