Share your ideas with us

Suggestion: Add Lazada Express (LEX MY / LEL) Support for Malaysia   Hi,   I would like to suggest adding Lazada Express (LEX MY / LEL) as a supported courier/carrier on your app and website.   Lazada Express is the official delivery courier used by Lazada in Malaysia, similar to how SPX Express / Shopee Express is the official courier for Shopee. Many Lazada shipments in Malaysia are handled by LEX, so having direct tracking support would be very useful for Malaysian users.   The official LEX Malaysia tracking website is: https://lex.com.my/   For testing purposes, you can use these example tracking numbers:   LXST191548638MY MYMPA257159996   I hope you can consider implementing Lazada Express (LEX MY / LEL) support soon. As Lazada is widely used in Malaysia, I believe many users would appreciate being able to add and track their LEX shipments directly through your app and website instead of having to visit the LEX website separately.   Thank you for considering this suggestion. I hope LEX MY support can be added in a future update!

I would find it very useful if I could pull the SMS communication metadata using an API. Currently it is only available as a download from the portal which makes automation impossible.

Can we have a way to export the report of the notifications? So for example, I would love to be able to export the list of people who had bounced emails for our shipping notifications or even to export the list of folks who did not open the message. 

As a business owner, I am seeking a system that can facilitate risk level scoring for each RMA (Return Merchandise Authorization) and enable my staff to input risk assessment findings based on actual RMA inspections. This system will enable us to assess risk levels effectively and respond accordingly. Moreover, the system will allow for the reporting of any detected fraud instances.   Implementing this system is crucial for mitigating fraud occurrences, as well as proactively preventing future fraudulent activities. Such measures are instrumental in safeguarding my business's profitability in the long term.

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.

We would love to be able to see the return comment information our customers provide when returning items within the return reports we download. Our customers are using the comment box to describe the return reason in depth but this information is lost when it comes to dowloading the return reports.

In our business we refund direcly in Shopify for our returns that are made from our online website. It would be nice if the status of Shopify shows refunded or partically refund that Aftership would show the return as resolved. Some of the tracking information has to be put in manaully and we have multiple people on our team and if they do not do it correctly our customers receive emails that their return was not send and is expiring when they have already been refunded. 

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

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

it would be great to be able to manually add a placeholder delivery in order to keep track of my deliveries.