Skip to content
Knowledge / Product Data & Architecture

Digital Product Passport & Product Data Glossary

A source-led glossary of Digital Product Passport, ESPR, Registry, standards, identity, data-carrier and freshness terms, each linked to its canonical explanation.

Last verified
Share
LinkedIn X Email
Navigate this page

This is one controlled vocabulary for the terms that most often change the meaning of a Digital Product Passport question. It is deliberately one page, not 32 thin pages. Definitions here are short. The linked canonical Knowledge page owns the deeper explanation, examples and edge cases. Where the law, standards or source version changes the meaning, the glossary entry should move with that source.

Quick index

Access rights · Adopted · Applies · CEN-CENELEC JTC 24 · Data carrier · Delegated act · Digital Product Passport · DPP Registry · DPP service provider · Economic operator · EPREL · ESPR · Granularity · GS1 Digital Link · GTIN · Harmonised standard · Implementing act · In force · Indicative timeline · Last verified · Legitimate interest · Official Journal citation · Presumption of conformity · Primary source · Proof of registration · QR code · Resolver · SCIP · Source version · Unique Product Identifier · Unique Registration Identifier · What would change this page

Access rights

Also used as: public/restricted access; role-based access Source family: Product-specific DPP law / standards

Rules determining which actors may access which DPP data.

Context: The exact rights depend on the applicable product legislation and technical implementation.

Common confusion: Assuming all DPP fields are public.

Primary/official source: https://eur-lex.europa.eu/eli/reg/2024/1781/oj Canonical Knowledge owner: Which Battery Passport Data Is Public, Restricted or Limited to Legitimate-Interest Users?

Adopted

Also used as: adoption Source family: EU legal status

The institution has formally adopted the act.

Context: Adoption is distinct from publication, entry into force and application.

Common confusion: Using adopted, in force and applies as synonyms.

Primary/official source: https://eur-lex.europa.eu/ Canonical Knowledge owner: How a DPP Requirement Moves from EU Planning to an Applicable Product Rule

Applies

Also used as: application date; applicable from Source family: EU legal status

The date from which specified provisions or obligations are to be applied.

Context: Check the exact article, product scope and transitional provisions.

Common confusion: Confusing application with adoption or planning dates.

Primary/official source: https://eur-lex.europa.eu/ Canonical Knowledge owner: How a DPP Requirement Moves from EU Planning to an Applicable Product Rule

CEN-CENELEC JTC 24

Also used as: JTC 24 Source family: European standardisation

The joint European technical committee that developed the horizontal DPP standards set requested by the Commission.

Context: Standards-body output is distinct from EU legal acts and OJ citation.

Common confusion: Treating JTC 24 statements as binding law.

Primary/official source: https://www.cencenelec.eu/news-events/news/2026/en-in-the-spotlight/2026-07-15-dpp/ Canonical Knowledge owner: DPP Standards and Presumption of Conformity

Data carrier

Also used as: QR code; NFC; 2D carrier Source family: ESPR / product-specific rule

The machine-readable carrier through which the DPP can be accessed.

Context: The permitted carrier and placement can be product-specific.

Common confusion: Treating QR as universally mandatory.

Primary/official source: https://single-market-economy.ec.europa.eu/single-market/digital-product-passport/explore-our-faqs_en Canonical Knowledge owner: 2D Product Identity Map: QR Code vs GS1 DataMatrix vs Data Matrix with GS1 Digital Link

Delegated act

Also used as: DA Source family: EU law

A Commission act that supplements or amends non-essential elements of a legislative act where the legislature has delegated that power.

Context: Use the specific legal basis and adopted text for each product group.

Common confusion: Confusing an announced adoption year with an adopted delegated act or compliance date.

Primary/official source: https://commission.europa.eu/law/law-making-process/adopting-eu-law/implementing-and-delegated-acts_en Canonical Knowledge owner: How a DPP Requirement Moves from EU Planning to an Applicable Product Rule

Digital Product Passport

Also used as: DPP Source family: ESPR / product-specific law

A set of product-specific data made electronically accessible through a data carrier under the applicable DPP rules.

Context: Exact contents, granularity, access and application date depend on the applicable legal act.

Common confusion: Treating one generic DPP data list as universal.

