How to Prepare an Iron & Steel DPP: Step-by-Step Mill Guide

Quick answer: Do not start by printing QR codes on coils. First, establish a reproducible data chain from raw materials → heat → cast/slab → rolling batch → coil/plate/bar → shipment. Capture product identity, grade, technical evidence, plant data and traceable emissions methods. Then test a flexible DPP publishing architecture at the granularity a customer needs, while keeping model-, batch- and item-level options open until the EU's iron and steel delegated act fixes the binding requirements.

Regulatory status, reviewed 13 October 2026: Iron and steel are priority intermediate products under Regulation (EU) 2024/1781 (ESPR). The European Commission expects a product-specific delegated act, indicatively in Q4 2026. The final covered products, attributes, required identity level and application date are not yet fixed. The general ESPR framework normally provides a transition period of at least 18 months after the relevant act enters into force, subject to the actual act. CBAM (EU) 2023/956 is a separate import-carbon framework, not itself a steel DPP mandate.

Editorial disclosure: GoodsTag provides DPP software. This article proposes practical project steps, not a claim that unadopted iron and steel DPP details are already legally binding. No specific carbon calculation method or identifier granularity is asserted to be universally mandatory here.

Step 1 - Draw a precise industrial and regulatory scope

Identify whether each site is producing pig iron, DRI/HBI, crude steel, semi-finished products, hot-rolled/flat/long products, coated products or processed finished products. List product codes, CN/commodity codes where relevant, EU import/export flows, contract ownership, site roles and end markets. Include service centres and importers in the mapping, but do not automatically classify all distributors or every steel-containing finished good as subject to a future DPP.

Create two independent compliance columns:

• ESPR iron and steel DPP candidate: pending product scope, granularity, data list and obligation date.
• Already applicable rules: CBAM import obligations where relevant, emissions/ETS, technical product standards and required customer certificates.

This separation prevents a common procurement error: implementing a CBAM reporting tool and believing it automatically creates the future steel passport.

Deliverable: product-family applicability map with owner and confidence flag: Confirmed existing obligation / Candidate pending delegated act / Outside currently evidenced scope / Legal review needed.

Step 2 - Map the heat-to-product genealogy

For many mills, the technically hardest work is not the passport page: it is joining production records across systems and transformations. Draw one complete example chain:

Raw materials + scrap lots → melt/heat H-1038 → cast batch C-19 → slab S-24 → rolling order R-51 → coils C001/C002 → shipment SH-88.

Document what happens when a heat is split into many products, a batch is combined or processed, material is returned, a coil is slit into smaller coils, or a service centre resells part of a batch. Never imply that the entire genealogy must be public: it may feed a controlled evidential record and only expose legally required outputs.

Deliverable: canonical join keys, parent-child links, edge-case transformations, and the authoritative system for each link. Test an upstream-to-downstream lookup in both directions: product to heat, and heat to products.

Step 3 - Build an evidence-first steel data model

Organise candidate data in layers and label unconfirmed data as preparation fields, not "mandatory DPP fields":

Layer	Example data to prepare	Typical system owner
Operator and plant	responsible economic operator, mill, route, manufacturing location	ERP/compliance
Product identity	product class, grade, dimensions, heat, batch, coil/plate/bar IDs	ERP/MES
Technical and quality	chemistry, mechanical properties, testing, applicable standards, inspection certificates	LIMS/QA
Traceability	scrap/raw-material lots, melt genealogy, production and downstream transformations	MES/procurement
Environmental information	energy and emissions evidence, documented boundaries, recycled-content method	Sustainability/plant data
Lifecycle documents	certificates, declarations, corrections, versions, distribution records	QA/document management

Keep the distinction between measured values, calculated results, estimated values and third-party declarations. A mill test certificate (for example EN 10204 documentation) can supply evidence but is not automatically a complete DPP. Similarly, steel EPD and product carbon footprint data cannot be pasted into the passport without checking product, site, time, allocation and boundary compatibility.

