Share your ideas with us

Hi, The data when the shipment is created at the carrier is important for shipment analysis. Example:  Info received   Shipment information received DHL Express Mar 25, 2025 at 12:01 pm

I was just tracking my packages and thought of something and was like man I wish there would be different layouts or sorting options. Like if I could sort it by ETD Dates, etc rather than just having them all listed and me doing the mental math of 3 days from now would be Friday, etc. Since of our would be able to be listed by delivery date I would know what packages I need to be on the lookout for that day at an early glance.

Hi,   I recently started buying products from India and sometimes they ship using : https://shipglobal.in/tracking/   Unfortunately Aftership is not yet supporting shipglobal.in and I need to use another app (actually 17tracks works) to track these shipments.   Please consider adding shipglobal.in as a supported career.   thank you!

Items + return reasons are not clearly highlighted/shown as selected, during the Return Request flow on the RC portal.    Request: During the return flow more clearly define that an item/return resolution is selected. i.e. have text say “Selected” or have the box change colour when an item/resolution is selected beyond just the black box. 

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.

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 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!

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.

As a merchant, I allow shoppers to exchange items for different variants during returns, which may have different prices. For example, a Small size costs $30 while a Large size costs $50.   Currently, Shopify allows me to adjust prices manually only after the Return Merchandise Authorization (RMA) is submitted. If aftership could facilitate charging or refunding price differences for variants during the return request process, it would greatly streamline our operations and enhancing the overall efficiency of RMA management.

leading latin america e commerce platform https://tiendanube.com