WEIMI / PRODUCT DATA PROCUREMENT
More digits in the field.
The same item in the file?
Separate a fixed-width representation from a new trade-item identity before importing the vending catalogue.
CATALOGUE NOTE 01
Introduction
A vending software supplier asks for every product GTIN in a 14-digit field. The beverage supplier sends a shorter identifier. The buyer sees extra zeros in the prepared file and has to decide whether the item has changed, whether a new product record is needed, or whether the two values are simply different representations of the same identifier.
This is a data-contract question with practical consequences for catalogue acceptance. The equipment may display the right pack image while a receiving integration creates a second record for the padded value. Alternatively, an overbroad rule may alter a different identifier that should have stayed distinct. A buying team needs a documented transformation and evidence of the resulting match.
GS1’s glossary defines leading zeros as leftmost additions when GTIN-8, GTIN-12 or GTIN-13 is represented in a GS1 carrier, message or database requiring 14 digits. It separately defines an indicator as a digit from 1 to 9 at the left of GTIN-14. That distinction provides the foundation for this guide. It does not justify inventing product identifiers or guessing packaging relationships from digit length.
CATALOGUE NOTE 02
Quick Answer
Padding an existing GTIN with leading zeros for a required 14-digit representation is a formatting operation, not a reason to invent a new product. Confirm that the source value is a complete, valid GTIN in the expected format and that the receiving field actually requires that representation. Then specify how the original value and normalized representation refer to the same approved catalogue item.
Do not treat a nonzero first digit as interchangeable filler. GS1 defines the GTIN-14 indicator in the range 1–9, while its leading-zero definition addresses padding shorter GTIN formats. A different complete identifier requires its own verified item mapping; the buyer should not infer the pack size, quantity or saleable unit from a changed first digit alone.
Ask the software supplier to demonstrate an import, a lookup and an export against an approved sample. The evidence should show which item was matched, whether a duplicate was created and how any ambiguous record was handled. This is proposed acceptance work, not a claim that a WEIMI platform already implements a particular normalization rule.
CATALOGUE NOTE 03
Comparison Table
| Incoming situation | Correct procurement question | Evidence to request |
|---|---|---|
| A complete shorter GTIN enters a required 14-digit field | What approved zero-padding rule represents this identifier? | Source value, resulting fixed-width value and same-item matching evidence. |
| A supplied 14-digit value starts with a nonzero digit | Which trade item does this complete identifier actually identify? | Supplier-confirmed product record and packaging relationship, where relevant. |
| A value is incomplete or its origin is unclear | Can the authoritative supplier resolve it before import? | An exception record and approved correction; no guessed reconstruction. |
| Two feeds use different representations for one item | Which canonical comparison rule prevents accidental duplicates? | Import and reimport results showing one intended catalogue identity. |
The table concerns identifier representation and matching, not barcode print quality or a new identifier-allocation decision. A correct comparison rule does not demonstrate that a physical scanner reads the package, that the item belongs to the supplier, or that the stock fits the cabinet. Keep those checks separate in the purchasing file.
CATALOGUE NOTE 04
Who Should Buy This
This guide is useful for operators moving product data between a wholesaler, a vending management platform and a warehouse system. It also serves distributors preparing a customer catalogue before equipment delivery. The issue becomes visible when one system expects a fixed-width GTIN and another provides the shorter original format.
For a small pilot, resolve the rule while the sample set is manageable. For a mixed fleet, involve the person responsible for each receiving integration. A single spreadsheet can look consistent while the systems consuming it apply different matching rules. Agreement must cover the actual path used to create and update products.
Buyers selecting only a standalone cabinet should establish whether GTINs are part of the supplied software scope at all. Do not add a normalization requirement to an unrelated field named “product code” without confirming its intended namespace. An internal stock code is not automatically a GTIN simply because it contains digits.
CATALOGUE NOTE 05
How We Evaluate Smart Vending Machines
Our method is a public-documentation review. We checked GS1’s glossary definitions for leading zeros, indicator and GTIN-14 on 21 October 2026. We use previously saved, same-date public WEIMI listings for the three equipment formats. We have not independently tested the products, imported a customer’s catalogue or verified a particular software integration.
We assess the proposed data service across source, transformation and destination. The source must identify what field was supplied. The transformation must say exactly when padding applies. The destination must show the intended item relationship and the behavior of subsequent updates. A visually tidy import file is only one piece of that evidence.
The evaluation also asks who owns exceptions. A supplier should distinguish an unsupported format, an incomplete identifier, an unresolved item and a conflicting record. Those conditions need different responses. Automatically padding every numeric-looking value can hide a source-data problem instead of resolving it.
The equipment shortlist is conditional on the planned shopping format. A touchscreen machine, an open-door fridge and a dual-cabinet station have different product-validation needs. None receives a score for GTIN normalization, because the public pages used here do not establish that capability. Include any required catalogue service explicitly in the final quotation.
CATALOGUE NOTE 06
Key Buying Factors
Define the field before the conversion
Ask the receiving supplier whether its field represents a GTIN, an internal identifier or something else. Document accepted source formats and the required stored or exchanged representation. GS1’s leading-zero definition is conditional on a context requiring 14 digits; it is not an instruction to force every field in every system into the same width.
Keep the authoritative supplied identifier available in the acceptance evidence alongside the transformed value. This makes the rule reviewable without treating an image of a pack label as the only source. If the receiving system stores only a canonical form, ask how the original supplier reference can be traced during support.
Separate padding from allocation
For an approved complete GTIN-13, adding one leading zero produces a 14-position representation. GTIN-12 and GTIN-8 require different numbers of leading zeros for that same width. This arithmetic describes representation only. It does not create an instruction to alter the existing identifier’s final digit or assign a new product identity.
A supplied GTIN-14 with an indicator in its leftmost position deserves a separate identity check. Do not remove its first digit merely to make it resemble another record. Obtain the supplier’s verified item description and the relevant packaging relationship. Different units must not be merged because their remaining digits look familiar.
Specify matching and conflict behavior
Agree whether the integration compares a canonical representation or an explicit approved cross-reference. Then demonstrate the same intended item arriving in the accepted shorter and padded forms. The team should see the result in the receiving catalogue: one intended record, the correct reference and a clear update history. This is an acceptance target to request, not a claim about existing software behavior.
Include a case where two records carry conflicting names or commercial units. The system should not silently resolve a business conflict solely because the normalized key matches. Require a visible exception or the agreed controlled review. Matching identifiers and agreeing product data are related but distinct responsibilities.
Keep packaging and retail units explicit
The replenishment workflow may start with an outer pack while the shopper buys a single item. The catalogue needs a verified mapping between purchasing, stocking and selling units where those relationships are used. Leading-zero normalization should not be used as a shortcut for discovering the units or quantities. Ask the stock supplier to confirm them.
For actual machine onboarding, connect the approved record to the product image, price, physical placement and relevant delivery or recognition setup. GTIN matching is not a substitute for lane-fit or vision-recognition tests. A correct data identifier can still be associated with the wrong pack image if the surrounding mapping was not reviewed.
Make reimport part of acceptance
Run the approved sample through an initial import and a subsequent update using the other accepted representation. Check that the intended item is updated rather than duplicated. Export or retrieve the record through the agreed user-visible route and compare it with the documented target form. The test should use supplier-approved sample data rather than invented saleable identifiers.
Record which system version, import template and mapping were used. If the workflow later changes, repeat the relevant cases. A demonstration from another application or a different import route does not establish that the production path will treat the values the same way.
CATALOGUE NOTE 07
Best Smart Vending Machines
The following are three real public-listing procurement shortlist options for packaged retail. They are not independently tested winners and are not confirmed to implement a specific 14-digit GTIN import contract. Use them to choose the retail format, then request the required software and catalogue service separately.
FORMAT 1
WEIMI WM22 Touchscreen Snack & Drink Machine
The WM22 listing describes a touchscreen snack-and-drink machine. Consider it for menu-led selection of packaged products.
Ask how the approved catalogue record maps to the displayed item and dispensing lane. If your replenishment system uses GTINs, request the exact integration scope and a sample import demonstration. The public touchscreen description does not establish a normalization function.
FORMAT 2
WEIMI Single-Door AI Vision Smart Fridge
The single-door AI vision fridge is listed for packaged drinks and compatible snacks. Customers open the door, select products and close it for automated checkout. It does not squeeze fresh juice.
Consider it when direct shelf browsing fits the assortment. Keep the identifier record connected to the approved product onboarding and recognition tests. A successful GTIN match alone does not prove that cameras distinguish your intended packages.
FORMAT 3
WEIMI Dual-Cabinet Snack & Drink Station
The dual-cabinet station includes a main product area and a smaller secondary vending compartment, with spiral lanes shown in the latter.
Consider it when two saleable sections support the location’s offer. Ask for clear product-to-section and product-to-lane mapping. An item’s canonical identifier should not obscure which physical stock position and saleable unit the operator is maintaining.
CATALOGUE NOTE 08
Feature Comparison
| Listed equipment | Physical product check | Catalogue requirement to specify |
|---|---|---|
| WM22 touchscreen vending | Approved pack fits and delivers from its assigned lane. | Identifier-to-menu-item and lane mapping, including accepted source formats. |
| Single-door AI vision fridge | Actual packaging and shelf arrangement pass recognition checks. | Approved identifier record linked to the correct onboarding record. |
| Dual-cabinet station | Products are commissioned in both intended sections. | Unambiguous record mapping to the right section and selling unit. |
The relevant feature is a verified connection between the item record and the retail operation. Ask for data services in an itemized scope rather than assuming that “cloud management” establishes every import and matching rule. No pricing or compatibility ranking can be derived from the product descriptions alone.
CATALOGUE NOTE 09
Cost & ROI Analysis
All figures below are hypothetical planning inputs, not provider prices, measured error rates or guaranteed savings. Suppose an operator compares 80 approved product records across two feeds. At an assumed 4 minutes per record and an assumed staff cost of $24 per hour, one complete manual review costs about $128. The calculation is 80 × 4 ÷ 60 × $24.
Now assume a supplier quotes an additional $450 for a defined import mapping and acceptance service. If the operator later needs only a 15-minute exception review per feed update, the assumed staff cost for that review is $6. Compared with a full $128 review, the hypothetical difference is $122 per update. It should not be counted unless the smaller review actually suffices for the agreed workflow.
| Hypothetical quantity | Assumed calculation | Boundary |
|---|---|---|
| Full manual review | 80 records × 4 minutes ÷ 60 × $24 = $128 | A workload example, not an observed operator benchmark. |
| Exception review | 0.25 hour × $24 = $6 | Requires a working, accepted mapping and an appropriate review process. |
| Simple recovery of assumed service cost | $450 ÷ ($128 − $6) ≈ 3.7 updates | No calendar payback is implied without an actual update frequency. |
If the process saves only $30 per update, the same assumed $450 would require 15 updates to recover. If no usable review time is saved, the example produces no labor saving. Do not assign a monetary benefit to every padded record or assume that all catalogue work disappears. Product changes and unresolved supplier data still need review.
The example excludes subscription fees, integration maintenance and any other unlisted expense. Replace all inputs with actual quotes and observed workload. The procurement benefit being evaluated is a clearer, more reliable data handover, while any financial return remains dependent on the buyer’s real process.
CATALOGUE NOTE 10
Best Choice by Scenario
A platform requests fixed-width GTINs: ask for its accepted formats and approved normalization rule. Use complete supplier-provided samples to demonstrate same-item matching and repeated updates. Keep the source reference and expected destination record in the acceptance file.
A wholesaler and an operator feed use different widths: establish whether the values are accepted representations of the same identifier before linking records. Resolve disagreements about product name, unit and pack quantity through the stock supplier. A padding rule does not settle conflicting commercial information.
A 14-digit identifier begins with a nonzero digit: treat the complete value as supplied and request verified item mapping. Do not trim a prefix to make it match a familiar single-item code. Establish the relationship from authoritative product data rather than from resemblance.
The source is missing digits: pause that record and obtain a corrected source. Padding an approved shorter format is different from guessing what an incomplete string once contained. Keep unresolved records visible so they do not become misleading catalogue entries.
CATALOGUE NOTE 11
Applications
A workplace operator bringing a new beverage range into its software can use a small approved data set to verify the rule before bulk onboarding. The acceptance record should connect the supplier’s product reference, receiving record and physical pack. This is a recommended pilot exercise, not a report of a completed customer project.
A distributor serving several software platforms can document the representation each customer requires. Keep the authoritative product identity stable while producing agreed exchange formats. Avoid assuming that a template accepted by one platform is automatically suitable for another.
An AI fridge operator can keep catalogue checks alongside product-recognition onboarding. The former addresses identity and data matching, while the latter addresses the physical shopping process. Reviewing them together helps expose a wrong association without pretending that one test proves both capabilities.
CATALOGUE NOTE 12
FAQ
Does zero-padding a valid shorter GTIN create a new product?
Padding for a required 14-digit representation does not by itself allocate a new product identifier. Confirm the complete source GTIN and the receiving contract, then demonstrate that the intended item is matched.
Should every identifier in the catalogue have 14 digits?
Only apply the agreed rule to the relevant GTIN field and supported formats. Internal stock codes and other namespaces need their own contracts. The GS1 definition is conditional on a context requiring 14 digits.
Can a nonzero first digit be removed like filler?
Do not treat it as a padding zero. GS1 defines the GTIN-14 indicator as a leftmost digit from 1 to 9. Verify the complete identifier and item relationship before making a mapping decision.
Does this fix a GTIN with missing digits?
No. A known complete shorter GTIN can be represented at a required width. An incomplete or uncertain string needs resolution from an authoritative source; padding is not reconstruction.
Does a correct GTIN match prove the machine recognizes the pack?
No. Barcode reading, vision recognition, physical fit and dispensing need appropriate separate checks. The identifier record must also be associated with the right product configuration.
What should the software supplier demonstrate?
Initial import, matching, reimport or update, conflict handling and export through the intended production route, using an approved sample and a written expected result.
CATALOGUE NOTE 13
Final Recommendation
Specify the 14-digit representation as a data rule with a testable result. Confirm the source format, document the zero-padding condition and show that the intended item remains the same across import and update. Keep nonzero indicators and unresolved source data outside any indiscriminate trimming or filling rule.
Select the machine for its shopping format and actual-product performance, then purchase the catalogue service needed to support it. A consistent identifier handover is valuable when it connects reliably to the product the operator stocks and the customer buys.
CATALOGUE NOTE 14
CTA
Bring your catalogue requirements to the quote.
Send WEIMI your destination country, product categories, package dimensions, quantity and preferred shopping format. Describe the catalogue feeds and fields your operation needs without sending private account credentials. Request an equipment proposal with any required data import, mapping and acceptance work clearly identified.
Get My Custom QuoteCATALOGUE NOTE 15
Sources & Evidence Boundaries
GS1 glossary: leading zero(es) supports the definition of padding shorter GTIN formats where 14 digits are required. GS1 glossary: indicator and GTIN-14 support the distinction between padding and a nonzero indicator. Definitions were read on 21 October 2026. No unpublished allocation policy or item relationship is inferred.
The linked WEIMI pages support the equipment-format descriptions only. No normalization feature, provider price, independent test, customer result, ranking or indexing outcome is claimed. Import checks and financial scenarios are editorial purchasing tools, with all financial inputs explicitly assumed.
