Share your ideas with us

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.

We are a worldwide dropshipping service catering to e-commerce entrepreneurs. Merchants can design and market personalized products through us, setting prices and choosing their sales platforms from our integrated e-commerce options.   Once merchants place orders, we will handle the manufacturing, fulfillment, and shipping logistics to consumers.   When I am using Aftership for tracking, I want to enable my premium customers (merchants) with the ability to customize white label branded tracking pages and possibly an API to create them (since they won't have access to Aftership admin, and it would be impossible for me to maintain all tracking pages for them).   So that I can add this ability as part of the product & service package for my main customers (merchants), which creates more value for my business.

Integration of Sharetown to schedule pickups of items being returned. The process involves Sharetown picking up items directly from the customer's doorstep without the need for packaging. Once the items are picked up, Sharetown will resell the items through their channels and provide business with an agreed-upon gain-share payback based on the resale price.   Key Requirements: No label generation is needed as Sharetown will handle the pickup. A system integration will be needed to push the return data to Sharetown as a pickup request in their system. Sharetown will manage the logistics and resale of the items.

Scenarios 1. We give a customer a partial refund for a coupon code they forgot to enter. This partial refund is currently stopping the customer and us from being able to request a return in Aftership. Please allow an option to make RMA or override in this scenario. 2. (similar to #1) Customer orders multiple items, gets RMA for one item, returns it and is refunded. Now they want to return the other item, however, because there is a refund in Shopify we are not able to open a RMA for the other item because the order shows as returned. Please allow option to make RMA or override in this scenario.  Thank you

That would be great if Feed could accommodate the listing of "not-for-sale products" on TTS. This feature is newly introduced in TTS, where the product is not for sale to shoppers but will be gifted to them instead.

We want the ability to display shipping reviews to front end customers/users to give them social proof and increase conversion rates. Fast, cheap, convenient and reliable delivery helps to boost conversion rates, especially when you're entering a new market and trying to build brand awareness/trust. It also helps to get customers who are used to visiting your retail stores to shift to shopping online instead of just going in to a store. Currently, shipping reviews are only available to back end users and internal teams in the aftership portal, but we want to be able to have a customisable widget that we can display on places like the homepage, PDPs, information pages like shipping & delivery info pages etc... We can pick and choose or set up rules to automate showing a handful of reviews related to the shipping customer experience.

There is a massive discrepancy between the notificaiton customization capabilities within the Tracking module and the Returns module.  In the Returns module, all you can do is update the messaging. There is no ability to alter colours, add logos, images, or otherwise truly 'brand' the notifications.  All of this exists in the Tracking module.  Recommendation is that you port over the same functionality into the Returns module ASAP.  Those notification emails are currently a horrific customer experience.

Fast and reliable delivery plays a vital role in customer satisfaction for heavy equipment buyers. When products arrive on time and in perfect condition, it builds trust, reduces downtime, and encourages repeat business and brand loyalty.

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.

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.