Share your ideas with us

My package is currently reading that it is out for delivery in my area, but is still showing to be located in a totally different country so the tracking needs to be updated and fixed because this has been an ongoing issue that I've contacted them about for support and it's still reading the same way

Some customers enter +1 before their phone number when requesting a return or exchange. This causes the shipping label to fail to generate and creates frustration for the customer and extra work for me. I would like the system to correct the phone number to allow successful label generation.

Add the option to pay online ~ $2 at checkout for free returns and extended warranty later.    Add tags to people / allow different RMA flow for those who optin to this. 

As a merchant, I would like to charge the cost of return when the shopper chooses to replace the returned item.  aftership Returns provides Stripe checkout only for this scenario, but I don't have a Stripe account, I would like to use my Shopify checkout to charge the exchange upsell and cost of return. So that I don't have to open a Stripe checkout and manage two accounts (Shopify and Stripe checkout) at the same time.

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.

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.

We want the feature for referral program page through which we can dedicated referr to the customers and one affiliate program for our influencer through which they can track their progress and commisions. 

Most major carriers already provide an estimated delivery date/time as part of their tracking data, but this isn't currently surfaced in the app. Context: Customers tracking a shipment want to know when it will arrive, not just its current status. Right now they have to infer this themselves or check the carrier's own site separately. Issue to address: Add a field that displays the carrier's estimated delivery date (and time window, where the carrier provides one) on the tracking/order page. This would reduce "where is my order" support inquiries and improve the post-purchase experience. Suggestion: Pull the estimated delivery data from carriers that already expose it via their APIs, and display it prominently near the shipment status.

Please add the shipping company ACI EXPRESS, which is based in South Korea. They have partnerships with multiple overseas shipping companies, and a lot of merchandise is being shipped through ACI Express to the USA and the Middle East, especially after the implementation of tariffs in the USA.

Support setting the total number of emails that can be sent by each contact within a certain period of time (frequency), including flows and newsletters.   I aim to reduce interruptions for my customers while still capturing important messages, which is why I am seeking more flexibility in the configurations.