Primary/official source: https://eur-lex.europa.eu/eli/reg/2024/1781/oj Canonical Knowledge owner: Digital Product Passport Requirements by Product Category

DPP Registry

Also used as: EU Digital Product Passport Registry Source family: ESPR + Implementing Regulation 2026/1778

The EU registry that stores required DPP registration information, including at least unique identifiers, under the applicable rules.

Context: It is not the same thing as the complete decentralised passport dataset.

Common confusion: Calling it the central database containing the full product passport.

Primary/official source: https://eur-lex.europa.eu/eli/reg_impl/2026/1778/oj Canonical Knowledge owner: DPP Registry & Operational Infrastructure: Where Passport Data Lives and How the System Fits Together

DPP service provider

Also used as: service provider; third-party DPP provider Source family: ESPR / future delegated act / standards

A provider that performs DPP-related services under the legal and technical framework.

Context: Specific provider requirements can depend on future delegated rules.

Common confusion: Treating current vendor practice as the final legal provider regime.

Primary/official source: https://eur-lex.europa.eu/eli/reg/2024/1781/oj Canonical Knowledge owner: DPP Service Providers: What the Law Actually Requires

Economic operator

Also used as: manufacturer; importer; authorised representative where applicable Source family: EU product law

A legally defined market actor with obligations under the applicable EU product legislation.

Context: Which role carries the DPP duty depends on the applicable act and supply-chain position.

Common confusion: Assuming "brand" or "seller" always means the responsible economic operator.

Primary/official source: https://eur-lex.europa.eu/eli/reg/2024/1781/oj Canonical Knowledge owner: Who Needs a Digital Product Passport?

EPREL

Also used as: European Product Registry for Energy Labelling Source family: EU product-data system

The EU registry used for products subject to energy-labelling/ecodesign registration requirements.

Context: It is a separate system from the DPP Registry, though reuse/interoperability questions can arise.

Common confusion: Assuming a DPP automatically replaces EPREL.

Primary/official source: https://energy-efficient-products.ec.europa.eu/eprel_en Canonical Knowledge owner: DPP vs EPREL: Does EPREL Replace, Feed or Sit Alongside a Digital Product Passport?

ESPR

Also used as: Ecodesign for Sustainable Products Regulation; Regulation (EU) 2024/1781 Source family: EU law

EU framework regulation for ecodesign requirements across product groups, including the DPP framework.

Context: It is a framework; product-specific obligations are set through applicable rules.

Common confusion: "ESPR applies" is not the same as "this product already needs a DPP".

Primary/official source: https://eur-lex.europa.eu/eli/reg/2024/1781/oj Canonical Knowledge owner: How a DPP Requirement Moves from EU Planning to an Applicable Product Rule

Granularity

Also used as: model-level; batch-level; item-level Source family: DPP architecture / product-specific rule

The level at which a passport/identifier applies, such as model, batch or individual item.

Context: The required level can vary by product/regime.

Common confusion: Assuming item-level serialization for every DPP.

Primary/official source: https://eur-lex.europa.eu/eli/reg/2024/1781/oj Canonical Knowledge owner: Model, Batch or Item Level for a Textile Passport

GTIN

Also used as: Global Trade Item Number Source family: GS1 identifier

A GS1 identification key for trade items.

Context: Whether it is the chosen/required DPP product identifier depends on the applicable system/rules.

Common confusion: Treating every UPI as automatically a GTIN.

Primary/official source: https://www.gs1.org/standards/id-keys/gtin Canonical Knowledge owner: GS1 Application Identifiers for Digital Product Passports: GTIN, Batch, Serial, Expiry and Variant

Harmonised standard

Also used as: European harmonised standard Source family: EU standardisation

A European standard whose reference can be published in the Official Journal for the relevant EU legislation, potentially supporting presumption of conformity for covered requirements.

Context: Publication by CEN/CENELEC and OJ citation are distinct events.

Common confusion: Calling every EN standard "harmonised" before OJ citation.

Primary/official source: https://single-market-economy.ec.europa.eu/single-market/goods/european-standards/harmonised-standards/digital-product-passport-dpp_en Canonical Knowledge owner: DPP Standards and Presumption of Conformity

