EU CBAM Carbon Border: What It Means for Thai Exporters

Over the past year or two, a number of Thai exporters selling into the European Union have started receiving a request from their EU customers that didn't used to be part of the conversation: a request for the carbon emissions associated with making the goods being shipped. It usually arrives buried in a purchasing email or a supplier questionnaire, phrased in a way that assumes the supplier already understands what's being asked and already has the numbers ready. Most don't, and the request itself is often the first anyone in the company has heard of it.

This is not a request the Thai exporter can trace back to any Thai law, because it doesn't come from one. It comes from a piece of EU legislation known as the Carbon Border Adjustment Mechanism, or CBAM, which is designed to attach a carbon cost to certain goods entering the EU market. The exporter is not the one legally obligated to comply with CBAM — the EU-based importer is. But because the importer cannot comply without information that exists nowhere except at the factory that made the goods, the obligation travels backward through the supply chain and lands, in practical terms, as a data request on the Thai supplier's desk.

This article explains the mechanism behind that request at the level a Thai business owner needs to act on: why the EU built it, who legally owes what, what kind of data is actually being asked for, why most suppliers can't produce it immediately, and what a reasonable first move looks like. It deliberately does not attempt to state which products are covered, on what timeline, or at what cost, because those details are set by EU law, they change, and stating them here as fixed facts would do a Thai reader more harm than good. What's fixed, and worth understanding regardless of how the details evolve, is the logic underneath it.

The economic logic: why the EU built a carbon border at all

The idea behind CBAM is straightforward once it's stated plainly, even though the compliance mechanics built around it are not. Inside the EU, certain carbon-intensive industries — producers of basic materials like iron and steel, aluminium, cement, and fertiliser, along with electricity and hydrogen production — already pay a cost for the carbon they emit, through the EU's own domestic carbon pricing system. That cost is built into what it takes to produce those goods inside the EU.

If that were the whole picture, EU producers of those goods would simply be more expensive to buy from than producers in a country where carbon has no price attached to it at all. A buyer inside the EU could import the same steel or fertiliser from outside the bloc, pay nothing for the carbon emitted making it, and undercut the EU producer purely on that basis — not because the imported goods are more efficient to make, but because nobody charged for the emissions. Multiply that across an economy and the incentive is to relocate carbon-intensive production outside the EU altogether, which does nothing to reduce global emissions and simply moves them somewhere the EU has no policy reach. This effect has a name in trade and climate policy: carbon leakage.

CBAM is the EU's attempt to close that gap at the border. It is built so that imported goods in the same carbon-intensive categories face a cost that reflects the carbon embedded in producing them, broadly equalising the position of an EU producer who already pays for its emissions and a foreign producer whose government may not price carbon at all. The goal, in principle, is not to punish imports or shield EU industry outright — it is to stop the EU's own carbon pricing from simply pushing production, and the emissions that come with it, somewhere else on the map.

Once that logic is understood, the rest of the mechanism — why it asks for emissions data specifically, why it targets certain sectors, why it attaches to the importer — follows from it rather than needing to be memorised as a separate set of rules.

Who actually carries the legal obligation

The single most important fact for a Thai exporter to hold onto through all of this is who the law actually obligates. CBAM's compliance and reporting duties sit with the EU-based importer — the company in Germany, the Netherlands, or wherever else in the bloc that is bringing the goods in and placing them on the EU market. It is the importer's name on the customs declaration, the importer's regulatory relationship with EU authorities, and, ultimately, the importer's exposure if the obligation isn't met correctly.

A Thai factory has no direct legal relationship with CBAM at all. No EU regulator is going to contact a supplier in Thailand, and no Thai law is being triggered. In a narrow legal sense, this could look like a problem that belongs entirely to the customer, not the supplier.

In practice, it doesn't stay contained that way, because of one simple fact: the importer cannot produce the number it needs to report without data that only exists at the point of production. An importer buying steel components, aluminium parts, or fertiliser blends from Thailand cannot calculate the emissions embedded in that specific batch of goods by looking at its own books — it has to get that information from the factory that made them, or accept a substitute value that the rules make deliberately unattractive to rely on. That need is what turns a piece of EU law into a commercial request arriving at a Thai supplier's inbox, usually phrased as part of ordinary supplier communication rather than as anything obviously regulatory.

