While using personalization, I want to understand the actual product results generated by these algorithms and the reason behind the chosen product displays for shoppers. If I can preview the recommendation results in the admin, it would reduce uncertainty, ensure optimal outcomes, and improve my marketing strategies to boost conversions.

It would be useful to have a Sku column amognst the list when editing the returns dashboard. The image of the item is useful but often the item is enclosed in a boxed which is marked with the sku. Therefore at first glance, the sku is seen before the physical item.

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.

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.

Perhaps with Aftership Reviews, we could set a custom rule where if the transit time is exceeds X days, the platform won't initiate reviews.

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

Related to BOPIS Track - set a Pickup deadline date and use it as a Merge Tag on Notifications. Ideally, set a date and time expiration date so the end consumer know when they need to pick up their order. If the end consumer doesn't pick up their package before the expiration date, then cancel the order, notify the client and possibly refund the end consumer.

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.

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.

I would like to include the RMA number barcode on the returns label. This way, upon receiving the returns label at my warehouse, I can simply scan the barcode to retrieve the RMA number. Subsequently, I can use this number to efficiently locate the corresponding RMA information within the returns system. This process will significantly enhance the operational efficiency of our RMA procedures.