A traditional retail barcode commonly identifies the product type: this is a particular GTIN, in this pack configuration. That remains useful, but it does not distinguish one production batch from another or one expiry date from another.

A 2D barcode expiry date lot number QR code workflow changes the level of detail available at the point of scan. A GS1-conformant QR Code or GS1 DataMatrix can carry a product identifier plus structured attributes such as a batch/lot number, expiration date, best-before date, or serial number. That means a single symbol can identify both *what the item is* and, where the operating systems can use it, *which specific production group or individual item it is*.

This matters to food brands, retailers, manufacturers, inventory teams, and packaging engineers because expiry and lot data support operational decisions that a GTIN alone cannot: targeted recall handling, stock rotation, receiving checks, warehouse holds, and product-level investigation.

GS1’s retail 2D guidance describes 2D barcodes as able to encode a GTIN with additional data including expiration dates, batch/lot numbers, and serial numbers. It also describes how GS1 Digital Link can connect a product identity to online information. See the GS1 2D barcodes in retail guideline for the implementation context.

The important distinction is this: a printed 2D symbol is not automatically an end-to-end traceability program. The value comes from a planned combination of the right GS1 data, correct printing, scanner configuration, and software workflows that can interpret and act on the data.

What can be encoded in a GS1-conformant 2D symbol?

GS1 Application Identifiers, often shortened to AIs, label the meaning and format of data elements in a GS1 barcode. They allow a scanner or connected application to distinguish a GTIN from a date, a lot number, or a serial number.

For expiry, lot, and recall workflows, the core data elements are often:

• GTIN (AI 01): Identifies the trade item and its packaging level.
• Batch or lot number (AI 10): Identifies a production batch or lot. It is variable length.
• Expiration date (AI 17): Records an expiry date in the GS1 date format of YYMMDD.
• Best-before date (AI 15): Can be used when best-before rather than expiration is the appropriate business date.
• Serial number (AI 21): Distinguishes an individual item from others carrying the same GTIN.

A hypothetical chilled product could use a data string conceptually represented as:

(01)09506000134352(17)270630(10)BATCH-7K29

In this example:

• 01 introduces the GTIN.
• 17 introduces an expiration date of June 30, 2027.
• 10 introduces the lot value BATCH-7K29.

The parentheses are shown here only to make the example readable. They are not necessarily the literal characters encoded into a scanner-ready data carrier. Your barcode generation and integration process must follow the relevant GS1 encoding rules, including how variable-length elements are delimited when another data element follows.

A serialized pharmaceutical device, durable item, or high-value component might add AI 21. A consumer-packaged food item may need only GTIN, date, and lot. More data is not inherently better: every added element must have a defined operational purpose and must fit the permitted data-carrier and packaging design constraints.

QR Code and GS1 DataMatrix: choose for the workflow, not visual preference

Both QR Code and Data Matrix can serve 2D barcode use cases, but they are not interchangeable in every environment.

QR Codes

QR Codes are familiar to consumers because phone cameras typically recognize them. In a GS1 context, a QR Code can support product identification and web resolution patterns, including GS1 Digital Link. This makes it useful when one printed mark needs to serve a consumer-facing scan journey as well as compatible business scanning workflows.

GS1 DataMatrix

GS1 DataMatrix is widely associated with compact, data-dense identification, especially where the code needs to fit a small label or component. Its physical size and marking requirements can make it attractive for technical, healthcare, or constrained-space applications.

The decision to make early

Do not select a symbology based solely on whether a phone camera can scan it. Define these questions first:

• Will the symbol be scanned at a retail POS, a warehouse receiving station, a production line, by a consumer phone, or all of the above?
• Which scanners, scales, POS software, warehouse management systems, and ERP integrations must receive the data?
• Does the destination need to vary by lot, market, or product status?
• How much package space, print resolution, contrast, and damage tolerance are available?
• Is the immediate goal product identification, process control, consumer information, or a combination?

GS1’s guidance positions the retail migration around 2D barcode capability and supports a gradual transition rather than a claim that all systems instantly become 2D-ready. GS1 describes 2027 as a target for retail POS systems to be capable of reading 2D barcodes, not a universal deadline that makes every legacy device or software stack ready overnight. Read GS1’s explanation of the 2027 transition goal before treating it as an implementation guarantee.

