Share your ideas with us

The “Back” button on the RC portal is not obvious or prominent enough. It is too hard to find and blends into the page. 

Change the update indicator Dot from the light blue color to the orange color you already use in your iOS app. It is hard to pick out the dot if you have a long list of shipments. If it was the orange color you already use in the app it should be a simple change to make for an updated version. Also so carriers on the list of carriers to pick from are now asking for receiving zip, so those carriers never update now.  Thanks

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.

The current OpenGraph meta preview generated by AfterShip's referral link system is unacceptable. We run a professional e-commerce business in South Africa selling premium seat covers, yet the influencer link preview looks like a child’s sticker book. Confetti, a USD coupon graphic, and a generic "Get special offers" line? Completely irrelevant, off-brand, and frankly embarrassing when shared by influencers. This isn’t just a design problem. It reflects poorly on our business when our partners share this link on Facebook and social platforms. It gives the impression of an unprofessional or scammy brand — damaging our credibility and costing us leads. We don’t even use USD as our currency. Why are you pushing American coupon-style banners to international stores?

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.

The background is that I sell my products on multiple marketplaces, and each has different return flows that the aftership Returns page cannot handle. It would be much easier if there is a Returns API that can meet my requirements below.   Need: - I need a Returns API to allow creating RMA/return requests without having to use the Returns Page to file it.  - I can call the API and pass the information regarding the Return Reason Resolution, etc in one go.  - Once I call this API, it will return creation in Pending or Auto-Approved Status.

the only customization allowed is subject line and preview text for the reminder email, can't change the body copy of the reminder email.    benefit would be to add a secondary reminder of receiving loyalty points/an incentivization 

I want to fully customize different free shipping thresholds for different currencies/regions.   This would better compensate for my shipping costs in different currencies and may also increase the order value.

When using the mobile App, currently shipments remain visible in the tracking list even after they have been delivered. Over time, this can make the main tracking screen feel cluttered, especially for users who receive a large number of packages. It would be very helpful to have an option to: - Archive delivered shipments manually, or - Automatically move delivered shipments to an archive after a certain period of time. This would allow users to keep their active tracking list clean and focused on packages that are still in transit, while still retaining access to past deliveries when needed.   Thank you,

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.