Deliverable: field dictionary mapping definition / unit / source / quality rule / publication rule / update trigger / legal status.

Step 4 - Design a trustworthy emissions and scrap-data process

Carbon questions generate some of the highest customer friction. Companies may use different scope boundaries or allocation approaches across blast furnace/basic oxygen furnace (BF-BOF), electric arc furnace (EAF), DRI and other process routes. A buyer might ask whether "low-carbon steel" means plant average, a defined product or a certificate-based allocation. Do not invent an EU steel DPP carbon accounting formula before the delegated act and its technical references settle the question.

For the pilot, record: originating plant and route; period and source of energy/fuel data; product boundary; relevant emissions methodology/version; allocation decisions and any assurance status; scrap/recycled-input provenance and mass-balance controls. Retain source evidence separately from public summaries. Provide provenance rather than unexplained low-carbon badges.

CBAM distinction: Regulation (EU) 2023/956 concerns covered imported goods, embedded emissions and declarations under a separate framework. CBAM evidence may be reused where methodologically appropriate, but a CBAM declaration is not a DPP and does not by itself resolve item-level product identity or downstream access rights.

Step 5 - Decide how physical goods link to digital identities

The future delegated act will determine the appropriate DPP granularity where required; do not hard-code "one QR per heat" or "one QR per coil" as European law. Design an identifier model that can link product type, heat, batch, delivery unit and optionally individual item. Choose a durable resolver scheme and review ISO/IEC 15459 / EN 18219 compatibility as applicable. GS1 Digital Link is one option, not proof of a universal future obligation to use GS1.

Test different physical realities:

• An individual coil with a durable tag that can survive storage and transport.
• A bundle of rebar with a shared delivery label and batch identifier.
• A bulk or semi-finished product whose documentation accompanies a shipment.
• A coil slit into two daughter coils by a service centre, preserving provenance links.

Agree who can reprint identifiers, what happens when a label is destroyed, and how a customer finds the right record after cutting, repackaging or redistribution.

Step 6 - Connect ERP, MES, laboratory systems and certificate repositories

Create a single product record from real systems. For example, import a heat from MES, associate chemistry from the lab, attach the inspection certificate from QA, connect a rolling batch and delivery from ERP, and add environmental evidence from the plant. Every field needs one source of truth; manually copying numbers between systems should be a transitional step, not the end-state architecture.

For each connection, specify frequency, error/retry handling, data format (API, event, CSV), field ownership, effective timestamp and fallback procedure. Build an exception dashboard for missing lab data, contradictory heat IDs, changed certificates and incomplete environmental records.

Minimum pilot acceptance test: a customer scans the correct QR and sees the correct product/heat, its applicable public characteristics and a controlled certificate link. An authorised user can inspect origin and supporting evidence without exposing unrelated proprietary information.

Step 7 - Handle commercial confidentiality and downstream sharing

Steel producers understandably resist sharing exact recipes, customer identities, process parameters and sensitive scrap sourcing. Separate (1) public legally required claims, (2) customer-restricted documents, (3) authority/assurance evidence and (4) non-published proprietary operational detail. The final delegated act may modify exact disclosure obligations; implement configurable permissions now.

For a processor/importer, build a handover rule for material documentation. Who can amend the original mill record? Who issues a new child record after processing? Which statements are inherited, and which need recalculation? Maintain provenance and audit logs through every change.

Industry discussions around DPP architecture repeatedly raise interoperability and governance. The CIRPASS-2 Community of Practice explicitly includes ERP, MES, PLM, PIM and DPP providers and explores compatibility and service-provider governance. That is evidence of active ecosystem work, not proof that it has prescribed one mandatory steel architecture.

Step 8 - Test versioning, backup and future regulatory change

