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.

I am the owner of a fashion company preparing to expand my business operations in the US. I have been utilizing Aftership EDD for some time now and I'm interested in learning how to configure my EDDs to accommodate multiple locations. Specifically, I have two separate locations in Australia and the US where identical SKUs are stocked. In cases where a particular SKU is out of stock at the US location, I would like orders to be fulfilled using available stock from the AU location as a fallback option. I am seeking guidance on integrating this specific logic into my EDD settings.

I would like to view the chart showing reasons for late shipments in the current on-time report that I am using.

Add the ability to block a return and direct the customer to the warranty portal. Bonus if you could log the customer in and auto fill information. Potential Mockup Potential User Experience

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.

I guess for shipping emails sent out to my customers, it would be nice to have dynamic info that updates as the package progresses through the network. I also want all my existing emails to stay current. The reason is simply that I wanna give my customers a unified experience by delivering consistent messages to them. I believe this will help with my customer satisfaction.

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.

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.

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.

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: