Share your ideas with us

It would be really useful to see how often the Gift Tracking Page is actually being used, separately from the regular tracking page. At the moment, it’s hard to tell uptake or performance unless the page has a unique URL or rely on Google Analytics. Having native reporting in AfterShip would make this much easier. Ideally this would show: - Views and unique visitors for the gift tracking page - How it compares to the standard tracking page - Basic engagement (e.g. CTA clicks) This would help merchants understand adoption and value of the gifting feature much more clearly.

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

There's quite a few couriers where the 'View on Carrier Website' doesn't take you directly to the trracking page, and instead requires you to enter the tracking number.  These can be easily fixed by correcting the URL.   For example, for Cainiao the link takes you to; https://global.cainiao.com/   This needs correcting to; https://global.cainiao.com/newDetail.htm?mailNoList=   Please submit any further examples below.

FedEx has master tracking numbers which can have multiple tracking numbers under 1 tracking numbers. I'd like to be able to add a group of numbers to a group, or master number, and it should be collapsable so I can open it and look at all attached tracking numbers. 

Fast and reliable delivery plays a vital role in customer satisfaction for heavy equipment buyers. When products arrive on time and in perfect condition, it builds trust, reduces downtime, and encourages repeat business and brand loyalty.

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!

Can we have a way to export the report of the notifications? So for example, I would love to be able to export the list of people who had bounced emails for our shipping notifications or even to export the list of folks who did not open the message. 

As a merchant, I would like to charge the cost of return when the shopper chooses to replace the returned item.  aftership Returns provides Stripe checkout only for this scenario, but I don't have a Stripe account, I would like to use my Shopify checkout to charge the exchange upsell and cost of return. So that I don't have to open a Stripe checkout and manage two accounts (Shopify and Stripe checkout) at the same time.

We want the ability to display shipping reviews to front end customers/users to give them social proof and increase conversion rates. Fast, cheap, convenient and reliable delivery helps to boost conversion rates, especially when you're entering a new market and trying to build brand awareness/trust. It also helps to get customers who are used to visiting your retail stores to shift to shopping online instead of just going in to a store. Currently, shipping reviews are only available to back end users and internal teams in the aftership portal, but we want to be able to have a customisable widget that we can display on places like the homepage, PDPs, information pages like shipping & delivery info pages etc... We can pick and choose or set up rules to automate showing a handful of reviews related to the shipping customer experience.

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.