Why lot and expiry data improves recall precision

A recall is rarely an instruction to remove every unit of a product from every location. Often, the relevant scope is a particular lot, production run, facility, time period, or date range. A GTIN-only scan establishes the product type, but it does not by itself establish whether a scanned unit belongs to the affected lot.

When the lot number is encoded with the GTIN, a compatible operational scan can capture the detail needed to match an item against a recall scope. When expiration or best-before information is also encoded, teams can add another practical verification point.

Consider a hypothetical soup brand with one GTIN used across several production runs. A quality investigation identifies lot L2408C as affected. With the lot printed only in human-readable text, store teams may have to inspect packs manually, read tiny characters, and decide whether each unit matches. With machine-readable lot information in a correctly implemented 2D code, compatible tools can compare scan data to the affected-lot list.

That does not eliminate recall governance. Teams still need documented procedures for quarantine, inventory status changes, supplier and retailer communication, evidence retention, and regulatory obligations. But it can reduce ambiguity at the moment an item is received, picked, counted, or checked on shelf.

A practical recall data design

For many lot-based food recall scenarios, the on-pack symbol should contain:

• The GTIN needed to identify the trade item.
• The batch or lot identifier used in the manufacturer’s quality and recall records.
• The relevant date element when it helps staff confirm product scope or manage stock.

The backend should hold or resolve:

• Recall status and scope.
• The reason for the action and approved communications.
• Market-specific consumer instructions.
• Lists of affected locations, shipments, or customers when permitted and appropriate.
• Internal investigation records and other sensitive operational detail.

This separation keeps the symbol focused on durable, machine-readable item facts while letting teams update recall messaging and workflows without changing data on packaging already in circulation.

Expiry management and stock rotation: where data becomes actionable

Expiry dates are useful only when staff and systems can see them in time to act. A 2D code does not physically rotate inventory; it makes date data available for a process that can.

Receiving checks

At receiving, a compatible scan can capture the product GTIN, lot, and date rather than requiring manual entry. The receiving system can compare the data against purchase orders, minimum remaining shelf-life rules, or supplier quality policies configured by the business.

For example, a distributor may accept a yogurt shipment only when its remaining shelf life meets its agreed receiving policy. The policy is the business’s own rule; the 2D barcode supplies a structured date value that an integrated system can evaluate.

Warehouse allocation

Warehouse systems commonly need a way to distinguish inventory that shares a GTIN but differs by lot or expiry. A scan at put-away, replenishment, or picking can support allocation logic when the WMS is designed to store and use those fields. This can support FEFO, or first-expired, first-out, where appropriate for the operation.

Store-level rotation and markdown workflows

In retail, date-bearing 2D codes can help store applications identify units nearing a threshold defined by the retailer. That can inform shelf rotation, disposition review, or markdown processes. The outcome depends on retailer policy, POS capability, pricing controls, and local legal requirements. Encoding an expiry date does not itself authorize a discount, block a sale, or determine food safety.

Production and quality holds

Manufacturers can use item-level or lot-level scanning to associate units with quality statuses. If a lot is placed on hold, the operational system must be the source of truth for whether that lot can ship or be consumed. The barcode provides the identifier used to find the relevant record; it should not be treated as a substitute for controlled quality systems.

What belongs in the barcode versus on the web?

This is the central design choice for a 2D barcode program. Put stable, scan-critical identifiers into the symbol. Put information that may change, vary by audience, or require access controls behind a web destination or enterprise system.

Good candidates for encoding in the symbol

Encode data that equipment needs immediately and consistently to identify or process the physical item:

• GTIN.
• Lot/batch number.
• Expiration date or best-before date, when operationally required.
• Serial number for an item that must be individually identified.
• Other approved GS1 data elements that have a defined business use and are supported by the intended workflow.

These values should correspond exactly to information managed by production, quality, and inventory records. A mismatch between human-readable lot text, encoded lot data, and backend lot records can create a costly exception during a recall or shipment dispute.

Better candidates for web resolution

Use a GS1 Digital Link or another controlled online destination for information that needs to stay current or differs by user:

