GS1 QR Code and Digital Link: A Practical Guide

A packaging file is waiting for approval. The brand team has selected the artwork, the printer is asking for the final symbol, and someone suggests adding a QR code that points to the product page. That decision looks small until the same printed mark must support checkout, consumer information, repair records, resale, and a future Digital Product Passport.

A GS1 QR Code isn't just a visual shortcut to a URL. It connects a physical product identity to operational systems and a governed digital record. If the identifier, resolver, print specification, and ownership model aren't agreed before production, the team can create a symbol that scans today but becomes difficult to trust tomorrow.

• Why a Printed Symbol Becomes a Compliance Decision
• What a GS1 QR Code Actually Is
• The identifier is not the webpage
• QR Code Versus Data Matrix Under Sunrise 2027
• Why legacy symbols still matter
• Carrier Design and Placement on Consumer Packaging
• Choose the panel before final artwork
• Resolving the Symbol to a Versioned Product Record
• Keep the primary identity stable
• ESPR, DPP and the Current Regulatory Landscape
• What a brand should do now
• Wiring the Carrier Into DPP Grid Workflows
• Separate data preparation from publication
• Governance Questions Before You Go to Print

The artwork approval stage is the point where a temporary design choice can become a long-lived operational commitment. Once a GS1 QR Code is printed on packaging, a label, or a product component, it ties together three distinct journeys:

• Retail scanning, where point-of-sale systems need to identify the trade item.
• Consumer access, where a phone should reach relevant product information.
• Lifecycle records, where repair, transfer, resale, or a future DPP may depend on the same identity.

GS1 marked the 50th anniversary of the barcode in 2024, after the first UPC-packaged product, a 10-pack of Wrigley's chewing gum, was scanned at Marsh Supermarket in Troy, Ohio, on 26 June 1974. GS1 also says barcode-based product identification is now scanned more than 10 billion times per day worldwide in its year review. That history matters because the migration to 2D isn't replacing an isolated label. It is changing a widely embedded identification layer.

The immediate planning pressure comes from Sunrise 2027. GS1 and industry partners are working toward broad adoption of standards-powered QR codes by the end of 2027, with the ambition that QR Code and GS1 DataMatrix can be read at retail point of sale around the world, as described in the GS1 historical timeline. Retail readiness is therefore relevant even if your product category isn't yet subject to a DPP requirement.

Practical rule: Treat the carrier, encoded identifier, resolver domain, and product-record owner as one release decision.

Before plates are cut, confirm which GTIN the symbol identifies, whether lot or serial qualifiers are needed, where the resolver is hosted, and who can approve changes to the linked record. Keeping a legacy UPC or EAN during transition may also be sensible where retail partners haven't completed their 2D rollout.

A printed code can remain physically unchanged while its destination evolves. That flexibility is valuable, but only if the team governs the destination instead of allowing catalogue, ERP, ecommerce, and compliance edits to drift apart.

A GS1 QR Code has three layers that teams often collapse into one. The first is the carrier, the QR symbol governed by the structure of ISO/IEC 18004:2015. The second is the GS1 identification data, expressed through Application Identifiers. The third is the Digital Link URI that makes the identifier resolvable on the web.

!An infographic explaining the three components of a GS1 QR code: carrier, identifier, and digital link.

