CBAM and EPDs: where they overlap and where they don't.

The EU's Carbon Border Adjustment Mechanism (CBAM) entered its definitive phase on 1 January 2026. The first annual declaration is due on 30 September 2027. Many manufacturers exposed to CBAM are also being asked to produce EPDs by their customers or their regulators. The two regimes are related but not equivalent — and treating them as one would be a costly mistake.

What CBAM actually is

CBAM is a carbon-pricing instrument that puts a price on the embedded greenhouse-gas emissions of certain goods imported into the EU. It currently covers cement, iron and steel, aluminium, fertiliser, hydrogen, and electricity. Importers (the "declarants") must report installation-specific emissions data for the goods they bring in, surrender CBAM certificates equivalent to those emissions, and adjust for any carbon price already paid in the country of origin.

The mechanism is administered by the European Commission and applied at the EU border. It is, in effect, a tariff calibrated to the carbon intensity of the imported product. The intent is to prevent "carbon leakage" — the relocation of EU production to jurisdictions with weaker climate policy.

What an EPD is, in this context

An EPD is a standardised disclosure document about a product's environmental performance — Global Warming Potential is one of the impact categories it reports, but it also covers ozone depletion, acidification, eutrophication, resource depletion, and others. EPDs are used in procurement, building certification, and customer transparency contexts. They are not a tariff instrument.

The overlap — where CBAM and EPDs touch

If you have a recent, well-built LCA model for an EPD, much of the underlying production data also feeds a CBAM declaration. Conversely, if you've stood up CBAM-compliant data collection at the plant level, you have most of what an EPD needs.

Where they differ — and the differences matter

1. Methodology

CBAM uses the EU's Monitoring and Reporting Regulation (MRR) methodology, which is closely aligned with the EU Emissions Trading System. EPDs follow ISO 14040/14044/14025 with EN 15804+A2 or ISO 21930 PCR conformance. The boundary definitions differ. The treatment of biogenic carbon, allocation rules, and inclusion of indirect emissions are not identical. An LCA model built for an EPD typically needs adjustment before it satisfies CBAM's MRR.

2. Scope of emissions

CBAM is GHG-only — it measures Scope 1 and Scope 2 (and, depending on the good, some upstream Scope 3) in CO₂-equivalent terms. EPDs report a multi-criteria life-cycle assessment across many impact categories. A CBAM declaration is not an EPD; an EPD's GWP value is not directly a CBAM declaration.

3. Default values

For the transitional period, CBAM permitted default values for embedded emissions where installation-specific data wasn't available. In the definitive phase, default values are penalised — installation-specific, third-party-verified primary data is the expected basis. EPDs have always required primary data from the manufacturer (or well-documented allocation from upstream EPDs); they were never compatible with default values.

4. Who pays

CBAM declarations are submitted by the EU importer, not by the non-EU producer. The producer provides the data; the importer files the declaration and pays the certificates. EPDs are commissioned by the manufacturer for their own use.

5. Renewal cycle

CBAM is annual. The first annual declaration is due 30 September 2027, with subsequent declarations annually thereafter. EPDs are typically valid for 5 years.

What this means practically

• If you're an EU importer of cement, iron and steel, aluminium, fertiliser, hydrogen, or electricity: prioritise CBAM-compliant data collection from your non-EU suppliers. EPDs from those suppliers are helpful raw material but won't satisfy CBAM on their own.
• If you're a non-EU producer selling into the EU: your EU customers will increasingly demand installation-specific MRR data. Investing in robust plant-level emissions data serves both CBAM and any EPD requirement you face. Don't build the systems twice.
• If you have a recent EPD for a CBAM-scope product: revisit the underlying LCA model with your consultant and a CBAM specialist. The data is mostly there; the methodology mapping is the work.
• If you don't have either yet and need both: build the data architecture once, then use it for parallel outputs. The marginal cost of producing an EPD once you have CBAM-quality data is much lower than building either from scratch.