• Product ingredients, allergens, nutrition, and usage information where applicable.
• Consumer-facing recycling or disposal guidance.
• Language or market-specific content.
• Updated recall notices and approved consumer instructions.
• Product support, certificates, manuals, or authenticity guidance.
• Campaign content that the brand may revise after packaging is printed.

GS1 Digital Link is designed to connect GS1 identifiers to online information while preserving a standards-based product identity. The GS1 retail 2D guideline explains this relationship in the context of 2D barcodes in retail.

Do not expose sensitive operational data by default

Consumer-accessible packaging is public. Avoid treating a consumer QR Code as a private data channel.

Do not place credentials, internal system URLs, unreleased formulation details, personal information, supplier contract information, or non-public logistics data directly in a public symbol. Even if the payload is encoded rather than printed as text, it can be read and copied.

For a restricted internal workflow, use authenticated systems and role-based access controls. The code can identify the item or route an authorized user to a secure service, but the security should come from the application and identity controls, not from obscurity in the QR Code payload.

Scanner and software readiness: the overlooked part of the project

A 2D code that scans successfully on a phone may still fail to deliver usable structured data to a POS, handheld scanner, WMS, ERP, or recall application. The physical symbol, device decoder, device configuration, middleware, and receiving application must work together.

Before releasing artwork, run a readiness review.

Confirm the physical scanning environment

Test the actual scanners and camera systems used in stores, warehouses, factories, and field locations. Verify scan distance, lighting, curved packs, reflective materials, thermal printing, label placement, and expected code damage. Use production-representative packaging rather than relying only on a clean image on a screen.

Confirm how data is parsed

Ask what the scan transmits to the receiving application. A scanner may decode the symbol but send the data in a format the application does not parse into GTIN, date, and lot fields. Confirm that variable-length fields, separators, and GS1 data formatting are handled correctly by every relevant layer.

Confirm POS behavior separately

Retail POS is its own workflow. Determine whether each retailer’s estate can read the selected 2D carrier, identify the GTIN, and process any additional data in the intended way. A retailer may be able to identify the product while not yet using lot and date data for every downstream function. Do not assume a 2D scan automatically enables recall blocks, markdowns, or inventory updates.

Test exception paths

Plan for unreadable symbols, missing lot assignments, invalid dates, recalled inventory, and system outages. Staff need clear instructions for what to do when scan data is incomplete or does not match the human-readable label.

Packaging engineering rules for usable data carriers

The most complete GS1 payload is not useful if the code is difficult to scan after printing, shipping, or refrigeration.

Build barcode quality into the packaging process:

• Keep a clear quiet zone around the symbol.
• Maintain high contrast between dark modules and a light background.
• Avoid placing the code across folds, seams, heavy curves, glare-prone varnish, or areas likely to scuff.
• Size the symbol for the chosen data payload and real scan conditions; do not compress it to fit an arbitrary design box.
• Keep human-readable lot and date text where operations, regulation, or customers require it.
• Validate final printed samples, including variable data applied by the actual printer or line equipment.
• Establish artwork and data-change controls so the encoded fields, printed text, and master data stay aligned.

For variable lot and date printing, define which system owns each value, when it is generated, how it is verified, and who approves exceptions. This is as important as selecting QR Code versus Data Matrix.

A phased implementation plan for food and retail teams

A practical rollout starts with a narrow, measurable workflow instead of attempting an enterprise-wide transformation in one packaging cycle.

1. Pick one operational problem

Choose a product family and a specific issue, such as receiving shelf-life checks, warehouse lot capture, store expiry review, or faster identification of recalled lots. Write the current process step by step, including manual lookups and exception handling.

2. Define the minimum data set

For a typical lot-managed food product, this may be GTIN plus lot plus expiration or best-before date. Add serialisation only when individual-item identification delivers value. Avoid adding data simply because the carrier has capacity.

3. Map data ownership

Identify the source for GTIN, lot, dates, status, and consumer content. Production systems may generate the lot; quality systems may assign a hold; a product-information platform may own consumer copy. Decide which system is authoritative for each field.

4. Choose the carrier and scan journey

