Share your ideas with us

Hi there,    We’re planning to fully transition to your warranty return platform and would like to see the following improvements: * Dynamic Reference Lines on Return Shipping Labels: We’d like the option to add customizable reference lines on shipping labels. While there are default placeholders available, we need a more flexible solution to include internal notes that will help us organize returns efficiently. * Delayed Replacement Order Processing: We’d prefer the ability to process a replacement order without sending it to Shopify until the carrier marks the warranty return as “en route.” * Regex Validation for Warranty Intake Form: Adding regex validation would help us ensure inputs follow specific formats, such as order numbers or serial numbers, for better accuracy.

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.

Background On the Return Summary page, the Return Status section is commonly used to display shipping instructions that guide customers on how to return their items. As part of these instructions, customers are often required to include both their RMA ID and Order ID with the return shipment so that the warehouse and processing teams can identify and process the return correctly. Currently, the RMA ID is only displayed at the top of the page, and the Order ID is not prominently visible within the Return Status section. Requested Enhancement Add configurable fields within the Return Status section of the Return Summary page to display: * Order ID * RMA ID These fields should be displayed alongside the shipping instructions and return status details, making them easily accessible to customers while preparing and packaging their return shipment. We are open to any placement within the Return Summary page that provides clear visibility and easy access to these details. Business Use Case Our client specifically requested this enhancement because their return instructions ask customers to include the RMA ID and Order ID with the return package. Having these details displayed directly within the Return Status section would: * Improve visibility of important return information. * Reduce customer confusion when preparing returns. * Eliminate the need for customers to search for these details elsewhere on the page. * Help ensure return shipments contain the correct identification information. * Improve operational efficiency and reduce return processing delays. Expected Outcome Customers can quickly locate the required Order ID and RMA ID in the same section where they view their shipping instructions, resulting in a smoother and more user-friendly return experience. Thank you for considering this enhancement. We believe it would benefit merchants who require customers to include reference identifiers with returned packages and would improve the overall returns experience.

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

FedEx has master tracking numbers which can have multiple tracking numbers under 1 tracking numbers. I'd like to be able to add a group of numbers to a group, or master number, and it should be collapsable so I can open it and look at all attached tracking numbers. 

Integration of Sharetown to schedule pickups of items being returned. The process involves Sharetown picking up items directly from the customer's doorstep without the need for packaging. Once the items are picked up, Sharetown will resell the items through their channels and provide business with an agreed-upon gain-share payback based on the resale price.   Key Requirements: No label generation is needed as Sharetown will handle the pickup. A system integration will be needed to push the return data to Sharetown as a pickup request in their system. Sharetown will manage the logistics and resale of the items.

I'd like to log an enhancement request for the Tracking page editor. Currently the section where we add social media connectors is limited in connection options. Specifically for Instagram (which is a really cool feature) the only way to connect is using our own credentials (user name/password login). This is an unacceptable option as it exposes us to being hacked and is a security concern obviously. The better way to do this is via Instagram's API connection: https://developers.facebook.com/docs/instagram-platform. Can you please log that as a high priority enhancement request? Should we decided to stay with AfterShip, this will be a critical branding requirement.

It would be incredibly helpful if there was a way to export the shipping data from the phone app. It would be extremely simple and improve the apps usefuleness.    It would also be incredibly helpful if there was a way to have the phone app on the computer. I know the browser version is different and designed for merchants while the phone app is designed for recipients. But, it would be easy to create a aftership.com/recipients version of the app on the computer that just syncs the shipments across devices. 

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

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.