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.
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
I work in the furniture industry with thousands of products and continuous new product listings.
Consumers often inquire about variations in materials and sizes between similar pieces of furniture, placing a significant burden on my support team. Generating comparison pages for every query we receive is unfeasible due to the volume of requests.
Given the potential of AI to suggest comparable items, could it also be leveraged to pinpoint disparities among products and present these distinctions to consumers? Such a system can alleviate my workload significantly and potentially reduce bounce rates as well.
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
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.
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
Would you be able to:
1. Add a functionality that restricts order views based on a ship from location or/or login? We have multiple ship from locations and we are 100% manula orders; it creates confusion when one warehouse sees orders from another warehouse.
2. Have a ship to address book and have that be varied based on ship from locations. We have set ship to locations and it doesnt change often.
I hope to insert a form in the email, allowing customers to fill out the form directly within the email.
For example, if there are some events or new product launches, I would like to invite users to participate and collect information on whether they are interested or not.