What Is GS1 Digital Link?
GS1 Digital Link is a URI syntax standard that transforms conventional product identifiers — GTINs, serial numbers, batch codes — into structured web addresses. A single URL encodes the complete identity of a physical product and, when scanned or resolved, connects any actor in the supply chain to the specific data they are authorised to see. It is, in practical terms, the internet address for physical things.
That short definition carries more weight than it might seem. Every EAN-13 barcode you have ever scanned contains a GTIN — a Global Trade Item Number. GS1 Digital Link takes that GTIN and turns it into a URL that a standard smartphone camera can resolve without a dedicated app. The same URL can route a consumer to a product sustainability page, route a recycler to a material composition report, and route a market surveillance authority to a full conformity declaration — simultaneously, using the same physical data carrier printed on the packaging.
For manufacturers preparing for EU Digital Product Passport obligations, understanding GS1 Digital Link is not optional. The ESPR regulation does not mandate GS1 Digital Link by name, but its technical requirements — a unique product identifier accessible via a machine-readable data carrier, resolving to multiple data endpoints based on actor permissions — map almost exactly onto what GS1 Digital Link was designed to do. If you are working through what a digital product passport actually requires at the implementation level, the data carrier question leads you here quickly.
How GS1 Digital Link Works: The URL Architecture
The standard is formally defined in the GS1 Digital Link specification (currently version 1.1.3, published by GS1 Global Office). The core idea is that GS1 application identifiers — the numeric codes that have structured barcode data since the 1970s — can be expressed as path segments or query parameters in a URI. This makes them readable by standard web infrastructure rather than requiring proprietary barcode readers.
Anatomy of a GS1 Digital Link URL
A conformant GS1 Digital Link URL follows a predictable structure. The canonical form looks like this:
https://id.gs1.org/01/{GTIN}/21/{serial}
Breaking this down:
| URL Component | GS1 Concept | Example | Notes |
|---|---|---|---|
https://id.gs1.org |
Resolver domain | https://id.gs1.org |
GS1-hosted; custom domain (e.g. https://id.example.com) is permitted |
/01/ |
Primary key qualifier — GTIN | /01/ |
Application Identifier 01 = GTIN. Always the first path segment |
{14-digit GTIN} |
Global Trade Item Number | 09521234543213 |
Zero-padded to 14 digits |
/21/ |
Secondary key qualifier — serial number | /21/ |
Application Identifier 21 = serial. Optional for batch-level DPPs |
{serial} |
Unit-level serial number | ABC123 |
Up to 20 alphanumeric characters |
| Query parameters | Additional qualifiers | ?linkType=gs1:sustainabilityInfo |
Used to request a specific link type rather than the default landing page |
A real-world example for a unit-serialised product with a batch qualifier might look like:
https://id.gs1.org/01/09521234543213/10/BATCH001/21/SN987654
Here /10/ is Application Identifier 10, representing the lot or batch number. The resolver processes these path segments in priority order: GTIN first, then serial or batch as secondary qualifiers. Everything after the primary and secondary key path is treated as additional data attributes.
The Resolver: How One URL Serves Multiple Audiences
The resolver is the server-side component that receives an incoming GS1 Digital Link request and decides where to send it. This is where the standard's multi-destination capability comes from, and it is the piece that makes GS1 Digital Link genuinely different from a URL shortener or a static QR code.
The GS1 resolver architecture uses a structured redirect mechanism based on two variables: the link type and the context (language, device type, actor permissions). When a smartphone camera scans a QR code encoding a GS1 Digital Link URL, the operating system sends an HTTP GET request to the resolver with standard headers — Accept-Language, User-Agent — plus any explicit linkType parameter in the query string.
The resolver's response is a JSON-LD document listing all available link types for that product, each pointing to a different destination URL. A consumer scanning in Germany might be routed to a German-language sustainability landing page. A repair technician might request linkType=gs1:instructions and land on a service manual PDF. A recycler might request linkType=gs1:eolInstructions for disassembly guidance. The regulator might query linkType=gs1:verificationService and reach the conformity declaration endpoint.
This is content negotiation applied to physical product identity. The same QR code, printed once at the factory, supports every actor who will ever interact with that product across its entire lifecycle.
| Link Type | Destination | Typical Audience |
|---|---|---|
gs1:productLandingPage |
Consumer product information page | End consumer |
gs1:sustainabilityInfo |
DPP sustainability data viewer | Consumer, ESG auditor |
gs1:instructions |
Repair manual or installation guide | Repair technician, professional installer |
gs1:eolInstructions |
Disassembly and recycling instructions | Recycling facility operator |
gs1:verificationService |
Conformity declaration, certification records | Market surveillance authority, customs |
gs1:safetyInfo |
Hazardous substance declarations | Professional handler, safety officer |
gs1:hasRetailers |
Authorised seller or distributor network | Buyer, procurement |
GS1 Digital Link vs Traditional Barcodes
The barcode landscape has accumulated decades of formats, each designed for a specific context. Understanding where GS1 Digital Link fits requires understanding what preceded it and why those formats fall short for modern DPP requirements.
| Format | Data Capacity | Reader Required | Supports Web Resolution | DPP Suitability |
|---|---|---|---|---|
| EAN-13 / UPC-A | 13 digits (GTIN only) | Laser or imaging scanner | No | Insufficient — no URL, no serial |
| GS1-128 (Code 128) | Multiple AIs, variable length | Imaging scanner | No | Partial — carries serial/batch but no URL |
| GS1 DataMatrix | Up to 2,335 alphanumeric chars | 2D imaging scanner | No (unless GS1 DL encoded) | Good in industrial; needs GS1 DL encoding for web |
| GS1 QR Code (GS1 Digital Link) | Full URL including all AIs | Smartphone camera, standard QR reader | Yes — native URL resolution | Optimal — one code for all actors and data layers |
| NFC / RFID tag | Variable (tag-dependent) | NFC-enabled device | Yes (if URL-encoded) | Good for high-value/industrial; cost prohibitive at scale |
The EAN-13 barcode that has lived on retail packaging since 1976 contains, at best, a 13-digit number. That number identifies a product class — not a unit, not a batch, not an instance. A supermarket scanner knows this is a specific model of shampoo. It does not know which factory produced this bottle, when, from which raw material batch, or what its carbon footprint was. The data simply is not there.
GS1-128 and DataMatrix formats can carry additional application identifiers — batch numbers, serial numbers, expiry dates — but they do not encode a URL. The scanner reads structured data and stops. There is no network call, no resolver, no possibility of linking to external data systems without custom integration work on every reader in the chain.
GS1 Digital Link QR codes carry a full URL. Any smartphone, any standard camera app, reads it and initiates an HTTP request to a resolver. No custom app, no proprietary infrastructure on the scanning side. This is the architectural shift that makes GS1 Digital Link practical for consumer-facing DPP access.
One point worth making explicitly: GS1 Digital Link can also be encoded in DataMatrix format for industrial contexts where QR codes are impractical — high-temperature printing, small label surfaces, legacy scanning equipment in warehouses. The GS1 specification permits both. The choice of visual format (QR vs DataMatrix) is separate from the question of whether the content follows the GS1 Digital Link URI syntax.
GS1 Digital Link and the ESPR Regulation
The ESPR regulation does not cite GS1 Digital Link in its text. What it does specify, in Article 9, is that the data carrier enabling access to a Digital Product Passport must be machine-readable, scannable at point of sale, and capable of being read by common devices without requiring proprietary software. It must link to a data record hosted in a system accessible for the entire useful life of the product plus ten years.
That functional description matches GS1 Digital Link's architecture closely enough that the European Commission's DPP technical working groups have consistently pointed to GS1 Digital Link as the reference implementation. The GS1 EPCIS event data model and the Digital Link resolver architecture were both cited in the Commission's technical documentation for the battery DPP, which is the most detailed implementation guidance currently published.
For the EU battery passport, the regulation requires unit-level serialisation for batteries above 2 kWh. That means every individual battery cell or pack needs its own unique identifier. At that granularity, GS1 Digital Link with the GTIN plus serial number (AI 21) path is the natural fit. The resolver can then route regulators to the full battery state-of-health data while routing consumers to a simplified sustainability summary.
For the textile product passport, where batch-level identifiers may be sufficient, the GTIN plus lot number (AI 10) path serves the same purpose at a coarser granularity. Manufacturers who establish GS1 Digital Link infrastructure for batteries will find that the same resolver and the same URL convention can be reused across product categories with minimal modification.
The critical Article 9 requirement that the data must remain accessible for the product's lifetime is a resolver persistence requirement. If a manufacturer uses id.gs1.org as their resolver domain, GS1 Global manages the uptime obligation. If they use a custom domain, that infrastructure must be maintained — or transitioned to a persistent resolver — for the regulated period. This is not a trivial operational commitment, and it is one reason purpose-built DPP platforms exist.
Implementing GS1 Digital Link: Three Approaches
There is no single correct way to implement GS1 Digital Link. The right approach depends on the volume of products, the complexity of data requirements, and how much infrastructure a manufacturer is willing to own and operate.
GS1-Hosted Resolver via id.gs1.org
GS1 operates a central resolver at https://id.gs1.org. Any GS1 member with a GS1 Company Prefix can register their product GTINs and configure link destinations through the GS1 Resolver Data Entry (RDSE) system. GS1 then manages uptime, SSL, and the resolver logic.
This is the lowest-barrier entry point. For manufacturers already in the GS1 ecosystem, GTIN registration is part of their existing membership. The limitation is flexibility: the GS1-hosted resolver supports the standard GS1 link type taxonomy, but deep customisation of routing logic — complex permission-based data access, integration with proprietary ERP systems — requires workarounds or additional middleware.
Self-Hosted Custom Domain Resolver
The GS1 Digital Link specification explicitly permits custom domain resolvers. A manufacturer can register id.example.com as their resolver domain and build the resolution logic themselves. The URL structure remains conformant with GS1 Digital Link — the path segments follow the AI-based convention — but all routing decisions happen on infrastructure the manufacturer controls.
Custom resolvers are the choice for large manufacturers with sophisticated ERP integration needs, or for cases where the data access control requirements exceed what the GS1-hosted resolver supports. The downside is clear: you own the uptime obligation, the security, and the persistence requirement for the regulated data lifetime.
DPP Platform with Built-In GS1 Digital Link Support
Purpose-built DPP platforms sit between these two options. They handle the resolver infrastructure, manage GTIN registration workflows, generate conformant QR codes, and provide the access-controlled data endpoints that ESPR requires — without the manufacturer needing to build or maintain the underlying systems. This is where DPP-Tool operates. The DPP generation tool generates GS1 Digital Link-conformant URLs for each product, manages the resolver routing, and outputs print-ready QR codes encoded with the correct URL syntax.
For most manufacturers entering DPP compliance for the first time, the platform approach reduces time to compliance significantly. The resolver uptime, the link type configuration, and the API endpoints required for third-party auditor access are all managed as part of the service. If you are comparing options, the DPP software comparison guide covers the key differentiators between platform types.
QR Code Best Practices for GS1 Digital Link
Encoding a GS1 Digital Link URL into a QR code introduces practical constraints that matter more than they might appear to. A QR code that fails to scan at retail, in a warehouse, or at a recycling facility is a compliance failure, not merely an inconvenience.
Error Correction Level
GS1 recommends error correction level Q (25% damage recovery) for QR codes on consumer packaging. Level M (15%) is acceptable for clean industrial environments. Avoid level H unless the QR code is large — it significantly increases symbol size, which creates problems on small labels. Never use level L (7%) for DPP data carriers; the code is too fragile for real-world conditions.
Minimum Size
The GS1 standard specifies a minimum module size of 0.38mm for QR codes at standard printing resolution. In practice, for consumer packaging, a QR code below 15mm × 15mm becomes unreliable with typical smartphone cameras at the scanning distances consumers actually use. Industrial DataMatrix symbols can be smaller, but the same principle applies: test at the low end of your target scanning distance before approving print artwork.
Quiet Zone
The quiet zone — the white border surrounding the QR code — must be at least four modules wide on all sides. This is not a suggestion. QR decoders use the quiet zone to locate and frame the symbol. Violating the quiet zone causes scanner failures. Printing QR codes to the edge of a label, without respecting the quiet zone, is one of the most common causes of scan failure in the field.
URL Length Management
Longer URLs produce denser QR codes, which require better optics to scan reliably. A GS1 Digital Link URL with a GTIN plus serial number will typically be 40–70 characters, well within QR capacity at reasonable sizes. Where URLs extend significantly beyond 100 characters due to multiple qualifier layers, consider whether all qualifiers need to be in the primary URL or whether some can be managed at the resolver level.
Placement
ESPR compliance requires the data carrier to be "easily accessible" and "scannable at point of sale." Place QR codes on flat surfaces where possible — curved surfaces introduce scanning angle problems. Avoid placing QR codes across fold lines, seams, or areas subject to abrasion or moisture. For products where packaging is removed at point of sale (accessories, components), the data carrier must also be present on the product itself.
Sunrise 2027 and the Retail Adoption Timeline
Retailers have operated with 1D barcodes — EAN-13, UPC — as their primary point-of-sale scanning format for close to fifty years. Retail checkout systems, POS software, loyalty platforms, and inventory management tools were all built around that format. Transitioning to GS1 Digital Link QR codes at scale requires coordinating changes across hundreds of thousands of retail endpoints simultaneously.
GS1 launched the Sunrise 2027 initiative precisely to manage this transition. The commitment, backed by major global retailers, is that point-of-sale scanning infrastructure will be capable of reading GS1 Digital Link QR codes as of January 1, 2027. This does not mean EAN-13 barcodes will disappear overnight — GS1 has been clear that the transition is additive, not replacement. Products will carry both a traditional barcode and a GS1 Digital Link QR code during the transition period.
For DPP compliance purposes, Sunrise 2027 matters because it coincides almost exactly with the battery DPP deadline of February 18, 2027. Manufacturers who need compliant data carriers on battery products for the EU market will be deploying GS1 Digital Link QR codes at the same time that retail scanning infrastructure reaches GS1 Digital Link readiness. This is not a coincidence — the timelines were coordinated.
Beyond retail, GS1 Digital Link integration into IoT infrastructure is progressing. Smart shelf sensors, automated warehouse scanners, and track-and-trace platforms are incorporating resolver client functionality. A product's GS1 Digital Link URL becomes a persistent identifier that can be logged at every point of movement through the supply chain, building the chain-of-custody record that ESPR's traceability requirements envision.
How DPP-Tool Implements GS1 Digital Link
When you use DPP-Tool to generate a Digital Product Passport, GS1 Digital Link is the identifier architecture underlying every passport record. The process works as follows.
During product setup, you provide your GS1 Company Prefix and the base GTIN for each product model. DPP-Tool constructs the canonical GS1 Digital Link URL using those inputs, applying the correct zero-padding and AI path segment conventions. If your products require unit-level serialisation — as battery DPPs do — the platform generates conformant URLs incorporating the serial number qualifier at AI 21.
The resolver is managed within the DPP-Tool infrastructure. When a product's QR code is scanned, the request reaches the DPP-Tool resolver, which performs content negotiation based on the link type parameter and the requesting actor's permissions. Consumer-facing requests receive the public sustainability data view. Third-party auditor requests, authenticated via API key, reach the full data record including supply chain documentation. Market surveillance authority queries resolve to the conformity declaration endpoint.
Print-ready QR code assets — in SVG, PNG, and PDF formats at print-ready resolution — are generated automatically for each product. The QR codes comply with GS1's error correction and quiet zone specifications. Label dimensions can be specified to ensure that the generated symbols meet minimum size requirements for your specific packaging format.
For teams working through the implementation process, the how to create a DPP guide walks through the end-to-end steps, including how GS1 identifier registration interacts with DPP-Tool's product setup workflow. The DPP requirements checklist maps each ESPR data field to the corresponding section of a DPP-Tool passport, so compliance teams can verify coverage before the first passport is published. Pricing for different production volumes and product categories is covered in the DPP plans overview.
Frequently Asked Questions About GS1 Digital Link
What is GS1 Digital Link?
GS1 Digital Link is a URI standard that converts product identifiers — primarily GTINs — into structured web addresses. A compliant URL encodes the product's identity (GTIN, serial number, batch code) as path segments following GS1 Application Identifier conventions, and resolves via a server-side resolver to multiple destination URLs depending on who is scanning and what data they are requesting.
How does GS1 Digital Link work?
When a QR code encoding a GS1 Digital Link URL is scanned, the device sends an HTTP request to the resolver domain specified in the URL. The resolver reads the GTIN and any qualifier path segments, performs content negotiation using the request headers and any explicit link type parameter, and responds with a redirect to the appropriate destination — a consumer landing page, a repair manual, a conformity declaration, or a recycling instructions page. The specification is managed by GS1 Global Office and the current version is 1.1.3.
What is the difference between GS1 Digital Link and a traditional barcode?
Traditional barcodes — EAN-13, UPC, GS1-128, DataMatrix — store structured numeric or alphanumeric data that a scanner reads and passes to a local application. They contain no URL and initiate no network request. GS1 Digital Link encodes a full web address as the barcode content. Scanning the code triggers an HTTP request to a resolver, which routes the device to live, updatable data stored in a backend system. The key practical difference is that the data behind a GS1 Digital Link URL can be changed without reprinting the product label, whereas the data in a traditional barcode is fixed at print time.
Is GS1 Digital Link required for EU Digital Product Passports?
The ESPR regulation (EU 2024/1781) does not mandate GS1 Digital Link by name. Article 9 requires a unique product identifier accessible via a machine-readable data carrier, scannable by standard devices, linking to a persistent data record. GS1 Digital Link satisfies all these requirements and is the reference implementation cited in the European Commission's technical working group documentation for the battery DPP. In practice, it is the dominant implementation approach for EU DPP compliance, though technically conformant alternatives exist.
How do I implement GS1 Digital Link for my products?
There are three main approaches. First, GS1-hosted resolver: register your products with GS1 and configure link destinations in the GS1 Resolver Data Entry system using your existing GS1 Company Prefix. Second, self-hosted resolver: build a custom resolver on your own domain following the GS1 Digital Link specification, with full control over routing logic and data integration. Third, a purpose-built DPP platform such as DPP-Tool: the platform manages identifier generation, resolver configuration, and print-ready QR code output, handling the infrastructure complexity so you can focus on populating the required data fields.
What is Sunrise 2027 and how does it relate to GS1 Digital Link?
Sunrise 2027 is a GS1-led industry initiative committing major global retailers to update their point-of-sale scanning infrastructure to read GS1 Digital Link QR codes by January 1, 2027. Currently, most retail checkout systems are optimised for 1D EAN-13 and UPC barcodes. Sunrise 2027 enables a transition period where products carry both traditional barcodes and GS1 Digital Link QR codes, with retail scanners gradually becoming capable of processing both. The 2027 date aligns with the EU battery DPP mandatory compliance date of February 18, 2027, creating a coordinated window for manufacturers to deploy GS1 Digital Link across both DPP and retail supply chain use cases simultaneously.
Can GS1 Digital Link be encoded in formats other than QR codes?
Yes. The GS1 Digital Link specification defines the URI syntax independently of the physical data carrier. The URL can be encoded in a QR Code (most common for consumer-facing applications), a GS1 DataMatrix symbol (used in industrial and pharmaceutical contexts), an NFC tag (for high-value products or interactive in-store experiences), or any other carrier capable of storing a URL string. The choice of carrier depends on the scanning environment, label size constraints, and the target reader devices. For EU DPP compliance at point of sale, QR codes are the practical default because they are readable by standard smartphone cameras without additional hardware.