RECEIVING NOTE 01

Introduction

A supplier case carries a clear batch reference. Inside, the individual drink bottles show only a date. A vending buyer photographs the case, approves the bottles and creates an “expiry” field in the stock system. Before those units reach the machine, a separate purchasing decision is needed: what is the permitted lot-identification indication on the actual sales unit, and is the date being relied on under the relevant rule?

Directive 2011/91/EU concerns indications or marks identifying the lot to which a foodstuff belongs. Its Article 5 permits the separate lot indication to be omitted when a minimum-durability or use-by date appears on the label and consists at least of the uncoded day and month in that order. That is a specific condition. It does not make every date in a supplier spreadsheet, warehouse record or vending dashboard a replacement for a physical lot indication.

This brief focuses on supplier pack approval and receiving acceptance for EU food vending. It complements a wider batch-movement and withdrawal process, but does not reproduce a recall guide. We checked the Directive and the January 2026 consolidated text of Regulation (EC) No 178/2002 on 8 October 2026. Three real WEIMI listings are procurement candidates based on public descriptions, not independently tested equipment.

RECEIVING NOTE 02

Quick Answer

A product barcode identifies a trade item in a typical retail workflow; do not assume it contains the changing production lot or that a machine decodes it. A supplier’s case code, a best-before date, a route refill date and a product code serve different record purposes. Identify them separately before data is imported into the vending catalogue.

The Directive includes specific exclusions, including individual ice-cream portions with the indication on the combined package. This is not a general permission to discard every outer case and sell unmarked loose food. Obtain product-specific assessment, including the destination Member State’s implementation and any more specific rules.

RECEIVING NOTE 03

Comparison Table

Use this as an evidence checklist, not an automatic legal classifier. The responsible food business determines the applicable product route; the buying team verifies that the supplied units and records match the approved specification. General traceability duties remain relevant even where the separate lot mark is not required under a particular condition.

RECEIVING NOTE 04

Who Should Buy This

This guide is useful for operators splitting wholesale cases into individual vending units, importers receiving differently coded market packs, and distributors preparing mixed snack-and-drink replenishment orders. The critical moment is often case opening: the physical unit and the retained case information can become separated before the stock reaches a shelf.

It also helps prepared-meal buyers who receive several batches under the same menu name. A meal title and portion weight may be unchanged while the supplier’s production lot differs. The procurement file should identify the indication on the supplied pack without asking the equipment manufacturer to invent the food producer’s coding system.

A quality or purchasing manager can use the workflow to approve a supplier and specify machine demonstrations. It does not decide whether food is safe, replace a recall procedure or prescribe a universal record-retention period. Those questions require the actual business, product and destination rules.

RECEIVING NOTE 05

How We Evaluate Smart Vending Machines

We separate item recognition from mark handling

An AI fridge identifies compatible retail products for checkout. A dispensing machine maps a selection to a lane. A meal retail machine describes inventory and expiry functions. None of those descriptions alone establishes that a changing lot mark is read, stored or linked to individual sales. We evaluate what a buyer should ask the supplier to demonstrate rather than attribute unlisted functions to a machine.

Real samples, not catalogue illustrations

Submit filled packs with final coding in the actual positions: bottle neck, lid, base, seam or label panel as appropriate to the supplier’s design. Check whether staff can inspect the indication during receiving and refilling without damaging the pack. Test whether the approved equipment handles it while preserving the relevant physical information. Do not treat a beautiful front image as evidence of a readable base code.

Evidence boundaries

The shortlist uses three WEIMI public pages. We have not independently measured dispensing reliability, camera accuracy, mark durability, cooling or lot-reading performance. We do not certify a supplier’s marking route or a machine’s legal compliance. The supplier file, physical trial and software demonstration answer different questions and should each have a named approval owner.

RECEIVING NOTE 06

Key Buying Factors

1. Understand who determines the lot

Article 1 defines a lot as a batch of sales units produced, manufactured or packaged under practically the same conditions. Article 3 assigns determination to the producer, manufacturer or packager, or the first seller established in the Union. Request the responsible operator’s coding explanation and the link between the code and the supplied unit. A vending operator’s route number is not automatically the producer’s lot.

2. Check the “L” condition, not a styling preference

The indication is preceded by “L” except when clearly distinguishable from other label indications. If a supplier omits it, ask for the assessed identification route and examine the actual finished label. Do not add a new arbitrary “L” code in the vending system and assume that this changes the supplier’s physical marking compliance. Any correction to food labels needs an approved responsible-business process.

