Share your ideas with us

We value your insights on AfterShip products and features. Let's innovate together!

Filter ideas

Shipment tracking dashboard automated report

Fielding Oliver
April 17, 2026 at 1:56 pm
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. 
Submitted
0
0

Provide Cost of tracking as data in analytics

Ethan White
May 23, 2024 at 1:17 pm
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!
Submitted
0
0

Branded Customization of Returns Notifications

Andrew Bird
August 15, 2025 at 12:41 pm
There is a massive discrepancy between the notificaiton customization capabilities within the Tracking module and the Returns module.  In the Returns module, all you can do is update the messaging. There is no ability to alter colours, add logos, images, or otherwise truly 'brand' the notifications.  All of this exists in the Tracking module.  Recommendation is that you port over the same functionality into the Returns module ASAP.  Those notification emails are currently a horrific customer experience.
Submitted
0
0

Publish Webhook Outgoing IPs as a Machine-Readable Plain-Text Endpoint

Martinho Dias
June 3, 2026 at 7:47 pm
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.
Delivered
0
0

Refund after Expiration

Jack Blenkinsop
March 5, 2026 at 9:53 pm
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.
Submitted
0
0

Enhancement Request: Advanced Customization for AfterShip Returns

Thomas Peigné
May 11, 2026 at 12:24 pm
Compared to AfterShip Tracking, Returns currently lacks key customization capabilities: * No page segmentation (by market, country, store, customer type, etc.) * No way to associate a return with a specific store * No configurable notification flows based on return status or parameters The absence of these settings significantly limits customization for clients and prevents them from offering tailored return experiences. Suggestion: Introduce advanced configuration options similar to Tracking, including: * Segmented return pages based on defined parameters * Store-level return association and rules * Conditional notification flows triggered by return events and attributes These improvements would greatly enhance flexibility, customer experience, and alignment across the AfterShip product suite.
Submitted
0
0

personalize reporting and scheduling

nailin yang
July 16, 2025 at 9:05 am
Our warehouse needs to know how many returns were requested on a daily basis so they can plan their resources accordingly. but it is not an option for now. It would be nice if we could build our own reports and schedule it. 
Accepted
0
0

Create tracking pages via API

Madison Morgan
July 17, 2024 at 3:03 pm
We are a worldwide dropshipping service catering to e-commerce entrepreneurs. Merchants can design and market personalized products through us, setting prices and choosing their sales platforms from our integrated e-commerce options.   Once merchants place orders, we will handle the manufacturing, fulfillment, and shipping logistics to consumers.   When I am using Aftership for tracking, I want to enable my premium customers (merchants) with the ability to customize white label branded tracking pages and possibly an API to create them (since they won't have access to Aftership admin, and it would be impossible for me to maintain all tracking pages for them).   So that I can add this ability as part of the product & service package for my main customers (merchants), which creates more value for my business.
Submitted
0
0

Each product page has searchable and filterable product reviews to set customer expectations.

James Wilson
June 19, 2024 at 3:49 pm
For instance, customers can quickly locate reviews based on size, incorporate images and videos, consider age, product characteristics, and the reviewer's recommendation status.
Planned
0
0

Customs clearance fees charged by shipping carriers

Yuichi Tanaka
August 27, 2026 at 12:14 pm
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.
Submitted
0
0