This is worth stating plainly and repeating: the legal obligation is the importer's, the data need is the supplier's problem to help solve, and the two are connected by nothing more formal than an ordinary commercial relationship — a customer asking a supplier for information it needs to do its own compliance. Understanding that distinction changes how a Thai exporter should read these requests. They are not enforcement notices. They are customers asking for help meeting an obligation that the customer, not the supplier, legally carries.

Which goods this actually touches — and why that answer keeps changing

It matters which goods this actually touches, and here is exactly where a Thai reader needs to be careful about anything written on the subject — including this article. CBAM, as EU legislation, applies to specific goods identified by their classification under the EU's own product list, and that list, along with the obligations attached to it and the timeline for phasing them in, is set entirely by EU law. It has changed since the mechanism was first introduced, and there is no reason to assume it has stopped changing. Any Thai-language explanation, including this one, that tries to give a fixed, current answer to "is my product covered" is already at risk of being wrong by the time it's read.

What can be said safely, at the level of general orientation rather than current fact, is which kinds of industries this mechanism is aimed at. It targets carbon-intensive basic materials and inputs — the kind of goods where a large share of the embedded cost is the energy and process emissions of turning a raw input into a usable material. Iron and steel, aluminium, cement, and fertilisers are the commonly cited examples, alongside electricity and hydrogen. These are, broadly, upstream, energy-intensive products rather than finished consumer goods — though how far downstream the coverage extends, and whether particular finished or semi-finished products made from these materials fall inside or outside the scope, is exactly the kind of detail that is decided by classification codes in the EU's own list and that changes as the mechanism evolves.

For a Thai exporter, the only reliable way to answer "does this affect me" is to check the product's own classification against the current, official EU guidance — not against a general description like this one, and not against what a competitor or industry association assumed last year. The EU customer placing the order and the customs broker handling the shipment are two of the most useful people to ask, because both have a direct stake in getting the classification right.

What the data request actually is

Assuming a product turns out to be in scope, the next question is what, exactly, is being asked for — and this is where the request often gets misunderstood inside a Thai company. What CBAM asks the importer to report, and what therefore gets asked of the supplier, is the embedded emissions in the specific goods being shipped: the greenhouse gases released in producing that quantity of that product, attributed to it directly.

This breaks into two parts. Direct emissions are those released by the production process itself — burning fuel to run a furnace, chemical reactions inherent to making cement or fertiliser, and similar process-level sources. Indirect emissions, relevant for some categories of goods, cover the emissions associated with the electricity consumed in making the product, since that electricity itself carried a carbon cost somewhere upstream, even though the factory didn't burn the fuel directly.

The critical point is that this is an accounting exercise done at the level of an installation and a production process, attributed to a specific quantity of a specific product — not a company-wide number. This is exactly why an existing corporate sustainability report or carbon footprint statement, if a Thai company already has one, usually does not answer the question being asked. A company-wide footprint might state total emissions across an entire factory, or an entire company, for a year. What's being requested here is emissions per tonne, or per unit, of one specific product line, produced through one specific process, at one specific site — a much narrower and more technical number than a general sustainability disclosure was ever built to produce.

A Thai exporter who has already invested in ESG reporting or a corporate carbon inventory sometimes assumes that work already covers this request. It's worth checking carefully before assuming so, because the two exercises measure genuinely different things, even when the underlying data — energy bills, fuel purchases, production volumes — overlaps.

Why most Thai suppliers can't answer on the first ask

Given what's actually being asked, it becomes clear why most Thai suppliers, even well-run and technically capable ones, cannot answer this request the first time it arrives. The gap isn't usually a lack of willingness — it's that the data was never collected in the shape this question needs.

