| Scope boundary | DPP is a legal compliance construct under ESPR. Products may only be placed on the market or put into service with a passport when the applicable delegated act requires one, and the passport data must be accurate, complete, and up to date. | GS1 Digital Link is not the DPP law. It is a GS1 technical standard for URI syntax and resolver-enabled access to product information using GS1 identifiers. | Treat GS1 Digital Link as a possible technical layer inside a DPP design, not as a replacement for the delegated act, required passport data, access rights, registry upload, or compliance evidence. |
|---|
| Covered actors | DPP scope depends on ESPR delegated acts for product groups. Those acts specify the covered products, data to include, data carrier, layout and positioning, passport granularity, accessible pre-sale information, access actors, update actors, update arrangements, and availability period. | GS1 Digital Link can be used by product teams before or outside an ESPR DPP trigger. Its scope follows GS1 identifier and application rules, not the ESPR product-group trigger. | Start DPP scoping with the product group and delegated act. Then decide whether a GS1 Digital Link URI can carry or resolve the identifier design for that scoped product. |
|---|
| Trigger | A DPP must be connected through a data carrier to a persistent unique product identifier. ESPR allows the delegated act to set whether the passport is established at model, batch, or item level. | GS1 Digital Link commonly starts from GS1 identifiers such as GTIN and can add attribute data in the URI. GS1 specifications distinguish class-level, sub-class-level, and instance-level identifiers, but the DPP granularity still has to match the delegated act. | Do not assume a GTIN-only design is enough for every DPP. If the DPP must operate at batch or item level, the identifier, URI path, barcode content, resolver records, and source systems must preserve that granularity. |
|---|
| Core obligations | ESPR requires the data carrier to be physically present on the product, packaging, or accompanying documentation as the delegated act specifies. It must connect the physical product to the persistent identifier and passport access route. | GS1 Digital Link can be encoded in QR Code or Data Matrix and may also be relevant for NFC. GS1 describes it as explicitly encoding a resolvable Web URI rather than only a direct product number. | A DPP label decision is not just a packaging artwork decision. It must cover physical placement, durability, pre-sale digital access, scanner behavior, and whether the encoded value resolves reliably for consumers and professional users. |
|---|
| Evidence record | DPP data is the regulated product information set. It must use open standards and interoperable formats and be machine-readable, structured, searchable, and transferable where appropriate without vendor lock-in. | GS1 Digital Link does not define the ESPR passport data set. It gives a standard way to encode GS1 data into a URI and route users or systems toward resources that the brand owner or service provider makes available. | Use a data model and evidence process for the passport itself. Use GS1 Digital Link, if selected, to reach that data or related resources without pretending the URI syntax supplies the required DPP content. |
|---|
| Access rights and role control | ESPR requires access to DPP data to be regulated by actor-specific access rights. It names customers, economic operators, repairers, recyclers, market surveillance authorities, customs authorities, civil society, trade unions, and other relevant actors. | A GS1 Digital Link resolver can route different link types or resources, but access control, credentials, authorization, and role-specific data release must be implemented by the DPP system and aligned with ESPR delegated-act access rights. | Design public, business, authority, repair, recycling, and update paths separately. A single public landing page reached from a GS1 Digital Link URI is not the same as a role-aware DPP access model. |
|---|
| Enforcement | ESPR creates Commission-managed DPP infrastructure: a registry that stores at least unique identifiers and, for customs release for free circulation, commodity code data; a public web portal to search and compare passport data; and customs verification through registry interconnection. | GS1 Digital Link is not the EU DPP registry, web portal, or customs system. A resolver can help discovery, but it does not automatically upload identifiers, obtain a unique registration identifier, support the EU portal, or satisfy customs registry checks. | Implementation plans need separate work packages for GS1 identifier and resolver governance, EU registry upload, unique registration identifier handling, portal discoverability, and customs data alignment. |
|---|
| Overlap and reuse | ESPR requires DPP storage by the responsible economic operator or a digital product passport service provider, a backup copy, and availability for the period specified in delegated acts, including after insolvency, liquidation, or cessation of activity in the Union. | GS1 Digital Link persistence depends on identifier governance, domain and resolver operation, and link maintenance. GS1 rules and CIRPASS architecture material both make clear that resolvable URIs and resolver records need operational stewardship. | Do not let the marketing domain or packaging code become the only persistence plan. Preserve ownership of identifiers, domains, resolver records, backup access, and service-provider handover before products enter the market. |
|---|
| Practical decision rule | DPP implementation starts with legal scoping and data governance: delegated-act requirements, product granularity, passport data model, source evidence, access rights, update rights, registry upload, portal search, customs data, backup, and retention. | GS1 Digital Link implementation starts with identifier governance and resolution: GS1 keys and attributes, URI syntax, barcode or NFC encoding, resolver records, link types, domain stewardship, scanner behavior, and routing to public or restricted resources. | The useful architecture is a crosswalk, not a substitution. Map each DPP obligation to the system component that fulfils it, then mark which components GS1 Digital Link can support and which must be handled elsewhere. |
|---|