For most Indian exporters, Scope 3 has historically meant answering a customer questionnaire. Under the EU's Carbon Border Adjustment Mechanism (CBAM), it means something closer to a customs declaration — and eventually, a bill.
What CBAM actually covers
CBAM applies to imports into the EU of a defined set of carbon-intensive goods: iron and steel, aluminium, cement, fertilisers, hydrogen, and electricity. It requires EU importers to report — and eventually pay for — the embedded emissions in those goods, calculated using the actual production route and inputs of the exporting facility, not a generic industry average.
This is the detail that catches exporters off guard: CBAM is not primarily about the EU importer's own emissions. It is about the emissions embedded in the specific product manufactured at a specific plant, in a specific country, using that plant's actual energy mix and production process. That data has to come from the exporter, because the importer has no way to generate it independently.
Why this is a Scope 3 problem for Indian manufacturers
For an Indian steel or aluminium producer selling into the EU, CBAM-compliant embedded-emissions reporting requires essentially the same underlying data as a rigorous Scope 1 and 2 inventory at the facility level — direct process emissions, fuel combustion, and the emissions intensity of purchased electricity, calculated per tonne of finished product. Where it becomes a genuine Scope 3 exercise is upstream: for products with significant embedded inputs (steel made partly from purchased billet or scrap, aluminium smelted from imported alumina), the embedded emissions of those inputs have to be captured and passed through the value chain as well.
That means an exporter's CBAM readiness depends not just on its own facility data, but on getting comparable data from its own domestic suppliers — the same supplier-engagement problem that shows up everywhere else in Scope 3 work, just with a harder deadline and a direct cost attached.
The practical gap
Three gaps show up repeatedly in Indian exporters preparing CBAM declarations:
- Facility-level granularity. Many plants track energy and emissions at the site level for domestic reporting (like BRSR or PAT scheme obligations under India's Perform, Achieve and Trade programme) but not broken out per product line or production route — which is what CBAM's methodology actually requires.
- Default values are a stopgap, not a strategy. Where an exporter can't yet supply verified actual emissions, CBAM permits the use of default reference values — but these defaults are calibrated to be conservative, and in most cases produce a higher embedded-emissions figure (and higher eventual cost) than a verified actual value would. Exporters who invest early in verified facility-level data typically end up materially better off financially than those relying on defaults.
- Verification readiness. CBAM's definitive regime requires third-party verification of embedded-emissions data. Getting a facility's monitoring, reporting, and data systems into a verifiable state is not a one-quarter project — it typically takes one to two reporting cycles to get right.
Where to start
For an exporter with EU-bound volumes in CBAM-covered categories, the sequence that works is: establish facility-level MRV (monitoring, reporting, verification) systems aligned to CBAM's methodology first, get comparable data from the two or three suppliers contributing the most embedded emissions to your export product second, and only then layer on the reporting and declaration workflow. Doing the reporting paperwork before the underlying data exists just locks in default values — and the higher cost that comes with them.