--- title: "EU DPP unique identifier requirements: product, operator and facility IDs" canonical_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/faq/unique-identifier-requirements" source_url: "https://www.sorena.io/artifacts/eu/digital-product-passport/faq/unique-identifier-requirements" author: "Sorena AI" description: "FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence." published_at: "2026-05-09" updated_at: "2026-05-09" keywords: - "EU DPP identifiers" - "ESPR unique product identifier" - "unique operator identifier" - "unique facility identifier" - "DPP data carrier" - "Digital Product Passport" - "ESPR" - "unique product identifier" - "data carrier" - "DPP registry" --- **[SORENA](https://www.sorena.io/)** - AI-Powered GRC Platform [Home](https://www.sorena.io/) | [Solutions](https://www.sorena.io/solutions) | [Artifacts](https://www.sorena.io/artifacts) | [About Us](https://www.sorena.io/about-us) | [Contact](https://www.sorena.io/contact) | [Portal](https://app.sorena.io) --- # EU DPP unique identifier requirements: product, operator and facility IDs FAQ on how ESPR Digital Product Passport identifiers connect products, economic operators, facilities, data carriers, resolvers and registry evidence. *FAQ* *ESPR DPP* *EU* ## EU Digital Product Passport unique identifier requirements ESPR links every required product passport to a persistent unique product identifier and, where specified for the product group, to operator and facility identifiers. Use this FAQ to separate the legal identifier duties from implementation choices such as GTIN, GLN, data carriers, resolvers, and registry records. Under Regulation (EU) 2024/1781, Digital Product Passport identifier work is not just a barcode exercise. The passport must be connected through a data carrier to a persistent unique product identifier, and delegated product-group rules can require operator and facility identifiers so the responsible actors and manufacturing locations can be traced. ## What unique identifiers does the ESPR Digital Product Passport require? 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. - Product identifier: the persistent identifier that connects the physical product, packaging or accompanying documentation to the passport. - Operator identifier: a unique string identifying an actor in the product value chain when Annex III and the delegated act require it. - Facility identifier: a unique identifier for the relevant location or building when facility traceability is required. - Registration identifier: the Commission registry stores at least unique identifiers for enforcement and customs checks; teams should not treat this as a public marketing ID. Sources for this answer: - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Defines the DPP, data carrier, unique product identifier and the Article 9 product-group decisions on model, batch or item level. - [Regulation (EU) 2024/1781 Annex III](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Lists the passport data elements that can include product, manufacturer, other operator, facility, importer and responsible economic-operator identifiers. ## How should teams connect the identifier to the data carrier and resolver? 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. - Document the exact carrier payload: identifier only, resolvable URL, GS1 Digital Link URI or another standards-based pattern. - Record the resolver behavior for public users, market surveillance, customs, repairers, recyclers and restricted-access actors. - Verify that the same identifier value is used consistently across the carrier, passport data model, backup copy, registry submission and ecommerce copy shown before purchase. - Keep carrier-quality evidence, because an identifier that cannot be scanned or resolved will not provide practical access to the passport. Sources for this answer: - [Regulation (EU) 2024/1781 Article 10](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Requires the DPP to be connected through a data carrier to a persistent unique product identifier and requires open, interoperable, machine-readable data where appropriate. - [CIRPASS DPP System Architecture](https://cirpassproject.eu/project-results/?ref=sorena.io) - Explains why the product identifier is the root of discovery and why identifier choice affects the protocols and systems used to reach DPP information. - [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Defines GS1 Digital Link URI as a web URI syntax for expressing GS1 identifier keys and attributes, useful when a DPP design relies on GS1 identifiers. ## When are operator and facility identifiers needed? 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. - For the manufacturer, map the manufacturer record to its unique operator identifier and required contact information. - For other value-chain actors, identify which actors the delegated act requires and avoid creating duplicate IDs without confirming whether one already exists. - For facilities, bind the facility identifier to the responsible location or building, not just to a supplier name or purchase-order record. - For standards alignment, check ISO/IEC 15459 or equivalent European or international standards where relevant to the products concerned. Sources for this answer: - [Regulation (EU) 2024/1781 Article 12](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Sets the process for missing unique operator and facility identifiers and points to the standards framework for those identifiers. - [Regulation (EU) 2024/1781 Annex III](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - States that data carriers, product identifiers, operator identifiers and facility identifiers must comply with listed ISO/IEC 15459 standards where relevant. - [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Provides examples of globally used GS1 identification keys, including GTIN for trade items and GLN for locations or parties. ## What evidence should teams keep for DPP identifier readiness? 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. - Identifier register with product model, batch or item level, identifier value, issuing system, owner, status and retirement rule. - Carrier specification showing payload syntax, carrier type, placement, sample artwork, scan test results and resolver target. - Operator and facility ID file showing existing-ID checks, requests made on behalf of actors, issued IDs and the actor/location each ID identifies. - Data-model mapping from identifier fields to passport records, backup service provider records, registry data and ecommerce access copies. - Resolver and access-rights test evidence for public users and restricted actors named in the delegated act. - Change log for product redesign, remanufacturing, supplier changes, facility moves, carrier artwork changes and resolver migrations. Sources for this answer: - [Regulation (EU) 2024/1781 Articles 10 and 11](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Supports evidence for access, backup copies, interoperability, security, availability and controlled rights to update passport data. - [CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Provides practical DPP design guidance on identifiers, carrier selection, carrier placement, scanability and registry/web-portal considerations. - [GS1 DPP standards overview](https://www.gs1.org/standards/standards-emerging-regulations/DPP?ref=sorena.io) - Describes GS1's DPP work around identification and data carriers for access to DPP data. ## Primary sources - [Regulation (EU) 2024/1781 (ESPR)](https://eur-lex.europa.eu/eli/reg/2024/1781/oj/eng?ref=sorena.io) - Primary legal source for ESPR Digital Product Passport requirements, including Articles 9 to 13 and Annex III identifier elements. - Quote: "Digital product passport" - [CIRPASS DPP System Architecture](https://cirpassproject.eu/project-results/?ref=sorena.io) - Technical architecture source for product-identifier-centric discovery, resolver design and decentralised DPP data access. - Quote: "rooted in the Product-ID" - [CEN-CENELEC CWA 18186:2025](https://www.cencenelec.eu/media/CEN-CENELEC/CWAs/RI/2025/cwa18186_2025.pdf?ref=sorena.io) - Practical DPP design guidance source for identifier selection, data-carrier choices, placement, scanability and registry planning. - Quote: "Guidelines to create a Digital Product Passport" - [GS1 General Specifications](https://ref.gs1.org?ref=sorena.io) - Standards source for GS1 identification keys, data carriers, GTIN, GLN and Digital Link URI terminology used in DPP implementation designs. - Quote: "unambiguous identification keys" - [GS1 DPP standards overview](https://www.gs1.org/standards/standards-emerging-regulations/DPP?ref=sorena.io) - GS1 overview source for preparing identifier and data-carrier implementations for EU DPP requirements. - Quote: "identification and data carrier" ## Topic Guides - [Annex III Data Model Planning for EU Digital Product Passports](/artifacts/eu/digital-product-passport/annex-iii-data-model-planning.md): Plan EU Digital Product Passport data fields, identifiers, access rights, update owners, registry inputs, and evidence records against ESPR Annex III and product-specific delegated acts. - [Digital Product Passport vs Digital Twin](/artifacts/eu/digital-product-passport/dpp-vs-digital-twin.md): Compare EU Digital Product Passports with digital twins: legal access duties, identifiers, public and restricted data, evidence, governance, and reuse limits. - [Digital Product Passport vs Paper Product Passports](/artifacts/eu/digital-product-passport/dpp-vs-traditional-product-passports.md): Compare EU regulated digital product passports with paper, PDF, web, and internal product passports across access, identifiers, data carriers, restricted data, customs checks, registry, and interoperability. - [DPP customs access review workflow for ESPR products](/artifacts/eu/digital-product-passport/customs-access-review-workflow.md): Review public, restricted, and customs access for EU Digital Product Passports, including registry handoffs, portal access rights, and release-for-free-circulation evidence. - [DPP Data Governance RACI Template for EU Digital Product Passports](/artifacts/eu/digital-product-passport/dpp-data-governance-raci-template.md): Assign accountable owners for EU Digital Product Passport data, access rights, supplier inputs, resolver links, registry uploads, verification checks, and retained evidence. - [DPP data-model intake workflow for EU Digital Product Passports](/artifacts/eu/digital-product-passport/dpp-data-model-intake-workflow.md): A grounded intake workflow for EU Digital Product Passport data models: product group, delegated-act status, source owner, supplier data, access class, identifiers, carrier, checks, and publication readiness. - [DPP Governance, Verification and Audit Controls](/artifacts/eu/digital-product-passport/governance-verification-and-audit.md): Build EU Digital Product Passport governance controls for data owners, supplier evidence, access logs, validation checks, audit records, and product release gates. - [DPP QR code vs NFC data carrier choices under EU ESPR](/artifacts/eu/digital-product-passport/faq/qr-code-vs-nfc-carrier-choices.md): How to choose QR code, NFC, or another data carrier for an EU Digital Product Passport without assuming ESPR mandates one universal carrier. - [DPP registry and web portal integration under EU ESPR](/artifacts/eu/digital-product-passport/dpp-registry-and-web-portal-integration.md): Grounded guide to EU Digital Product Passport registry and web portal integration under ESPR, covering identifiers, data carriers, access rights, service providers, and lookup design. - [DPP vs Battery Passport: ESPR and Battery Regulation Comparison](/artifacts/eu/digital-product-passport/dpp-vs-battery-passport.md): Compare the ESPR Digital Product Passport framework with the EU Batteries Regulation battery passport by scope, timing, data, access rights, identifiers, registry, governance, and evidence. - [DPP vs EPREL Comparison](/artifacts/eu/digital-product-passport/dpp-vs-eprel.md): Compare the EU Digital Product Passport with EPREL: product-passport scope, energy-label database role, access model, identifiers, data carriers, and overlap limits. - [DPP vs GS1 Digital Link: Duties vs Standard](/artifacts/eu/digital-product-passport/dpp-vs-gs1-digital-link.md): Compare EU Digital Product Passport requirements with GS1 Digital Link: legal scope, identifiers, data carriers, access rights, registry, portal, customs checks, and implementation consequences. - [EU Digital Product Passport access: public, restricted, and customs views](/artifacts/eu/digital-product-passport/public-restricted-and-customs-access.md): How ESPR Digital Product Passport access should be split across public users, restricted actors, authorities, customs, the EU registry, and the web portal. - [EU Digital Product Passport API and resolver architecture](/artifacts/eu/digital-product-passport/api-and-resolver-architecture.md): Grounded DPP architecture guidance for data carriers, product identifiers, resolver lookup paths, access rights, registry integration, and interoperability without premature protocol mandates. - [EU Digital Product Passport Applicability Test](/artifacts/eu/digital-product-passport/applicability-test.md): Check whether an ESPR delegated act or battery passport rule may require a Digital Product Passport, which operator owns it, and what evidence to keep. - [EU Digital Product Passport architecture and integration](/artifacts/eu/digital-product-passport/architecture-and-integration.md): Grounded guide to EU Digital Product Passport architecture: data carriers, identifiers, access rights, registry, portal, supplier flows, customs checks, and governance. - [EU Digital Product Passport checklist](/artifacts/eu/digital-product-passport/checklist.md): A concrete EU Digital Product Passport readiness checklist covering product-group scope, passport fields, identifiers, data carriers, access rights, supplier evidence, registry preparation, and publication controls. - [EU Digital Product Passport compliance: ESPR requirements](/artifacts/eu/digital-product-passport/compliance.md): Grounded EU Digital Product Passport compliance guide covering ESPR passport data, identifiers, data carriers, access rights, registry readiness, supplier validation, and evidence. - [EU Digital Product Passport Data Carriers, Access Control, and UX](/artifacts/eu/digital-product-passport/data-carriers-access-control-and-ux.md): How to choose DPP data carriers, identifiers, access rights, and scanning UX under ESPR Articles 9-14, with QR, NFC, RFID, registry, and customs constraints. - [EU Digital Product Passport data requirements and fields](/artifacts/eu/digital-product-passport/data-requirements-and-fields.md): How to plan Digital Product Passport data fields under ESPR: delegated-act scope, Annex III data categories, access rights, customs data, and supplier validation. - [EU Digital Product Passport deadlines and compliance calendar](/artifacts/eu/digital-product-passport/deadlines-and-compliance-calendar.md): Grounded EU Digital Product Passport calendar for ESPR and battery passport milestones, with product-group dates flagged as dependent on delegated acts. - [EU Digital Product Passport FAQ](/artifacts/eu/digital-product-passport/faq.md): Direct answers on EU Digital Product Passport scope, creators, product groups, registry, customs checks, access rights, identifiers, data carriers, and governance. - [EU Digital Product Passport identifier and data carrier design](/artifacts/eu/digital-product-passport/unique-identifier-and-data-carrier-design.md): How to design Digital Product Passport identifiers, QR or other data carriers, resolver links, registry records, access paths, and evidence without overclaiming the EU rules. - [EU Digital Product Passport penalties and enforcement](/artifacts/eu/digital-product-passport/penalties-and-fines.md): What ESPR says about Digital Product Passport penalties, Member State fine rules, market surveillance, customs checks, and unresolved product-specific delegated acts. - [EU Digital Product Passport Product Group Readiness](/artifacts/eu/digital-product-passport/product-group-readiness.md): Prepare product groups for EU Digital Product Passport rules by tracking ESPR delegated-act status, data fields, suppliers, identifiers, access rights, and registry handoffs. - [EU Digital Product Passport requirements under ESPR](/artifacts/eu/digital-product-passport/requirements.md): source-linked overview of EU Digital Product Passport requirements under ESPR: product-specific delegated acts, data fields, identifiers, carriers, registry, access rights, supplier data validation, and open points. - [EU Digital Product Passport supplier data validation controls](/artifacts/eu/digital-product-passport/supplier-data-validation.md): Build a supplier data validation file for EU Digital Product Passports: source owner, product link, access class, data model fit, evidence quality, approval record, and release gate. - [EU DPP customs access: registry, portal, and restricted data](/artifacts/eu/digital-product-passport/faq/customs-access.md): FAQ on customs access under the EU Digital Product Passport: what customs can verify, how the registry and public portal differ, and how access rights limit DPP data. - [EU DPP implementation playbook and vendor selection](/artifacts/eu/digital-product-passport/implementation-playbook-and-vendor-selection.md): Select Digital Product Passport vendors against ESPR requirements for identifiers, data carriers, access rights, decentralized storage, registry readiness, portal access, and verification evidence. - [EU DPP Product-Group Readiness Checklist](/artifacts/eu/digital-product-passport/product-group-readiness-checklist.md): A source-grounded checklist for preparing a product group for an EU Digital Product Passport delegated act, covering data fields, suppliers, identifiers, carriers, access rights, and registry readiness. - [EU DPP QR Code and Data Carrier Implementation Guide](/artifacts/eu/digital-product-passport/dpp-qr-code-implementation-guide.md): Grounded guidance for using QR codes and other data carriers in EU Digital Product Passport programs, including unique identifiers, access, resolver testing, and evidence. - [EU DPP supplier data validation workflow](/artifacts/eu/digital-product-passport/supplier-data-validation-workflow.md): A grounded workflow for checking supplier data before it is used in an EU Digital Product Passport, covering product linkage, evidence, owners, access class, and approval records. - [Public vs restricted EU Digital Product Passport data](/artifacts/eu/digital-product-passport/faq/public-vs-restricted-passport-data.md): How to separate public, restricted, authority, and customs access in EU Digital Product Passport designs under ESPR and battery passport rules. - [What is a Digital Product Passport under ESPR?](/artifacts/eu/digital-product-passport/what-is-a-dpp.md): A visitor-friendly explanation of EU Digital Product Passports under ESPR: product data, identifiers, data carriers, access rights, registry, web portal, and delegated acts. - [What is the EU Digital Product Passport registry?](/artifacts/eu/digital-product-passport/faq/dpp-registry.md): FAQ on the ESPR Digital Product Passport registry: what it stores, who uploads data, how identifiers work, and what teams should avoid assuming. - [Which products come first for the EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/which-products-come-first.md): FAQ on EU Digital Product Passport product priority: batteries have a separate passport rule, while ESPR product groups depend on the working plan and delegated acts. - [Who must create an EU Digital Product Passport?](/artifacts/eu/digital-product-passport/faq/who-must-create-a-digital-product-passport.md): DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together. *Recommended next step* *Placement: after evidence section* ## Check whether your DPP identifiers resolve cleanly Map product, operator and facility identifiers to carrier payloads, resolver behavior, passport fields, registry data and evidence before product-group delegated acts force packaging or data-model changes. - [Open Research Copilot](/solutions/research-copilot.md): Ask DPP identifier questions against cited ESPR and standards material. - [Discuss DPP identifier readiness](/contact.md): Review identifier, carrier, resolver and evidence gaps before implementation hardens. --- [Privacy Policy](https://www.sorena.io/privacy) | [Terms of Use](https://www.sorena.io/terms-of-use) | [DMCA](https://www.sorena.io/dmca) | [About Us](https://www.sorena.io/about-us) (c) 2026 Sorena AB (559573-7338). All rights reserved. Source: https://www.sorena.io/artifacts/eu/digital-product-passport/faq/unique-identifier-requirements