Share your ideas with us

Instead of directly integrating Aftership with Gmail, I would like to send my emails with package information to an aftership email address associated with my account, for aftership to parse and automatically show tracking information. 

Currently it's possible to view returns analytics only per 1 store at a time. It would be great to be able to select multiple stores and have a consolidated view on returns. 

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!

It would be great if we could allow the discount to carry over to the new order if a customer is just exchanging a size, at the moment our customer is choosing to refund rather then exchange sizing because they have to pay the difference between the original discounted price and the price. 

Seems like a basic thing, but when I have an enhancement I'd like to submit, I want to ensure I don't duplicate someone else's submission.  Obviously that's why there is an 'upvote' button.  The only way to determine if there is something worth upvoting is to scroll through the entire list from top to bottom.

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.

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. 

Description: Aftership is a powerful tracking solution, but one major limitation is its inability to seamlessly track shipments handled by multiple carriers under a single tracking number. This creates gaps in tracking visibility, especially for cross-border shipments, multi-leg deliveries, or packages transferred between courier services. Why Aftership Needs ParcelApp Integration ParcelApp is a cutting-edge tracking solution that can consolidate multiple carrier updates into a single tracking number, ensuring a continuous, uninterrupted tracking experience—something Aftership currently lacks. Integrating ParcelApp into Aftership would provide several benefits: One Tracking Number, Full Visibility Many shipments pass through multiple carriers (e.g., a package starts with FedEx, then transfers to USPS). ParcelApp aggregates tracking data across different couriers, allowing customers to track their shipments without needing multiple tracking numbers or checking different carrier websites. Eliminate Tracking Gaps & Improve Accuracy Currently, when a package changes carriers, Aftership often loses visibility until the new carrier scans the shipment. With ParcelApp’s integration, tracking would remain consistent, even if the carrier changes mid-transit. Essential for Cross-Border and Dropshipping Businesses Global commerce relies on multi-carrier logistics. Many eCommerce sellers and dropshipping businesses depend on third-party logistics providers (3PLs) that transfer packages between multiple carriers before final delivery. ParcelApp ensures that customers don’t lose visibility just because a package has switched to a new courier. Enhanced Customer Experience & Reduced Support Inquiries When customers see tracking gaps, they flood support teams with "Where is my order?" questions. By integrating ParcelApp, Aftership can provide end-to-end tracking accuracy, reducing customer frustration and cutting down unnecessary support requests. Proposed Solution: Integrate ParcelApp (https://parcelsapp.com/) directly into Aftership’s tracking system to allow shipments with multiple carriers to be tracked under a single tracking number. Ensure that ParcelApp's multi-carrier tracking capabilities work seamlessly within Aftership’s dashboard, API, and branded tracking pages. Offer this as a standard feature for all Aftership users, as it enhances the core value of Aftership by improving tracking consistency, accuracy, and customer satisfaction. By adding this integration, Aftership would take a huge leap forward in solving a major pain point for businesses and customers alike, making it an even more indispensable tracking solution in the logistics and eCommerce space.

I would find it very useful if I could pull the SMS communication metadata using an API. Currently it is only available as a download from the portal which makes automation impossible.

1. What is the context?  * We are currently a Premium plan subscriber operating a high-volume merchant shipping 68% of our Canadian orders via GLS Canada. We are looking to utilize the Enhanced MPS Visibility feature to improve our customer experience.   * Currently, your documentation lists carriers like FedEx, UPS, and DHL as supported for MPS, but GLS Canada is excluded. When we contacted support, we were told this is due to "carrier limitations.   2. What issue do you want to address? We believe the "carrier limitation" rationale may be outdated or incorrect because AfterShip is already successfully pulling data for GLS child packages. * Evidence: On GLS Canada tracking number P97186751, AfterShip retrieves events for both Package 1 (Delivered Nov 21) and Package 2 (Delivered Nov 19). * The Problem: Because GLS Canada is not on your "Supported Carriers" list for MPS logic, your system aggregates these distinct events into a single "scrambled" timeline instead of separating them into tabs. * The Gap: The data exists in your system; the parsing logic to separate "Master" vs. "Child" is simply missing for this specific carrier. 3. What outcome do you expect? * We request that the product team add GLS Canada to the Enhanced MPS Visibility supported carrier list * We need the system to recognize the child packages it is already detecting and display them in separate tabs (Piece 1, Piece 2), just as it does for FedEx or UPS.   4. Who will benefit from your idea? * Merchants: This allows Canadian merchants to use your Enterprise MPS features for their dominant carrier, reducing support tickets regarding "confusing" status updates. * AfterShip: It improves the value of your Enterprise plan for the Canadian market by supporting the region's major logistics provider.