# Steel and Aluminium Carbon Data: EPD, PCF, CBAM and Facility Emissions

Source: https://activatedigital.ai/knowledge/evidence/metals-carbon-data-epd-pcf-cbam
Last verified: 10 September 2026
Summary: Compare EPD, product carbon footprint, CBAM embedded-emissions and facility figures for steel and aluminium, including when data can be reused and when scope blocks substitution.

## Direct answer

An Environmental Product Declaration, a Product Carbon Footprint, CBAM embedded emissions and an installation or facility emissions figure are different evidence objects. Each can be valid and still be the wrong evidence for another field.

Steel and aluminium businesses can hold several carbon numbers for the same material at the same time. The difficult part is not finding a unit such as kg CO2e. It is deciding whether two figures describe the same subject, method, boundary, period and purpose closely enough for one to support the other.

Do not reuse a carbon value just because the number and unit look compatible. First match the methodological basis, system boundary, declared or functional unit, material scope, granularity, facility scope, reporting period, allocation method, energy treatment, verification status and intended purpose.

There are then four sensible outcomes:

- **Direct reuse:** the destination asks for the same fact and the source evidence matches the required method, scope, unit, period and binding.
- **Re-binding:** the evidence can support an assertion about a particular product only because separate evidence proves that the product sits inside the source declaration's scope. Re-binding does not turn an average into a batch measurement.
- **Transformation or recalculation:** the underlying activity data can be reused, but the result must be recalculated or transformed under the destination method.
- **Separate evidence:** the methods, boundaries, granularity or legal purpose are different enough that the source result must remain a separate object.
That is the core rule for both metals: **reuse inputs where they are genuinely reusable, but do not silently substitute outputs.**

## Four carbon objects side by side

The labels are easy to collapse because all four may eventually be expressed as greenhouse-gas quantities or intensities. Their evidence jobs are different.

| Evidence object | What it is trying to answer | Typical subject and boundary | Granularity and period | Verification and purpose | Main reuse risk |
|---|---|---|---|---|---|
| **Environmental Product Declaration (EPD)** | What environmental results does a declared product or product group have under a stated EPD programme, PCR and lifecycle-module structure? | A declared product, family or range, sometimes linked to one or more production sites. The declared unit and lifecycle modules are part of the result. | Often product or family level. Validity and reference data periods are declaration-specific. | Programme rules commonly include independent verification. Its purpose is an environmental declaration, often for market or construction information. | Treating a family or site declaration as the measured result for an exact delivered batch. |
| **Product Carbon Footprint (PCF)** | What greenhouse-gas result is assigned to a product under a stated footprint method and boundary? | A product, product group or sometimes a more specific production object. Boundaries may be cradle-to-gate, cradle-to-grave or another defined scope. | Depends on the method and declaration. The reference period, data quality and production scope matter. | Assurance varies by scheme. ISO 14067-based evidence can be verified, but verification remains tied to the declared scope. | Assuming any PCF is equivalent to an EPD climate-change indicator or to a regulatory emissions calculation. |
| **CBAM embedded emissions** | What embedded emissions must be determined for covered imported goods under the Carbon Border Adjustment Mechanism? | The covered goods, production processes, installation data and relevant precursors under the CBAM legal method. | Bound to the CBAM reporting and compliance framework. Actual and default-value routes are distinct. | Current definitive-period rules include calculation, verification, verifier and Registry controls. The purpose is CBAM compliance. | Copying EPD or PCF results into a CBAM field without a valid methodological bridge. |
| **Installation or facility emissions** | What emissions are associated with a site or installation over a period under the relevant accounting or monitoring basis? | A facility, installation, process or source set. It is not automatically a product result. | Site and reporting-period level unless a governed allocation creates a product result. | Can contain measured, calculated or modelled components depending on the system. Its purpose may be regulatory, operational or corporate. | Substituting a site total or site intensity for a product value without allocation and product binding. |

A verification mark does not erase those differences. Verification tells you that an object was checked against its own rules and scope. It does not certify that the result is valid for a different method or regulatory purpose.

EPDs and PCFs are also commonly calculation outputs rather than physical measurements of an individual coil, billet or ingot. Facility records can combine metered and calculated data. CBAM actual embedded emissions use the legal monitoring and calculation framework, while CBAM defaults are regulatory default values. The word "actual" in one system and a verified result in another are not shortcuts around the method comparison.

## Scope and granularity gate

Before moving a number from one object to another, run the same gate every time.

