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

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

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.

The ability to see how much it cost per tracking label for the carrier, alongside all the other analytics would be beneficial to business operations. Having “cost” as a piece of data collect and display in analytics will help us make larger business decisions when it comes to choice of carrier preferences to know which carrier is best to work with in the long run. I believe this feature will be great value add to Aftership as well!

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.

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.

Titles should update with count of items in the section so you know it's updating and should be clicked on.

Enable merchants to customize the duration before an RMA is automatically canceled. Currently, the system only allows for auto-cancellation after 28 days of inactivity. To better suit our company's needs, we would like the option to extend this period.

So, as a seller who often runs campaigns, I would love to have a cool discount setup that can be customized based on how customers behave. For example, I could keep discounts hidden for shoppers with shopping carts over $1,000 but display them for those who have smaller carts, so that they would shop more to get a better discount. This strategy can be effectively applied to our product recommendations, enhancing conversion rates and boosting average order values.

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.