Run five concrete scenarios: a chemistry test corrected; a coil slit; a certificate revoked/reissued; a plant carbon figure recalculated; the primary DPP platform unavailable. Each scenario should preserve an auditable change history and a working consumer/customer path. Check independent backup coverage, controlled export and hosting/QR continuity, but do not present a particular commercial retention term as a legal universal.

Set a regulatory monitoring trigger for publication of the iron and steel delegated act. On publication, revise your applicability matrix and publish policy; do not extrapolate the eventual compliance date from a working-plan target alone.

Step 9 - Launch one plant, one product family and one downstream scenario

A useful first pilot is one mill, one grade family, three heats, a realistic number of coils and one downstream service-centre/customer handoff. This samples genealogy complexity without requiring a full factory transformation. Require demonstrated evidence for the following:

• 100% of sample items resolve to the correct parent heat.
• Lab and certificate records belong to the actual production batch.
• The passport distinguishes verified values from placeholders or unverified estimates.
• Access restrictions work for customer, authority and public roles.
• Corrections propagate through version history without breaking links.
• The record is exportable and recoverable independently.

These are recommended project acceptance criteria, not numbers prescribed by the ESPR.

Critical questions from steel manufacturers

Is a Steel DPP already mandatory in October 2026?

No universal steel passport obligation is in force from that date. The relevant product-specific delegated act must first define binding requirements and application timing.

Will every steel-containing final product need a separate Steel DPP?

Do not assume so. The delegated act will define which iron and steel products are in scope; downstream products may have different sector legislation.

Heat, batch or coil: what will be the legal unit of the passport?

Not settled. Design a relational identity model now and defer binding granularity decisions until the sector-specific act is adopted.

Can an EN 10204 material certificate replace a DPP?

No. It is potentially useful evidence, but lacks the complete regulated passport functionality and connected access architecture.

Is the CBAM carbon figure the same as the DPP carbon figure?

Not necessarily. Methods, boundaries, product mapping and reporting uses differ; validate any reuse explicitly.

What if one heat produces different grades, products or shipments?

Keep split/merge genealogy and child identities, link each output to appropriate quality and environmental data, and avoid misattributing a parent-level figure to every daughter product.

Should we publish detailed alloy chemistry and supplier prices?

Only information required under relevant rules and authorised contractual sharing should be disclosed. Prepare access classification; do not treat sensitive source evidence as automatically public.

Do importers and steel service centres need to act?

They should map their economic-operator role, product flows and data handoffs now, but their eventual DPP obligations depend on the delegated act and the specific activity.

Should we commission a fully built DPP before the final rules?

A flexible data and integration pilot is justified. A costly final template that assumes unadopted data fields or QR granularity is not.

Eight-week preparation sprint - example, not statutory timing

Period	Workstream	Output
Weeks 1-2	Scope, operator roles, heat genealogy	Portfolio map and process diagram
Weeks 3-4	MES/ERP/lab/certificate data mapping	Field dictionary and gap register
Weeks 5-6	Identifier and production pilot	QR-linked sample products and controlled data
Weeks 7-8	Downstream handoff, versioning, backup, review	Signed pilot report and regulatory watchlist

Sources and related GoodsTag content

Primary EU sources: ESPR; Commission iron & steel DPP overview; ESPR Working Plan 2025-2030; CBAM Regulation (EU) 2023/956.

Industry context: CIRPASS-2 Community of Practice (interoperability, PIM/PLM/MES/ERP and provider governance); GoodsTag Iron & Steel DPP FAQ; GoodsTag regulatory timelines by sector.

Related: Compare Iron & Steel DPP solutions - General DPP implementation guide - Iron & Steel DPP solution.

Next step: Discuss an Iron & Steel DPP readiness assessment. Bring a sample heat-to-coil record, one inspection certificate and an emissions dataset; a sales presentation is not a substitute for testing the data chain.

Reviewed 13 October 2026. Proposed regulatory timelines and likely data fields must be reconfirmed on adoption of the product-specific act. This article is not legal advice.