EU CBAM and Indian Exporters: Why Your ESG Data Can No Longer Wait

A Carbon Tax That Stopped Being Theoretical

For two years, the EU's Carbon Border Adjustment Mechanism was something Indian exporters filed away as "a compliance thing to watch." That changed on 1 January 2026, when CBAM moved from its reporting-only transitional phase into its definitive phase, and carbon costs became real money at the border. Within weeks, Indian steel MSMEs were reporting shipment holds at European ports, cancelled orders, and unexpected charges running into crores on single consignments, all triggered by missing or incomplete carbon declarations.

If your business exports to the EU, sells to someone who does, or sits two or three tiers down a supply chain that eventually reaches Rotterdam or Antwerp, this is no longer a European regulatory footnote. It is a live cost, and the businesses that treated their emissions data as a BRSR checkbox rather than a business asset are the ones now scrambling.

What CBAM Actually Requires

CBAM puts a carbon price on certain imports into the EU, calculated based on the greenhouse gas emissions embedded in the production of those goods. The logic is straightforward: if a European steelmaker pays a carbon price under the EU's own emissions trading system, an overseas producer selling the same product into the EU should face an equivalent cost. Otherwise, EU industry argues, production simply shifts to countries with looser climate rules, a problem known as carbon leakage.

In practice, this means EU importers of covered goods now need verified, product-level emissions data from their overseas suppliers, including Indian manufacturers and exporters. Where that data is missing or cannot be verified, the EU applies default emissions values that are deliberately conservative and expensive, which is exactly what is pushing effective carbon costs on some Indian shipments well above what accurate, verified data would show.

The Timeline: Where We Are and What Comes Next

● October 2023 to December 2025: Transitional phase. Importers had to report embedded emissions quarterly, with no charge attached, essentially a data-collection dry run.

● From 1 January 2026: Definitive phase begins. Importers of covered goods above a 50-tonne annual threshold must register as authorised CBAM declarants, and financial exposure starts accruing from this date.

● From 1 February 2027: The EU opens certificate sales through its central platform, where importers buy CBAM certificates corresponding to embedded emissions.

● By 30 September 2027: The first annual declaration and certificate surrender are due, covering emissions embedded in 2026 imports, verified by an accredited third party.

● Through 2034: The system phases in fully as free allocation under the EU's own emissions trading scheme is gradually withdrawn, meaning the carbon cost on imports keeps rising over the decade.

The gap between now and the 2027 surrender deadline can feel like breathing room. It isn't. Emissions data has to be collected and verifiable for every 2026 shipment, which means the systems for tracking it need to be running today, not assembled retroactively next year.

Which Sectors Are Directly in Scope

CBAM currently applies to iron and steel, aluminium, cement, fertilisers, electricity, and hydrogen, chosen because they are both carbon-intensive and exposed to international competition. The EU has already signalled its intention to widen this list over time to include downstream products with high steel or aluminium content, such as fabricated metal goods, machinery components, and certain automotive parts. Businesses in adjacent sectors should read that as an early warning rather than an exemption.

What's Already Happening to Indian Exporters

The disruption is not hypothetical. Indian steel and aluminium exports to the EU had already declined sharply in the run-up to the definitive phase, as buyers grew cautious about compliance risk. Trade analysts estimate that to remain price-competitive after absorbing CBAM costs, some Indian steel and aluminium exporters may need to cut prices by 15 to 22 percent, a margin many MSME producers simply do not have.

The structural problem runs deeper than pricing. Even India's cleaner "green steel" production carries embedded emissions above the EU's benchmark for tax-free entry, meaning that even relatively efficient Indian producers face some carbon charge by default. For exporters without verified emissions data of their own, the EU's default values push that charge dramatically higher, with some MSMEs reportedly seeing effective carbon costs multiply several times over compared to what accurate reporting would have shown.

India's free trade agreement with the EU, concluded in January 2026, did not secure any carve-out or transition relief on CBAM. The EU has been consistent in treating CBAM as a climate measure, not a trade measure, and therefore not something to be negotiated away in a bilateral deal. For Indian exporters, that closes off the hope that CBAM might soften through diplomacy. The practical response now has to be operational: better data, better verification, better readiness.

