CBAM Compliance Software for US Importers: What You Actually Need in 2026

If you sell carbon-intensive goods into the EU, the software you need for CBAM does one job above all others: it captures verified embedded-emissions data per product and per supplier once, then reuses it on every shipment so your EU customers can file accurately and cheaply. The legal filing obligation under the Carbon Border Adjustment Mechanism sits with the EU importer, not with you as a US exporter, but the data that filing depends on comes from your side of the ocean. Suppliers who can hand over clean, actual emissions figures instead of punitive default values are the ones EU buyers keep. Good CBAM software turns that data from a quarterly spreadsheet scramble into an audit-ready record. Here is what it should actually do, and exactly where teams get stuck.

The short version

• The EU importer files, but you supply the numbers. The authorized CBAM declarant in the EU is legally on the hook, so your job as a US exporter is to feed them defensible emissions data, and doing that well is a competitive advantage, not just a favor.
• Actual values beat default values. When you cannot document real emissions, your EU customer must use higher default values, which raises their cost and makes you the pricier supplier. Clean data is money.
• 2026 changed the rules in your favor. The definitive regime began on January 1, 2026, but a new 50-tonne annual exemption now spares roughly 90 percent of importers, and certificate purchases do not start until 2027.
• Spreadsheets fail on three fronts. Per-product emissions math, documents that disagree with each other, and the absence of a tamper-evident trail when an auditor asks how you got a number.
• Capture emissions once, reuse everywhere. Centralize supplier and installation data, attach it to the SKU, and let every invoice and report inherit the same figure automatically.
• Audit defensibility is the whole point. A screenshot of a spreadsheet is not a record. What survives scrutiny is a system that shows where each number came from and who touched it.

What is CBAM, and who actually has to file it?

CBAM puts a carbon price on specific goods entering the EU: iron and steel, aluminum, cement, fertilizers, hydrogen, and electricity, with the covered list set to widen over time. The mechanism exists to stop "carbon leakage," the shifting of dirty production outside the EU to dodge its emissions pricing, by charging imported goods for their embedded emissions the way EU-made goods already pay under the bloc's emissions trading system.

Here is the point most US coverage gets wrong. The party that must register as an authorized CBAM declarant, report embedded emissions, and eventually buy CBAM certificates is the EU importer of record, not the foreign producer. As a US exporter you are almost never the filer. You become directly liable only when you are the importer into the EU yourself, for instance when you ship on delivered-duty-paid terms or sell through your own EU entity. In every other case your exposure is commercial rather than legal: your EU buyer needs emissions data from you to file, and how good that data is determines how much CBAM costs them and how attractive you remain as a supplier. The official European Commission CBAM definitive-regime guidance is the authoritative reference for who is obligated and how.

What changed for CBAM in 2026, and what got easier?

The transitional period, which ran from October 2023 through the end of 2025, was reporting only: importers filed quarterly emissions data but paid nothing. The definitive regime started on January 1, 2026, and this is when the obligation grows teeth. But a simplification package known as the Omnibus regulation, adopted in October 2025, softened the edges in ways that matter for smaller US suppliers and their buyers.

• A new 50-tonne de minimis. Importers whose total annual mass of covered goods stays under 50 tonnes (electricity and hydrogen aside) are now exempt. The Commission estimates this removes roughly 90 percent of importers from the obligation while still capturing about 99 percent of the embedded emissions, because the tonnage is concentrated in a handful of large importers. The old 150 euro per-shipment value threshold was scrapped in favor of this cleaner mass-based line.
• Certificates deferred to 2027. Although the definitive regime is live for 2026, the actual purchase and surrender of CBAM certificates, the part where money changes hands, does not begin until February 2027, covering emissions embedded in 2026 imports. That gives everyone a real year to get data pipelines right before the meter starts running.

The practical read for a US team: if your EU customers are large importers, CBAM is live for them now and your data quality directly shapes their 2026 costs. If your buyers are small, some may fall under the new exemption entirely, and confirming that early saves everyone a pile of unnecessary work.

Why do spreadsheets fail at CBAM?

CBAM is not conceptually hard, but it is unforgiving in exactly the ways spreadsheets are weak.

