WEIMI INSIGHTS / CUSTOMER EXPERIENCE
Build a consistent purchase journey for international customers, from product selection to payment errors and support.
PRODUCTS
Names, sizes and essential product details.
PAYMENT
Instructions, outcomes and cancellations.
SUPPORT
The next step when something goes wrong.
A language button is useful only when the customer can finish the whole transaction in the language they selected.
01 / BUYER NOTES
Start with a screen-by-screen journey: attract screen, language selection, product list, basket, payment, collection and receipt. Add the less comfortable paths, such as sold out, declined payment and a transaction timeout. These are often the places where untranslated text survives.
Decide which languages the location needs using visitor and staff knowledge. An international hotel may have different needs from a local office. Confirm that the quoted software supports those languages and writing systems; a translated marketing image is not evidence of a working interface.
02 / BUYER NOTES
Maintain one approved product list with a stable identifier for each item. Translate the name, pack size and relevant description from that source. Do not let different teams rename the same item independently across the machine, refill sheet and receipt system.
Use a competent reviewer for product information, particularly ingredients, allergens and storage instructions. Where information is legally required, confirm how it must be presented locally. Automatic translation can help create a draft, but it should not become the final authority for safety-related wording.
03 / BUYER NOTES
Translated text can take more space than the original. Check buttons, product tiles, line breaks and confirmation messages on the actual display. Verify currencies, decimal separators and date formats as well. A perfectly translated phrase can still be unusable if it is cut off.
Pay attention to the payment terminal, which may have its own language settings. Test whether a customer’s chosen language carries through or whether the terminal behaves separately. Instructions should make the next action clear even when two components cannot share a language preference.
04 / BUYER NOTES
Assign an owner for language updates. A new product, refund route or software message can introduce a gap after launch. Include translation review in the change process and keep a record of which interface version was checked.
Ask someone unfamiliar with the machine to buy an item using each supported language. Watch for hesitation and requests for help. The goal is a successful purchase, not a literal word-for-word match. Short, direct wording usually works better than promotional language on a transaction screen.
Scope: Navigation, product selection, collection and exceptions.
Owner: Agree who changes the software text and approves the result.
Scope: Tap, insert, verification, approval and decline prompts.
Owner: Confirm the options with the payment provider.
Scope: Help label, receipt portal and issue-reporting route.
Owner: Ensure the support team can handle the languages promised.
PRACTICAL ANSWERS
Choose the languages relevant to the site and support them well. A longer menu adds little value if important parts of the journey remain untranslated.
Sometimes, but it depends on the integration. Ask for a demonstration with the exact terminal rather than assuming the settings are shared.
Usually the brand remains recognisable while the descriptive information is localised. Check the approved product naming and any applicable labelling requirements.
YOUR NEXT STEP
List the languages, currencies and support routes needed at your location. Pair this review with a complete purchase-accessibility test.
Explore equipment →Discuss your requirements →