A plain QR code containing ` isn't automatically a GS1 QR Code. A GS1 Digital Link implementation uses a structured URI and GS1 identifiers, such as AI 01 for GTIN, AI 10 for lot or batch, and AI 21 for serial number. The exact data model depends on the use case and the qualifiers encoded, but the important distinction is that the symbol carries a governed product identity rather than an arbitrary campaign URL.

GS1 describes the carrier as dual-purpose. It can support point-of-sale identification and act as a web entry point for smartphones. The same printed code can therefore support checkout without depending on an internet connection while also routing a consumer or service system to product-specific online content, as explained in the GS1 Digital Link quick-start guide.

The GTIN identifies the trade item. The resolver determines which representation to return to a particular user, device, or system. That separation lets a brand update product information without changing the printed symbol, provided the canonical identifier and resolver remain controlled.

A valid implementation also depends on GS1-issued identity. A brand shouldn't invent a company prefix or assign a fictitious GTIN and call the result compliant. GS1 registration, correct Application Identifier use, URI construction, and resolver hosting all belong in the implementation plan. Teams should validate the encoded data with GS1-aware tooling and confirm that their POS and web systems interpret it as intended.

For a practical product-tracking example, see this guide to QR code product tracking. The useful mental model is simple: the QR grid is only the carrier. The identity and the governed record behind it determine whether the implementation can support retail and lifecycle use.

QR Code and Data Matrix can both carry GS1 data and support GS1 Digital Link. The choice isn't a question of one being universally compliant and the other being unsuitable. It is an engineering decision based on who scans the mark, how much physical space exists, and how the product will be printed and handled.

The GS1 guidance on QR codes powered by GS1 identifies QR Code and GS1 DataMatrix as approved open-use carriers for consumer mobile applications. GS1's Digital Link guidance also makes clear that a GS1 QR Code can perform both POS identification and online resolution. That makes QR Code a natural candidate for apparel, packaged consumer goods, and ecommerce-led DPP journeys where consumers are expected to scan the product.

Data Matrix can be the better fit where the mark must occupy a constrained area, survive difficult production conditions, or serve a controlled supply-chain process. Don't select it merely because it appears smaller in a design file. Test the complete workflow, including the actual scanner, print substrate, camera experience, and downstream parser.

Sunrise 2027 is a migration target, not an instruction to erase every UPC or EAN immediately. Retailers are upgrading POS estates at different speeds, and manufacturers need to avoid creating a new symbol that fails at a trading partner's checkout.

A sensible rollout may keep the linear barcode beside the 2D carrier until the retailer confirms operational readiness. That dual-marking approach adds artwork and placement constraints, but it can protect current retail operations while the GS1 QR Code begins supporting richer consumer and lifecycle content.

A technically correct GS1 QR Code can still fail because the printed version is too small, too close to artwork, distorted by packaging, or difficult for a scanner to isolate. GS1 UK specifies an X-dimension range of 0.396 mm to 0.990 mm for consumer-unit packaging when using GS1 Digital Link URI syntax, according to its QR code design guidelines. Treat that range as a production constraint, not a decorative recommendation.

The quiet zone is equally important. A clear margin around the symbol helps scanners distinguish the QR pattern from surrounding text, borders, logos, and price graphics. Use dark modules on a light background, preserve a 1:1 module aspect ratio, and avoid allowing brand styling to damage the symbol's structural contrast.

!An infographic showing five key steps for designing and placing GS1 QR codes on consumer product packaging.

Reserve a flat, stable area rather than placing the code across a seam, fold, curved edge, or closure. Shrink-wrap, condensation on refrigerated goods, metallic films, textured paper, and over-laminates can all change the optical conditions at scan time.

The symbol shouldn't sit where a retailer's price sticker, promotional label, or shelf ticket can cover the quiet zone. On flexible packaging, check how the mark behaves after filling and handling, not only on a flat proof.

Give the artwork and packaging teams a short acceptance checklist:

• X-dimension target: Confirm the production value falls within the applicable GS1 guidance.
• Quiet-zone clearance: Keep the required margin free from text, borders, logos, and stickers.
• Contrast and print quality: Verify dark-on-light reproduction, module sharpness, and absence of bleed.
• Placement zone: Select a flat panel away from folds, seams, high-gloss distortion, and condensation exposure.
• Scan validation: Test the final printed sample with the intended POS equipment and smartphone journeys, including multiple scanner models and lighting conditions.

A verifier should assess the physical mark, while a GS1-aware decoder should assess the data structure. Those are separate checks. A code can look clean and open a webpage while still failing the identification requirements that retail and supply-chain systems expect.

The resolver is the component that turns a printed identity into a usable digital experience. A GS1 Digital Link URI typically combines a controlled domain with a primary key such as a GTIN and may include qualifiers for lot, production date, expiry, or serialisation. In operational terms, the QR Code points to an identity endpoint, not to a permanently hard-coded page copy.

!A diagram illustrating the four steps of resolving a GS1 QR code to a product record.

A scanner captures the URI. The resolver interprets the GTIN and any recognised qualifiers. It then selects the appropriate representation, such as a consumer page, machine-readable JSON, traceability content, or a service workflow. GS1's Digital Link standard overview describes this dual-purpose model, where one carrier can connect POS identification with web content.

Packaging artwork will change. Product copy will be corrected. Supplier evidence will be replaced. A canonical GTIN-based path should remain stable while the back-end record stores versioned attributes and lifecycle events.

That architecture is more durable than printing a campaign URL into every label. It also gives compliance and sustainability teams a place to record who supplied an assertion, what evidence supports it, which version was approved, and when a replacement or correction took effect.

The resolver and the versioned record are therefore the spine of a DPP implementation. The symbol itself doesn't prove a material claim, establish conformity, or preserve repair history. It provides the durable connection that lets authorised systems and consumers reach the record containing those details.

A persistent link is valuable only when the organisation can explain why the content changed, who approved it, and which product state the scan represents.

Many QR projects stop too early. They test whether a phone opens a page, but they don't test whether a recalled batch resolves differently, whether an item transferred to resale retains the correct identity, or whether an inspector can retrieve machine-readable data without receiving the consumer presentation.

The Ecodesign for Sustainable Products Regulation, Regulation (EU) 2024/1781, provides the framework for product-specific ecodesign and Digital Product Passport measures. It doesn't create one general DPP obligation for every product. The European Commission states that DPP requirements are introduced progressively through product-specific delegated acts, rather than through a product-wide obligation applying immediately to all goods, in its DPP frequently asked questions.

The Commission published its first ESPR Working Plan in April 2025, with an indicative schedule for priority product groups and future product-specific rules. An indicative schedule isn't the same as a final category obligation. Teams should distinguish framework law from delegated acts, implementing measures, proposals, and industry preparation.

The Commission says technical preparation includes identifiers and data carriers, access rights, the registry, and the web portal. It also reports that the DPP Registry is live, established under Regulation (EU) 2024/1781, as described in its registry announcement.

Don't print a symbol because a category deadline has been assumed. First establish whether the product is in scope under an applicable act, which data fields are required, who must provide them, and how access should differ between consumers, authorities, recyclers, and repair partners.

At the same time, building a structured, evidence-backed record is a forward-compatible readiness decision. It reduces the risk that the printed carrier survives while the underlying data model remains a collection of unreviewed marketing claims. This ESPR and Digital Product Passport guide is useful for separating regulatory applicability from preparation work.

The operational workflow should begin with the catalogue, not the QR artwork. A brand can start from a spreadsheet or ERP export, map products to GTINs and SKUs, collect supplier documents, and identify which fields need evidence or legal review. Shopify synchronization can mirror catalogue identity for ecommerce teams, while an API can support controlled writes from other systems where the implementation requires it.

DPP Grid provides evidence-backed product records, approval workflows, persistent passport links, and GS1 Digital Link-compatible resolution for supported identifiers. Its documented workflows include manual entry, CSV or XLSX templates, Shopify synchronization, API access, outgoing webhooks on eligible plans, QR carriers, printable PDFs, and browser-resolvable public passports.

!A four-step infographic illustrating the workflow for wiring a carrier into the DPP Grid system.

A practical sequence looks like this:

1. Ingest the catalogue. Bring in product identifiers, variants, materials, suppliers, and existing documentation through a spreadsheet, ERP export, Shopify sync, or API workflow.
2. Structure the record. Map the GTIN and relevant attributes to a persistent product, batch, or item identity.
3. Review the evidence. Attach source documents, record confidence and conflicts, and require human approval before public publication.
4. Activate the carrier. Publish the approved passport and connect the supported GS1 Digital Link-compatible identifier to the public record.

When a material declaration or repair event changes, the team should update the governed record, approve the new version, and preserve the previous publication history. The resolver remains the connection point, while the passport surface can present different information to a consumer, an inspector, a recycler, or a resale operator according to the access model.

DPP Grid stores and structures evidence, routes approval, and surfaces passports. It doesn't issue GS1 company prefixes, certify ESPR conformity, or provide legal advice. The useful handover artefacts are an evidence log, version history, approved publication snapshot, and canonical Digital Link URI that ties downstream copies back to one controlled record. See the Digital Product Passport QR code workflow for the carrier-to-passport relationship.

The difficult question isn't whether the GS1 QR Code opens. It is whether the organisation can keep the destination accurate after the product leaves the artwork queue.

Assign ownership before launch. Someone must be responsible for the linked record after the original packaging team has moved on. That owner may coordinate compliance, sustainability, ecommerce, suppliers, repair operations, and resale partners, but responsibility can't remain implicit.

Ask these questions in the approval meeting:

• Record ownership: Which team controls the canonical product identity and resolver destination?
• Evidence approval: Who approves a material, origin, safety, or recyclability assertion before publication?
• Conflict handling: What happens when the ERP, catalogue, supplier portal, and compliance record disagree?
• Version control: Can the team show what was published previously and why it changed?
• Repair and resale: Does a repaired or transferred item retain its identity, acquire a new state, or require a linked event?
• Access control: What can consumers, authorities, recyclers, repairers, and resale platforms retrieve?
• Recall response: Can the resolver expose the relevant affected product or batch without reprinting every package?

Repairs and resale expose weak governance quickly. A replacement component may alter the product record. A marketplace may copy a GTIN into a listing that doesn't represent the original item. A consumer-facing page may continue showing a broad claim after the underlying evidence has expired. Versioned records, approval states, signed publication manifests, and explicit ownership transfers help prevent those changes from becoming invisible.

Before print: approve the identity, the resolver behaviour, the evidence owner, the change process, and the recovery plan for a compromised or incorrect record.

A platform can support those controls, but it can't decide whether a claim is legally sufficient or whether a product falls within a delegated act. The brand remains accountable for its records, approvals, supplier relationships, and regulatory interpretation.

DPP Grid provides persistent product, batch, and item-level passport links, evidence management, human approval workflows, QR carriers, and supported GS1 Digital Link-compatible resolution. Visit DPP Grid to book a demo and pressure-test your carrier, resolver, evidence trail, and repair or resale workflow before the next packaging run.