WEIMI / DATA DESIGN BEFORE IMPORT
Your shorthand has meaning.
The trade-item key points to data.
Separate the internal code, supplied GTIN and approved handling attributes.
Introduction
An operator’s internal item code may begin with letters used to mean chilled drinks. That shorthand can be useful inside the operator’s own system. A mistake begins when the purchasing team expects the supplied GTIN to contain the same meaning, or asks software to derive storage conditions from selected digits.
GS1’s FAQ describes each identification key as a unique reference to an entity whose master data is held in a database record. For a GTIN-identified trade item, linked information may include brand, name, size, colour, flavour or weight. It says the system is based on non-significance of the numbers. Its separate internal-code FAQ says compatibility depends on how the internal codes were defined; often they must be cross-referenced to the GTIN.
This is a guide to defining the initial catalogue relationship. It is not a pack-replacement cutover or an instruction to encode a new GTIN. The buyer needs a mapping that joins the operator’s vocabulary to the supplier’s trade-item reference without inventing meaning from the identifier.
Quick Answer
Keep internal item code and supplied GTIN as explicitly named fields. Cross-reference them to the approved item record. Store category and handling requirements as separately sourced attributes, rather than deriving them from GTIN digits.
Non-significance does not mean the number has no defined structure. It means the identifier is not the product description or a shortcut for its handling requirements. Do not strip letters from an internal code, append digits or treat a matching suffix as proof of a valid cross-reference.
Sources reviewed 11 October 2026: GS1 — Will my own internal codes fit into the GTIN? and GS1 — Information linked to an identification key. Both FAQs display modification dates of 28 August 2024. Practical mapping checks below are proposed procurement controls, not extra GS1 rules.
Comparison Table
| Data element |
What it represents |
Acceptance question |
| Operator’s internal item code |
Meaning defined by the operator’s own convention |
Where is that convention documented? |
| Supplied GTIN |
Trade-item reference for linked master data |
Which approved item does it reference? |
| Category, flavour or size |
Attributes in the linked item information |
Which source approved the attribute? |
| Storage requirement |
Separately obtained product-handling information |
What supplier instruction supports it? |
| Cabinet position |
Physical placement or dispensing configuration |
How does it point to the approved record? |
A single field called “product code” can conceal which kind of value is expected. Require the vendor to label the input, report and operator procedure so that a user can tell whether it needs an internal code or the trade-item number.
Who Should Buy This
Use this guide when a buyer brings an established warehouse coding convention into a new vending proposal, combines supplier product files, or requests reports using internal category shorthand. It also helps teams evaluating an import form that accepts one ambiguous code field.
A small operator can maintain a controlled cross-reference sheet if the workflow and ownership are clear. A larger fleet may require supported catalogue tools. Neither scale justifies guessing the mapping from similar digits. Identify who approves the relationship, which system maintains it and how a discrepancy reaches that person.
This source does not establish a universal internal-code format or a required software schema. The proposal should state the actual fields and constraints of the supplied configuration before the buyer plans the import.
How We Evaluate Smart Vending Machines
The three machines are a public-list procurement shortlist, not independent tests. Their listings establish retail formats and selected features. They do not establish separate internal-code and GTIN fields, supported cross-reference imports or automatic master-data resolution. Request evidence for the quoted configuration.
Prepare a small accepted item set with clearly distinguished internal codes, supplied GTINs and approved descriptions. Include a product whose internal category shorthand could be misread as a handling instruction. Do not generate sample GTINs or alter real supplier identifiers merely to simplify a test.
Follow one item from the prepared file into the customer offer, operator stock view and sample report. Ask which value is shown at each point. Then submit a vendor-approved mismatch example and observe the supported review process. The goal is to reveal the relationship, not to prove it from a successful physical dispense alone.
Key Buying Factors
Name the namespaces
An operator code and a GTIN can both identify something within their respective systems without being interchangeable. Ask whether the application records both, which is required for each operation and whether reports preserve the distinction. A field that merely accepts characters does not prove that the value has the intended interpretation.
Keep attributes beside the reference
Use product master data for descriptions such as flavour and size. Obtain storage requirements from the relevant product supplier. A code convention used internally to group chilled products can be documented as that convention; it is not a measurement of the goods and should not override actual supplier instructions.
Reject a guessed bridge
Require a reviewed mapping rather than a transformation that takes part of one code to construct the other. Two values sharing a suffix does not establish the same trade item. If the vendor proposes a transformation, ask what authorised allocation or verified source supports the result. Do not call a convenient algorithm a validated identity relationship.
Make the mismatch actionable
Ask how the system handles an internal code paired with the wrong supplied GTIN. The accepted process might require manual review or a controlled import rejection; the exact behaviour remains to be demonstrated. Keep the original file, the explanation and the approved correction together, so a later operator can understand why the mapping was changed.
Best Smart Vending Machines
Shortlist by physical retail format; data mapping remains a configuration-specific question.
01 / PACK RECOGNITION
Single-Door AI Vision Smart Fridge for Packaged Drinks
This listing describes camera-based checkout for packaged drinks and compatible snacks, five shelf levels and five baskets, with a top screen or lightbox. Confirm the cooling option and accepted arrangement for the intended goods. The cabinet does not prepare juice.
Ask how an approved item record connects to the pack information used in recognition. A recognised appearance is not an internal-code-to-GTIN cross-reference. Demonstrate the operator code in the relevant view and the correct approved description, without assuming a supported GTIN import or recognition performance.
Review the AI vision fridge format
02 / NAMED SELECTION
WM22 Snacks and Drinks Vending Machine
WM22 is listed with a 21.5-inch touchscreen, cooling and inventory-related management. Mechanism options include spiral, conveyor, direct push and hanging. Confirm which mechanism is quoted; conflicting generic capacity and energy statements are excluded from this comparison.
Ask which code identifies the menu entry, which identifies the stock record and what value appears in the report. Demonstrate that the selected description and loaded pack agree with the reviewed mapping. A touchscreen catalogue does not prove that separate identifier fields or cross-reference validation are supplied.
Review the WM22 selection format
03 / MULTIPLE STOCK POSITIONS
Two Cabinets, More Choice: Snack & Drink Vending Station
The station listing presents a main display and an additional visible spiral stock area. It is relevant when one accepted trade item may occupy more than one position. Request the actual quoted arrangement and complete product-to-position mapping.
Demonstrate the same approved item record wherever that item is offered, while preserving the distinct cabinet positions. Position numbers should not be mistaken for supplier GTINs. Shared software, independent cooling, another display and particular capacities are unproven from the appearance and require confirmation.
Review the two-cabinet format
Feature Comparison
| Public format |
Cross-reference proof to request |
Attribute inference to avoid |
| Camera-based checkout |
Approved internal record connected to the recognised pack information |
Appearance determines the supplier identifier |
| Touchscreen with mechanism options |
Menu, stock and report values point to the same approved item |
Selection position defines GTIN meaning |
| Main display plus extra stock area |
Approved item mapped to each intended physical position |
A position code is the trade-item number |
If the application uses only one visible identifier, ask where the other relationship is maintained. A separate sheet may be workable, but it adds an operating responsibility. Specify that responsibility and any recurring maintenance effort before accepting the proposal.
Cost & ROI Analysis
Cost the actual mapping activity: collecting supplier files, approving cross-references, entering attributes, demonstrating the import and resolving mismatches. Request any software or vendor configuration fees separately. No such price or supported import feature is established by the public listings.
Hypothetical preparation: 60 items at three minutes of review each require 180 minutes, or three hours. At an assumed $20 per hour, that is $60. Add an assumed $40 for a demonstration session and the illustrative preparation cost becomes $100. This is not a vendor quotation or a measured process.
| Assumed review time for 60 items |
Labour at $20/hour |
Plus assumed $40 demonstration |
| 2 minutes each |
$40 |
$80 total |
| 3 minutes each |
$60 |
$100 total |
| 5 minutes each |
$100 |
$140 total |
If one avoided reconciliation exercise is hypothetically worth $25, four actually avoided exercises would recover the base $100 preparation. There may be none. Do not equate a correct mapping with extra sales, better cooling or lower product waste; those outcomes require their own evidence. Include ongoing review time in the actual ownership comparison.
Best Choice by Scenario
For a browsable packaged-drink range, shortlist the AI fridge and request the link between approved data and pack recognition. For a named customer selection, shortlist WM22 and follow the values through menu, stock and report. The format choice should match the shopping workflow; the cross-reference requirement applies separately.
For an expanded assortment with multiple positions, inspect the two-cabinet station and demonstrate position mapping across both areas. Keep one approved identity relationship for the item while documenting each physical position. If the required data relationship is unsupported, agree a sustainable external process or leave the requirement unresolved.
Applications
A warehouse uses meaningful category prefixes in internal codes. The vending brief can preserve those codes without claiming that GTIN digits encode the same category. A distributor imports supplier records with different naming conventions and records the approved cross-reference instead of normalising the identity by guessing.
A route operator wants reports grouped by its internal categories. That grouping can be defined as an operator attribute while the GTIN remains the trade-item reference. A refill team can then use separately approved handling instructions rather than treating the category shorthand as the product’s temperature requirement.
These are proposed workflows, not actual customer cases. The cited sources define the identity and master-data distinction; they do not establish any specific WEIMI database layout or an automatic attribute feed.
FAQ
Does a GTIN contain the product’s flavour or storage requirement?
The cited GS1 FAQ describes the numbers as non-significant references to linked master data. Do not infer flavour or handling instructions from selected digits. Obtain the relevant attributes from approved product information.
Can my internal code be used directly inside a GTIN?
GS1 says this depends on how the internal codes were defined, and that often the internal item code must be cross-referenced to the GTIN. This guide does not authorise construction or modification of a GTIN.
Does non-significant mean GTINs have no structure?
No. The distinction concerns using the number as a reference rather than treating it as a product description. Do not turn that statement into a claim that identifiers lack defined structures or allocation rules.
Can I match codes by the last few digits?
Shared digits alone are not evidence of the same item. Require a reviewed relationship supported by the supplier’s identity data instead of guessing from a suffix.
Where should storage instructions be kept?
Maintain them as separately sourced product-handling information in the approved operational record. An operator’s category shorthand should not override the relevant supplier instruction.
Do the shortlisted machines validate internal-code mappings automatically?
That capability is not established by the public listings. Request a configuration-specific demonstration and agree where the approved relationship is maintained.
Final Recommendation
Write the initial catalogue specification with separate internal codes, trade-item references, approved attributes and physical positions. Use an explicit cross-reference where the internal convention and supplied GTIN differ. Keep product meaning in the data record and handling instructions in their approved source.
Choose the vending format that demonstrates the intended customer and operator workflow with that relationship intact. A matching suffix, a valid-looking entry and a successful dispense answer different questions. Accept only the mapping and attribute scope supported by the reviewed evidence.
CTA
Send WEIMI your internal-code convention, supplier GTIN list, approved product attributes and intended stock layout. Ask which fields the quoted system supports and request a demonstration linking the prepared data to the customer offer and operator record.
Get My Custom Quote
