Skip to content
Start a passport+ {Activate} Passport
Evidence & Trust

DPP Claims Audit: What Is Actually Established?

Recurring Digital Product Passport claims checked against current EU primary sources, with the canonical Knowledge page for each full answer.

Reading time
8 min
Written by
ActivateDigital
Last verified
Published
Sources
6
Share article
LinkedIn X Email
A workbench heaped with crumpled papers and label cards with a magnifier and a canvas tote bag.
Jump around this page

In 60 seconds

This is not a myth list. It is a short audit of Digital Product Passport claims that recur in current search, vendor material and implementation conversations and can change a real business decision.

  • There is no general ESPR rule that every EU product needs a DPP from one universal 2027 date. Verdict: TOO_BROAD.
  • GS1 Digital Link as mandatory EU DPP law and a generic 10 mm DPP QR-code size are both NOT_ESTABLISHED.
  • As at 3 September 2026, Commission Implementing Decision (EU) 2026/1736 cites six DPP harmonised-standard references, not eight.
  • A final textile DPP field list has not been adopted. The Commission shows an indicative Q4 2027 adoption point.
  • Registration in the EU DPP Registry does not validate the product data. Verdict: NOT_SUPPORTED.

It separates what is established from what is too broad, product-specific or not yet supported by the strongest current source.

Each entry stays short. The linked Knowledge page covers the full explanation.

Status labels

The labels on this page are claim-audit verdicts, not our legal lifecycle/status vocabulary. They must not replace or collapse the Action Radar / methodology statuses such as APPLICABLE NOW, PROPOSED, INDICATIVE or NOT ESTABLISHED. A claim verdict answers whether a specific market statement is supportable; the linked page keeps the underlying legal status.

TOO_BROAD There is a real rule, programme or direction underneath the claim, but the claim applies it too widely or collapses several legal states into one.

NOT_ESTABLISHED The strongest current primary or official sources do not establish the claim in the form stated.

PRODUCT_SPECIFIC The answer depends on the applicable product rules rather than one generic DPP rule.

SUPPORTED_WITH_CONDITIONS The claim is supportable only with the conditions stated in the source.

OUTDATED The claim may once have described the source state but a later material source change has superseded it.

Every product in the EU needs a DPP from 2027.

Status: TOO_BROAD Last checked: 3 September 2026

There is no general ESPR rule that every EU product needs a DPP from one universal 2027 date. The Commission says DPPs are introduced product by product through the applicable rules. Working Plan years are planning signals, not one cross-market compliance deadline.

Why it matters: A universal date can make a business overbuild for product groups with no final obligation yet, while missing the categories with real adopted requirements.

Primary source: European Commission DPP FAQ Full answer: Does My Product Category Need a Digital Product Passport? Food, Cosmetics, Jewellery and Common Misstatements ; Digital Product Passport Timeline: What Applies When?

ESPR itself already requires a DPP for every product it covers.

Status: TOO_BROAD Last checked: 3 September 2026

ESPR creates the framework, but the Commission FAQ says there is no general ESPR obligation for a product to have a DPP. Whether a product needs one, what it contains and when it applies depend on the applicable product-specific rules or other legislation.

Why it matters: Framework scope and current product obligation are different procurement and compliance questions.

Primary source: European Commission DPP FAQ Full answer: Does My Product Category Need a Digital Product Passport? Food, Cosmetics, Jewellery and Common Misstatements

The EU DPP Registry stores the full Digital Product Passport or complete product dataset.

Status: TOO_BROAD Last checked: 3 September 2026

The Registry is a secure EU index/database for identifiers, registration data and high-level metadata. The Commission describes the DPP architecture as decentralised: detailed passport information is held by the economic operator or a DPP service provider under the applicable rules.

Why it matters: This changes hosting, architecture, service-provider, security and data-governance decisions.

Primary source: European Commission DPP Registry Full answer: The EU DPP Registry: what it stores and where passport data lives

An ESPR Digital Product Passport always has to use a QR code.

Status: PRODUCT_SPECIFIC Last checked: 3 September 2026

The Commission says the data carrier will be specified for each product group. QR codes and NFC are among the options considered. A QR code can be a strong practical choice without being the universal carrier rule for every future DPP.

Why it matters: Carrier choice affects packaging, printing, identity, resolver and user-journey decisions.

Primary source: European Commission DPP FAQ Full answer: 2D Product Identity Map: QR Code vs GS1 DataMatrix vs GS1 Digital Link

ESPR sets a generic 10 mm minimum DPP QR-code size, plus one generic contrast and error-correction rule, across product groups.

Status: NOT_ESTABLISHED Last checked: 3 September 2026

Current primary ESPR and Commission guidance do not establish one generic cross-product 10 mm DPP QR-size rule. Data-carrier requirements are set through the applicable product rules and technical standards. Treat vendor layout rules as implementation guidance unless the applicable legal or standards source supports them.

Why it matters: A made-up universal physical rule can create unnecessary redesign work and false assurance.

