Companies report under the CSRD. Products will carry passports under the ESPR. Underneath, both regimes ask for much of the same material: what a product is made of, where its inputs came from, how much carbon and waste sit behind it, and what happens at the end of its life. Collected twice, by two teams, that material becomes two versions of the truth. Collected once, it becomes a data backbone.

Two laws, two units of account

The Corporate Sustainability Reporting Directive, Directive (EU) 2022/2464, works at the level of the undertaking and the group. It amended Directive 2013/34/EU to require a sustainability statement in the management report (Articles 19a and 29a), prepared under the European Sustainability Reporting Standards (ESRS) and built on double materiality: the undertaking’s impacts on people and the environment, and how sustainability matters affect the undertaking itself.

The Digital Product Passport under the ESPR, Regulation (EU) 2024/1781, works at the level of the product. Articles 9 to 11 require a persistent record, tied to a unique product identifier, at the model, batch or item level the delegated act chooses (Article 9(2)(d)), with access tiered by role. Same factory, two lenses: one asks how the company performed this year, the other asks what this product is, for its whole life.

What changed in 2026

Any honest map must start with the recalibration. The “stop-the-clock” Directive (EU) 2025/794 postponed the second reporting wave to financial years starting on or after 1 January 2027. Then the Omnibus I Directive (EU) 2026/470 of 24 February 2026, in force since 18 March 2026, narrowed mandatory CSRD reporting to undertakings and groups with more than 1,000 employees on average and net turnover above EUR 450 million, and removed listed SMEs from the scope. Undertakings below both thresholds fall outside mandatory reporting from financial years starting on or after 1 January 2027; Member States transpose the CSRD changes by 19 March 2027, and assurance stays at the limited level. The revised ESRS followed: Delegated Regulation (EU) 2026/1563 entered into force on 10 November 2026 and applies to financial years beginning on or after 1 January 2027.

One consequence is routinely misread. Leaving the CSRD scope does not remove product duties: the ESPR and battery passports are product law, independent of company size thresholds, and customers who do report will still request product data from their value chain.

Where the data overlaps

Data familyCompany reporting (ESRS)Product passport (ESPR)
Climate & energyE1: transition plan, energy use, gross Scope 1, 2 and 3 emissionsProduct carbon footprint; for batteries, the Article 7 declaration per model, per plant
Materials & circularityE5: resource inflows, outflows for products and services, and wasteComposition, recycled content, recyclability and dismantling data
Value chainESRS 1, Chapter 5: own operations plus upstream and downstream chainOperator and facility identifiers for the actors and plants behind the product

Read E5 closely and the overlap is concrete: E5-4 asks for the total mass of key materials consumed, with the shares of secondary, reused, recycled and biomass materials — the same supplier file a passport needs for composition and recycled content. E1-8 asks for gross Scope 1, Scope 2 (location- and market-based) and Scope 3 emissions; the product footprint is the same carbon logic, cut per model and per plant instead of per group.

Where they differ: share data, not outputs

  • Test: double materiality (ESRS 1, paragraphs 35 to 38: material if it is material for impact or for finance, or both) versus product-level data duties set by a delegated act;
  • Check: limited assurance of an annual statement versus registration in the EU registry and verification by customs (ESPR Articles 13 and 15) — and the registration identifier is expressly not proof of compliance;
  • Rhythm: a yearly statement versus a persistent passport that must remain available, including after the operator’s insolvency (Article 11).

The conclusion is precise: build one data layer, and keep the two outputs — the assured statement and the product record — formally distinct.

The value chain is the shared bottleneck

Both regimes interrogate suppliers, and Omnibus I now disciplines how far that can go. Under Directive (EU) 2026/470, a reporting undertaking may not require from a protected undertaking in its value chain — one with up to 1,000 employees — more than the voluntary reporting standard allows, and the protected undertaking may refuse the excess. Where value-chain information is not available after reasonable efforts, the revised ESRS allow the gap to be explained and estimates, including sector averages and proxies, to be used (ESRS 1, paragraphs 73 to 75). The practical rule follows: ask each supplier once, at product level, in a structured format, inside the cap — and reuse the answer for both regimes.

What companies should do now

  • Map products against topics: start with E1 and E5, the two ESRS that share the passport’s data families;
  • Use one data dictionary: product, operator and facility identifiers shared by reporting and passports alike;
  • Collect at source, per model and plant: not as a year-end spreadsheet reconstruction;
  • Keep versions as evidence: assurance and passport integrity both fail on untraceable edits.

How Ledger Consortium helps

Ledger Consortium aggregates the product data held by you and your suppliers, anchors each record on a governed blockchain — timestamped and tamper-evident — and keeps it updated as the rules land. Anchoring proves a record existed and has not been altered; it does not certify that the data a client supplied was true — accuracy remains the operator’s responsibility. Costs are predictable, there is no token and no crypto exposure, and the platform is GDPR- and eIDAS-aligned. In Italy, the Ledger DPP is distributed by Il Sole 24 Ore (Valore24), whose channel onboards dozens of companies per month. See a working passport in our live demo, browse News, and read the identifier layer it rests on in Unique Identifiers, Explained.