Share your ideas with us

We should be able to update the email address on the returns and warranty pages in case the cx is unable to access the default email.

Show all packages to a us zip code

Hi there,    We’re planning to fully transition to your warranty return platform and would like to see the following improvements: * Dynamic Reference Lines on Return Shipping Labels: We’d like the option to add customizable reference lines on shipping labels. While there are default placeholders available, we need a more flexible solution to include internal notes that will help us organize returns efficiently. * Delayed Replacement Order Processing: We’d prefer the ability to process a replacement order without sending it to Shopify until the carrier marks the warranty return as “en route.” * Regex Validation for Warranty Intake Form: Adding regex validation would help us ensure inputs follow specific formats, such as order numbers or serial numbers, for better accuracy.

Requesting to provide an option for the end consumers to edit the review on the AfterShip tracking page after the product is being delivered.    Currently, the customers are able to leave the review but unable to edit them. 

We want to refer to the customer's username when packing the order. Right now, to do this, we need to download the tiktok orders, connect them to the shopify order number via the tiktok order in the notes field and then connect that to the order number in shipbob.   If we had the username in shopify, we could eliminate the step where we have to connect tiktok to shopify.

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.

It would be great if you could automate sending out the shipment tracking dashboard, and allow filters for that report, lijke the analysis report.  This enbales us to send the report to customers and others in our team as a live snapshot of their shipments. It consolidates all their shipments into one view so they don't have to track them individually each day. 

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?

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.

Allow me to still refund if I choose even if the return request has expired. Now I have to recreate the return request making more work for me.