Primary source: European Commission DPP FAQ Full answer: Which Digital Product Passport standards carry a presumption of conformity? ; 2D Product Identity Map: QR Code vs GS1 DataMatrix vs GS1 Digital Link

A Working Plan or planned adoption year is the legally binding compliance deadline.

Status: TOO_BROAD Last checked: 3 September 2026

The Commission labels its DPP timeline indicative. A planned adoption period is a monitoring signal. The binding compliance/application position comes from the adopted applicable act and the dates written into it.

Why it matters: “2027” can mean planned adoption, a known statutory application date or a market shorthand. Those are not interchangeable.

Primary source: European Commission DPP hub Full answer: Digital Product Passport Timeline: What Applies When? ; How a DPP Requirement Moves from EU Planning to an Applicable Product Rule

All eight DPP standards are already cited in the Official Journal.

Status: NOT_ESTABLISHED Last checked: 3 September 2026

As at 3 September 2026, Commission Implementing Decision (EU) 2026/1736 cites six DPP harmonised-standard references: EN 18216, 18219, 18220, 18221, 18222 and 18223. The Commission timeline shows the remaining two as an indicative September 2026 watch item. Standards-body publication is not the same state as OJ citation.

Why it matters: OJ citation affects the legal standards status. Teams should not collapse “published by CEN-CENELEC” into “cited in the OJ”.

Primary source: Commission Implementing Decision (EU) 2026/1736 Full answer: Which Digital Product Passport standards carry a presumption of conformity?

A final mandatory textile DPP field list has already been adopted.

Status: NOT_ESTABLISHED Last checked: 3 September 2026

A final textile-specific DPP field list has not yet been adopted. The Commission textile/apparel page says the textile-specific DPP requirements will be defined through a future delegated act and currently shows an indicative Q4 2027 adoption point. Readiness models can still be useful, but they are not the final statutory textile field list.

Why it matters: Businesses need a practical data model before the final act, but should be able to distinguish readiness coverage from the final legal minimum.

Primary source: European Commission textile/apparel DPP page Full answer: Textile DPP Data: 22-Field Guide ; What Is a Textile Digital Product Passport?

A Digital Product Passport shows that a product is sustainable.

Status: NOT_SUPPORTED. A Digital Product Passport is a product-specific data mechanism. ESPR is sustainability legislation and the passport is intended to improve access to information, compliance checking and traceability, but the existence of the passport is not evidence that the product has achieved a sustainability outcome. A broader sustainability conclusion still needs evidence, scope, method and an applicable claim rule.

A Digital Product Passport proves that a product is recyclable.

Status: NOT_SUPPORTED as a general statement. Recyclability can be a product parameter addressed by product-specific rules, and a DPP can carry relevant material or end-of-life information. A field or declaration does not by itself verify that the finished product meets every condition behind a recyclability claim. The required information remains product-specific.

A Digital Product Passport proves that a product has a low carbon footprint.

Status: NOT_SUPPORTED. ESPR allows product-specific information requirements to relate to a carbon footprint or environmental footprint as appropriate. It does not create one universal carbon field or a universal threshold for what counts as “low carbon”. Where a carbon number exists, its meaning still depends on method, boundary, product scope, data quality and version. See Does a Digital Product Passport include a carbon footprint?.

Having a Digital Product Passport protects a business from environmental-claim or greenwashing exposure.

Status: NOT_SUPPORTED. A passport can make source information and provenance easier to govern, but environmental-claim rules apply to the marketing statement and the evidence supporting it. A mandatory disclosure is not automatically a voluntary environmental claim, while voluntary marketing built around passport data still has to satisfy the rules that apply to that claim. See EU Environmental Claims Rules from 27 September 2026 and What a Passport Field Can and Cannot Prove.

Registration in the EU DPP Registry validates the product data.

Status: NOT_SUPPORTED. The EU DPP Registry is an indexing service for identifiers, registration data and high-level metadata. It is not the store of the full passport dataset and registry presence does not amount to universal third-party validation of the information carried in the DPP. Accuracy remains an operator obligation and verification is handled through the applicable compliance and market-surveillance framework.

Why this page stays small

A claim only belongs here when there is evidence that it recurs and the correction can be grounded in a stronger current source. We do not manufacture “myths” to fill a page.

When a claim needs a long legal, standards or implementation explanation, the answer belongs on the Knowledge page that covers it. This page should remain a decision shortcut and a route into that page.

How the audit changes

A claim can move status. NOT_ESTABLISHED may become supported after a delegated act, implementing act, Official Journal citation or official guidance update. An old claim can also become OUTDATED when a source changes.

So the source date matters. “True” and “false” are often too blunt for a DPP programme that is still being implemented product by product.

ActivateDigital is not the regulator. The status labels above describe our reading of the cited current source state and link you to the underlying authority.

Keep exploring

Next question: which products actually need a Digital Product Passport, and when?

Primary sources

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.

Activate my product How a value is decided