Share your ideas with us

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.

As a retailer, it would be great if customer preferences can be collected and determine whether to send an SMS notification based on the subscription status synchronized via API.   Moreover, a customer-facing page that allows users to manage their preferences would be even better. We would love to communicate more with our shoppers, which will efficiently improve our customer satisfaction and brand reputation.

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.

On the tracking dashboard customers/users need to be able to click to grab, then drag and drop the order we desire our packages to be in.

It would be very helpful if customers could select their preferred size during the exchange process, with real-time visibility of stock availability on the website. For example, when a customer initiates an exchange, the system should show whether the requested size is currently in stock. If the size is unavailable, it should display “Sold Out” instead of allowing the exchange to proceed. This feature would prevent unnecessary back-and-forth communication, improve customer experience, and reduce manual handling for merchants. Platforms like Revolve already offer this type of functionality, and it would be an excellent addition to AfterShip Returns.

In our business we refund direcly in Shopify for our returns that are made from our online website. It would be nice if the status of Shopify shows refunded or partically refund that Aftership would show the return as resolved. Some of the tracking information has to be put in manaully and we have multiple people on our team and if they do not do it correctly our customers receive emails that their return was not send and is expiring when they have already been refunded. 

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.

Related to BOPIS Track - set a Pickup deadline date and use it as a Merge Tag on Notifications.   Ideally, set a date and time expiration date so the end consumer know when they need to pick up their order. If the end consumer doesn't pick up their package before the expiration date, then cancel the order, notify the client and possibly refund the end consumer.

There's quite a few couriers where the 'View on Carrier Website' doesn't take you directly to the trracking page, and instead requires you to enter the tracking number.  These can be easily fixed by correcting the URL.   For example, for Cainiao the link takes you to; https://global.cainiao.com/   This needs correcting to; https://global.cainiao.com/newDetail.htm?mailNoList=   Please submit any further examples below.

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.