Introduction
A distributor supplies a CSV with product names containing accents or non-English characters. The stock owner’s approved list looks correct. A buyer opens the file for review and sees unfamiliar characters, then sends a “corrected” copy to the vending supplier. The team has changed the handoff before establishing whether the source file, the review route or the receiver was responsible for the difference.
Microsoft’s official article on opening UTF-8 CSV files in Excel gives a specific condition: the file can be opened normally if it was saved with a Byte Order Mark, or BOM. Otherwise, it describes import routes through Power Query or Get Data From Text. This supports a practical acceptance distinction between having a stock file and having an agreed way to interpret it.
This guide concerns multilingual item text travelling into a vending catalogue. It does not establish that a particular cabinet supports every language, font or script. It also does not prove that a source file is correctly encoded merely because its supplier calls it UTF-8. Request evidence along the actual route used by your project.
Quick Answer
Agree the outgoing CSV encoding and the receiver’s BOM expectations, then document how the review team opens the file. If the team uses Excel, follow an appropriate route for that file rather than treating a double-clicked preview as the only source of truth. Retain the untouched supplier file before anyone saves a reviewed copy.
Microsoft states that a UTF-8 CSV saved with BOM can be opened normally in Excel. For other cases, it lists Power Query using Data > Get Data > From file > Get Data from Text/CSV, or Get Data From Text, which opens the Text Import Wizard. The latter route is described as not creating external links to the workbook.
That Excel guidance is not a universal requirement that every vending importer accept a BOM, nor evidence that every receiver automatically detects UTF-8. Ask the equipment supplier to declare the accepted file contract and demonstrate the resulting item text. Review correctly first; validate the catalogue separately.
Source reviewed 11 October 2026: Microsoft Support — Opening CSV UTF-8 files correctly in Excel. Proposed procurement checks below have not been executed on a WEIMI platform.
Comparison Table
| Boundary |
Evidence to request |
What it does not establish |
| Supplier’s original file |
Declared encoding, BOM expectation and approved reference text |
How every review application will interpret it |
| Excel review |
Documented normal-open or import route appropriate to the file |
Receiver parser compatibility or cabinet font support |
| Staged catalogue |
Accepted text compared with approved source |
Translation quality or physical dispensing performance |
| Customer-facing screen |
Readable approved text on the quoted display |
That every future script or file variant is supported |
Keep the questions separate in your acceptance notes. A correct spreadsheet review can coexist with a receiver mismatch. A correctly received text field can coexist with a display problem. A cabinet’s appearance cannot identify which file-reading step needs correction.
Who Should Buy This
Use this brief for buyers receiving multilingual stock lists, operators importing supplier catalogues and distributors preparing product names for several market teams. The issue is especially relevant when one organisation produces the file, another reviews it and a third loads the launch catalogue.
Include the stock-data owner and reviewer in the equipment discussion. They can provide the approved text and the exact handoff route. The commissioning team should not need to guess whether an accented name changed because someone retyped it, an application interpreted the file differently or a screen lacked a suitable display capability.
An English-only procurement article can still support a multilingual project. Request the languages actually needed and have a competent reviewer approve the source labels. This guide supplies a data-acceptance process; it provides no translated customer copy and no claim of multilingual machine certification.
How We Evaluate Smart Vending Machines
The three formats below are shortlisted from public WEIMI listings. No independent hardware tests, encoding experiments or customer cases are reported. Public equipment descriptions help identify a format for a quotation, but they do not confirm UTF-8 import behaviour, BOM handling, font coverage or translation management.
Prepare an isolated demonstration file with approved harmless sample labels representative of the actual languages. Ask a competent reviewer to approve those labels before the demonstration. Include an ordinary English label as a comparison. The samples should exercise the project’s text requirements rather than inventing a claim that all scripts are supported.
Follow the same original file through the reviewer’s documented route and the receiver’s staging process. Capture the approved reference text and accepted catalogue text. If they disagree, retain the file and record where the first observed difference appears. Do not report this suggested demonstration as a completed test.
After data acceptance, show the labels on the quoted customer-facing screen. Inspect wrapping, readability and the connection to the correct physical product. If the cabinet uses a label outside a digital display, inspect that separate route too. A readable name should identify the selected pack without relying on an operator’s private knowledge.
Key Buying Factors
A declared file contract
Ask the supplier and receiver to agree the encoding and BOM handling of the actual file type. Name who produces it and who may change it. The Microsoft source addresses Excel opening behaviour; it does not specify the format contract of a vending platform. Document the receiver’s requirement instead of extending the source beyond its scope.
A reproducible review route
Record how the review team opens the file, including the relevant application and version. Microsoft offers the Power Query and Text Import Wizard routes for the cases described. Confirm that the route exists in the team’s environment, and record the imported result. Do not replace evidence with a copied menu sequence that nobody has used.
If a reviewed preview looks wrong, keep the original file unchanged while investigating. Resaving the displayed text can create another version before the team knows whether the interpretation was correct. The proposed control is to return to the original file and repeat the agreed review, not to manually repair unfamiliar characters by guesswork.
Source approval independent of encoding
Correct character interpretation is not translation approval. The stock owner must approve the product names, variants and any customer-facing wording. The reviewer checks that the accepted text matches that approved source. A technically readable label can still be the wrong flavour or language for the intended market.
Received data independent of display
Request the staged catalogue value and the quoted screen result as separate evidence. If the accepted text is correct but the display is unreadable, investigate display capability with the supplier. If the stored text differs from the source, inspect the file-reading route before assuming the screen caused the change.
A controlled release and correction
Hold a mismatching label for review. Record the authorised replacement file and repeat the affected comparison. These are proposed project controls, not claims that a WEIMI platform provides a particular audit log, rollback function or staging environment. Agree who performs each check if the work happens outside the cabinet.
Best Smart Vending Machines
Compare the physical formats after defining your assortment and text requirements. Treat each listing as an equipment lead; request language and file-handling evidence for the quoted configuration.
01 / DIRECT PACK SELECTION
Single-Door AI Vision Smart Fridge for Packaged Drinks
The public listing describes camera-based checkout for packaged drinks and compatible snacks, five shelf levels with five baskets, and a top screen or lightbox. Confirm cooling and accepted packaging with the supplier. The presence of a screen or lightbox does not establish an encoding contract or coverage of the required languages.
Ask where approved product text appears in the quoted customer experience. Demonstrate its relationship to the accepted sample pack. Camera-based recognition and multilingual text presentation are separate requirements; the public listing does not prove either an import route or a specific language demonstration for this project.
Review the public fridge listing
02 / TOUCHSCREEN SELECTION
WM22 Snacks and Drinks Vending Machine
The WM22 listing describes a 21.5-inch touchscreen, inventory management and cooling. Optional mechanisms include spiral, conveyor, direct push and hanging arrangements. Confirm the chosen mechanism and the screen configuration included in the quote. Do not infer multilingual import or font support from screen size.
Use the displayed selection as the final text-review point after the catalogue comparison. Ask a competent reviewer to inspect approved labels and follow a choice to its loaded pack. This proposed demonstration establishes no independent test score or reported pass for the product.
Review the public WM22 listing
03 / MORE PHYSICAL STOCK SPACE
Two Cabinets, More Choice: Snack & Drink Vending Station
The public page shows a main display and an additional cabinet with visible spiral stock space. Request this format when the project needs another physical assortment area. The listing does not prove shared software, independent cooling, another screen or a common text-import route.
Clarify whether one catalogue handoff or several setup steps populate the available assortment. If separate steps exist, compare the accepted labels at each one. An additional cabinet cannot establish that a successful Excel review reaches every product choice automatically.
Review the public two-cabinet listing
Feature Comparison
| Public format |
Evidence used |
Text requirement to demonstrate |
| Single-Door AI Vision Smart Fridge for Packaged Drinks |
Camera-based packaged-goods checkout and shelf arrangement |
Where approved item text appears and how it links to the accepted pack |
| WM22 Snacks and Drinks Vending Machine |
Touchscreen, inventory management, cooling and mechanism options |
Accepted catalogue text followed into the quoted selection view |
| Two Cabinets, More Choice: Snack & Drink Vending Station |
Main display and additional visible spiral stock area |
Text handoff responsibility for every assortment area |
No product is ranked for multilingual performance because no such test has been completed. The most suitable physical format follows the pack, assortment and selection requirements. The file and display checks remain quotation requirements with their own evidence.
Cost & ROI Analysis
Budget for text acceptance without claiming that it creates a particular equipment return. The following example uses hypothetical assumptions, not WEIMI pricing, measured savings or a customer deployment. Assume a review session takes two and a half staff hours at $28 per hour.
| Hypothetical assumption |
Calculation |
Meaning |
| Initial review and demonstration |
2.5 hours × $28 = $70 |
Assumed labour cost |
| One avoided text-rework cycle |
1.25 hours × $28 = $35 |
Assumed labour avoided |
| Simple labour recovery |
$70 ÷ $35 = 2 cycles |
Two such avoided cycles recover the assumed initial labour |
This does not predict two errors or guarantee a saving. It excludes licences, supplier support, professional language review, equipment capital, printing, travel and lost sales. Substitute actual quotations and observed workload before using a figure in a buying decision.
A clear review route can be valuable even when the file requires no correction. In that case, the value is documented acceptance, while the hypothetical avoided rework does not occur. Keep that distinction when describing the project’s cost rather than presenting a prevention process as measured ROI.
Best Choice by Scenario
A distributor sends one multilingual CSV
Agree the file contract and review route once, then retain the original and accepted versions. Use a representative label comparison before launch. The cabinet choice follows the assortment, while the review evidence follows the distributor-to-receiver handoff.
A market team reviews labels in Excel
Document the route described by Microsoft that is appropriate for the file and available environment. Obtain approval of the text itself from a competent reviewer. An apparently corrupted preview should trigger investigation before a replacement file is authorised.
A supplier prepares customer-facing selections
Ask to see the accepted source text and the quoted display together. If the supplier re-enters labels instead of importing the file, that is a different handoff requiring comparison. Record who approves the resulting catalogue rather than assuming file delivery alone completed the task.
Applications
Apply this brief when packaged-stock names, variant descriptions or replenishment labels move across teams using different review tools. The acceptance question remains where the approved text first differs, whether the cabinet will sit in a workplace, a retail site or another suitable indoor project.
During an assortment update, retain the original new file and compare the changed labels before release. The process does not decide whether a product needs a new identifier; it checks that the approved wording travels through the agreed interpretation route. Keep item identity and language approval as separate project decisions.
For future language additions, repeat the representative display review. A previous successful file with one language is not evidence for every other script, font or layout. Request the actual planned content and inspect its effect on the quoted screen.
FAQ
Does a CSV extension prove that the file is UTF-8?
No encoding proof is established by this guide from the extension alone. Ask for the declared file contract and demonstrate the interpretation of approved sample text along the actual route.
What condition does Microsoft give for normal opening in Excel?
Its article states that a UTF-8 CSV can be opened normally if saved with BOM, meaning Byte Order Mark. The statement concerns Excel opening behaviour, not every receiving system.
How does the source suggest opening other cases?
It lists Power Query through the Get Data dropdown and Get Data From Text, which opens the Text Import Wizard. Confirm the available route in the team’s environment and inspect the imported result.
Should every vending CSV include BOM?
Agree that with the receiver. The Excel source does not define a universal vending importer requirement. A review-friendly file still needs to match the receiving platform’s accepted contract.
Can we fix unfamiliar characters by retyping them?
Use the approved original text and an authorised correction process. Guessing at unfamiliar characters does not establish the intended label. Retain the original file and identify the first observed difference.
Do the listed machines support all languages?
The public listings used here do not establish that claim. Request evidence for the actual languages, accepted catalogue values and quoted display. No multilingual machine pass is reported.
Final Recommendation
Accept three linked results: an approved source file, a documented review interpretation and the receiving catalogue’s matching text. Inspect the customer-facing result separately. When a difference appears, retain the original and identify its first observed boundary before authorising a replacement.
Use the fridge, WM22 and two-cabinet listings to start equipment discussions based on the actual stock and selection format. Request multilingual file and display evidence for the quoted build. A named review owner and reproducible file route give commissioning a firmer basis than a general “languages supported” statement.
CTA
Tell WEIMI which languages your assortment requires, how the stock CSV is prepared and who approves the product labels. Request the appropriate equipment format and a demonstration connecting the accepted file text to the quoted customer-facing selection.
Get My Custom Quote
