What is a Digital Product Passport?

Plain meaning

In the EU context, a Digital Product Passport is not just a QR page or a marketing transparency page. It is a structured product information system that can become mandatory when a product-specific delegated act under ESPR requires it.

What is already fixed

The ESPR fixes the architecture: a passport can be required for a product group, it must stay accurate, complete and up to date, and it must connect a data carrier to a persistent unique product identifier.

• The delegated act decides which data goes in the passport.
• The data carrier can be on the product, packaging, or accompanying documentation depending on the product act.
• Passport data must be structured, searchable, interoperable, and transferable without vendor lock-in.

What is not fixed for every category

Final field lists, public/private access rights, model-versus-batch-versus-item level, passport lifetime, and category deadlines are not identical across products. Treat those as product-category questions, not one universal DPP checklist.

Why operators should still prepare

The useful early work is internal: product identifiers, material and component data, supplier evidence, proof behind public claims, access rights, and update responsibility. None of that work is wasted if the final rules differ.

Editorial rule for DPP Atlas

A claim is not treated as official unless it traces back to legal text, a Commission working plan, a delegated act, or another primary source. Vendor claims and preparation advice are kept in separate lanes.