Implementing act

Also used as: IA; implementing regulation; implementing decision Source family: EU law

A Commission act setting uniform conditions for implementing legally binding EU acts.

Context: Form and effect depend on the specific implementing act.

Common confusion: Treating every Commission implementation document as guidance.

Primary/official source: https://commission.europa.eu/law/law-making-process/adopting-eu-law/implementing-and-delegated-acts_en Canonical Knowledge owner: How a DPP Requirement Moves from EU Planning to an Applicable Product Rule

In force

Also used as: entry into force Source family: EU legal status

The legal act has entered into force under its own provisions.

Context: A provision can be in force before its obligations apply to businesses.

Common confusion: Assuming in force means immediate compliance deadline.

Primary/official source: https://eur-lex.europa.eu/ Canonical Knowledge owner: How a DPP Requirement Moves from EU Planning to an Applicable Product Rule

Indicative timeline

Also used as: indicative date; planned adoption Source family: Commission planning

A non-binding planning date or window that can change and remains subject to the relevant legal/publication process.

Context: Do not present as a compliance deadline.

Common confusion: Turning Working Plan/DPP hub years into fixed legal dates.

Primary/official source: https://single-market-economy.ec.europa.eu/single-market/digital-product-passport_en Canonical Knowledge owner: Digital Product Passport Timeline: What Applies When?

Last verified

Also used as: verification date Source family: ActivateDigital editorial governance

The date an ActivateDigital editor/reviewer genuinely checked the page's material current claims against the relevant primary/official sources.

Context: It is not the build date, publication date or source update date.

Common confusion: Using dateModified as proof the law was rechecked.

Primary/official source: https://single-market-economy.ec.europa.eu/single-market/digital-product-passport_en Canonical Knowledge owner: How ActivateDigital Determines DPP Regulatory Status and Uses Sources

Legitimate interest

Also used as: legitimate-interest user Source family: Product-specific access rules

A legal/access concept used in certain DPP contexts to determine access beyond public data.

Context: Meaning and evidence requirements depend on the applicable act.

Common confusion: Treating it as a generic self-declared user role.

Primary/official source: https://eur-lex.europa.eu/ Canonical Knowledge owner: Which Battery Passport Data Is Public, Restricted or Limited to Legitimate-Interest Users?

Official Journal citation

Also used as: OJ citation; OJEU citation Source family: EU standardisation/legal status

Publication in the Official Journal of a reference to a harmonised standard under the relevant legal framework.

Context: Check the exact implementing decision and reference/version.

Common confusion: Equating standards-body release with OJ citation.

Primary/official source: https://eur-lex.europa.eu/eli/dec_impl/2026/1736/oj Canonical Knowledge owner: DPP Standards and Presumption of Conformity

Presumption of conformity

Also used as: PoC Source family: EU product law / harmonised standards

A legal effect that may arise for requirements covered by cited harmonised standards when the conditions of the applicable law are met.

Context: It applies to covered requirements, not an automatic blanket certification of the product.

Common confusion: "Uses a harmonised standard" = fully compliant with all product law.

Primary/official source: https://eur-lex.europa.eu/eli/dec_impl/2026/1736/oj Canonical Knowledge owner: What the Six Published DPP Standards Actually Cover

Primary source

Also used as: primary authority; official source Source family: ActivateDigital editorial governance

The strongest direct legal, official, standards-body or authoritative system source supporting the page's central current claim, labelled by source layer.

Context: "Primary" does not mean every source has equal legal status.

Common confusion: Calling industry guidance a legal authority.

Primary/official source: https://eur-lex.europa.eu/ Canonical Knowledge owner: How ActivateDigital Determines DPP Regulatory Status and Uses Sources

Proof of registration

Also used as: registration evidence Source family: DPP Registry / legal status

Evidence that a required registration step has been completed in the DPP Registry.

Context: Registration/Registry identifier is not, by itself, proof that the product complies with all applicable EU law.

Common confusion: Treating Registry response as a compliance certificate.

Primary/official source: https://eur-lex.europa.eu/eli/reg/2024/1781/oj Canonical Knowledge owner: DPP Proof of Registration: What It Actually Proves

QR code

