How ready are you for the Digital Product Passport?

Now

• Map every product line to its regulatory category and delegated actAll products · Obligations start per product group, not company-wide.
• Name an accountable DPP owner across compliance, product and ITAll products · Passport data spans several departments.
• Decide identifier granularity (model, batch or item) and a GS1-compatible schemeAll products · Delegated acts set granularity; identifiers are hard to change later.

Next 6 months

• Inventory existing product data: BOMs, declarations, test reports, supplier certificatesAll products · Most passport fields reuse evidence you already hold.
• Add data-sharing clauses to supplier contractsAll products · Material and origin data usually comes from upstream.
• Secure a domain you control for QR/NFC resolver linksAll products · Printed codes must keep working for the product's lifetime.
• Define public vs. restricted data tiers (consumers, repairers, authorities)All products · ESPR requires differentiated access rights.

Before deadline

• Pilot a passport on one product line and test scanning end-to-endAll products · Pilots expose data gaps before enforcement does.
• Contract for full machine-readable export and an independent backup copyAll products · ESPR requires passport continuity if a provider fails.
• Confirm registry identifiers are available for customs checks on importsAll products · Customs will verify against the EU registry (Art. 15).