Share your ideas with us

Upload label manually from external source and link (instead of file only) Today its only possible to upload label manually through file via computer.   Hope this will change and we ca upload via external url

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. 

Add the ability to block a return and direct the customer to the warranty portal. Bonus if you could log the customer in and auto fill information.   Potential Mockup Potential User Experience

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. 

Titles should update with count of items in the section so you know it's updating and should be clicked on. 

im trying to figure out how to connect my store Discreet Life to shopify to get this app going. Thanks!

Would you be able to: 1. Add a functionality that restricts order views based on a ship from location or/or login? We have multiple ship from locations and we are 100% manula orders; it creates confusion when one warehouse sees orders from another warehouse.  2. Have a ship to address book and have that be varied based on ship from locations. We have set ship to locations and it doesnt change often. 

Hi AfterShip Community, Context: I run a small Shopify store (~50 orders/month) using AfterShip’s free plan to track shipments (USPS, UPS). While the free plan offers basic tracking (Web:10), there’s no way to analyze tracking page performance (e.g., visitor clicks, engagement) without upgrading to premium plans, which can be costly for small businesses (Web:18). Issue: Small merchants lack access to basic analytics on the free plan to understand how customers interact with tracking pages, limiting optimization efforts. Outcome: I propose a lightweight analytics dashboard in the free plan, showing metrics like tracking page visits and click-through rates (e.g., to return portals). This would help optimize post-purchase experiences without needing a paid plan. Beneficiaries: Small e-commerce businesses, startups, and solo entrepreneurs using the free plan would gain insights to improve customer engagement and retention. What do you think? Any similar needs or suggestions to refine this idea?

In Shopify, merchants cannot identify which orders were combined in TTS. This will increase the risk of merchants repeatedly fulfil the same order items.   To address this issue proactively, I would recommend that we introduce a hint or tag within Shopify to alert merchants about combined orders, thus avoid this situation from happening.

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.