The “Back” button on the RC portal is not obvious or prominent enough. It is too hard to find and blends into the page.

Good morning, When viewing notification emails on a mobile device, the background colour only appears at the top as a small strip. As a result, the background colour on the sides and beneath the email is completely lost. I therefore propose hiding the background area entirely on mobile, displaying only what is within the content background, which is the main body of the email. Thank you.

Items + return reasons are not clearly highlighted/shown as selected, during the Return Request flow on the RC portal. Request: During the return flow more clearly define that an item/return resolution is selected. i.e. have text say “Selected” or have the box change colour when an item/resolution is selected beyond just the black box.

Currently you can manually refund the shipping fee in the admin manually, but would like the ability for it to be automatic.

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.

Hi there, We ship wine, which means orders are often held by our fulfilment center when temperatures along the route are above or below certian threshold we have set. I would like to create a flow that automatically notifies the customer that their order has been flagged for a weather hold and ensures them it is still on the way. Is this possible? Thanks

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.

在英语版本下，缺货订阅按钮会正常显示：https://eu.elegoo.com/products/elegoo-pla-filament-1-75mm-3d-printer-filament-1kg-spool-2-2-lbs?variant=45521201037588 在法语及其他语言版本下，缺货订阅按钮未显示：https://eu.elegoo.com/fr/products/elegoo-pla-filament-1-75mm-3d-printer-filament-1kg-spool-2-2-lbs?variant=45521201037588

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.

If you are working with many different returns in one day, there needs to be a quick way to copy information like in Shopify as example. Please reference the far right side of this image: