EU Digital Product Passport requirements are not one universal checklist. The ESPR sets system-level requirements, while delegated acts and sector legislation decide which product groups need a passport, what data it contains, who can access it and when the duty starts.
What does the ESPR require from the DPP system?
The passport must connect a persistent unique product identifier to a data carrier, use interoperable formats, enforce the access rights in the applicable act and remain available for the required period. Passport data must be accurate, complete and current.
Where do product-specific fields come from?
A delegated act or sector regulation defines the product scope, identifier granularity, required data, access groups and application date. Treat a generic template as preparation, not as proof that a particular product is compliant.
What should an implementation checklist cover?
Record the legal source and version, responsible economic operator, product and facility identifiers, carrier placement, public and restricted fields, evidence owner, review gate, hosting and backup arrangements, retention period and update process.
Frequently asked questions
Does the ESPR already require a DPP for every product?
No. Product-specific delegated acts are needed to apply ESPR passport requirements to a product group.
Who is responsible for DPP accuracy?
The responsibility follows the applicable law and economic-operator role; using a service provider does not turn the provider into a regulator or certifier.