| Gate | Question | Pass condition | If it fails |
|---|---|---|---|
| **1. Method** | Was the source result calculated under a method the destination accepts? | The same method or an explicit, defensible mapping exists. | Recalculate or keep separate. |
| **2. System boundary** | Do both results include the same lifecycle stages, processes and precursors? | Included and excluded processes align. | Recalculate from underlying data. |
| **3. Unit** | Are the declared, functional or reporting units genuinely equivalent? | The quantity, product basis and conversion are explicit. | Transform only if the conversion preserves meaning. |
| **4. Product scope** | Is the source about the same material, product definition or product family? | Product definitions and exclusions match. | Re-bind with evidence or reject. |
| **5. Granularity** | Is the destination asking about a family, model, batch, coil, billet or item? | The source is at the same level, or the destination only asks whether a broader declaration applies. | Do not promote a broader average to a narrower result. |
| **6. Facility** | Is the relevant installation or site the same? | Production-site scope is explicit and matched. | Re-bind or recalculate. |
| **7. Period** | Do the production and reporting periods align? | The source period is acceptable for the destination use. | Update or recalculate. |
| **8. Allocation** | Were co-products, recycled inputs, scrap, precursors and shared processes allocated in the same way? | Allocation rules align or can be mapped transparently. | Recalculate. |
| **9. Energy treatment** | Are electricity and other energy inputs treated consistently? | Electricity source, factors and method treatment match the destination rules. | Recalculate. |
| **10. Assurance and purpose** | Does the evidence meet the destination's verification and legal or commercial purpose? | Evidence form and assurance are accepted for that use. | Obtain the required evidence or keep the objects separate. |

This gate is stricter than a unit check. Two results can both say `kg CO2e per kg aluminium` and still fail on five other rows.

