DPPPenaltiesEU

EU Digital Product Passport penalties and enforcement

ESPR does not set one EU-wide fine table for Digital Product Passport failures. It requires Member States to set effective, proportionate and dissuasive penalties, including fines and time-limited exclusion from public procurement.

Penalty exposure depends on the applicable ESPR delegated act, the product group, the economic operator role, and the enforcement route used by market surveillance or customs authorities.

Author
Sorena AI
Published
May 9, 2026
Updated
May 9, 2026
Sections
5

Structured answer sets in this page tree.

Primary sources
2

Cited legal and guidance references.

Publication metadata
Sorena AI
Published May 9, 2026
Updated May 9, 2026
Overview

The EU Digital Product Passport is part of the Ecodesign for Sustainable Products Regulation (ESPR). For penalties, the key point is negative: the framework regulation does not publish fixed EU fine caps for passport failures. Article 74 leaves penalty rules to Member States, while setting minimum penalty types and criteria. Teams should therefore avoid quoting unsupported national amounts until the relevant Member State rules and product-specific delegated act are confirmed.

Section 1

What penalty rule applies to Digital Product Passport failures?

Article 74 of ESPR requires Member States to lay down penalties for infringements of the Regulation and to take the measures needed to implement them. Those penalties must be effective, proportionate and dissuasive.

The same article says Member States must at least be able to impose fines and time-limited exclusion from public procurement procedures. ESPR does not itself provide a single EU-level euro amount, percentage-of-turnover cap, or fixed fine range for a missing, inaccurate, inaccessible, or non-current Digital Product Passport.

  • Use Article 74 for the EU-level penalty mechanism, not for national fine amounts.
  • Treat national amounts as blocked unless a grounded national source is available for the specific Member State.
  • Separate administrative penalties from other consequences, such as corrective action, product withdrawal, recall, or customs release delays.
Recommended next step

Build a defensible DPP enforcement file

Use the penalty assessment to separate grounded ESPR duties from unresolved delegated-act and Member State enforcement questions before product release or import planning.

Section 2

Which DPP facts create enforcement exposure?

A DPP issue becomes enforceable when the product is covered by an ESPR delegated act that makes passport requirements applicable. ESPR Article 9 says products can only be placed on the market or put into service if the passport is available in accordance with the applicable delegated act and the core DPP requirements.

The delegated act matters because it defines the covered product group, the required passport data, the data carrier, whether the passport is at model, batch or item level, access rights, update rights, and how long the passport must remain available. Without that product-specific act, a penalties page cannot responsibly state a product-specific DPP fine trigger.

  • Check whether the product group is covered by an adopted ESPR delegated act.
  • Identify the economic operator placing the product on the market or putting it into service.
  • Verify whether the passport data is accurate, complete and up to date.
  • Confirm that the data carrier, unique product identifier, access rights, backup copy, and registry upload duties match the applicable delegated act.
  • Keep delegated-act uncertainty visible when advising product teams before product-specific rules are adopted.
Section 3

How can authorities enforce DPP non-compliance before imposing penalties?

ESPR enforcement is not only a fine question. Market surveillance authorities can evaluate products covered by a delegated act, require the relevant economic operator to take corrective action, and escalate if the non-compliance persists.

If corrective action is not taken or the problem continues, authorities can take provisional measures to prohibit or restrict making the product available, withdraw it from the market, or recall it. Formal non-compliance can also trigger requirements to end the problem and, if it persists, measures to restrict, prohibit, recall, or withdraw the product.

  • Document authority requests, response deadlines, corrective actions, and evidence supplied.
  • Treat a missing or unreliable passport as a product-release risk when the applicable delegated act makes the passport mandatory.
  • Do not describe a fine as the only consequence; product restrictions, withdrawal and recall can matter more operationally.
Section 4

How do customs checks change the risk profile?

For imported products covered by an ESPR delegated act, Article 15 requires the person placing the product under release for free circulation to provide or make available the unique registration identifier. Customs authorities may release the product only after checking that the identifier and commodity code correspond to registry data, once the relevant registry and interconnection are operational.

That customs check is not proof that the product complies with ESPR or other Union law. It is a gate that can expose missing registry data, mismatched identifiers, or an incomplete passport setup before goods are released.

  • Align DPP registry uploads with customs data before import workflows go live.
  • Retain the unique registration identifier, commodity code, passport link, and evidence of any customs submission.
  • Flag release-for-free-circulation risks separately from monetary penalties.
Section 5

What should not be claimed yet?

Do not publish a DPP penalties table with national fine amounts unless the Member State source is available and linked. The grounding for this page supports the EU framework rule, not country-by-country monetary caps.

Do not imply that every product already has the same DPP penalty trigger. ESPR is framework legislation, and the Commission sets concrete product rules through delegated acts after product-group analysis and consultation. The penalty assessment should therefore name the product group, the delegated act status, the relevant DPP requirement, the operator role, and the Member State enforcement rule.

  • Blocked without national source: exact fine amounts, turnover caps, criminal penalties, and authority-specific sanction bands.
  • Blocked without product-specific delegated act: exact DPP data fields, item-versus-batch-versus-model level, access rights, and update obligations for a product group.
  • Grounded now: Member States must set penalties, penalties must include fines and time-limited public-procurement exclusion, and authorities can use market surveillance and customs controls around covered products.
Primary sources

References and citations

eur-lex.europa.eu
Referenced sections
  • Article 4 and Article 8 show that concrete product-group requirements are set through delegated acts; Article 74 leaves penalty rules to Member States.
"Member States shall lay down"
Related guides

Explore more topics

Annex III Data Model Planning for EU Digital Product Passports
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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
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 Product Group Readiness
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
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
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
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
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
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
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
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.
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.
Public vs restricted EU Digital Product Passport data
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?
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?
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?
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?
DPP responsibility under the EU ESPR: how manufacturers, importers, distributors, suppliers, service providers, and delegated acts fit together.