ESPR Articles 9–15
Digital Product Passport requirements, without the hype.
ESPR defines the DPP architecture. The applicable delegated act for each product group determines the specific fields, carrier, product level and access rules.
Core design principles
- Connected through a data carrier to a persistent unique product identifier.
- Data based on open standards and, as appropriate, machine-readable, structured, searchable and transferable.
- Designed for interoperability between required digital product passports.
- Access provided according to the rights established for relevant actors.
- Stored by the responsible economic operator or a DPP service provider, subject to the applicable rules.
What data can be involved?
ESPR Annex III provides categories that product-specific rules can draw from, including unique product identifiers, GTIN where applicable, commodity codes, compliance documentation, manufacturer/importer information, instructions, operator identifiers and service-provider references.
Does every product need a DPP now?
No. ESPR is the framework. Product-specific delegated acts determine when a DPP is required for a particular product group. Separate EU legislation, such as the Battery Regulation, can also establish passport obligations.