---
title: How does SyncForce support the EU Digital Product Passport?
description: Learn how SyncForce Circular PIM, prodigi.link and Perennis support the EU-DPP through the SyncForce Golden Hierarchy, standards-based identifiers, persistent resolution and long-term regulatory data availability.
---

[Skip to content](https://support.syncforce.com/knowledge/how-does-syncforce-support-the-eu-digital-product-passport#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)

# How does SyncForce support the EU Digital Product Passport?

#### Short answer

SyncForce supports the EU-DPP through three complementary services:

**SyncForce Circular PIM** manages Product Models, Sales Units, Packaging Systems, regulatory data and their lifecycles.

**prodigi.link** provides persistent, standards-based identification and resolution for Product Models, Sales Units, Packaging Systems and Serialized Items.

**Perennis** provides publication and long-term persistence of regulated EU-DPP information.

The architecture is based on the **SyncForce Golden Hierarchy**, which separates Product identity, commercial identity and Packaging identity while maintaining the relationships between them. 

The fundamental principle is:

Sales Unit = Product(s) + Packaging

A Sales Unit can contain one Product, multiple Products and one Packaging System.

Those objects can have different identities, lifecycles and regulatory obligations.

That distinction is fundamental for the EU-DPP.

---

#### Why does the EU-DPP require more than a GTIN?

A GTIN identifies a commercial Trade Item or Sales Unit.

An EU-DPP may apply to a Product Model, Batch or individual Serialized Item.

These are not necessarily the same object.

Consider a laptop sold online or in a retail store.

The customer purchases:

**one Sales Unit**

with:

**one GTIN**

Inside the Sales Unit are:

- a Laptop Product Model
- a Charger Product Model
- one Packaging System

After unboxing, the laptop and charger continue their physical lives independently, while the Packaging System enters its recycling, reuse or waste lifecycle. 

The charger may also be used with several other laptop models and may later be sold separately as a replacement charger.

There is still only one Charger Product Model.

The Product Model identity therefore cannot depend on the GTIN of one particular Sales Unit. 

This results in a many-to-many relationship:

**Product Models ↔ Sales Units**

A Product Model can occur in multiple Sales Units.

A Sales Unit can contain multiple Product Models.

---

### How does SyncForce identify a Product Model for the EU-DPP?

For EU-DPP Product Model identification, SyncForce uses the ASC MH10.8.2 Data Identifier route supported by the European EU-DPP standards.

A Product Model can be identified using:

**25P + VTA Product Model ID**

For example:

`VTA-MPLA-PM-346UJI3NUM`

represented as:

`https://prodigi.link/?.25P=VTA-MPLA-PM-346UJI3NUM`

In this structure:

- **25P** identifies the Product reference
- **VTA** is the ISO/IEC 15459 Issuing Agency Code
- **MPLA** identifies the organization or namespace
- **PM** identifies the Product Model object
- the remaining value uniquely identifies the Product Model

The Product Model identity is therefore independent from GTIN, market, Packaging configuration and Sales Unit.

---

#### Can an EU-DPP exist at Model, Batch or Item level?

Yes.

The applicable Product regulation or delegated act determines the required EU-DPP granularity.

SyncForce supports:

#### Product Model

`https://prodigi.link/?.25P={VTA-PM}`

#### Batch

`https://prodigi.link/?.25P={VTA-PM}&.1T={lot}`

#### Serialized Item

`https://prodigi.link/?.25P={VTA-PM}&.S={serial}`

SyncForce can alternatively create a globally unique Serialized Item identity using:

`https://prodigi.link/?.25S={VTA-SN}`

The Product Model, Batch and Serialized Item therefore remain independent from the GTIN of the commercial Sales Unit. 

**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)

---

#### How does the Sales Unit fit into the EU-DPP architecture?

The Sales Unit remains a separate commercial object.

Its primary identifier is the GTIN.

prodigi.link supports GS1 Digital Link for the Sales Unit:

`https://prodigi.link/01/{GTIN}`

A Sales Unit can also include normal GS1 qualifiers such as:

`/10/{lot}`

or:

`/22/{CPV}`

SyncForce deliberately keeps the GS1 identifier route and the EU-DPP Data Identifier route separate.

The rule is:

> **One identifier stays within one identification system.**

A GS1 primary identifier uses GS1 Application Identifiers.

An EU-DPP Data Identifier route uses Data Identifiers.

The two identity domains can be linked through the SyncForce Golden Hierarchy without mixing their identifier syntax.

**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)

---

### How does SyncForce distinguish Sales Unit Variants and Revisions?

GTIN identifies the commercial Trade Item.

However, not every physical or information change requires a new GTIN.

SyncForce therefore uses CPV with the format:

`V001R001`

The two dimensions have different meanings.

**Variant**, such as `V001`, `V002`, `V003`, represents configurations that may exist in parallel.

Examples include:

- regular packaging
- promotional packaging
- seasonal artwork

