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.

For the tracking page I am currently using, it would be great to have the Delivery Instructions feature, so that my customers can provide specific instructions to carriers, and ensure successful deliveries. This feature will also be valuable for drivers who can have all the necessary information at their fingertips, even for dispatchers who can manage delivery more effectively with all that info. A seamless last-mile delivery experience can create a sense of reliability and convenience that fosters long-term customer relationships and encourages repeat purchases for my brand.

Upload label manually from external source and link (instead of file only) Today its only possible to upload label manually through file via computer. Hope this will change and we ca upload via external url

There's quite a few couriers where the 'View on Carrier Website' doesn't take you directly to the trracking page, and instead requires you to enter the tracking number. These can be easily fixed by correcting the URL. For example, for Cainiao the link takes you to; https://global.cainiao.com/ This needs correcting to; https://global.cainiao.com/newDetail.htm?mailNoList= Please submit any further examples below.

We want to refer to the customer's username when packing the order. Right now, to do this, we need to download the tiktok orders, connect them to the shopify order number via the tiktok order in the notes field and then connect that to the order number in shipbob. If we had the username in shopify, we could eliminate the step where we have to connect tiktok to shopify.

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.

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

leading latin america e commerce platform https://tiendanube.com

Add the ability to upload a separate images for desktop and mobile header logos. An example of the what the UI could like like is below. Returns > Customizations > Returns page

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.