Share your ideas with us

A notification to give the customer the opportunity to change their requested ship date. This allows wineries to change the date without re-directing.  Using the RSD and sending a notification 3 days or so before. 

I want to fully customize different free shipping thresholds for different currencies/regions.   This would better compensate for my shipping costs in different currencies and may also increase the order value.

When exporting, it would be handy if there was a third Data Format option.  In addition to Standard and Custom, something like “Same as current display” or something like that.  An option that would create the csv or xlsx file with the same columns in the same order that are displayed in the current view on the web page. I find myself adding or removing columns in the dashboard in order to see what I want to look at but, if I want to then export it, I need to either recreate the view again in the export wizard (which isn’t always even possible) or export it standard and move stuff around in excel. 

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

When I receive tracking from suppliers, I add manually to AfterShip.  Usually there's more than 1 tracking number, for the same courier, so it would be great to able to add multiple tracking numbers at the same time as comma separated.   When clicking Save, it would then use all the information entered, for example; Customer name, order number etc etc.   Below example for tracking number 123456789 and 987654321  

Our warehouse needs to know how many returns were requested on a daily basis so they can plan their resources accordingly. but it is not an option for now. It would be nice if we could build our own reports and schedule it. 

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.

Good morning, When viewing notification emails on a mobile device, the background colour only appears at the top as a small strip. As a result, the background colour on the sides and beneath the email is completely lost. I therefore propose hiding the background area entirely on mobile, displaying only what is within the content background, which is the main body of the email. Thank you.

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.

I was just tracking my packages and thought of something and was like man I wish there would be different layouts or sorting options. Like if I could sort it by ETD Dates, etc rather than just having them all listed and me doing the mental math of 3 days from now would be Friday, etc. Since of our would be able to be listed by delivery date I would know what packages I need to be on the lookout for that day at an early glance.