EU Digital Product Passport unique identifier requirements

At minimum, a required DPP must be connected through a data carrier to a persistent unique product identifier. ESPR defines that identifier as a unique string that identifies the product and enables a web link to the product passport.

The product-specific delegated act decides whether the passport is established at model, batch or item level. That choice matters because a model-level identifier supports shared product information, while batch or item identifiers support more granular traceability and lifecycle updates.

Start with the required access path: scanning the carrier must lead to the right passport for the relevant product level. ESPR allows a linear barcode, two-dimensional symbol or other automatic identification data capture medium, but the delegated act can specify which carriers, layout and positioning apply to the product group.

Do not overload the carrier with the whole passport. In practice, teams should encode the identifier or a resolvable web link, then resolve users to the passport data according to access rights. Technical guidance from CIRPASS and GS1 treats the identifier choice as architecture-shaping because it determines which resolver, URI, Digital Link or equivalent path can get a scanner from the product to the DPP.

Operator and facility identifiers are not generic company labels. They are passport data elements used when the product-group delegated act requires traceability of value-chain actors or manufacturing locations.

If a required operator or facility identifier is not already available, Article 12 puts work on the economic operator creating or updating the passport: first seek confirmation that no identifier exists, then request one on behalf of the relevant actor or the actor responsible for the location or building, and provide the details once issued.

Keep evidence that proves the identifier can be traced from the product to the correct passport and that each required actor or facility ID is controlled, unique and maintainable. The evidence should be understandable to product, packaging, ecommerce, customs, market-surveillance and supplier teams.

Avoid unsupported commitments that a chosen identifier scheme is always sufficient. ESPR leaves important product-group details to delegated acts, and technical standards are still part of the implementation layer. Evidence should therefore show both the current rule basis and the design assumptions that may need to change.