Share your ideas with us

Expose an REST API for creating Warranty Claims.

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.

There is a massive discrepancy between the notificaiton customization capabilities within the Tracking module and the Returns module.  In the Returns module, all you can do is update the messaging. There is no ability to alter colours, add logos, images, or otherwise truly 'brand' the notifications.  All of this exists in the Tracking module.  Recommendation is that you port over the same functionality into the Returns module ASAP.  Those notification emails are currently a horrific customer experience.

I want all orders over $30 to show a shipping fee of only $2, because this is subsidized by TikTok.

Currently, I can only choose from 3 resolution options in Warranty admin: Repair item, Replace item & Other. At the end of the day, I need to manually export a list of Warranty claims and see how many store credit resolutions were recorded. (By using the “Other” option with a note.) This process is very time-consuming and inefficient.    It would be very helpful if a direct "issue store credit" feature were integrated, potentially automating the process across platforms like Shopify.

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.

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.

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. 

We are a worldwide dropshipping service catering to e-commerce entrepreneurs. Merchants can design and market personalized products through us, setting prices and choosing their sales platforms from our integrated e-commerce options.   Once merchants place orders, we will handle the manufacturing, fulfillment, and shipping logistics to consumers.   When I am using Aftership for tracking, I want to enable my premium customers (merchants) with the ability to customize white label branded tracking pages and possibly an API to create them (since they won't have access to Aftership admin, and it would be impossible for me to maintain all tracking pages for them).   So that I can add this ability as part of the product & service package for my main customers (merchants), which creates more value for my business.

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?