Cement was one of the original CBAM sectors, and for importers of clinker and cement it brings a particular mix of challenges: high process emissions, heavy tonnages that cross the threshold quickly, and suppliers who may not yet measure emissions the way CBAM expects.
Why cement is in scope
Cement production is carbon-intensive in two distinct ways: the calcination of limestone releases CO₂ as a chemical process emission, and the kilns burn significant fuel. That combination puts cement at clear risk of carbon leakage, which is why it sits inside CBAM. The covered goods — clinker, cement, and related products — are defined by CN code in Annex I of the regulation, so the first task is confirming which of your imported products are actually covered (how CN-code scope works).
The threshold is easy to cross
The 2025 Omnibus simplification set a 50-tonne annual mass-based de minimis per importer. Cement and clinker are heavy and shipped in bulk, so this threshold is trivial to exceed — often in a single delivery. If you import cement commercially, assume you are in scope, and remember that crossing 50 tonnes mid-year pulls your entire year of relevant imports into the regime.
The data: process emissions from the producer
The embedded-emissions figure for cement comes from the producing plant and reflects both process and combustion emissions. As with other sectors, accurate supplier data generally costs you less than falling back on conservative default values — but getting it requires a structured request to the producer, tracked over time. The supplier emissions data process is the same discipline cement importers need: a clear request, a cadence of follow-ups, and a log of what is still missing.
What a clean cement CBAM file looks like
Your first annual CBAM declaration covers 2026 imports and is due 30 September 2027 (full timeline). To get there without a scramble, build the file as shipments happen:
- Invoices, customs declarations, and transport documents linked per consignment.
- The CN code and the in-scope reasoning for each product.
- Plant-level emissions data — or a logged gap and the default value applied.
- A traceable line from every declared figure back to a source document.
That is the evidence archive your declarant or adviser reviews, and it is also your best protection against penalty risk.
Where CarbonBorder Desk fits
We run the operational layer for cement importers: confirming scope, building the shipment register, chasing producer emissions data, tracking the gaps, and keeping the evidence archive review-ready. We are not a law firm, customs broker, or tax adviser and we do not file declarations — we make the file underneath them correct and traceable. Most importers start with a pilot diagnostic on one import flow.