Specify the selected GS1 data carrier, intended scan points, data output requirements, and, if relevant, GS1 Digital Link routing. Include both operational scans and consumer scans in the design review, but do not force sensitive operations into the consumer journey.

5. Pilot with real equipment and packaging

Print production-representative samples. Test every intended scanner, POS configuration, mobile device, and application integration. Test each lot/date combination and deliberately test malformed or unreadable cases.

6. Train around decisions, not scanning alone

Staff should know what a successful scan means and what action follows it. For example: quarantine this lot, reject this receipt, rotate this stock, or open this consumer information page. A scan without a defined decision path creates another manual check rather than an operational improvement.

7. Measure process quality

Track practical implementation measures such as scan exceptions, mismatches between encoded and printed data, manual overrides, and time spent resolving lot/date questions. Use those findings to refine data rules, print controls, and system integrations before expanding.

Where QR Rapid fits—and where specialist systems remain essential

QR Rapid can help brand and packaging teams create polished QR Codes for consumer-facing product information, support resources, recall-information landing pages, and controlled campaign destinations. A dynamic website URL QR code is useful when the destination needs to change after packaging is printed, such as when a product support page moves or approved public recall guidance must be updated.

For a GS1 Digital Link-based consumer journey, coordinate the URI structure, identifier governance, and resolver approach with your GS1, packaging, IT, and retail partners. Do not assume that a general-purpose URL QR Code alone creates a GS1-conformant operational barcode or that it will feed lot and expiry data into enterprise systems.

Likewise, QR Rapid is not a replacement for an ERP, WMS, manufacturing execution system, quality-management system, retailer POS integration, or recall-management process. Those systems govern the inventory and status decisions. QR Rapid is most valuable for making the public-facing scan experience clear, branded, manageable, and adaptable alongside the operational barcode architecture.

If your team is planning a package refresh, use QR Rapid to prototype the consumer destination and scan experience while your technical stakeholders validate the GS1 payload, 2D carrier, print quality, and scanner integration requirements.

The operational opportunity behind the 2027 shift

The 2027 retail transition target is best understood as an opportunity to prepare for richer product identification at scan time, not as a promise that every business will instantly operate on lot and expiry data. The brands that gain the most will make deliberate choices now: encode data that supports real decisions, preserve a clean consumer experience, and test every system that touches the symbol.

A well-designed 2D barcode expiry date lot number QR code strategy can give teams a more precise way to identify product units and lots. Combined with ready scanners, reliable master data, and clear operating procedures, it can support tighter recall scope, better stock handling, and more useful consumer information without turning packaging into a container for sensitive internal data.

Start with one product line, one scan workflow, and one source of truth for lot and date data. Then expand only after the physical code and the operational response have both been proven.

FAQ

Can a QR Code contain both an expiry date and a lot number?

Yes. A GS1-conformant QR Code can encode a GTIN together with GS1 Application Identifiers for data such as an expiration date and batch/lot number. The scanner and connected software must be configured to interpret and use those fields.

What is the difference between an expiry date and a best-before date in GS1 barcode data?

They use different GS1 Application Identifiers. AI 17 is used for an expiration date, while AI 15 is used for a best-before date. Select the data element that matches the business and labeling requirement for the product.

Can a 2D barcode stop a recalled product from being sold?

Not by itself. The barcode can provide the GTIN, lot, and date data needed to identify an affected item. A POS or inventory system must be capable of comparing that data with recall rules and triggering the appropriate action.

Should a consumer-facing QR Code include internal recall and supply-chain data?

Usually no. Public packaging codes can be copied and decoded. Put stable identifiers needed at scan time in the symbol, but keep sensitive operational records behind authenticated business systems and publish only approved consumer information.

Do all retail scanners support GS1 QR Codes and Data Matrix today?

Readiness varies by retailer, device, configuration, and software integration. GS1's 2027 goal is for retail POS to be capable of reading 2D barcodes, but brands should test the exact retailer and operational environments relevant to their products.

Does QR Rapid generate a complete GS1 traceability system?

QR Rapid can help create and manage consumer-facing QR Code destinations, including updateable product information or recall communication pages. A complete GS1 traceability workflow also requires validated barcode data, production controls, scanners, and integrated inventory, quality, and recall systems.