The emissions math compounds. Embedded emissions are calculated per product, per production route, and often per installation, then multiplied across suppliers and shipments. One aluminum product from two plants with different carbon intensities is two different numbers, and a spreadsheet that blends them produces a figure that matches no actual product and survives no audit.

The documents drift apart. The commercial invoice, the certificate of origin, and the CBAM emissions figures live in different files maintained by different people, and they quietly stop agreeing. When a broker or an EU customer's declarant reconciles them, the mismatches surface at the worst moment. Stopping that drift is the whole argument for validating data at the point of entry instead of hoping to catch errors downstream.

There is no defensible trail. When a number is questioned, "it was in the spreadsheet" is not an answer. You need to show the source of each emissions figure, the supplier attestation behind it, and who changed what and when, which is precisely the tamper-evident audit trail that a shared spreadsheet cannot provide. An auditor trusts a system of record, not a screenshot.

What should good CBAM software do?

Judge any tool, ours or anyone else's, against a short list of concrete jobs rather than a marketing promise.

1. Calculate embedded emissions from structured product and supplier data, not from manual lookups retyped each quarter, and keep actual values wherever you have them so your buyers avoid the higher defaults.
2. Generate compliant commercial invoices in the same flow, carrying HS codes, Incoterms, and the matching CBAM figures, so the paperwork and the emissions data can never disagree because they were produced together. This is the same discipline behind auto-generating branded, consistent PDFs from one source of truth.
3. Produce tamper-evident records you can hand to a broker, a customer's declarant, or an auditor with confidence that they will hold up.
4. Connect to the systems you already run. Product data, supplier attestations, and shipment records should flow in through integrations rather than re-keying, because copy-and-paste is where the numbers diverge, a case we made in full in why API integrations beat copy and paste.
5. Bundle the adjacent customs work that always rides along: HS-code classification, sanctions screening, and landed-cost estimates, so one tool covers the boring-but-critical edges instead of three.

This is exactly the problem we built customs-invoice.com to solve: customs invoices and EU CBAM compliance produced in minutes instead of days, from data you enter once.

Step by step: a CBAM rollout for a US team

1. Map which SKUs are actually in scope. Check your catalog against the covered categories, and separate the goods that fall under CBAM today from the ones on the expansion roadmap so you are not boiling the ocean.
2. Confirm whether your buyers even cross the threshold. Ask your EU customers whether their annual tonnage of your goods clears the new 50-tonne line. Some will be exempt, which changes what you need to provide.
3. Centralize supplier and installation emissions data once. Collect actual emissions figures per production installation, attach them to the SKU, and store the supplier attestation alongside each number so its provenance is never in doubt.
4. Wire the invoice and the CBAM calculation to the same data. Make one source feed both, so the commercial invoice and the emissions report are the same numbers by construction, not by careful copying.
5. Turn on the audit trail from the first shipment. Every figure timestamped, sourced, and attributed. Retrofitting a trail after a question has been asked is far harder than keeping one from day one.
6. Reconcile a real shipment before you trust the system. Run one live order end to end, compare the generated documents against the actual goods and the requirements, and only then let a border depend on it. This is the same cautious, prove-it-first sequencing we bring to deciding what to automate first.

Checklist: is your CBAM data audit-ready?

• Every in-scope SKU has an assigned emissions figure, and you know whether it is an actual value or a default.
• Each actual value traces to a named supplier installation and a document you can produce on request.
• Your commercial invoices and emissions reports come from one source, so they cannot silently disagree.
• Changes are logged. You can show who altered any figure, when, and why.
• HS codes are consistent across products, invoices, and reports, not re-entered per shipment.
• A named person owns the data, with a defined cadence for refreshing supplier attestations before they go stale.

Common pitfalls

The failures here are specific to emissions data, and they cost you as a supplier even though the filing is someone else's.

Blended emissions that match no product. Averaging across plants or product lines to save effort produces a number that is convenient and indefensible. The moment a declarant needs installation-level actual values, a blend forces them back to default values, and the higher cost lands on your deal.

Stale supplier attestations. Emissions figures collected once and never refreshed drift out of date as production changes, and an old attestation is worth little when the underlying process has moved on.

