CartVisualCreate account

When Does a Retail 2D Barcode Need Human-Readable GTIN Text?

Do not remove GTIN text just because a package has a QR code. GS1 General Specifications release 26.0 distinguishes a sole retail 2D barcode, adjacent linear and 2D symbols, non-adjacent symbols and consumer-engagement codes. Confirm the symbol type and arrangement before choosing the text. UPC-E has a specific exception, so it must not be treated like an adjacent UPC-A or EAN-13.

Published · By CartVisual editorial team

Start with the saleable unit and barcode purpose

A packaging designer sees two codes and wants to remove the digits beneath one of them to make room for a promotional claim. That decision needs a barcode inventory before an artwork edit. Identify the saleable unit, authoritative GTIN, each symbol's encoded data, and whether it serves checkout or consumer engagement. A phone opening a website does not answer which readable identifier belongs on the pack.

Human-readable interpretation, HRI, represents encoded data. Marketing instructions such as “Scan for recipes” are a different kind of text. Retrieve the identifier from the product record rather than recreating it from the AI mockup; see why a generated pack is not a GTIN source.

Use the current retail text rules

The GS1 General Specifications, release 26.0, section 4.14.2 on pages 308–310, distinguishes these cases:

ArrangementText decision to verify
2D symbol is the only barcode for the GTINDisplay the 14-digit GTIN HRI. The specified retail 2D formats use (01) before the GTIN.
EAN-8, EAN-13 or UPC-A is adjacent to the 2D symbolGTIN HRI is required only for the linear symbol.
Linear and 2D symbols cannot be adjacentThe GTIN should accompany both; this is a recommendation, not identical wording to a mandatory requirement.
UPC-E is adjacent to a 2D symbolGTIN HRI is required and should accompany both. Do not apply the UPC-A shortcut.
Additional consumer-engagement Digital Link codeIts HRI is at the brand owner's discretion; retain the separate POS barcode's applicable text.

Confirm the actual symbol and syntax with the barcode owner. This table does not determine every application requirement or partner acceptance condition. The earlier retail implementation guideline points to section 4.15; the release 26.0 standard places the relevant retail text rules in section 4.14.2. Follow the named rule in the actual edition, rather than copying an old section number.

A fictional artwork change that needs a second review

Tea-box layout A has an EAN-13 beside a Digital Link QR and retains the approved EAN digits. Layout B moves the QR to a different panel to make room for an illustration. The designer copies layout A's text treatment unchanged. The reviewer returns B for a new arrangement check: moving the symbol changed a condition used for A's approval.

The review record identifies the exact layout revision and asks the barcode specialist to document the applicable text decision. A later draft using UPC-E is reviewed separately. Nobody invents digits, assumes every linear symbol behaves identically, or approves the new layout because an earlier concept looked attractive. These are fictional desk-review scenarios; no physical code was produced or scanned.

Close the handoff with evidence

Retain the encoded identifier, symbol type, intended use, adjacency, text treatment, standard edition and responsible approver with the final artwork. Keep readable text outside the symbol's quiet zone. Continue with the barcode space and physical-proof workflow to check the real printed pack. A concept review settles the planned layout; production approval still needs the actual supplier and retail requirements.

Sources

Scope and evidence

Prepared by CartVisual with AI assistance and checked against the listed sources. The official release26 PDF was retrieved and relevant pages303–310 read, with pages308–309 rendered and visually inspected. This is an editorial explanation of the named retail HRI rules, not a complete standards audit or certification of a real package. No print or scanner test was performed.

Related decisions

Explore the packaging mockup generator workflow