If the first problem is understanding what an environmental number actually represents, start with [environmental figure evidence and scope](https://activatedigital.ai/knowledge/evidence/environmental-figures). The metals question only becomes answerable once the source number's own boundary is clear.

### A useful distinction: binding versus calculation

Binding answers **which physical or commercial object the evidence applies to**. Calculation answers **how the environmental result was produced**.

Suppose an EPD covers a defined family of coils from a named production scope. Separate order, certificate or producer evidence may show that a delivered coil belongs to that family. That can justify attaching the EPD as an applicable declaration for the coil. It does **not** mean the family-average GWP result has become a measured coil-specific footprint.

The same distinction works in reverse. An exact coil identifier can be excellent binding evidence while saying little about whether the attached carbon result used the right method for CBAM, an EPD or a future DPP field.

## Steel worked example: EAF, a family EPD and CBAM

Take a buyer receiving a hot-rolled steel coil. The supplier can show three useful facts:

- the production route is EAF;
- a current EPD covers a hot-rolled steel product family;
- the shipment may also sit inside CBAM where the legal scope and importer conditions are met.
Those facts do not collapse into one carbon answer.

The current SSAB Zero EPD is a useful real example of an environmental declaration at product-family level. Its public record and declaration describe hot-rolled steel coils, a declared unit of 1 kg and a family-weighted model. That can be strong evidence for the environmental declaration it actually makes. It is not automatically the carbon footprint of each delivered coil.

The EAF route does not fix that gap. Production route is a relevant process fact, but route alone does not prove a recycled-content percentage or a carbon value. Two EAF operations can have different electricity mixes, scrap inputs, yields, upstream precursor impacts, allocation choices and reporting periods. A route label can therefore be an input to a calculation without being the result of the calculation.

CBAM adds a second boundary. For goods imported from 2026, Commission Implementing Regulation (EU) 2025/2547 sets the definitive-period methodology for calculating embedded emissions. It works through the CBAM framework for goods, production processes, installations and relevant precursors. Actual and default-value routes have their own rules. Current verification rules for declared actual embedded emissions sit in Commission Implementing Regulation (EU) 2025/2546.

A steel EPD's GWP result therefore must not be copied into a CBAM actual specific embedded-emissions field simply because both use a carbon unit. The underlying activity data may be useful. Electricity, fuel, material inputs or precursor data might be reused if the CBAM method accepts them and the installation, period and process bindings are sound. But that is a recalculation path, not direct value substitution.

The practical decision looks like this:

- **Need to reference the EPD?** Use the EPD as the EPD.
- **Need a carbon result under the EPD's own declared scope?** Use the verified declaration within that scope.
- **Need a batch-specific footprint?** Establish batch binding and a method that genuinely produces a batch-specific result. A family declaration alone is not enough.
- **Need CBAM embedded emissions?** Use the current CBAM method and its required evidence. Reuse compatible source data where allowed, not the EPD output by default.

## Aluminium worked example: site, product, coil and electricity

Aluminium makes the same problem more visible because electricity, primary versus recycled input, production route and allocation can have a large effect on the result.

Public aluminium evidence already appears at several levels. Hydro has separate EPD records for products such as extrusion ingot and wire rod, with persistent declaration identifiers. One Hydro declaration is explicitly tied to the Clervaux plant, while another declaration has its own stated product and production scope. Those records are valuable because they make the declaration subject visible. They still do not prove that every delivered ingot, billet or coil has its own individually measured EPD result.

At the other end of the granularity spectrum, Speira publishes an exact digital record for a named coil. The public record can bind product, alloy/temper and production-site information to that coil, while some deeper batch and input evidence is access-controlled. That demonstrates an important architectural point: exact product identity can be public even when the evidence needed to establish every upstream environmental input remains private.

PCF evidence can have another boundary again. EGA's DNV assurance statement for CelestiAL-R uses an ISO 14067 basis, a declared unit of 1,000 kg ingot and a cradle-to-gate boundary. It also distinguishes historic production evidence from an assumption-based validation case. The fact that both are described in one assurance document is a useful warning against reading "verified PCF" as one universal evidence type. Period, site, product, data basis and assurance conclusion still matter.

Now add CBAM. A covered aluminium import may require embedded-emissions data under the CBAM method, with installation and production-process information relevant to the calculation. The definitive-period rules also distinguish actual from default-value routes. The current default-value act is Commission Implementing Regulation (EU) 2025/2621, read with its correction in Commission Implementing Regulation (EU) 2026/1740.

None of those objects should be silently replaced by a facility total. A smelter or rolling site's total emissions can be a valuable input, but a product result requires a governed way to allocate those emissions to the product scope and period. Electricity treatment is part of the same problem. A site total, a PCF and a CBAM calculation can all use electricity data while applying different rules to it.

So for an aluminium coil with an exact identity record, a product-family EPD, a PCF and a facility emissions inventory, the correct data model is not "choose the best carbon number". It is "store four evidence objects, bind each to its own subject and calculate or reuse only through an explicit acceptance rule".

## When reuse is legitimate

Reuse becomes legitimate when the destination question is narrower and the evidence path remains visible.

### 1. Reuse the evidence reference when that is what is required

If a system needs to record that an applicable EPD exists for a product, the EPD identifier, validity, declared product and programme evidence can be reused as an EPD reference. You do not need to convert its climate result into another carbon method simply to reference the declaration.

The same principle applies to a PCF assurance statement or a CBAM evidence record. Keep the source object intact and expose the metadata needed to understand it.

### 2. Reuse underlying inputs across calculations where the destination method accepts them

A company may have one governed source for electricity consumption, production quantity, precursor mass or facility identity. Those facts can sometimes feed more than one calculation. The method-specific calculations should still remain separate.

This is where the largest useful reuse often sits. Reusing a governed input can remove repeated data collection without pretending that the EPD, PCF and CBAM outputs are the same.

### 3. Re-bind only to the claim the evidence really supports

A product or delivery record can prove that a particular coil sits within an EPD's declared product scope. That supports the statement "this EPD applies to this product" if all relevant scope conditions are met. It does not support "this EPD value is the measured carbon footprint of this individual coil" unless the declaration itself and the destination method genuinely operate at that level.

### 4. Preserve method metadata when carbon data moves between systems

A PCF value travelling without its boundary, unit, period, method, version, data quality and provenance becomes very easy to misuse. Good [product carbon footprint exchange](https://activatedigital.ai/knowledge/product-data/product-carbon-footprint-exchange) architecture can preserve that context. Exchange conformance helps move the evidence object safely. It does not make unlike methods equivalent.

## What cannot be substituted

Some shortcuts should fail by design.

| Proposed shortcut | Why it fails | Safe treatment |
|---|---|---|
| **EAF or BOF route -> carbon value** | Route is a process fact, not a complete emissions calculation. | Keep route as an input. Calculate carbon under the required method. |
| **Family EPD -> exact batch footprint** | The declaration may be a family or average result and may not resolve batch variation. | Bind the EPD as an applicable declaration only where supported. Obtain or calculate batch evidence if a batch value is required. |
| **EPD GWP -> CBAM actual embedded emissions** | Method, legal purpose, production-process treatment and reporting rules differ. | Recalculate under current CBAM rules using reusable inputs where valid. |
| **Facility total -> product footprint** | A site figure lacks product allocation and can cover multiple products or processes. | Apply an accepted allocation method with product and period binding. |
| **CBAM default -> actual PCF** | A regulatory default is not evidence of the actual product footprint. | Keep it labelled as a CBAM default. |
| **PCF -> future DPP carbon field** | The future Steel and Aluminium product-specific DPP requirements and methods are not final. | Keep the PCF as present evidence and wait for the adopted product rule before mapping it to a mandatory field. |
| **Same unit -> same fact** | `kg CO2e` says nothing by itself about method, boundary, object or purpose. | Run the reuse gate. |

The governing principle is simple: **scope compatibility must be proved, not guessed from numerical similarity.**

## Current law and future DPP requirements

As at 10 September 2026, the CBAM definitive period is current. Commission Implementing Regulation (EU) 2025/2547 is the calculation-method act for goods imported from 2026. Its recitals expressly distinguish that regime from Commission Implementing Regulation (EU) 2023/1773, which covered the transitional period from 1 October 2023 to 31 December 2025.

The associated current source set also includes verification rules for actual embedded emissions, verifier accreditation and oversight, Registry rules and definitive-period default values with their current corrections. That source set matters because CBAM is version-sensitive. A calculation built from an old transitional template can look plausible while using the wrong legal method for a 2026 import.

Steel and Aluminium DPP carbon requirements are a different maturity question. ESPR provides the horizontal framework, but the product-specific measures that would settle future mandatory fields, methods, granularity and application dates for these metals are not final. For Aluminium, the Commission's 2025-2030 Working Plan gives an indicative 2027 adoption timetable for the product measure. That is not a binding 2027 compliance date.

For the broader question of why a passport and an environmental declaration are different information objects, use [DPP versus EPD](https://activatedigital.ai/knowledge/regulation/dpp-vs-epd). The answer here is narrower: even where two systems both contain carbon information, the evidence can only cross the boundary when the destination's method and scope let it.

## What would change this page

Recheck this comparison if any of the following occurs:

- the CBAM calculation, verification or default-value rules materially change;
- the Commission adopts a Steel or Aluminium product-specific ESPR measure that fixes carbon information requirements or a mandatory method;
- an adopted rule creates an explicit bridge to an EPD, PCF or another environmental method;
- a recognised scheme changes the product, site, period or assurance semantics relied on for reuse.
Until then, keep the four evidence objects separate and make reuse an explicit decision rather than a field-mapping assumption.

## Sources

- [Commission Implementing Regulation (EU) 2025/2547 on calculation of CBAM embedded emissions, European Union, 10 December 2025.](https://eur-lex.europa.eu/eli/reg_impl/2025/2547/oj/eng)
- [Commission Implementing Regulation (EU) 2025/2546 on verification of declared embedded emissions, European Union, 10 December 2025.](https://eur-lex.europa.eu/eli/reg_impl/2025/2546/oj/eng)
- [Commission Delegated Regulation (EU) 2025/2551 on CBAM verifier accreditation and oversight, European Union, 20 November 2025.](https://eur-lex.europa.eu/eli/reg_del/2025/2551/oj/eng)
- [Commission Implementing Regulation (EU) 2025/2621 on CBAM default values, read with Commission Implementing Regulation (EU) 2026/1740.](https://eur-lex.europa.eu/eli/reg_impl/2025/2621/oj/eng)
[https://eur-lex.europa.eu/eli/reg_impl/2026/1740/oj/eng](https://eur-lex.europa.eu/eli/reg_impl/2026/1740/oj/eng)

- [European Commission CBAM legislation and guidance, current source index checked 10 September 2026.](https://taxation-customs.ec.europa.eu/carbon-border-adjustment-mechanism/cbam-legislation-and-guidance_en)
- [Hot rolled SSAB Zero steel coils EPD record, International EPD System, revision current 4 June 2026.](https://www.environdec.com/library/epd18717)
- [Hydro REDUXA 4.0 Extrusion Ingot EPD, EPD Norge.](https://epd-global.com/epder/byggevarer/stal-armering-aluminiumskonstruksjoner/hydro-reduxa-4-0-extrusion-ingot)
- [Hydro Reduxa 4.0 Wire Rod EPD, EPD Norge.](https://www.epd-norge.no/epder/byggevarer/stal-armering-aluminiumskonstruksjoner/hydro-reduxa-4-0-wire-rod)
- [speira.ID example coil 9013514010, Speira.](https://www.speira.com/sustainability/transparency/digital-product-passport/?speiraID=9013514010)
- [CelestiAL-R Product Carbon Footprint Verification / Validation Statement, EGA / DNV, 10 April 2025.](https://www.ega.ae/media/1qolxiqb/product-carbon-footprint-verification-statement-of-ega-celestial-r-product-in-accordance-with-iso-14067-2018-aug2025.pdf)