Artifact GuideEU

EU Digital Product Passport (DPP) Deadlines & Compliance Calendar

Turn ESPR milestones into calendar entries your teams can ship against.

Includes registry and customs readiness, delegated act timing constraints, and audit/evidence cadence planning.

Back to main artifact Review sources

Author

Sorena AI

Published

Mar 4, 2026

Updated

Mar 4, 2026

Sections

Structured answer sets in this page tree.

Primary sources

Cited legal and guidance references.

Publication metadata

Sorena AI

Published Mar 4, 2026

Updated Mar 4, 2026

Overview

DPP timelines are product-group specific (driven by delegated acts), but ESPR provides hard anchors that your program should calendarize now: entry into force, working-plan sequencing, delegated act constraints, registry deadline, and the portal and customs system dependencies. This page turns those anchors into a compliance calendar template.

Section 1

Hard anchors from ESPR (dates you can put on a calendar today)

Even before your product group is covered by a delegated act, ESPR sets baseline milestones that affect architecture and readiness planning.

Use these anchors to plan platform capability build-out and supplier onboarding.

18 Jul 2024: ESPR entered into force (20 days after publication in the Official Journal on 28 Jun 2024).
19 Apr 2025: deadline for the Commission to adopt the first ESPR working plan.
Apr 2025: first ESPR working plan for 2025-2030 released, giving the first concrete signal on which product groups will move first.
19 Jul 2025: the first delegated act adopted under ESPR Article 4 must not enter into force before this date (timing constraint on product-group rules).
By 19 Jul 2026: Commission must set up the EU digital product passport registry storing at least unique identifiers (and commodity codes for release-for-free-circulation products).

Recommended next step

Operationalize EU Digital Product Passport (DPP) Deadlines & Compliance Calendar across ESG workflows

ESG Compliance can take EU Digital Product Passport (DPP) Deadlines & Compliance Calendar from planning deadlines, owners, and milestones from this page to a reusable workflow inside Sorena. Teams working on EU Digital Product Passport (DPP) can keep owners, evidence, and next steps aligned without copying this guide into separate documents.

ESG workflow

Open ESG Compliance for EU Digital Product Passport (DPP) Deadlines & Compliance Calendar

Start from EU Digital Product Passport (DPP) Deadlines & Compliance Calendar and manage cross team sustainability work, reporting, and evidence from one workflow.

Explore next step

Talk to Sorena

Talk through EU Digital Product Passport (DPP)

Review your current process, evidence gaps, and next steps for EU Digital Product Passport (DPP) Deadlines & Compliance Calendar.

Explore next step

Section 2

Current DPP program milestones (what changed after ESPR entered into force)

The period after ESPR entry into force matters because the Commission has already started defining the operating model for DPP service-provider storage and governance.

Use these dates as program-governance milestones, even if your delegated act is still pending.

9 Apr 2025: the Commission launched a public consultation on future DPP rules for service providers.
1 Jul 2025: deadline for feedback to that service-provider consultation.
2028: the first ESPR working plan is expected to be reviewed and revised, which can shift product-group sequencing and DPP rollout expectations.

Section 3

Your DPP calendar template (per product group / per DPP level)

Delegated acts specify DPP level (model/batch/item), carrier details, access rights, and availability period. Your calendar should mirror that.

Create a calendar per product group and per DPP level - item-level DPP typically requires more lifecycle events.

T0: delegated act adopted (start "requirements finalization" and gap assessment).
T0 + internal lead time: data model freeze (Annex III subset), identifier scheme, and carrier design freeze.
T0 + implementation window: portal and access control build + integration with source systems (PLM/ERP/labeling/compliance docs).
Go-live readiness: pre-purchase access in store and distance selling; audit logging; evidence pack ready.
Ongoing: update workflows for new versions, repairs/refurbishment updates where required, and data quality monitoring.

Section 4

Registry readiness milestones (Article 13 + customs dependency chain)

ESPR introduces an EU registry and a unique registration identifier associated with uploaded unique identifiers. That identifier becomes a compliance control surface for customs once operational.

Treat registry integration like a payment integration: it affects go-live sequencing, error handling, and operational SLAs.

Plan upload pipeline: unique identifiers (and any additional registry data specified in delegated acts) must be uploaded by the economic operator placing the product on the market.
Plan for the unique registration identifier response: store it, version it, and expose it where required for customs workflows.
Customs: once registry operational, release for free circulation requires providing/making available the unique registration identifier; customs verify electronically and automatically when interconnections are operational.

Section 5

Customer access deadlines (pre-purchase access and distance selling)

Delegated acts must specify how the DPP is made accessible to customers before they are bound by a contract - including distance selling.

This requirement should be translated into explicit product deliverables and tests.

In-store: data carrier scannable and positioned per delegated act; public DPP view accessible without unnecessary friction.
Online: product pages must expose the DPP public view and unique identifier (or a link), with consistent access rights and stable URLs.
Operational control: ensure dealers/online marketplaces can receive a digital copy of the carrier/identifier or link quickly (Article 10 obligations).

Section 6

Audit and evidence cadence (how to stay compliant after launch)

ESPR requires DPP data to be accurate, complete and up to date. That implies governance, monitoring, and periodic review.

Treat this as an operating cadence: you don't "finish" a DPP - you operate it.

Monthly: data quality checks for high-risk fields (compliance docs, operator IDs, manuals, identifiers).
Quarterly: access rights review and security/privacy review, especially for restricted data and credentials.
Annually (or per delegated act): evidence refresh and sampling audits for traceability and authenticity (registry linkage, identifier resolvability).

Primary sources