Also used as: 2D barcode Source family: Implementation technology

A two-dimensional barcode that can be used as a DPP data carrier where the applicable rules allow or require it.

Context: QR-specific print/size rules are not automatically universal ESPR rules.

Common confusion: Treating vendor/GS1 print guidance as EU law.

Primary/official source: https://single-market-economy.ec.europa.eu/single-market/digital-product-passport/explore-our-faqs_en Canonical Knowledge owner: 2D Product Identity Map: QR Code vs GS1 DataMatrix vs Data Matrix with GS1 Digital Link

Resolver

Also used as: link resolver; Digital Link resolver Source family: Web/DPP implementation

A service that maps an identifier or web-addressable identifier to one or more relevant information resources/services.

Context: Resolver behaviour is technical architecture, not itself proof of legal compliance.

Common confusion: Confusing resolver, Registry and DPP host.

Primary/official source: https://ref.gs1.org/standards/digital-link/ Canonical Knowledge owner: GS1 Digital Link for Digital Product Passports: What It Is and Whether You Need It

SCIP

Also used as: Substances of Concern In articles as such or in complex objects (Products) Source family: ECHA / Waste Framework Directive system

ECHA database for information on substances of concern in articles under the applicable legal framework.

Context: It is separate from DPP and has its own data/operational rules.

Common confusion: Assuming DPP automatically replaces SCIP or that all SCIP data becomes public DPP data.

Primary/official source: https://echa.europa.eu/scip-database Canonical Knowledge owner: DPP vs SCIP: Does a Digital Product Passport Replace a SCIP Notification?

Source version

Also used as: document version; source update date Source family: ActivateDigital editorial governance

The exact version/publication metadata of a versioned dependency, recorded separately from the host page's own update date where those differ.

Context: Not every source has a version number; for laws use legal status/amendment/consolidation information instead.

Common confusion: Collapsing a PDF version and Commission web-page update date into one ambiguous date.

Primary/official source: https://single-market-economy.ec.europa.eu/single-market/digital-product-passport_en Canonical Knowledge owner: How ActivateDigital Determines DPP Regulatory Status and Uses Sources

Unique Product Identifier

Also used as: UPI; product identifier Source family: ESPR / DPP standards

A unique identifier used to identify the product at the granularity required by the applicable DPP rules.

Context: Do not assume a specific identifier scheme without the applicable rule/standard.

Common confusion: Equating UPI automatically with GTIN in every regime.

Primary/official source: https://eur-lex.europa.eu/eli/reg/2024/1781/oj Canonical Knowledge owner: Barcodes and Product Identifiers: What You Need

Unique Registration Identifier

Also used as: Registry URI; registration identifier Source family: Registry Implementing Regulation

An identifier communicated by the DPP Registry after required registration data is uploaded for a specific product registration.

Context: Do not confuse with the public web URL or product identifier.

Common confusion: URI can mean Uniform Resource Identifier in web standards, so context matters.

Primary/official source: https://eur-lex.europa.eu/eli/reg_impl/2026/1778/oj Canonical Knowledge owner: How to Register a DPP in the EU Registry, and What Happens After Submission

What would change this page

Also used as: review trigger; watch trigger Source family: ActivateDigital editorial governance

A named official event or source change that would require the page's current conclusion to be checked.

Context: Must be specific enough to monitor.

Common confusion: Vague "we are watching regulation" copy.

Primary/official source: https://eur-lex.europa.eu/content/help/my-eurlex/my-rss-feeds.html?locale=en Canonical Knowledge owner: How ActivateDigital Determines DPP Regulatory Status and Uses Sources

Why one glossary

The search and AI value comes from stable names, aliases and definitions resolving to one canonical owner. Splitting each term into a separate page would create thin content, duplicate stronger articles and make the entity graph harder to govern.

If a term becomes large enough to deserve substantive treatment, the existing canonical owner is where that depth belongs. The glossary entry should continue to act as the compact definition and routing node.

Keep exploring

Next question: how does a term on this page become an obligation for a product?

Does this reach your products?

Give ActivateDigital one product and it works out which obligations apply from the product's own character, and says which it cannot decide.

Worth sharing?

Help someone else make sense of product passports.

LinkedInXEmail

Primary sources