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

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.

I work in the furniture industry with thousands of products and continuous new product listings. Consumers often inquire about variations in materials and sizes between similar pieces of furniture, placing a significant burden on my support team. Generating comparison pages for every query we receive is unfeasible due to the volume of requests. Given the potential of AI to suggest comparable items, could it also be leveraged to pinpoint disparities among products and present these distinctions to consumers? Such a system can alleviate my workload significantly and potentially reduce bounce rates as well.

The current capability features a static returns approval notification. There are instances where the approval notification should be customized before being sent to the customer. Currently, the only way of doing this is to change the approval notification for all returns, save, go back to the RMA in question, approve it with the new notification, make sure no other returns are approved, go back to the nofication and amend it to how it was prior and save. Use case: there may be a specific product that is available for exchange in store, this needs to be checked with the store first so cannot be a hard rule. If the approval notification could be amended on an adhoc basis, you could give the customer the option at the point of approval and avoid back and forth via email.

Currently the aftership is one way communication making it diffucult for business to see integrated full status at one place again when customer login to their shopify page they see status of item still on the way as shopify stops at fullfilled stge. Though the track order option by Aftership is good it is still a bad customer experience.

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.

Honestly, this would help us to ease our shoppers through possible delays proactively.

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 utilizing an HTML email editor, I aim to display and personalize shipment or order items within my tracking notifications. This feature would allow shoppers to conveniently view their purchases directly in the email, thereby improving customer satisfaction.

After RMA is created, admin needs the ability to edit details of the return. Including: editing products on return editing customer email/address details add remove return fees prior to receipt of return Often customers will call and need a return label sent to a new email address or want to add or remove items on their return. Also, if items are returned that are not included the return must be canceled and reopened, which is a messy process that sends a ton of unneccessary emails to the customer.