Treating CBAM as a document instead of a data problem. Teams generate a nice PDF per shipment and consider themselves done, until an audit asks how the number was derived and there is no lineage behind the pretty output.

Consider a common pattern: a US maker of aluminum extrusions sells to several EU distributors and keeps its emissions data in a spreadsheet that blends output from two plants with different carbon intensities. For a year that blended figure travels on every shipment. Then one distributor's authorized declarant, trying to lower their CBAM bill, asks for installation-level actual values. The exporter cannot produce a defensible per-installation number, so the declarant falls back on default values, the distributor's cost jumps, and a competitor who tracked emissions per plant wins the next contract on a lower landed carbon cost. Nothing here was dishonest. The exporter simply treated a data problem as a paperwork problem and lost business to a supplier who did not. The fix was unglamorous: capture emissions per installation once, attach each figure to the SKU with its supplier attestation, and let every invoice and report inherit it. If EU shipments are a channel you want to defend, tell us about your setup and we will show you what to centralize first.

Where this fits in your business

For a US business trying to keep EU shipments moving without drowning in quarterly compliance work, CBAM is one instance of a broader pattern: a regulatory obligation that lives in your data long before it shows up in a filing. The teams that handle it calmly are the ones who treat emissions figures as a first-class part of their systems rather than a spreadsheet someone updates under deadline. That is the kind of custom software and automation we build, and if your cross-border selling runs through Shopify specifically, the companion piece on Shopify cross-border customs and CBAM covers where the platform's own tools stop and a real compliance layer has to begin.

FAQ

Do US companies have to comply with CBAM?

Usually not as the filer. Registration, reporting, and certificate purchases are the EU importer's legal duty, so most US exporters never submit a CBAM filing at all. The one exception is acting as your own EU importer, on delivered-duty-paid shipments or through an EU entity you control. Short of that, your obligation is narrower but still real: hand your EU buyers accurate embedded-emissions figures on time, because that number, not any paperwork of yours, is what CBAM ends up costing the relationship.

What goods are covered by CBAM?

The current scope is iron and steel, aluminum, cement, fertilizers, hydrogen, and electricity, along with certain downstream products made from them. The European Commission has signaled that the list will expand over time, so a category outside the net today may not stay that way. The practical step is to check your own catalog against the official covered-goods list rather than assume, because a single product line crossing into scope changes what data your EU buyers will ask you for.

When does CBAM start charging money, not just reporting?

The transitional, report-only period ran from October 2023 through the end of 2025. The definitive regime began on January 1, 2026, but under the 2025 Omnibus simplification the actual purchase and surrender of CBAM certificates, the step where importers pay, does not start until February 2027, covering emissions embedded in 2026 imports. So 2026 is a live-obligation year for data and reporting, with the financial meter switching on in 2027.

What is the 50-tonne CBAM threshold?

It is a new de minimis exemption introduced by the 2025 Omnibus regulation: importers whose total annual mass of covered goods stays below 50 tonnes (setting aside electricity and hydrogen) are exempt from CBAM obligations. The European Commission estimates this exempts roughly 90 percent of importers while still covering about 99 percent of the embedded emissions, because the tonnage concentrates among a few large players. It replaced the earlier 150 euro per-shipment value threshold with a cleaner mass-based test, and it is worth confirming with each EU buyer whether they fall under it.

What data do my EU customers need from me for CBAM?

They need the embedded emissions of the goods you ship, ideally as documented actual values tied to the specific production installation, rather than the higher default values the system applies when real data is missing. That means emissions per product and production route, backed by a supplier attestation an auditor could accept, along with accurate HS classification. Providing clean actual values lowers your customer's CBAM cost and keeps you competitive, which is why treating this as a data-quality task rather than a paperwork chore pays off.

Can CBAM reporting be automated?

Yes, and it should be, because the parts that go wrong in spreadsheets, per-product emissions math, documents that drift out of agreement, and the lack of an audit trail, are precisely the parts software handles well. A good setup captures emissions and supplier data once, attaches it to each SKU, feeds both the commercial invoice and the emissions report from that single source so they cannot disagree, and logs every change for defensibility. That turns a recurring quarterly scramble into a few minutes of review per shipment.