**Revision**, such as `R001`, `R002`, `R003`, represents successive production states.

For example:

`V001R001` 30% PCR bottle

↓

`V001R002` 50% PCR bottle

↓

`V001R003` revised closure

A specific Sales Unit configuration can therefore be identified through:

**GTIN + CPV**

while the underlying Product Model retains its own EU-DPP Product identity. 

---

#### How does Packaging fit into the EU-DPP and PPWR architecture?

Packaging is another independent domain in the SyncForce Golden Hierarchy.

SyncForce distinguishes:

**Packaging Component**

**Packaging Master**

**Packaging Unit**

and:

**Packaging System**

A Packaging Component is the physical item procured or produced, such as a bottle, cap, label, tray or film.

A Packaging Master contains reusable technical and compliance information for equivalent Packaging Components.

A Packaging Unit describes the physical BOM of Packaging Components.

The Packaging System is the PPWR compliance object representing the complete Packaging configuration placed on the market.

For Packaging Systems, SyncForce uses the standardized 31B Global Unique Packaging Number mechanism.

For example:

`31B + VTA-MPLA-PS-T46GD61T`

prodigi.link can resolve the Packaging System through:

`https://prodigi.link/31B/VTA-MPLA-PS-T46GD61T`

and through the equivalent Data Identifier query representation:

`https://prodigi.link/?.31B=VTA-MPLA-PS-T46GD61T`

Both represent the same Packaging System identity. 

