Share your ideas with us

I would like to view the chart showing reasons for late shipments in the current on-time report that I am using.

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.

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.

As a merchant, I would like to break down the shipping volume report by Carrier and Lane. Currently, it can be broken down by only one condition.   This would allow us to understand how a carrier is performing in a specific market.

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.

As online shopping continues to expand, cities and businesses are looking for ways to simplify last-mile delivery. In this shift, automated parcel lockers have become a practical solution, helping reduce missed deliveries and improving convenience for both couriers and customers. Their use is steadily shaping the future of contactless and efficient package management.

We would love to be able to see the return comment information our customers provide when returning items within the return reports we download. Our customers are using the comment box to describe the return reason in depth but this information is lost when it comes to dowloading the return reports.

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. 

Hi there, We ship wine, which means orders are often held by our fulfilment center when temperatures along the route are above or below certian threshold we have set. I would like to create a flow that automatically notifies the customer that their order has been flagged for a weather hold and ensures them it is still on the way. Is this possible? Thanks

Goal: To make it easier for customers to accurately select the correct item for return when using the return portal. Preconditions: The customer has placed an order containing multiple items, some of which may have similar or identical titles, colors, or sizes. The SKU numbers for the items exist in the system but are not currently displayed in the return portal. Trigger: The customer initiates a return and accesses the return portal to select the item(s) they wish to return. Basic Flow: The customer logs into the return portal. The portal displays the items from their order, including details such as title, color, size, and now the SKU number for each item. The customer uses the SKU number to cross-reference their order confirmation or invoice, ensuring they select the correct item for return. The customer completes the return process with confidence that the correct item has been selected. Postconditions: The customer successfully returns the correct item without confusion. The support team receives fewer inquiries about mismatched returns. Benefits: For Customers: Improved user experience by reducing confusion when selecting items for return. Greater confidence in completing returns independently. For the Business: Reduced customer support requests related to returns. Increased efficiency in processing returns, minimizing errors caused by incorrect item selection. Priority: Medium – This enhancement has a high potential to improve customer satisfaction with a relatively low implementation effort. Technical Requirements: Modify the front-end display of the return portal to include SKU numbers as part of the product details. Ensure the SKU numbers are fetched and displayed consistently across all customer orders. This use case focuses on enhancing the clarity of the return process for customers while streamlining operational efficiency for the business.