CEN-CENELEC’s Digital Product Passport framework: evidence infrastructure before industrial automation

External-source research synthesis, not an OfferSignal client result. Based on the retained October 2026 research and source-specific dates.

A steel beam, fabricated frame or container can carry extensive evidence without making that evidence usable at the moment of a bid. Material grade, dimensions, recycled content, tests, certificates and traceability may sit across different systems and revisions. The business problem is therefore not simply creating a QR code. It is preserving identity, provenance and permissions so that a buyer, engineer or regulator can find the right evidence without treating it as authority to quote or approve.

What CEN-CENELEC established

CEN-CLC/JTC 24 is developing the horizontal technical framework for Digital Product Passports under the European Union’s Ecodesign for Sustainable Products Regulation (ESPR), Regulation (EU) 2024/1781, and Standardization Request M/604. The first CEN-CENELEC series contains eight product-agnostic standards: exchange protocols, unique identifiers, data carriers, storage and persistence, lifecycle and search APIs, interoperability, access rights/security/business confidentiality, and authentication, reliability and integrity. 1

CEN-CENELEC reported that six of the eight standards had been cited in the Official Journal as of 15 July 2026. The remaining two were expected to receive an implementing decision in November 2026. These are framework and regulatory milestones, not evidence that a steel producer has improved win rate, quote cycle, quality or revenue. 1

The intended flow is concrete: a source record is linked to a persistent model, batch or item identifier; a physical carrier such as a QR code points to a unique identifier or URI; registry metadata identifies the product, operator and facility; an operator or service provider stores the operational data; and a role-based API or search service exposes permitted information for a human decision. ESPR calls for open, interoperable, machine-readable, structured, searchable and transferable data without vendor lock-in. It does not provide RFQ, CPQ, quote approval, contracting, ordering, logistics, invoicing or maintenance functions. 2

Sector requirements are still being defined

For iron and steel, the European Commission says a future delegated act may address product identification and classification, technical and material data, recycled content, sustainability attributes, compliance and traceability documentation. The indicative timing at the research cutoff was Q4 2026. The fields, units, granularity, access roles and transition rules were not final. 3

Construction follows a separate path. CEN-CENELEC’s 2026 work programme supports the Construction Products Regulation (CPR) 2024/3110 and a common technical language among manufacturers, regulators, designers and contractors. The Commission indicated construction-product DPP requirements for Q2 2027. 2 These dates describe expected policy and standards work, not completed sector implementations.

The architecture is deliberately hybrid. The Commission registry holds identifier information, while operational product data, persistence and backup can be delegated to third-party providers. Access is governed by legitimate interest and product-group rules, with protections for confidential business information and personal data. ESPR requires customer personal data only with explicit consent and requires a free digital carrier or identifier copy to dealers and marketplaces within five working days after request. 1 2

What this can—and cannot—do for custom manufacturing

For a made-to-order beam, frame, container or subassembly without a conventional stock-keeping unit, a persistent item or batch identity could link material grade, dimensions, tests, declarations, certificates and later maintenance evidence. That is a useful foundation for a reviewed bid evidence pack. It need not expose drawings, capacity strategy or commercial price logic to every reader.

This is an illustrative application, not a reported deployment. A manufacturer could pilot one product family by preserving the source, revision, units, timestamp, authority, certificate scope and authentication behind its identifier. A buyer-facing view could expose approved evidence; an internal view could support engineering review. The authoritative systems would still be ERP, product lifecycle or document management, customer/quoting systems and named human owners. Permissions do not authorise a price approval, revision change, capacity promise or contract acceptance.

The failure chain is also practical: a wrong identifier can point to the wrong revision or batch, which can imply an incompatible material or tolerance, stale certification or stale capacity, and then a false pre-vetting result or unauthorised release. The framework does not, on the cited evidence, search archived drawings, check weld or tolerance constraints, match equipment capability, validate current capacity or generate a quote.

Test the evidence layer before granting authority

Start with one steel or construction family and test identifier accuracy, revision conflicts, permissions, stale certificates, cross-border fields and backup recovery. Measure source-linked retrieval and reviewer correction, not just whether a carrier resolves to a page. Include near-duplicate batches, expired documents and conflicting units. Keep the final engineering, quality and commercial decisions with their named owners.

No cited source names a live steel or construction customer implementation that converted a request into an approved quote, accepted offer, order, quality release, invoice or maintenance result. No bid-win, quote-cycle, defect, revenue or aftersales metric was found. CEN-CENELEC’s efficiency and data-exchange statements are intended benefits of the framework, not measured sector outcomes. The useful lesson is enabling compliance and interoperability infrastructure—not an autonomous sales workflow.

Sources and next reading

Explore OfferSignal · Focused Business & AI Workshop · All research

References