**Read more:** [Packaging System: a new PPWR compliance object in your Golden Hierachy](https://support.syncforce.com/knowledge/packaging-system-a-new-ppwr-compliance-object-in-your-portfolio?hsLang=en)

---

### Can one Sales Unit contain several Products with separate EU-DPP information?

Yes.

A remote-controlled car is a good example.

One Sales Unit can contain:

- the RC car
- a remote control
- a battery for the car
- a battery for the remote control
- one Packaging System

Commercially, this can still be:

**one Sales Unit**

**one GTIN**

and:

**one Marketing Landing Page**

The two batteries may nevertheless have separate regulatory information requirements.

The Sales Unit Marketing Landing Page can therefore link to separate Product-level regulatory pages.

This is **indirect access**.

The battery itself can simultaneously carry its own QR code identifying its own Product Model.

This is **direct access**.

Indirect access provides an additional consumer-friendly route. It does not replace the Product's own EU-DPP data carrier where the applicable EU-DPP rules require one. 

---

#### Is a Marketing Landing Page an EU-DPP?

No.

A QR code, identifier, resolver, Marketing Landing Page and EU-DPP are different concepts.

**QR code**  
The physical data carrier.

**Identifier**  
Identifies the Product Model, Batch, Serialized Item, Sales Unit or Packaging System.

**prodigi.link**  
Resolves an identifier to one or more digital resources.

**Marketing Landing Page**  
Provides a commercial or consumer digital experience.

**EU-DPP**  
The regulated European Digital Product Passport.

A Marketing Landing Page may display information originating from an EU-DPP or link to an EU-DPP.

That does not make the Marketing Landing Page itself the EU-DPP.

---

#### How does direct EU-DPP access work?

Where a Product has an EU-DPP at Product Model level, its physical data carrier can encode the Product Model identifier directly.

For example:

`https://prodigi.link/?.25P=VTA-MPLA-PM-BATTERY01`

The flow is:

**QR on Product**

↓

**Product Model identifier**

↓

**prodigi.link**

↓

**EU-DPP**

For public EU-DPP information, the direct EU-DPP route is designed to work without requiring an intermediate Marketing Landing Page, login or app.

---

### How are the different objects linked?

The SyncForce Golden Hierarchy maintains relationships between the different business objects.

For example:

**Sales Unit**

`containsProduct → Product Model A`

`containsProduct → Product Model B`

`usesPackagingSystem → Packaging System C`

A Product Model can expose:

`hasEUDigitalProductPassport → EU-DPP`

A Packaging System can expose:

`hasDeclarationOfConformity → Declaration of Conformity`

These relationships can also be exposed through APIs and structured data such as JSON-LD.

This allows software and AI systems to follow the same relationships that users see when navigating between digital resources. 

---

### Who is responsible for the EU-DPP?

Every EU-DPP identifies the responsible **Economic Operator**.

The Economic Operator is the legal entity responsible for placing the Product on the EU market.

SyncForce supports:

1. **LEI**
2. otherwise the national business register number expressed as **EUID**
3. otherwise a VTA Economic Operator ID using **18V**

The manufacturing **Facility** is modelled separately from the Economic Operator.

SyncForce can identify a Facility using:

**GLN**

or:

**VTA Facility ID using 25L**

This keeps legal-entity identity, physical manufacturing location and Product identity as separate concepts. 

**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.

Three different identifiers must be distinguished:

| Identifier | What does it identify? |
| --- | --- |
| **Unique Product Identifier** | The Product Model, Batch or Serialized Item |
| **EU-DPP ID** | The EU-DPP itself |
| **Registration ID** | The EU-DPP entry in the EU DPP registry |

SyncForce uses a UUID for the EU-DPP ID.

For example:

`urn:uuid:3f2b8c1e-6a4d-4e2b-9c7a-1d5e8f0a2b34`

The EU-DPP ID remains separate from the Product identifier.

The EU DPP registry subsequently returns its own Registration ID. 

**Read more:** [*Which identifiers are used in an EU-DPP?*](https://support.syncforce.com/knowledge/which-identifiers-are-used-in-an-eu-dpp?hsLang=en)

---

### What does prodigi.link do for the EU-DPP?

prodigi.link provides the persistent identification and resolution layer.

Its function is:

**persistent identifier**

↓

**prodigi.link**

↓

**one or more appropriate digital resources**

For a Sales Unit, these resources may include:

- Marketing Landing Page
- Product information
- linked Product Models
- regulatory information
- Packaging information

For a Product Model:

- EU-DPP
- Product Model information
- Battery Information Page
- repair information
- instructions

For a Packaging System:

- PPWR dossier
- Declaration of Conformity
- recycling information

The persistent identifier can remain unchanged even when the digital resource to which it resolves changes during the Product lifecycle. 

Public EU-DPP routes are kept separate from marketing functionality and are designed to work without requiring login, app installation or tracking-based marketing interactions. 

**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 does SyncForce Circular PIM do for the EU-DPP?

SyncForce Circular PIM is the operational system where Product, Packaging, Sales Unit, traceability and compliance information is created and governed.

This includes:

- Product Models
- Product specifications
- Packaging Components
- Packaging Masters
- Packaging Units
- Packaging Systems
- Sales Units
- GTIN and CPV
- Batches
- Serialized Items
- regulatory data
- technical documentation
- approvals
- compliance evidence
- EU-DPP information

SyncForce therefore manages the Product information and lifecycle relationships from which the EU-DPP is created. 

---

#### How does EU-DPP information remain available after a Product is discontinued?

The lifetime of regulated Product information can be much longer than the commercial Sales Unit lifecycle.

A Product may remain physically in use after:

- its Sales Unit is discontinued
- its e-commerce page disappears
- the manufacturer's website changes
- the PIM platform changes
- the original marketing campaign ends

Perennis provides the long-term regulatory publication and persistence layer.

The architecture is:

**SyncForce**

creates and governs Product and compliance information

↓

**prodigi.link**

maintains persistent identity and resolution

↓

**Perennis**

publishes and preserves EU-DPP information for the required period. 

**Read more:** [*How does EU-DPP information remain available after a Product is discontinued?*](https://support.syncforce.com/knowledge/how-does-eu-dpp-information-remain-available-after-a-product-is-discontinued?hsLang=en)

---

### Which European standards does SyncForce support for the EU-DPP?

The European EU-DPP architecture is defined by a family of horizontal standards.

| Standard | Scope |
| --- | --- |
| **EN 18216** | Data exchange protocols |
| **EN 18219** | Unique identifiers |
| **EN 18220** | Data carriers |
| **EN 18221** | Data storage, archiving and persistence |
| **EN 18222** | EU-DPP lifecycle and search APIs |
| **EN 18223** | System interoperability |
| **EN 18239** | Access rights, security and confidentiality |
| **EN 18246** | Authentication, reliability and integrity |

These standards define the horizontal EU-DPP infrastructure.

Product-specific regulations and delegated acts determine which information must be included, where the EU-DPP data carrier must be placed, which stakeholders can access which information and whether the EU-DPP exists at Model, Batch or Individual Item level.

**Read more:** [*Which European standards define the EU-DPP architecture?*](https://support.syncforce.com/knowledge/which-european-standards-define-the-eu-dpp-architecture?hsLang=en)

---

### What is the SyncForce Golden Hierarchy?

The simplest way to understand the SyncForce architecture is:

**We manufacture Products.**

**We procure or manufacture Packaging Components.**

**We combine Packaging Components into Packaging Units.**

**We group equivalent Packaging Components through Packaging Masters.**

**We assess the complete Packaging configuration as a Packaging System.**

**We combine Product(s) and Packaging into a Sales Unit.**

**We sell the Sales Unit using a GTIN.**

**We identify Product Models independently from that GTIN.**

**We identify Packaging Systems independently from that GTIN.**

**We use prodigi.link to connect those identities to digital resources.**

**We use Perennis when regulatory information needs to outlive the active commercial systems and pages.**

This is the **SyncForce Golden Hierarchy**, an information model designed to support PPWR, EU-DPP, the EU Battery Regulation and future Product-specific regulation without forcing fundamentally different objects and identities into a single GTIN/Sales Unit model. 

### In one sentence

**SyncForce Circular PIM manages what the Product is and how it relates to Sales Units and Packaging, prodigi.link provides persistent standards-based identity and resolution, and Perennis keeps regulated EU-DPP information available beyond the commercial lifecycle.**

- [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