Production data at most factories is tracked at the level useful for running the business: output volumes, order fulfilment, quality control. It is rarely tracked per product line in a way that separates the energy consumed making one product from the energy consumed making another on the same line, in the same period, from the same electricity meter. Energy metering itself is frequently installed at the site level — one meter for the whole factory — rather than sub-metered by process or by product, which makes attributing how much energy went into a specific batch a genuine technical exercise rather than a simple lookup.

On top of that, many products incorporate precursor materials — steel made from imported billet, fertiliser blended from several base chemicals — and the emissions embedded in those inputs were generated by someone else's factory, often in another country. Answering the full question requires the Thai producer to also obtain emissions data from its own upstream suppliers, who may be facing exactly the same unfamiliar request themselves, one step further back in the chain.

None of this means the request is unreasonable or unanswerable — it means it takes real, specific work to answer well, and that work has to start with an honest look at what data already exists, what doesn't, and where the gaps sit. A supplier that treats the first request as a one-off form to fill in as best it can, rather than as a signal that this kind of data collection needs to become a standing capability, is likely to face the same scramble again on the next order.

The practical first steps toward being able to answer

The practical response to that gap doesn't need to be built all at once, and it doesn't need outside consultants brought in on day one, though larger or more complex operations may eventually want that kind of support. A reasonable first sequence looks like this.

First, identify which specific products might be in scope at all, based on their classification, rather than guessing at a company-wide level — a factory that makes ten product lines may find that only two or three are even candidates for this kind of request. Second, map the production process for those specific lines: what stages it goes through, what fuel and electricity it consumes at each stage, and where those inputs are currently metered or estimated. Third, work out how energy use can be allocated to a specific product line where metering is currently shared — this might mean installing sub-metering, or it might mean a defensible allocation method based on production time or output volume, at least as an interim step. Fourth, identify which inputs are bought in from other suppliers rather than made in-house, and start the conversation with those suppliers about what emissions data they can provide for their own materials — this step often takes the longest, because it depends on someone else's readiness, not just the Thai factory's own.

Finally, and this applies from the very first step onward, keep records in a form a customer's compliance team can actually rely on — dated, tied to a specific product and period, and consistent in method from one reporting cycle to the next. A number produced once, informally, and never repeated in a consistent way is of limited use to an importer that needs to report on an ongoing basis. None of these steps require knowing the exact current EU rule to begin — they build a capability that will be useful whatever the specific requirement turns out to be once confirmed.

The commercial consequence of not being able to answer

It's worth being honest about what happens commercially when a supplier genuinely cannot produce this data, because the EU importer's obligation doesn't disappear just because the data isn't available. Where actual, supplier-specific emissions figures aren't provided, the EU's rules generally allow the importer to fall back on a default or standardised value instead — but that fallback is deliberately built to be a less attractive option than a real number would be, which is part of how the system is designed to encourage genuine data collection rather than reliance on estimates.

The directional consequence for a Thai supplier is straightforward, even without attaching a specific figure to it: a supplier that can hand its EU customer credible, well-documented, product-level emissions data becomes commercially easier to keep buying from than one whose customer has to rely on a generic fallback. This isn't a hypothetical incentive dreamed up for the purposes of this article — it follows directly from how the mechanism is structured, since the importer bears a real cost difference between using a supplier's actual figure and using the fallback, and importers factor real costs into sourcing decisions the same way they always have.

This doesn't mean a supplier without the data today is about to lose the business tomorrow. Most EU buyers understand that their own supply base is at very different stages of readiness, and the transition is happening gradually across an entire trading relationship, not as a single pass-fail test. But it does mean that "we don't have that information" is not a permanently comfortable answer to give a customer who is under a legal reporting duty of their own. Suppliers who treat the first data request as an early signal, rather than a one-time inconvenience to get past, are the ones positioning themselves as the easier, lower-friction option the next time the customer is choosing where to place an order.

The logistics and documentation angle this touches

This is also, at its core, a documentation and classification problem, which is exactly the part of the picture a freight forwarder and customs broker are positioned to help with, even though neither can supply the emissions data itself.

