What happened

GS1 published its 2D Barcode Playbook for Retail POS Host and Backend Systems in March 2026. Its version archive dates version 1.0.0 to 11 March and version 1.0.1 to 28 May 2026. The update is guidance for retailers, software suppliers and integrators preparing point-of-sale systems.

The playbook refers to an industry ambition that retail checkout systems be able to read and process a defined set of GS1-compliant 2D barcodes by the end of 2027. Adoption varies by market and organization. This is a readiness goal, not an announcement that every checkout can already scan every QR code or that familiar linear barcodes will disappear on a fixed day.

How the retail system works

A capable scanner is only the first step. The POS host must interpret the data and find the product's Global Trade Item Number (GTIN) for price lookup. To use extra fields such as expiry date, batch or serial number, downstream systems must accept and preserve them. GS1 describes changes to data models, parsing and governance as well as possible scanner upgrades.

A GS1 Digital Link QR uses a standardized identifier syntax; a QR that simply contains a restaurant menu or marketing URL does not thereby become a compliant retail product identifier. During migration, products may carry both a linear barcode and a suitable 2D code. The checkout must also avoid treating two scans of one item as two purchases.

What it means for users

For shoppers, a 2D symbol could eventually connect product information with checkout functions, but the benefit depends on the store's systems and the data the brand supplies. For a small business, choosing artwork for a flyer and choosing a code for regulated product packaging are different projects. Ask retail partners which GS1 syntax and verification process they require before printing packaging.

For a campaign, you can make a QR code for a website and test its destination on several phones. If the artwork needs to scale for signage, see when to download QR as PNG or SVG. You can resize a separate campaign image before combining the artwork. These visual tasks do not register a GTIN or implement GS1 point-of-sale data.

Practical checklist

  • Decide whether the code is for a visitor opening a URL or for retail product identification.
  • For POS use, confirm GTIN ownership, GS1 syntax, packaging rules and retailer requirements with the relevant GS1 organization.
  • Test real printed codes with checkout scanners and host software, not only a phone camera.
  • For URL QR artwork, test contrast, quiet space, destination and final print size.

Limitations and what has not changed

The playbook is not a certification of any particular generator or scanner. A phone opening a URL proves only that the QR can be read as a URL; it does not prove that a checkout will parse GTIN and attributes. Convertios' QR tool is for ordinary content and does not claim GS1 retail POS compliance. Existing linear codes continue to coexist during the transition.

Primary sources