DPP data carrier and Registry readiness

What this screen checks

This screen looks at Digital Product Passport implementation: the data carrier, a persistent unique product identifier, physical placement, Registry registration, a backup copy, dealer or marketplace handoff, and access before sale. It is separate from the general DPP readiness checker and from the economic-operator role checker.

Data carrier

Where a DPP is required, it is connected through a data carrier to a persistent unique product identifier. The carrier is physically present on the product, the packaging, or the accompanying documentation, following the applicable product-specific rule. This page does not pick that location.

DPP Registry

Before a covered product is placed on the EU market, the relevant economic operator registers the DPP in the Commission DPP Registry. The Registry keeps identifiers, registration data, and high-level metadata. It does not have to store the whole DPP. The Commission published a DPP Registry User Guide for Economic Operators in September 2026. This page does not copy that guide and does not state a revision number.

Unique product identifier

The product identifier is persistent and unique at the level the applicable legislation uses. This screen does not assume a model, batch, or item level.

Dealer and marketplace handoff

The operator placing the product on the market gives dealers and online marketplace providers a digital copy of the data carrier or the unique product identifier, as relevant. On request, a digital copy or a webpage link is provided promptly and in any event within five working days.

Distance selling

Distance selling may need the DPP to be reachable before the customer is bound by the contract, when the applicable delegated act requires it. If that product-specific rule is unknown, the result stays on rule review.

Backup copy

The economic operator makes a backup copy of the DPP available through a DPP service provider. A missing backup is an operational gap here. It is not called a legal violation.

Illustrative examples

Identifier, carrier, and DPP data are in place, but Registry registration is not: registry readiness gap.
Registry preparation is in place, but the data carrier is not: data carrier gap.
The technical items are in place, but the product-specific delegated act is unknown: product-specific rule review.
Distance selling is used and pre-contract access is missing: distribution or access gap.

Limits

This does not establish legal compliance, and it does not approve a Registry record. There is no numeric readiness score. Exact fields, carrier type, placement, and the model, batch, or item level depend on product-specific legislation, which this tool does not invent. A new delegated act or a Registry technical specification is a reason to update the ruleset by hand.