The background is that I sell my products on multiple marketplaces, and each has different return flows that the aftership Returns page cannot handle. It would be much easier if there is a Returns API that can meet my requirements below. Need: - I need a Returns API to allow creating RMA/return requests without having to use the Returns Page to file it. - I can call the API and pass the information regarding the Return Reason Resolution, etc in one go. - Once I call this API, it will return creation in Pending or Auto-Approved Status.

When exporting, it would be handy if there was a third Data Format option. In addition to Standard and Custom, something like “Same as current display” or something like that. An option that would create the csv or xlsx file with the same columns in the same order that are displayed in the current view on the web page. I find myself adding or removing columns in the dashboard in order to see what I want to look at but, if I want to then export it, I need to either recreate the view again in the export wizard (which isn’t always even possible) or export it standard and move stuff around in excel.

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

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

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

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.

leading latin america e commerce platform https://tiendanube.com

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

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.

When a warranty is approved, you can choose to include an label. In the “Warranty claim approved” email, there is no ability to account for this decision. We would need to add an ability to have wording around a label being included as well as a label not being included. Below is an example email we have now. Two ways this could be addressed: 1. Split this notification into 2 notifications: “Warranty claim approved - with label” and “Warranty claim approved - no label”. 2. Add Flows to Warranties with Split functionality for generated labels.