--- title: Which identifiers are used in an EU-DPP? description: Learn which identifiers are used in an EU Digital Product Passport, including the Unique Product Identifier, Economic Operator ID, Facility ID, EU-DPP ID and EU DPP Registry Registration ID. --- [Skip to content](https://support.syncforce.com/knowledge/which-identifiers-are-used-in-an-eu-dpp#main-content) [![Syncforce\_logo\_tagline](https://support.syncforce.com/hs-fs/hubfs/Syncforce_logo_tagline.webp?width=480&height=72&name=Syncforce_logo_tagline.webp)](https://www.syncforce.com/) Open main navigation Close main navigation Hello. How can we help you? - There are no suggestions because the search field is empty. 1. [Home](https://support.syncforce.com/knowledge?hsLang=en) 2. [Industry & Regulatory Knowledge](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en) 3. [EU Digital Product Passport - DPP](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#eu-digital-product-passport-dpp) # Which identifiers are used in an EU-DPP? #### Short answer An EU-DPP involves several identifiers because different identifiers identify different things. The most important distinction is between: - **Unique Product Identifier**, identifying the Product Model, Batch or Serialized Item - **Economic Operator ID**, identifying the legal entity responsible for the Product - **Facility ID**, identifying the relevant manufacturing site - **EU-DPP ID**, identifying the passport itself - **Registration ID**, identifying the passport's registration in the EU DPP registry These identifiers should not be collapsed into one identifier. The SyncForce Golden Hierarchy keeps the Product, organisation, Facility, EU-DPP and registry registration as separate but related objects. --- #### What is the Unique Product Identifier? The **Unique Product Identifier** identifies the Product that is the subject of the EU-DPP. Depending on the applicable Product regulation or delegated act, this can identify: - a Product Model - a Batch - an individual Serialized Item For the VTA-based EU-DPP route, SyncForce uses ASC MH10.8.2 Data Identifiers. For example, a Product Model can use: `25P + VTA Product Model ID` with a resolver representation such as: `https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM` This is the identifier encoded in the Product's EU-DPP data carrier when the passport is created at Product Model level. --- #### How is a Batch identified? A Batch belongs to a Product Model. The identity is therefore: **Product Model ID + Lot/Batch Number** For the Data Identifier route: - `25P` identifies the Product Model - `1T` identifies the Batch or Lot For example: `https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM&.1T=LOT-2028-00425` The Batch Number qualifies the Product Model rather than replacing the Product Model identity. --- ### How is an individual Serialized Item identified? SyncForce supports two approaches. Product Model + Serial Number A contextual Serialized Item can use: `25P + S` For example: `https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM&.S=000012345` The Serial Number is unique in the context of that Product Model. Globally unique Serialized Item Alternatively, SyncForce can use: `25S + VTA Serialized Item ID` For example: `https://prodigi.link/?.25S=VTA-MPLA-SN-7F4K9X2Q` Here the individual physical item has a globally unique identity of its own. **Read more:** [*How are Product Model, Batch and Serialized Item identified for an EU-DPP?*](https://support.syncforce.com/knowledge/how-are-product-model-batch-and-serialized-item-identified-for-an-eu-dpp?hsLang=en) --- #### Is the Product identifier the same as the GTIN? Not necessarily. A GTIN identifies the commercial Trade Item or Sales Unit. The Unique Product Identifier identifies the regulated Product that is the subject of the EU-DPP. One Product Model can occur in several Sales Units, and one Sales Unit can contain several Product Models. The two identifiers therefore answer different questions: **GTIN** Which commercial proposition is being sold? **Unique Product Identifier** Which regulated Product is this? **Read more:** [*Why is a GTIN not necessarily the Product Model identifier for an EU-DPP?*](https://support.syncforce.com/knowledge/why-is-a-gtin-not-necessarily-the-product-model-identifier-for-an-eu-dpp?hsLang=en) --- #### What is the Economic Operator ID? The Economic Operator ID identifies the legal entity responsible for the EU-DPP and for placing the Product on the EU market. SyncForce uses the following order: 1. **LEI**, where available 2. otherwise **EUID**, based on the national business register 3. otherwise **18V + VTA Economic Operator ID** For the VTA form, a resolver representation can be: `?.18V={VTA-EO}` The Economic Operator ID is not part of the Product identifier. It is a separate EU-DPP data element identifying the responsible legal entity. --- #### What is the Facility ID? The Facility ID identifies the relevant physical manufacturing site. In the SyncForce Golden Hierarchy, the working definition is the manufacturing site where the Product itself is produced or receives its final assembly before packing. SyncForce supports: - **GLN** for the physical location, where available - otherwise **25L + VTA Facility ID** For example: `/414/{GLN}` or: `?.25L={VTA-FA}` The Facility is kept separate from the Economic Operator because a legal entity and a manufacturing location are different objects. **Read more:** [*How are the Economic Operator and Facility identified in an EU-DPP?*](https://support.syncforce.com/knowledge/how-are-the-economic-operator-and-facility-identified-in-an-eu-dpp?hsLang=en) --- #### Does the EU-DPP itself have an identifier? Yes. This is one of the most important distinctions. The Product has an identifier. The **EU-DPP itself also has its own identifier**. These are not the same value. SyncForce refers to the passport identifier as the: EU-DPP ID The EU-DPP ID identifies the digital passport record itself. SyncForce uses a globally unique UUID represented as a URI. For example: `urn:uuid:3f2b8c1e-6a4d-4e2b-9c7a-1d5e8f0a2b34` The UUID is generated once when the EU-DPP is created. It remains the identity of that passport throughout its lifecycle. --- #### Why does the EU-DPP need its own identifier? Because the Product and its passport are different objects. For example: **Product Model** `VTA-MPLA-PM-346UJI3NUM` is the physical Product Model identity. Its EU-DPP may have: **EU-DPP ID** `urn:uuid:3f2b8c1e-6a4d-4e2b-9c7a-1d5e8f0a2b34` The first identifies the Product. The second identifies the passport record describing the regulated information about that Product. This distinction also allows the passport to have its own lifecycle, versions and registry information without changing the Product identifier. --- #### Does the EU-DPP ID change when the passport is updated? No. The EU-DPP ID identifies the passport itself rather than one specific version. When the information in the EU-DPP changes, new versions can be created while the EU-DPP ID remains the same. Conceptually: **EU-DPP ID** ↓ Version 1 Version 2 Version 3 The passport remains the same regulated information object while its content evolves over time. --- #### What is the Registration ID? The **Registration ID** identifies the EU-DPP's registration in the EU DPP registry. It is assigned by the EU DPP registry after the passport is registered. This means the Registration ID is different from both: - the Unique Product Identifier - the EU-DPP ID The sequence is: **Product identified** ↓ **EU-DPP created** ↓ **EU-DPP ID generated** ↓ **EU-DPP registered** ↓ **Registration ID returned by the EU DPP registry** --- #### Is the EU-DPP ID assigned by the EU? No. The EU-DPP ID must already exist when the passport is submitted for registration. It is created by the system responsible for creating and hosting the passport. In the SyncForce architecture: **SyncForce Circular PIM** manages the Product and compliance information ↓ **Perennis** creates and publishes the regulated EU-DPP ↓ **EU-DPP ID** is generated when the passport is created ↓ **EU DPP registry** registers the passport and returns the Registration ID The EU therefore assigns the **Registration ID**, not the EU-DPP ID. --- #### What information is submitted to the EU DPP registry? The registration includes identifiers needed to connect the Product, passport and responsible parties. The SyncForce architecture maintains: - Unique Product Identifier - EU-DPP ID - Economic Operator ID - back-up DPP service provider identifier - EU-DPP API endpoint The EU DPP registry subsequently provides the Registration ID. The Registration ID is stored with the EU-DPP. --- #### Is the Registration ID placed in the QR code? No. The Product data carrier identifies the Product. For example, at Product Model level: `https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM` The Registration ID does not replace that Product identifier in the data carrier. This distinction is important: > **The QR code identifies the Product subject of the passport, not the registry record.** --- #### What about the DPP service provider? The DPP service providers also need their own organisation identities. In the SyncForce architecture: **Perennis** is the main DPP service provider and: **SyncForce** is the back-up DPP service provider. These are legal entities and therefore use organisation identifiers, just as the Economic Operator does. Their identifiers should not be confused with: - the Product identifier - the EU-DPP ID - the Registration ID --- #### What does the complete identifier model look like? | Identifier | What does it identify? | Example approach | | --- | --- | --- | | **Unique Product Identifier** | Product Model | `25P + VTA-PM` | | **Batch identifier** | Specific Batch of Product Model | `25P + 1T` | | **Serialized Item identifier** | Individual Product | `25P + S` or `25S + VTA-SN` | | **Economic Operator ID** | Responsible legal entity | LEI, EUID or `18V + VTA-EO` | | **Facility ID** | Manufacturing location | GLN or `25L + VTA-FA` | | **EU-DPP ID** | Passport itself | `urn:uuid:{UUID}` | | **Registration ID** | EU registry entry | Assigned by EU DPP registry | --- #### Why is it important not to merge these identifiers? Because each identifier answers a different question. Product identifier **What Product is this?** Economic Operator ID **Who is legally responsible for it?** Facility ID **Where was it manufactured?** EU-DPP ID **Which digital passport is this?** Registration ID **Which EU registry entry belongs to this passport?** Using one identifier to answer all of these questions would blur fundamentally different business and regulatory objects. The SyncForce Golden Hierarchy instead maintains explicit relationships between them. --- #### How are these identifiers connected? Conceptually: **Economic Operator** ↓ responsible for ↓ **Product Model** `25P + VTA-PM` ↓ may be produced as ↓ **Batch / Serialized Item** ↓ at ↓ **Facility** and: **Product Model / Batch / Serialized Item** ↓ has EU-DPP ↓ **EU-DPP ID** ↓ registered as ↓ **Registration ID** This allows systems to navigate the complete regulatory relationship without changing the underlying identities. --- #### What role does prodigi.link play? prodigi.link resolves the persistent identity of the object to the appropriate digital resources. For example: `https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM` can resolve the Product Model to its EU-DPP. The Product identifier remains stable even when the digital destination or hosting environment changes. **Read more:** [*How does prodigi.link support EU-DPP identification and resolution?*](https://support.syncforce.com/knowledge/how-does-prodigi.link-support-eu-dpp-identification-and-resolution?hsLang=en) --- #### What is the SyncForce Golden Hierarchy principle? The SyncForce Golden Hierarchy gives each real-world and regulatory object its own appropriate identity. It does not treat: - Product - Sales Unit - legal entity - Facility - EU-DPP - registry registration as if they were the same object. Instead, SyncForce manages their relationships. This creates a scalable architecture for EU-DPP and other Product-specific regulation while retaining the commercial GTIN structure manufacturers already use. **See the full overview:** [*How does SyncForce support the EU Digital Product Passport, EU-DPP?*](https://support.syncforce.com/knowledge/how-does-syncforce-support-the-eu-digital-product-passport?hsLang=en) In one sentence **An EU-DPP uses separate identifiers for the regulated Product, responsible Economic Operator, manufacturing Facility, passport itself and EU registry registration, with the SyncForce Golden Hierarchy connecting them without merging their identities.** - [Industry & Regulatory Knowledge](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#main-content) - [Product Portfolio](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#product-portfolio) - [Packaging & PPWR](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#packaging-ppwr) - [EU Digital Product Passport - DPP](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#eu-digital-product-passport-dpp) - [GS1 & GDSN](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#gs1-gdsn) - [Food & Label Information](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#food-label-information) - [EPR & Sustainability Data](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#epr-sustainability-data) - [Product Identification & GTIN](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#product-identification-gtin) - [PIM & Data Architecture](https://support.syncforce.com/knowledge/industry-regulatory-knowledge?hsLang=en#pim-data-architecture) - [Product Data Management](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#main-content) - [Packaging Data Management](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#packaging-data-management) - [Product data imports](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#product-data-imports) - [PDM setup and config](https://support.syncforce.com/knowledge/product-data-management?hsLang=en#pdm-setup-and-config) - [Digital Asset Management](https://support.syncforce.com/knowledge/digital-asset-management?hsLang=en#main-content) - [FileConvert](https://support.syncforce.com/knowledge/digital-asset-management?hsLang=en#fileconvert) - [Project Portfolio Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#main-content) - [Team & Planning](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#team-planning) - [Proofing & Approval](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#proofing-approval) - [Budget & Spend Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#budget-spend-management) - [Resource Management](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#resource-management) - [To Do (task & actions)](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#to-do-task-actions) - [Project definition](https://support.syncforce.com/knowledge/project-portfolio-management?hsLang=en#project-definition) - [Product Catalog](https://support.syncforce.com/knowledge/product-catalog?hsLang=en) - [Media Library](https://support.syncforce.com/knowledge/media-library?hsLang=en) - [Product Data Syndication](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#main-content) - [GS1-GDSN](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#gs1-gdsn) - [DataPorts](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#dataports) - [PS in Foodservice](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#ps-in-foodservice) - [REST API](https://support.syncforce.com/knowledge/product-data-syndication?hsLang=en#rest-api) - [Document Automation](https://support.syncforce.com/knowledge/document-automation?hsLang=en) - [Exports & reports](https://support.syncforce.com/knowledge/exports-reports?hsLang=en) - [Business Network Management](https://support.syncforce.com/knowledge/business-network-management?hsLang=en#main-content) - [Single Sign-On](https://support.syncforce.com/knowledge/business-network-management?hsLang=en#single-sign-on) - [Services & Support](https://support.syncforce.com/knowledge/services-support?hsLang=en) - [Partner Support](https://support.syncforce.com/knowledge/partner-support?hsLang=en) - [General setup](https://support.syncforce.com/knowledge/general-setup?hsLang=en) - [Campaign management](https://support.syncforce.com/knowledge/campaign-management?hsLang=en) - [General](https://support.syncforce.com/knowledge/general?hsLang=en) [![Chill listening crop-3](https://support.syncforce.com/hs-fs/hubfs/SyncForce_plus_1024-2.png?width=105&height=24&name=SyncForce_plus_1024-2.png "Chill listening crop-3")](https://www.syncforce.com/) Copyright © 2026, SyncForce