3. Preserve the date exception exactly

Article 5 refers to the minimum-durability or use-by date appearing on the label, with at least the uncoded day and month in that order. A fictional “15 October” illustrates day/month content; a fictional “October 2027” does not include the day. These examples explain the stated condition, not a complete date-label approval. Other date-marking and product requirements still need review.

Keep the actual date type distinct from an internal stock date. A receiving date, refill date, purchase timestamp or software warning date is not the stated minimum-durability or use-by date merely because it is stored in a field called “expiry”. Record the original printed indication and the supplier’s assessed basis before normalising it for software.

4. Approve the retail unit after case splitting

For prepackaged foods, Article 4 concerns the prepackaging or attached label. Examine the unit that will be offered for sale, not only the shipping case. Where the supplier relies on a specific exclusion, obtain that assessment rather than generalise from a different product. Keep the necessary combined-package information linked to units under the approved process.

5. Treat exclusions as product-specific

Article 2 excludes certain agricultural movements, certain point-of-sale non-prepacked or immediately packed foods, packaging whose largest side is less than 10 cm², and individual ice-cream portions with the lot indication on the combined package. These conditions are not interchangeable. A small-looking wrapper is not proof that its largest side is below the stated area, and the ice-cream provision is not an exemption for every frozen meal.

6. Inspect visibility, legibility and durability

Article 4 requires the indication to be easily visible, clearly legible and indelible. Ask for finished-pack samples and inspect coding after representative receiving and handling. Check condensation, abrasion from the proposed delivery mechanism and over-labels that may cover the mark. A purchasing test should record observations; it does not replace a validated supplier marking process or create a new statutory test method.

7. Retain raw and normalised data

A useful receiving record keeps a photograph or exact transcription of the original mark alongside any normalised field. Avoid deleting leading zeros, changing character case or converting an alphanumeric lot into a date without the supplier’s explanation. If two products use the same text, retain product and supplier identity so that the bare code is not assumed globally unique.

8. Confirm the software boundary

Ask whether the platform stores only SKU-level quantity, an expiry date, a batch field, or multiple batches simultaneously. Request a supported demonstration with two actual marked batches of the same SKU. If the platform cannot represent that distinction, define a suitable supplementary record. Do not claim that cloud inventory, a camera or a weight sensor automatically performs lot tracking.

9. Keep wider traceability separate

Article 18 of Regulation 178/2002 addresses traceability throughout production, processing and distribution, identifying suppliers and other businesses supplied, systems available to competent authorities, and adequate identification with relevant information. The Directive’s marking rule is one part of that picture. The date exception does not erase broader traceability responsibilities or prove that stock can be located across a fleet.

The Directive is addressed to Member States; confirm the applicable national implementation and more specific sector provisions for the actual project. This brief does not set a universal retention interval, tell an operator to identify every final consumer, or provide a complete withdrawal and notification opinion.

RECEIVING NOTE 07

Best Smart Vending Machines

These three WEIMI formats are a public-listing procurement shortlist. “Best” means relevant to investigate for a defined pack-handling task. It is not a test-based ranking or a claim that any model includes complete lot identification and traceability.

Agree destination power, payment support, network compatibility, storage, installation and service scope in the final quotation. Send genuine pack samples, including the code positions that receiving staff must inspect. The equipment supplier can demonstrate handling; the food business supplies and approves the marking evidence.

RECEIVING NOTE 08

Feature Comparison

Ask for a demonstration that begins with receiving two marked samples and ends with the operator finding the relevant record. If a function is not supported, document the complementary manual or external workflow and its responsibility. A limitation can be planned around; an assumed function cannot be verified.

RECEIVING NOTE 09

Cost & ROI Analysis

The following fictional euro example budgets pack-mark acceptance work. It is not a WEIMI equipment quote, coding-system quotation, customer case or sales prediction. Assume 15 SKUs each need 20 minutes of mark/date review at €30 per hour: €150. Assume five suppliers each require 1.5 hours of evidence clarification at €30: €225. Assume ten hours of receiving, software and pack-handling trials at €30: €300. Initial allowance is €675.

Assume recurring receiving checks add four staff hours per month at €30, or €120. If hypothetical monthly contribution after food purchase and existing recurring operating costs is €1,500 before that allowance, capital, finance and tax, the adjusted figure is €1,380. The €675 setup allowance alone would be recovered in approximately 0.49 months at that assumed contribution. This is not total machine payback and does not monetise a regulatory outcome.

