What Is a GS1 Digital Link Resolver
A GS1 Digital Link resolver is a web service that acts as an intelligent intermediary between a product identifier and the information associated with that product. When a consumer scans a QR code on a product, or when a system queries a product's identifier programmatically, the resolver receives the GS1 Digital Link URI and determines where to direct the request based on the product identity, the type of information requested, and the context of the request.
Think of a resolver as a smart signpost for product information. Just as a DNS server translates domain names into IP addresses, a Digital Link resolver translates product identifiers into the URLs where product information, including Digital Product Passport data, can be found. This indirection is critically important because it decouples the permanent product identifier from the potentially changing location of product data.
For Digital Product Passports under the ESPR, the resolver plays a central role. The data carrier on the product encodes a GS1 Digital Link URI. When scanned, this URI reaches a resolver, which redirects the request to the DPP data source. If the DPP platform changes, or if the data moves to a new host, only the resolver configuration needs to be updated, the millions of QR codes already printed on products continue to function correctly.
The Architecture of a Digital Link Resolver
A GS1 Digital Link resolver consists of several logical components that work together to process incoming requests and deliver appropriate responses.
The URI parser is the first component that processes an incoming request. It extracts the GS1 identifiers from the Digital Link URI, the primary identifier (typically a GTIN), any qualifiers (serial number, batch/lot number), and any additional attributes. It validates that the URI conforms to the GS1 Digital Link syntax specification and rejects malformed requests.
The link resolution engine is the core of the resolver. It maintains a database of link records, mappings between product identifiers and the URLs where information about those products can be found. Each link record specifies the product identifier it applies to, the type of information available (product page, Digital Product Passport, safety data, recall information), the target URL, and any conditions that determine when this link should be used.
The content negotiation module examines the incoming request to determine what type of response the requester expects. This is achieved through HTTP Accept headers, query parameters, or the structure of the URI itself. A web browser requesting text/html will receive a redirect to a human-readable page. A machine requesting application/json will receive structured data. A system requesting application/ld+json will receive JSON-LD linked data. This single-URI, multiple-representation approach is fundamental to the Digital Link architecture.
The response module generates the appropriate HTTP response, typically a 307 (Temporary Redirect) that sends the requester to the target URL identified by the link resolution engine. For API requests, the resolver may instead return a link set (a JSON document listing all available information resources for the identified product) rather than performing a redirect.
How Resolution Works: Step by Step
To understand how a Digital Link resolver works in practice, consider the following scenario: a consumer scans a QR code on a product. The QR code encodes the URI https://resolver.example.com/01/05012345678901/21/SN12345.
First, the consumer's smartphone decodes the QR code and opens the URI in a web browser. The browser sends an HTTP GET request to resolver.example.com with the path /01/05012345678901/21/SN12345. The request includes an Accept header indicating the browser prefers text/html content.
The resolver's URI parser extracts the GTIN (05012345678901) and serial number (SN12345) from the path. It validates these identifiers and passes them to the link resolution engine.
The link resolution engine looks up the identifier combination in its database. It finds multiple link records for this product:
- A Digital Product Passport link pointing to https://dpp.example.com/passport/SN12345
- A product information page link pointing to https://brand.example.com/products/widget-pro
- A recall information link pointing to https://recalls.example.com/check/05012345678901
- A JSON-LD linked data endpoint pointing to https://api.example.com/01/05012345678901/21/SN12345
The content negotiation module notes that the request is from a web browser requesting HTML. Based on the resolver's default link type configuration and the request context, it selects the Digital Product Passport link as the most appropriate response for a consumer scanning a QR code.
The resolver returns a 307 Temporary Redirect response with the Location header set to https://dpp.example.com/passport/SN12345. The consumer's browser follows the redirect and displays the Digital Product Passport page.
Link Types and the GS1 Conformance Framework
GS1 defines a vocabulary of link types that resolvers use to categorise the information resources associated with products. These standardised link types ensure that different resolvers provide consistent experiences and that consuming systems can reliably request specific types of information.
Key link types relevant to Digital Product Passports include:
- gs1:digitalProductPassport, the primary DPP data resource, containing the comprehensive product passport information required by ESPR
- gs1:productSustainabilityInfo, environmental and sustainability information about the product
- gs1:pip, product information page, typically the brand's consumer-facing product webpage
- gs1:safetyInfo, safety-related information including material safety data sheets and hazard warnings
- gs1:recallStatus, information about whether the product is subject to a recall
- gs1:traceability, supply chain traceability information, potentially linking to EPCIS event data
- gs1:certificationInfo, certificates and compliance declarations associated with the product
GS1 has published a conformance framework for Digital Link resolvers that defines different levels of capability. Level 0 resolvers perform basic HTTP redirects. Level 1 resolvers support content negotiation. Level 2 resolvers support the full link set API, enabling machines to discover all available information resources for a product. Level 3 resolvers add support for compressed Digital Link URIs and other advanced features.
For DPP implementations, a Level 1 or Level 2 resolver is recommended. Content negotiation (Level 1) ensures that both human users and machine systems receive appropriate responses. The link set API (Level 2) enables regulatory systems and DPP registries to programmatically discover and access passport data for any product.
Implementation Options: Build, Buy, or Use GS1
Businesses implementing DPPs have three main options for Digital Link resolver infrastructure: building a custom resolver, using a commercial resolver service, or leveraging the GS1 resolver network.
Building a custom resolver gives maximum control over the resolution logic, branding, and integration with existing systems. GS1 has published open-source reference implementations that can serve as starting points. However, operating a resolver at scale requires robust web infrastructure, monitoring, and ongoing maintenance. The resolver must be highly available, if it goes down, every QR code pointing to it becomes non-functional.
Commercial resolver services, offered by various technology providers including DPP platforms, provide managed resolver infrastructure without the operational burden. These services typically offer web-based administration interfaces for managing link records, analytics dashboards showing scan activity, and integration APIs for programmatic link management. For most businesses, a managed resolver service offers the best balance of functionality and operational simplicity.
The GS1 resolver network (id.gs1.org) provides a global resolution service maintained by GS1 itself. Brand owners can register their products and configure resolution targets through their GS1 member organisation. This approach leverages the GS1 domain's global recognition and trust, but may offer less flexibility for customisation and branding compared to operating your own resolver domain.
Many DPP platforms, including MyProductPassport, include built-in resolver functionality as part of their offering. This integrated approach means that businesses do not need to set up separate resolver infrastructure, the platform handles URI resolution, content negotiation, and link management alongside passport data management and QR code generation.
Resolver Configuration for DPP Compliance
Configuring a resolver for ESPR-compliant Digital Product Passports requires attention to several regulatory and technical requirements.
The resolver must support persistent access to passport data. The ESPR requires that DPP information remain accessible for a defined period after a product is placed on the market. This means the resolver must continue operating and resolving requests for the duration of this retention period, even if the product has been discontinued. Businesses should ensure their resolver infrastructure or service provider commits to the required retention periods.
Resolver responses should include appropriate HTTP headers for caching and CORS (Cross-Origin Resource Sharing) to enable DPP data to be accessed from web applications, mobile apps, and regulatory systems. The Link header should advertise available link types, enabling HTTP-native discovery of information resources.
For products with serial-level identification, the resolver must handle serial number qualifiers in the URI path. This means the link database must contain records at the serial level (or support wildcard matching that resolves serial-specific requests to the correct passport instance). For products identified at the batch level, the resolver must similarly handle batch/lot qualifiers.
Security considerations are important for resolver implementations. The resolver should use HTTPS exclusively, implement rate limiting to prevent abuse, and consider authentication for administrative functions. While the resolution itself should be publicly accessible (to allow open access to DPP data as the ESPR intends), the management interface must be protected.
Advanced Resolver Features for DPP Ecosystems
Beyond basic resolution, several advanced resolver features enhance the DPP ecosystem:
- Analytics and scan tracking, resolvers can log scan events, providing brands with insights into where, when, and how frequently their products' passports are accessed
- Geolocation-aware resolution, resolvers can direct requests to language-specific or region-specific passport content based on the requester's location
- Temporal resolution, resolvers can maintain historical versions of link records, enabling access to passport data as it existed at a specific point in time
- Fallback resolution, resolvers can implement cascading resolution logic, trying multiple data sources in sequence if the primary source is unavailable
- Compressed URI support, GS1 Digital Link defines compressed URI formats that reduce the data density requirements for QR codes, enabling smaller codes or higher error correction
These features are not required for basic ESPR compliance but can significantly enhance the usability and reliability of DPP implementations. Scan analytics, for example, provide valuable market intelligence about consumer engagement with sustainability information, helping businesses understand the return on their DPP investment.
As the DPP ecosystem matures, resolver capabilities will likely expand further. The European Commission's DPP registry, open since 20 July 2026, interacts with resolvers to index and access passport data across the entire EU market. Resolver operators should monitor these developments and ensure their implementations remain compatible with evolving infrastructure requirements.
Testing and Validating Your Resolver Implementation
Before deploying a resolver in production, thorough testing is essential to ensure compliance with GS1 specifications and reliable operation under real-world conditions.
GS1 provides conformance test suites that validate resolver behaviour against the Digital Link specification. These tests verify correct URI parsing, proper HTTP response codes, accurate content negotiation, and conformant link set generation. Running these tests against your resolver implementation identifies specification deviations before they cause problems with real products and real consumers.
Load testing is equally important. A resolver for a high-volume consumer brand might need to handle thousands of requests per second during peak periods, a product launch, a viral social media moment, or a regulatory inspection campaign. Understanding your resolver's capacity limits and implementing appropriate scaling strategies (caching, load balancing, CDN distribution) ensures consistent performance.
End-to-end testing should verify the complete chain from QR code scan to passport display. This means physically printing QR codes, scanning them with various smartphone models and operating systems, and confirming that the resolver correctly directs each request to the appropriate passport content. Testing with both consumer devices and programmatic clients ensures that all access paths function correctly.
Finally, monitoring and alerting should be established for production resolver infrastructure. Uptime monitoring, response time tracking, and error rate alerting enable rapid detection and resolution of issues that could prevent consumers and regulators from accessing Digital Product Passport data.
Was this article helpful?
Glad it helped. Thanks for letting us know.