Share your ideas with us

The website is in dutch but then after login, the portal is in english.

I see that Aftership is already having public api end points available for tracking and returns. i would like to have similar one for reviews.

Consider leveraging Estimated Delivery Dates for Return Shipments as a column on the Returns Dashboard

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.

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.

the only customization allowed is subject line and preview text for the reminder email, can't change the body copy of the reminder email.    benefit would be to add a secondary reminder of receiving loyalty points/an incentivization 

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

When I receive tracking from suppliers, I add manually to AfterShip.  Usually there's more than 1 tracking number, for the same courier, so it would be great to able to add multiple tracking numbers at the same time as comma separated.   When clicking Save, it would then use all the information entered, for example; Customer name, order number etc etc.   Below example for tracking number 123456789 and 987654321  

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.

Brand noted they’d like to be able to clearly communicate why certain Products are on the Blocklist - instead of the general text we have in place, without specifically making the customer review the Policy as a whole. Asking if we could define the error at the Blocklist Product Tag entry level. If the value is left blank, use default content.   Current state: After end consumer logs in with Order, non returnable items are greyed and out and we show at the line level a message that states "Does not comply with our return policy."   Desired State: After end consumer logs in with Order, non returnable items are greyed and out and we show at the line level a message from a configurable setting within RC where we can pass SKU or Product Category specific messages that state why an item is nt returnable like "Digital Goods are not returnable" or "Bundled Item cannot be returned" or "Last years models are not returnable but warranty available".   We'd like to be able to configure our own blocklist message for order item display when the end consumer logs into RC.