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.

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.

Background: At the moment, a user with a specific domain can easily create a new organization when creating an account in AfterShip We don’t indicate to this use that an existing organization is already linked to the same domain This can create confusion when member are trying to get access to an organization proactively (without being added by the current owner) Hence we end up with support tickets from member not able to get access to their main org. Expectation: Alert message during new inscription if we identify that the email domain is already used. Eventually an option to send a request to the owner of the main org. Possibility to delete the new account to avoid unnecessary org and member creations for our clients. Could be active only for ENT client if we want to reduce the scope

Is it possible to increase the bulk search limit from 50? We often have to peform bulk search a number of times to retrieve the data that we're looking.

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.

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

For instance, customers can quickly locate reviews based on size, incorporate images and videos, consider age, product characteristics, and the reviewer's recommendation status.

Can we get an option to automatically restock the item based on resolution, not just when received. We still need to process, and inspect the item before we issue the refund, and we can't have our inventory adjusted upon recept. Thanks!

We should be able to update the email address on the returns and warranty pages in case the cx is unable to access the default email.

we provide return shipping label after approving the return request. Our product contains hazarious material, which should be shipped with hazmat label. Aftership doesn't grant the api access of selecting the Hazmat label when auto-generating return shipping label Please fix it