You Don't Need to Export Directly to Be Exposed

This is the part most MSMEs miss. CBAM's 50-tonne threshold and its focus on direct EU importers create an illusion of safety for smaller suppliers who never see a European customs form. In reality, large exporters and merchant traders consolidate shipments from dozens of smaller producers, and the moment those combined volumes cross the reporting threshold, every supplier feeding that shipment becomes part of the emissions picture the importer has to account for.

Industrial clusters built around foundries, rolling mills, and component manufacturing, the kind that supply Tier 1 exporters rather than selling to Europe themselves, are already being asked by their larger customers to start sharing emissions data. Estimates suggest that tens of thousands of Indian MSMEs are indirectly exposed in this way, compared to a much smaller number of direct exporters. If your customer's customer sells into the EU, your emissions data is already someone else's compliance problem, whether you have measured it yet or not.

The Data Gap Is the Real Cost Driver

Every account of CBAM's early disruption points to the same root cause: the absence of reliable, product-level emissions data. It isn't the carbon price itself that is catching Indian exporters off guard; it's not having numbers to defend a lower one. Businesses with weak internal emissions tracking get assigned the EU's punitive default values. Businesses with verified Scope 1 and Scope 2 data, tracked consistently and ready for third-party assurance, can demonstrate their actual, often lower, carbon footprint and pay accordingly.

The government has recognised the strain this is placing on smaller exporters and is reportedly working on a scheme to cover a large share of MSME compliance costs. That kind of support can ease the financial burden of getting audit-ready. However, it does not remove the underlying requirement: someone still has to measure, document, and verify the emissions embedded in what you make.

Where CBAM and BRSR Data Overlap

Here is the part that should change how Indian businesses think about BRSR: the emissions data BRSR already asks for is largely the same data CBAM needs. BRSR's core disclosures require Scope 1 (direct emissions from your own operations), Scope 2 (indirect emissions from purchased electricity), and, increasingly, Scope 3 (emissions across your value chain, including suppliers). CBAM's product-level embedded emissions calculations draw on exactly these categories, just applied at the level of a specific product or shipment rather than the company as a whole.

A manufacturer that has already built the discipline of tracking Scope 1 and 2 emissions for BRSR reporting- energy consumption by process, fuel use, purchased power, emission factors- is most of the way to having what a CBAM declaration needs. The gap is usually granularity: BRSR wants company-level annual numbers; CBAM wants that same underlying data broken down by product and shipment, verified to a standard an accredited assessor will accept. Businesses that treat their BRSR data collection as a one-off compliance exercise rather than a live operational system will find themselves rebuilding it from scratch when a CBAM-linked customer asks for it.

This is also where the CA and consultant community has a genuine opportunity. Emissions data built for BRSR assurance, structured well and documented properly, becomes a reusable asset for CBAM support work, rather than two entirely separate compliance exercises run in parallel.

A Practical Readiness Checklist

● Map your exposure honestly: list every product you export directly, and separately, every customer you supply who exports to the EU, even indirectly.

● Start Scope 1 and Scope 2 tracking at the product or process level, not just the company level, if you haven't already.

● Align your emissions methodology with recognised standards early, since the EU's verification requirements will only get stricter as the mechanism matures.

● Treat your BRSR data collection as infrastructure, not paperwork, so it can be reused rather than rebuilt when a CBAM request lands.

● Budget for third-party verification costs now, rather than treating them as a 2027 problem.

● Talk to your Tier 1 customers directly. If they export to the EU, ask what data they will need from you and by when, rather than waiting for that request to arrive as an emergency.

The Window to Prepare Is Now

CBAM's financial phase-in runs through 2034, which means the cost of carbon at the EU border only goes up from here. Businesses that build verified, product-level emissions data now are the ones who will pay for their actual footprint. Businesses that wait will keep paying under the EU's default assumptions, which are conservative and expensive by design.

The good news for Indian MSMEs is that this isn't a second compliance mountain to climb. The emissions accounting discipline that strong BRSR readiness already demands- accurate Scope 1 and 2 data, a documented methodology, and audit-ready records- is the same foundation CBAM compliance is built on. Getting that foundation right once means it works for both.