PRICE DATA / REGIONAL CONVENTIONS
A different price?
Write the number convention before approving the price transfer.
Introduction
A vending operator prepares a product-price sheet in the number format familiar to the local team. The supplier reviews it on another computer. Both people recognise the item names, yet a comma in an amount may not carry the same meaning for both reviewers. The file can look orderly while the price convention remains unstated.
Microsoft’s official support article explains that Excel uses the system separators defined in regional settings by default. It also describes a temporary override for decimal and thousands separators. This matters to a cross-border purchasing team because a familiar spreadsheet view is not evidence that every participant is using the same convention.
This guide helps buyers specify the price-data handoff around a vending equipment order. It separates what the author intended, what a reviewer sees and what the receiving system actually accepts. It does not claim that a particular WEIMI import tool exists, that all spreadsheets parse a file identically or that changing an Excel setting configures vending software.
Quick Answer
Ask for a written numeric example with its meaning. State the currency, whether the amount is per saleable item or another unit, the decimal character and whether grouping characters are allowed. Do not approve a price merely because both teams can open the workbook.
For illustration, the text 1,250 is ambiguous without a convention: a comma might be used for grouping or as a decimal separator. Write the intended amount in words or provide an agreed ungrouped representation with the decimal rule stated. These are explanatory examples, not prices for equipment or stock.
Before release, ask the receiver to show the accepted numeric value for identified sample products. Compare it with the approved source and the intended customer-facing price. Keep an original copy so that a misunderstood display is investigated from evidence rather than repaired by guessing.
Comparison Table
| Handoff item | What to state | What it does not prove |
|---|---|---|
| Currency | Name the agreed currency separately from the numeric amount. | A punctuation mark does not identify the currency. |
| Decimal separator | Identify the character that separates whole and fractional units. | The receiver uses the author’s local setting. |
| Thousands separator | State whether grouping is permitted and which character is used. | A grouping mark will be ignored by every importer. |
| Workbook view | Record the review environment and any custom separators. | A screenshot establishes the received numeric value. |
| Receiving evidence | Show product identifier, accepted value, currency and unit together. | Opening the file means all prices were accepted. |
The comparison is a proposed procurement checklist. The Microsoft source explains Excel separator settings; it does not prescribe the field schema or import behaviour of a vending platform. Obtain those details from the supplier for the offered system.
Who Should Buy This
Use this guide when a distributor transfers product-price data between markets, an operator sends a workbook to a supplier or a project team approves a catalogue before commissioning. The issue is especially visible when people are accustomed to different decimal and grouping characters.
The commercial owner should approve the intended amounts. The person preparing the file should preserve the source values and document the convention. The supplier or integration provider should explain the receiving format and demonstrate the result. One person’s familiarity with Excel does not replace the other roles.
This is a numeric-notation review, separate from deciding the selling price, choosing the payment currency or calculating a margin. It also differs from rounding: rounding changes precision under a stated rule, while a separator misunderstanding can change what number the text is taken to mean.
How We Evaluate Smart Vending Machines
We compare three real WEIMI public listings as a procurement shortlist based on their published retail formats. We have not independently tested the machines, imported a live price sheet or confirmed any particular parser. “Best” means suitable for further enquiry after the actual product and operating requirements are defined.
Microsoft’s separator article supplies the factual foundation for the workbook review. By default, Excel follows the system separators in regional settings. Its documented override is through File > Options > Advanced, under Editing options, by clearing Use system separators and entering the decimal and thousands separators. This article reports that route; no settings on the buyer’s computer have been changed.
Our proposed acceptance method then goes beyond the workbook view: request a supported handoff format, a controlled sample and evidence of the values the receiver accepted. The supplier must confirm which steps are available in the offered deployment. A hardware listing alone cannot establish numeric compatibility.
Key Buying Factors
Start with meaning, then choose notation
Attach every price to its product identifier, currency and saleable unit. An amount for one pack must remain distinguishable from an amount for a case. Write an unambiguous explanation for the review samples before asking anyone to reformat the sheet. A clean-looking number is not useful if its commercial meaning is missing.
Record decimal and grouping rules separately
Do not write only “European format” or “international format.” Identify the exact characters and any restriction on grouping. If the supplier requests values without grouping separators, use that documented requirement for the handoff. Do not assume that simply removing punctuation preserves the original amount.
Distinguish an Excel override from the system default
Microsoft describes custom separators as a temporary replacement for the system separators. Its guidance says to select Use system separators again when returning to the system convention; for a permanent solution it points to Control Panel regional settings. Treat any setting change as an intentional review choice with an owner, rather than an unexplained fix to a shared computer.
Ask the receiving system for its own contract
Confirm the accepted file type, price field, numeric representation and handling of an unaccepted value. Those are supplier questions. A CSV column delimiter, a decimal character and a thousands character have different roles; this guide does not infer one from another or provide a universal CSV recipe.
Approve sample outcomes before the full release
Choose clearly identified sample records with fractional and larger amounts relevant to the actual catalogue. Ask the receiver to return the accepted amounts with their identifiers, currency and units. Use a supported test or review route. Do not publish temporary customer prices to prove a parser, and do not treat a successful file upload as proof that every row is correct.
Preserve evidence when conventions change
Keep the original approved source, the handoff version and the receiving evidence. If a reviewer finds an unexpected amount, stop release and resolve the intended value with its owner. Avoid a global search-and-replace of commas and dots across an unknown workbook: text descriptions, formulas and different fields may require different treatment.
Best Smart Vending Machines
Single-Door AI Vision Smart Fridge for Packaged Drinks
The public page describes a single-door fridge for packaged drinks and compatible snacks, five shelf levels with five baskets, and a 21.5-inch top screen or light box. Customers select products directly from the cabinet; it does not squeeze juice.
For a recognition-led assortment, ask how each approved SKU is connected to its configured selling price. Keep that question separate from recognition testing. Correctly identifying a package does not establish that the price entered for it was interpreted correctly. No spreadsheet import capability is assumed here.
Read the public smart-fridge listing
WM22 Snacks and Drinks Vending Machine
The WM22 page describes a 21.5-inch touchscreen, cooling and inventory-management functions. It lists optional dispensing arrangements that require confirmation for the order. These published features make it a candidate for a touchscreen snack-and-drink brief, not a proven answer to a regional data-format issue.
Ask the supplier to demonstrate the configured product price in the actual selection flow and provide the supported method for entering or transferring it. The screen’s size and the existence of inventory features do not establish an import schema, currency precision or automatic punctuation conversion.
Two Cabinets, More Choice: Snack & Drink Vending Station
The public page presents a main product cabinet and a secondary compartment with visible spiral lanes. It asks buyers to confirm product mapping, control and payment integration for the two sections. Capacity, dispensing routes and cooling remain configuration questions.
For a two-section catalogue, keep each sample price tied to the product and its confirmed selling location. Demonstrate the intended price for products in both sections using the supplier’s supported process. A larger assortment makes a documented handoff useful, but it does not prove that this station has a bulk-import function.
Feature Comparison
| Public candidate | Published retail format | Price-handoff question |
|---|---|---|
| AI vision fridge | Compatible packaged-product selection with camera-based recognition. | How is the approved amount linked to each recognised SKU? |
| WM22 | Touchscreen selection, cooling and inventory functions. | What supported entry route produces the displayed product price? |
| Dual-cabinet station | Main cabinet and a secondary spiral-lane section. | How are sample prices demonstrated for products in both sections? |
No candidate receives a score for import compatibility because that capability has not been established. Ask for the supplier’s current documentation and a configuration-specific demonstration before adding it to the purchase specification.
Cost & ROI Analysis
Hypothetical preparation allowance: assume 45 minutes to document the notation and sample amounts, 30 minutes for supplier review and 30 minutes to reconcile receiving evidence. At an invented internal rate of $40 per hour, 105 minutes equals 1.75 hours and costs $70.
This arithmetic describes assumed staff time only. It is not a quoted service fee, a machine price, a measured task duration or evidence that the process prevents a specific monetary loss. The dollar symbol belongs to this fictional planning example and does not define the deployment’s selling currency.
No return on investment or payback is calculated. To build a real project budget, obtain the equipment quotation and any actual catalogue-setup or integration fees. If the supplier offers manual entry instead of file import, cost that confirmed workflow rather than assuming automation is included.
Keep the reason for review clear: the team is seeking agreement on intended and received prices. A dramatic hypothetical pricing error would not establish the likelihood or value of a real loss, so it is not used as a sales claim here.
Best Choice by Scenario
One market, several reviewers
Use the machine format that fits the actual assortment and service plan. Agree a single price convention and identify whether reviewers use the system default or a custom Excel view. Shared geography alone does not confirm identical application settings.
A distributor preparing catalogues for several markets
Maintain separately approved currency and amount rules for each deployment. Ask the supplier whether the handoff process and market configuration support those rules. Do not reuse a successful sample from one receiving environment as proof for another.
A new two-cabinet installation
Consider the dual-cabinet format when the actual site and assortment justify it. Include samples from both selling sections in the agreed price review. This checks the scope of the handoff without assuming that the two sections have independent currencies or a particular internal data model.
Applications
At enquiry stage, send a small fictional sample that explains the desired price notation without exposing commercial data unnecessarily. Ask the supplier to describe the supported entry method, any template and the evidence it can return. This helps make the catalogue-setup scope concrete before an order.
At commissioning, use approved records and a controlled review route to compare the intended price with the value accepted by the receiving system. Record the relevant software configuration and the version of the source sheet. A screenshot should identify the product and context, not just an isolated number.
During later price updates, repeat the relevant check when the authoring environment, template or receiving process changes. Preserve the previous approved version and use the supplier’s supported correction procedure if an amount is disputed. This article does not describe an actual fault, customer incident or successful deployment.
FAQ
Does a comma always mean a decimal separator?
No. Its meaning depends on the agreed convention and context. State the decimal and grouping rules explicitly instead of inferring them from a reviewer’s location.
Does Excel always use the regional system separators?
Microsoft says those are the default, and documents a custom override. Verify the actual review settings when that distinction matters.
Does changing Excel configure the vending importer?
No such conclusion follows from the source. Ask the supplier for the receiving system’s own supported format and verify the accepted values.
Should every comma and dot be replaced before sending a sheet?
Do not apply an uncontrolled replacement. First establish the intended values and field-specific requirements, preserve the original and use an approved transformation process.
Does a successful upload prove that prices are correct?
It does not by itself demonstrate the accepted amounts. Request identified sample results and reconcile them with the approved source, currency and unit.
Does the $70 example establish savings or payback?
No. It is an invented staff-time allowance of 1.75 hours at $40 per hour. No financial benefit or equipment return has been verified.
Final Recommendation
Choose the retail format around the products and customer workflow, then make the price handoff an explicit part of the commissioning brief. Preserve the intended amount, currency and unit, document decimal and grouping conventions, and require evidence of the receiving result before release.
The factual source is Microsoft Support’s Change the character used to separate thousands or decimals. It explains Excel’s system default, temporary custom separators and how to return to the system setting. The sample acceptance workflow is our procurement proposal; it is not a Microsoft endorsement of a vending product or a description of a verified WEIMI importer.
A price that looks familiar to its author is the beginning of the review. A documented match between the approved source and the receiving value gives the team a clearer basis for accepting the catalogue configuration.
CTA
Send WEIMI your destination market, intended assortment, saleable units and price-data handoff requirements. Ask for a configuration-specific quotation and the supported catalogue-entry process, including any templates, review steps and setup fees. Use fictional sample amounts until real commercial data are needed and authorised for sharing.
The enquiry helps define equipment and setup scope. It does not confirm import compatibility or approve prices for a live deployment.