For a code-clarification scenario, assume 240 packs at €0.90 each are held and, solely for this illustration, never recovered for sale: €216. Add three staff hours at €30 and an assumed €150 supplier/document review: total €456. An unreadable or disputed mark does not automatically establish that food is unsafe or requires disposal; the responsible process decides the actual outcome.

Use actual receiving workload, supplier responsiveness, pack trials and system quotations to budget the project. Do not assume that a machine feature eliminates food-business responsibilities or that buying a scanner guarantees a usable record. Test the proposed evidence chain before paying for custom integration.

RECEIVING NOTE 10

Best Choice by Scenario

Many batches share one shelf SKU

Investigate the AI fridge if direct browsing suits the approved packs, but require a receiving process that keeps batch distinctions usable. A checkout product name may remain unchanged between lots. Demonstrate whichever stock records are actually offered and keep the original physical code evidence outside product-image recognition if needed.

A stable lane-based refreshment range

Investigate WM22 when tested delivery and a clear refill map suit the project. Use code positions in the pack trial. If a new supplier puts the mark on a seam contacted by the mechanism, retest that handling rather than assume the unchanged bottle volume settles the issue.

Supplier-prepared meals with a defined label

Investigate the meal/microwave format when final trays, required storage and heating instructions are documented. Verify the mark before loading and keep the supplier’s date meaning distinct from a machine warning date. A cooking or heating step cannot reconstruct an identity that was never recorded.

The supplier says “the expiry is the batch”

Ask for the specific marking route. If Article 5 is relied on, inspect the actual date type and uncoded day/month in order on the label. If a separate lot code is used, retain its definition instead. Do not accept a generic statement for every product and destination without the relevant assessment.

RECEIVING NOTE 11

Applications

A supplier pack-approval sheet

Keep supplier and product code; retail-unit description; responsible marking operator; lot-indication position; “L” or distinguishability basis; date type and exact printed format if Article 5 is relied on; any assessed exclusion; outer-case relationship; finished-pack photographs; and the person approving the market pack. This is a suggested procurement record, not an official EU form.

A three-sample date exercise

Use invented training samples to expose assumptions. Sample A has “L00482” plus a month/year minimum-durability date: review the separate lot code. Sample B has a minimum-durability date stated as “15 October 2027”: review the Article 5 route and other applicable requirements. Sample C has only an internal digital warehouse date: that record is not the label date described by Article 5. These examples do not approve real packaging.

A case-opening check

Before discarding an outer case, compare its identification with the individual retail units and the approved supply route. If a specific combined-package provision is relevant, preserve the required connection under the responsible procedure. If units should be individually marked but are not, raise the supplier discrepancy before loading them into a machine. Do not conceal it by adding a case photograph to the sales screen.

A focused equipment acceptance record

Photograph each code before and after the agreed handling trial, record which pack and mechanism were used, and note visibility or abrasion issues. Check the actual stock fields with a supported demonstration. For the wider movement/withdrawal procedure, use the separate food vending batch traceability guide; this article addresses the earlier pack-identification approval.

RECEIVING NOTE 12

FAQ

RECEIVING NOTE 13

Final Recommendation

Specify the permitted physical indication before configuring a digital stock field. Identify the responsible supplier, the exact retail unit and either the separate lot route or the assessed date-based condition. Keep the “L” qualification, unit-mark placement, legibility requirements and specific exclusions intact. Do not substitute an internal refill date or product barcode for evidence about the supplied label.

Choose a retail mechanism after the actual marked pack has been trialled: shelf browsing in an AI fridge, tested lanes in WM22, or a defined meal/microwave workflow. Verify software functions with real examples and document any complementary receiving record. The mark identifies the food lot; the equipment and operator workflow must preserve a usable connection to it.

Sources and boundaries

Directive 2011/91/EU, Articles 1–6 and 9; Regulation (EC) No 178/2002, consolidated 1 January 2026, Article 18. Read on 8 October 2026. Equipment facts come from the three linked public WEIMI pages.

Confirm the destination’s implementation, sector-specific provisions and actual food-business responsibilities. This is not a complete date-labelling, recall, notification or food-safety opinion. No real pack has been certified, no code durability or machine performance has been independently tested, and numerical examples are fictional.

RECEIVING NOTE 14

CTA