The starting point for almost everything here is the goods' classification code. Whether a specific shipment is even a candidate for CBAM scope, and which of the mechanism's specific requirements might apply to it, is decided by how the goods are classified — the same classification code that already governs duty treatment and import documentation for entirely separate reasons. A product classified one way may sit outside scope entirely; a closely related product classified differently may sit inside it. This makes getting the classification right, and being able to justify it, more consequential than it may have seemed before this request arrived, and it's a good reason to have that classification checked and confirmed rather than carried forward unreviewed from an old shipment.

From there, the commercial invoice description needs to actually match the classified goods precisely — a vague or inconsistent description creates exactly the kind of ambiguity that makes it harder for anyone downstream, including the EU importer's own compliance team, to confirm scope with confidence. Customs brokers on both the Thai export side and the EU import side are increasingly part of what is really a data conversation now, not just a clearance conversation, because the classification and documentation they already handle is the same information the emissions reporting hangs off.

One practical pattern worth noting: because the importer needs this information to plan its own compliance, emissions-related data requests are increasingly showing up attached to the purchase order itself, before a shipment is even booked, rather than arriving later alongside shipping instructions. A Thai exporter who waits for the request to show up at shipment time, rather than expecting it at the ordering stage, will consistently find themselves reacting under more time pressure than necessary.

Keeping this in proportion

It's worth stepping back and placing this in proportion, because reactions to a new EU compliance mechanism tend to run in one of two unhelpful directions. One is to treat it as an existential threat to exporting to Europe at all — a message that this is somehow a ban or a blanket new tariff on Thai goods. It isn't. CBAM is a reporting and cost-allocation mechanism attached to a defined, carbon-intensive set of goods categories, decided by classification, not a general barrier on trade with the EU.

The other unhelpful reaction is to dismiss it entirely as someone else's problem, on the theory that a Thai SME exporter is too small or too far downstream to be affected. That's not accurate either. The mechanism affects a genuinely narrow band of Thai exporters directly — those making or trading in the specific covered material categories, in forms that fall inside the current classification scope. But it affects a considerably wider band indirectly, because any Thai manufacturer supplying components or finished goods into an EU customer's own supply chain may find that customer starting to ask questions further back than before, as EU buyers get more attentive to the carbon content of everything that feeds into their own reporting obligations, even goods not directly in CBAM's scope today.

The realistic position sits between those two reactions: this is a real, specific, and growing compliance and data expectation that a defined set of Thai exporters needs to take seriously and act on now, and a broader set of Thai exporters should be aware of and watch, without assuming it currently applies to them or assuming it never will. Getting the proportion right matters, because overreacting wastes resources chasing a requirement that may not apply, while underreacting risks being genuinely unprepared when a customer's question turns out to be a real one.

What to do this quarter, and the wider trend to watch

None of the uncertainty around exact rules and timelines is a reason to do nothing this quarter. There are concrete, low-risk steps available regardless of how the specifics evolve.

Start by asking the EU customer directly what they need, in what format, and by when — customers making this request usually have a template or a specific data format in mind, and asking directly is faster and more accurate than guessing. Next, check the classification of the products actually being sold into the EU, since that classification is what determines whether any of this applies at all, and confirm it rather than assuming it's unchanged from an earlier shipment. Third, find out internally whether anyone in the company — production, engineering, or facilities — already holds energy consumption and production volume data that could form the starting point for this kind of calculation; often the raw data exists somewhere in utility bills and production logs even if no one has assembled it into the shape a customer needs. Finally, decide who inside the company actually owns this going forward — production, quality, sustainability, or commercial — because a request that lands without a clear owner tends to get answered late, inconsistently, or not at all.

It's also reasonable to keep half an eye on the broader direction of travel. The EU is not the only jurisdiction discussing a carbon border mechanism of this general kind, and other governments have at various points signalled interest in similar approaches. No dates, no specific countries, and no particular design should be assumed from that observation — it isn't a prediction about what will happen or when. What it does suggest is that the underlying capability a Thai exporter builds in response to CBAM — knowing the production process well enough to produce credible, product-level emissions data on request — is not a one-off compliance cost tied to a single customer or a single market. It's closer to infrastructure: something built once, that is likely to remain useful as more of the world's major markets start asking versions of the same question.