GS1 Digital Link:
One QR Code for Everything

What Is GS1 Digital Link?

Every product sold globally carries a GTIN (Global Trade Item Number) — the number encoded in a traditional 1D barcode like EAN-13 or UPC-A. That barcode has served retail checkouts well for fifty years. But it carries only a number. It cannot link to a product page, cannot surface allergen information for a mobile user, and cannot feed into a real-time traceability system without a separate lookup step.

GS1 Digital Link (standardised as ISO/IEC 18975) solves this by encoding GS1 identifiers — including the GTIN — into a standard HTTPS URI and storing that URI inside a QR code. The result is a single physical code that a POS scanner, a smartphone camera, and a supply-chain API can all read — each receiving the data it needs.

For a broader grounding in QR code encoding mechanics, see our pillar guide on QR code technical specifications, which covers version sizing, error correction levels, and data capacity in depth. This article focuses specifically on the GS1 Digital Link layer that sits on top of those fundamentals.

URI Structure & GTIN Encoding

The GS1 Digital Link URI follows a precise structure built around Application Identifiers (AIs) — the same two-to-four-digit numeric prefixes that appear in parentheses on GS1-128 logistics barcodes. In a Digital Link URI, these AIs become path segments of an HTTPS URL.

The primary key is always the GTIN, encoded with AI 01. A minimal Digital Link URI looks like this:

The domain (id.example.com) is the brand's resolver domain, registered with GS1. The path segment /01/ declares that the following value is a 14-digit GTIN. GTINs shorter than 14 digits are zero-padded on the left.

Additional qualifiers append to the primary key path, separated by further AI segments:

In this example: /10/AB1234 is the batch/lot number (AI 10) and /17/260331 is the expiry date in YYMMDD format (AI 17). Serial number (AI 21), country of origin, and dozens of other data attributes can be appended in the same pattern.

The full URI is stored in a standard QR code (typically error correction level M or Q). The QR code itself requires no special encoding mode — it is simply a URL. Any modern smartphone camera can scan it.

Resolver Architecture

The resolver is the server-side infrastructure that receives HTTP requests from scanners and routes them to the appropriate response. When a smartphone camera scans a GS1 Digital Link QR code, it makes an HTTP GET request to the URI inside the code. The resolver inspects the request — specifically the HTTP Accept header and the URI path — and decides where to redirect the user.

A well-implemented resolver supports link type negotiation via the HTTP Link response header. The GS1 Digital Link standard defines a vocabulary of link types, including:

• gs1:pip — Product Information Page (consumer-facing landing page)
• gs1:certificationInfo — sustainability or certification records
• gs1:traceability — batch-level supply-chain data
• gs1:verificationService — anti-counterfeiting and authentication
• gs1:allergenInfo — allergen and nutritional information
• gs1:epcis — EPCIS traceability event data for supply chain systems

Brands can host their own resolver or delegate to a third-party resolver service. GS1 also operates a global resolver at https://id.gs1.org/ that brands can use as a fallback.

One Code, Multiple Uses

The defining promise of GS1 Digital Link is that a single printed QR code can serve completely different purposes depending on who is scanning it and how.

Consider a food product with a GS1 Digital Link QR code printed on its packaging:

• Consumer scan (smartphone camera): The resolver detects a browser user agent and redirects to the product information page — ingredients, allergens, recipes, sustainability story.
• Retail POS scan: The scanner extracts the GTIN from the URI path (AI 01) and processes checkout identically to a legacy EAN-13 barcode. No resolver call required for basic checkout.
• Supply-chain traceability system: An EPCIS-enabled API client sends a request with appropriate Accept headers. The resolver returns batch-level provenance data — farm of origin, processing date, cold-chain events.
• Authentication check: A brand protection platform queries the serial number (AI 21) against a registry and confirms whether the unit is genuine.

This multi-purpose capability directly supports requirements emerging from legislation like the EU Digital Product Passport, which mandates machine-readable product data accessible via a 2D code. GS1 Digital Link is the leading candidate technical implementation for DPP compliance.

For practical guidance on printing GS1 Digital Link codes on retail packaging, see our article on QR codes for product packaging, which covers size, placement, and quiet zone requirements for consumer goods.

Sunrise 2027

Sunrise 2027 is the GS1 industry programme that sets 2027 as the target date by which all point-of-sale scanning systems globally should be capable of reading 2D symbologies — specifically GS1 DataMatrix and GS1 QR codes (Digital Link) — alongside legacy 1D barcodes.

The challenge is enormous: hundreds of thousands of retail checkout lanes worldwide currently rely on laser scanners tuned to 1D barcodes. Upgrading to 2D-capable imagers requires both hardware investment and POS software updates to parse Digital Link URIs and extract GTINs correctly.

GS1 has been coordinating a phased rollout with major retailers, scanner manufacturers, and software vendors. Key milestones include:

• 2023–2025: Pilot programmes with leading grocery retailers in Europe, North America, and Asia-Pacific. Proof-of-concept deployments on fresh produce and pharmaceuticals.
• 2025–2026: POS scanner vendors certifying 2D reading capability as standard. Retailer upgrade programmes accelerating.
• 2027: Target date for industry-wide readiness. After this point, brands can begin replacing legacy 1D barcodes on new packaging runs with GS1 Digital Link QR codes — confident that checkout systems can process them.

Packaging Implementation Checklist

Implementing GS1 Digital Link correctly requires coordination across brand, supply chain, and digital teams. The following checklist summarises the key steps:

1. Obtain a GS1 Company Prefix if you do not already have one. This is the foundation for constructing valid GTINs.
2. Assign GTINs to all products that will carry Digital Link QR codes.
3. Register or configure a resolver domain. This can be your own infrastructure or a third-party GS1 resolver service. Register the domain with GS1 so it appears in the global resolver registry.
4. Define link types and endpoints for each GTIN — product information page URL, traceability endpoint, allergen page, and so on.
5. Generate the Digital Link URIs including any qualifiers (batch, serial, expiry) required for your use case.
6. Encode the URIs into QR codes using error correction level M or Q. Minimum print size is 10×10 mm for packaging; 20×20 mm recommended for reliable consumer scanning at arm's length.
7. Verify with a GS1-certified verifier before committing to a print run. The GS1 Digital Link Verifier tool checks URI syntax, resolver response, and QR code print quality against the standard.

Frequently Asked Questions