Introduction: Connecting Physical Products to Digital Information
For decades, barcodes have been the backbone of product identification and retail commerce. The familiar lines of a UPC or EAN barcode encode a number, typically a GTIN (Global Trade Item Number), that identifies a product at the point of sale. But in a world where products need to carry rich digital information for consumers, regulators, repair technicians, and recyclers, a simple numeric identifier is no longer sufficient.
Enter GS1 Digital Link, a standard that bridges the gap between the physical world of products and the digital world of the web. GS1 Digital Link transforms product identifiers into web addresses (URIs), enabling a single scan of a QR code to connect users to a wealth of product information online. It is the key technology that makes Digital Product Passports practical and scalable.
GS1 Digital Link at a Glance
| Aspect | Detail |
|---|---|
| Standard owner | GS1 Global |
| What it is | Web-resolvable URI standard for encoding GS1 product identifiers |
| Format | https://example.com/01/12345678901234/21/serial |
| Carriers | QR code, RFID, NFC, Data Matrix |
| Primary identification keys | GTIN (01), batch (10), serial (21), expiry (17), and more |
| EU DPP relevance | Leading candidate for DPP identification under ESPR implementing acts |
| Existing adoption | Retail, healthcare, food sectors already deploying widely |
| Resolver service | Maps the URI to product information at the manufacturer or registry |
As the EU's ESPR regulation mandates Digital Product Passports for an expanding range of products, GS1 Digital Link is emerging as the de facto standard for linking physical products to their digital passports. Understanding how it works is essential for any business preparing for DPP compliance.
What is GS1 Digital Link?
GS1 Digital Link is a standard developed by GS1, the global organisation responsible for the most widely used product identification standards in the world, including GTINs (the numbers behind barcodes), EAN/UPC barcodes, and GS1-128 logistics labels.
At its core, GS1 Digital Link defines a way to express GS1 identifiers (such as GTINs) as web URIs, that is, as web addresses that can be resolved in a standard web browser or by any internet-connected device. This transforms a product identifier from a simple number into a gateway to digital content.
For example, a traditional barcode might encode the GTIN 05412345000013. Under GS1 Digital Link, this same identifier becomes a URI like: https://id.example.com/01/05412345000013. This URI can be encoded in a QR code, and when scanned, it directs the user to web-hosted information about the product.
The brilliance of GS1 Digital Link is that it does not replace existing GS1 identifiers, it extends them into the digital realm. Businesses that already use GTINs can build on their existing identification infrastructure. The same GTIN that identifies a product in the supply chain and at the point of sale now also serves as the key to its Digital Product Passport.
The URI Structure: How GS1 Digital Link Works
Understanding the URI structure of GS1 Digital Link is important for implementation. The standard defines a specific syntax for constructing web-resolvable URIs from GS1 identifiers.
The basic structure follows this pattern: https://[domain]/[primary-key-AI]/[primary-key-value]. The domain is the web address of the resolver, the server that hosts or routes to the product's digital content. The primary key Application Identifier (AI) and value encode the GS1 identifier. For most products, the primary key is AI 01 (GTIN).
The URI can include additional qualifiers to identify specific batches, serial numbers, or other granularity levels. For example:
- Product level: https://id.example.com/01/05412345000013
- Batch level: https://id.example.com/01/05412345000013/10/BATCH123
- Serial level: https://id.example.com/01/05412345000013/21/SERIAL456
The AI codes used in the URI path correspond to the same Application Identifiers used in GS1-128 barcodes and other GS1 data carriers. AI 01 is the GTIN, AI 10 is the batch number, AI 21 is the serial number, AI 17 is the expiration date, and so on. This consistency across GS1 standards simplifies implementation for businesses already using GS1 identifiers.
For Digital Product Passports under the ESPR, serial-level identification (using AI 21) is particularly important. The regulation requires DPPs to be associated with individual products or batches, and serial-level URIs enable unique identification of each item.
GS1 Digital Link vs Traditional Barcodes
To appreciate why GS1 Digital Link is transformative, it helps to understand the limitations of traditional barcodes and how Digital Link addresses them.
Traditional barcodes, both 1D (UPC/EAN) and 2D (GS1 DataMatrix), encode data directly in the barcode symbol. The scanner reads the barcode and extracts the encoded number. But the barcode itself does not connect to the internet; it is a static, self-contained data carrier. To access product information, a system must look up the scanned number in a local or proprietary database.
GS1 Digital Link QR codes, by contrast, encode a web URI. Any smartphone can scan the QR code and navigate to the URI using a standard web browser, no special app or proprietary database required. This web-native approach is what makes GS1 Digital Link suitable for consumer-facing applications like Digital Product Passports.
Key differences between traditional barcodes and GS1 Digital Link include:
- Traditional barcodes encode numbers; GS1 Digital Link encodes web URIs
- Traditional barcodes require proprietary scanners and databases; Digital Link works with any smartphone
- Traditional barcodes serve a single purpose (POS scanning); Digital Link enables multiple uses from a single code
- Traditional barcodes are static; Digital Link URIs can point to dynamic, updated content
- Traditional barcodes cannot differentiate between users; Digital Link supports content negotiation for different audiences
An important practical consideration: GS1 Digital Link QR codes can still be used at the point of sale. Retail scanners can extract the GTIN from the URI, so a single GS1 Digital Link QR code can serve both retail checkout and consumer information purposes. This "dual use" capability means that businesses may be able to replace traditional barcodes with GS1 Digital Link QR codes without disrupting existing retail processes.
The Role of GS1 Digital Link in Digital Product Passports
GS1 Digital Link is not just one of several options for implementing Digital Product Passports, it is emerging as the primary standard. The ESPR regulation specifies that DPP identifiers should follow internationally recognised standards, and GS1 Digital Link is the most mature, widely adopted standard that meets this requirement.
The fit between GS1 Digital Link and DPP requirements is natural. The ESPR requires that each product carry a data carrier (such as a QR code) that links to the product's digital passport. GS1 Digital Link provides exactly this capability, a standardised way to encode a product identifier in a QR code that resolves to a web-hosted DPP.
The standard also supports the ESPR's requirement for differentiated data access. Through content negotiation and resolver logic, a GS1 Digital Link URI can serve different content to different users. A consumer scanning the QR code with a smartphone browser might see a human-readable web page with product sustainability information. A market surveillance authority querying the same URI via an API might receive structured JSON-LD data for automated compliance checking. A recycler scanning the code might receive material composition data formatted for waste management systems.
The resolver architecture behind GS1 Digital Link is what enables this flexibility. A resolver is a web service that receives requests for GS1 Digital Link URIs and routes them to the appropriate content based on the requester's needs. The GS1 conformance standard for resolvers ensures interoperability, a resolver operated by one company can direct users to DPP data hosted by another.
QR Code Generation for GS1 Digital Link
Generating QR codes for Digital Product Passports using GS1 Digital Link requires attention to several technical details to ensure compliance and usability.
The QR code must encode the full GS1 Digital Link URI, including the domain, primary key (GTIN), and any qualifiers (batch number, serial number). The URI should use HTTPS to ensure secure communication. The resulting QR code will be a standard ISO/IEC 18004 QR code, no special symbology is required.
Size and print quality are critical. The QR code must be large enough to be reliably scanned by a smartphone camera at a reasonable distance. GS1 recommends a minimum module size (the smallest element in the QR code) and a minimum quiet zone (clear space around the code). For most applications, a QR code of at least 15mm x 15mm is recommended, though larger sizes may be needed for products scanned from a distance.
Error correction level affects both the robustness and data capacity of the QR code. Higher error correction levels make the code more resistant to damage (scratches, partial obscuring) but increase the code's size or reduce the data capacity. For DPP applications, a medium error correction level (level M, which can tolerate approximately 15% damage) is typically a good balance.
Testing is essential. Generate sample QR codes and test them with multiple devices and scanning apps under real-world conditions, including different lighting, angles, and distances. Ensure that the codes scan reliably on both iOS and Android devices and that they correctly resolve to the intended DPP content.
Resolver Architecture: The Engine Behind Digital Link
The resolver is the critical infrastructure component that makes GS1 Digital Link work. When a user scans a GS1 Digital Link QR code, their device makes an HTTP request to the resolver, the server at the domain encoded in the URI. The resolver then determines what content to serve based on the request.
A GS1 conformant resolver must support several key functions. Link resolution is the primary function, the resolver looks up the GS1 identifier and returns the appropriate content or redirects to where the content is hosted. Content negotiation allows the resolver to serve different formats based on the HTTP Accept header, for example, returning HTML for browsers and JSON-LD for machine clients.
The resolver can also support link type differentiation. A single GS1 identifier might have multiple associated resources, a product page, a DPP data endpoint, a safety data sheet, a recall notice, a recycling instruction page. The resolver can direct users to the most appropriate resource based on context, link type parameters, or user preferences.
For DPP implementation, the resolver architecture has important implications. You can either operate your own resolver (giving you full control over the infrastructure) or use a third-party resolver service. Many DPP platforms include resolver functionality as part of their offering, simplifying deployment for businesses that do not want to manage their own infrastructure.
GS1 operates a global resolver discovery service that enables interoperability across different resolver implementations. This means that even if different companies use different resolvers, the system can still function cohesively, a key requirement for the decentralised DPP ecosystem envisioned by the ESPR.
Content Negotiation: Serving the Right Data to the Right User
Content negotiation is one of the most powerful features of GS1 Digital Link and is directly relevant to DPP implementation. The concept is straightforward: the same URI serves different content depending on who is requesting it and what format they need.
In the HTTP protocol, content negotiation uses the Accept header in the request to indicate what content types the client can handle. A web browser typically sends Accept: text/html, indicating it wants a web page. An API client might send Accept: application/ld+json, requesting structured data in JSON-LD format.
For Digital Product Passports, content negotiation enables a single QR code to serve multiple purposes:
- Consumers scanning with a smartphone browser receive a visually designed web page showing product sustainability information, repair instructions, and recycling guidance
- Market surveillance authorities querying via API receive structured, machine-readable data for automated compliance verification
- Recyclers and waste handlers receive material composition and disassembly data formatted for waste management systems
- Business partners receive supply chain data relevant to procurement and due diligence
This multi-stakeholder approach is exactly what the ESPR envisions. The regulation requires that DPP data be accessible to different user groups with different access levels, and content negotiation provides the technical mechanism to achieve this through a single data carrier on the product.
Implementing content negotiation requires careful planning of your data architecture. You need to define what content each user group should see, how to authenticate restricted-access content (for authorities and business partners), and how to format data for both human and machine consumption.
Understanding GTINs: The Foundation of GS1 Digital Link
The GTIN (Global Trade Item Number) is the foundational identifier in the GS1 system and the most common primary key used in GS1 Digital Link URIs. Understanding GTINs is essential for implementing GS1 Digital Link correctly.
A GTIN is a globally unique number that identifies a trade item, any product or service that may be priced, ordered, or invoiced at any point in the supply chain. GTINs come in several formats: GTIN-8 (8 digits), GTIN-12 (12 digits, the UPC format used in North America), GTIN-13 (13 digits, the EAN format used globally), and GTIN-14 (14 digits, used for logistics units).
To obtain GTINs, a company must be a member of their local GS1 Member Organisation, which assigns a GS1 Company Prefix. The company then uses this prefix to create GTINs for each of its products. The last digit of the GTIN is a check digit calculated from the preceding digits.
For GS1 Digital Link URIs, GTINs are always expressed in their 14-digit format (GTIN-14), with shorter formats padded with leading zeros. So a GTIN-13 of 5412345000013 becomes 05412345000013 in the URI path. This ensures consistency and simplifies parsing.
If your business does not yet use GTINs, obtaining them should be an early step in your DPP preparation. Contact your local GS1 Member Organisation to apply for a GS1 Company Prefix and begin assigning GTINs to your products.
Implementation Steps: Getting Started with GS1 Digital Link
Implementing GS1 Digital Link for your products involves several practical steps. Here is a roadmap for businesses getting started.
Step one: ensure you have GTINs for all products that will require a DPP. If you are already a GS1 member with assigned GTINs, you are ahead. If not, register with your local GS1 Member Organisation and obtain a company prefix.
Step two: define your identifier structure. Decide whether your DPPs will be at the product model level (GTIN only), batch level (GTIN + batch number), or serial level (GTIN + serial number). The ESPR delegated act for your product category will specify the required granularity, but serial-level identification is likely for many categories.
Step three: set up your resolver. You can operate your own resolver, use a GS1 Member Organisation resolver service, or use a DPP platform that includes resolver functionality. The resolver must be accessible at the domain encoded in your GS1 Digital Link URIs and must remain available for the lifetime of the DPP.
Step four: configure your content. Create the web pages and API endpoints that the resolver will direct users to. Ensure that consumer-facing pages are well-designed and informative, and that machine-readable endpoints provide structured data in the required formats.
Step five: generate and test QR codes. Use a GS1 Digital Link compliant QR code generator to create codes for your products. Test extensively across devices, scanning conditions, and use cases.
Step six: integrate into your production and packaging processes. Determine how QR codes will be printed on products or packaging, update your packaging artwork, and establish quality control procedures to verify that codes are correctly printed and scannable.
- Obtain or verify GTINs for all products requiring DPPs
- Define identifier granularity (model, batch, or serial level)
- Deploy or subscribe to a GS1 Digital Link resolver service
- Build consumer-facing and machine-readable DPP content endpoints
- Generate QR codes using GS1 Digital Link compliant tools
- Integrate QR code printing into production and packaging workflows
- Test QR codes across devices, environments, and stakeholder use cases
- Establish ongoing processes for maintaining resolver availability and data accuracy
Data Carriers Beyond QR Codes
While QR codes are the most common data carrier for GS1 Digital Link, they are not the only option. The ESPR allows for various data carriers including RFID and NFC, and the choice of carrier depends on the product, use case, and industry context.
NFC (Near Field Communication) tags can encode GS1 Digital Link URIs and be read by tapping a smartphone against the tag. NFC is particularly useful for products where a printed QR code might be impractical, for example, clothing items where labels are small and washing might damage printed codes. NFC tags can be woven into garment labels, embedded in product casings, or integrated into product tags.
RFID (Radio Frequency Identification) is widely used in logistics and supply chain management. UHF RFID tags can encode GS1 Digital Link URIs and be read at a distance, enabling automated reading during warehousing, shipping, and retail operations. However, RFID reading typically requires specialised equipment and is less suitable for consumer-facing DPP access.
GS1 DataMatrix is a 2D barcode format commonly used in healthcare, industrial, and logistics applications. It can encode GS1 Digital Link URIs, and its smaller size compared to QR codes makes it suitable for small products or components. However, DataMatrix codes are less universally recognised by consumers than QR codes.
Was this article helpful?
Glad it helped. Thanks for letting us know.