No more open-ended man-day invoices.Buy outcomes, not man-days.We offer Implement at a fixed price based on the validated scope.

MindDX Blog

CBAM 2026: A Guide to Integrating Carbon Data into Your ERP System

TopicsCarbon and ESGDigital TransformationGovernance and SustainabilityTechnology SolutionsCBAM

MindDX cover: a typographic graphic with the article title «CBAM 2026: A Guide to Integrating Carbon Data into Your ERP System».

Reading time: 8 minutes | Updated in July 2026 | Relevant for: Manufacturing · Export · ERP · CBAM · Carbon management · Sustainability · Digital transformation

The misconception manufacturers exporting to Europe most often run into about CBAM is this: “CBAM is the EU importer’s problem; it doesn’t concern me.”

Yet with the definitive period starting on 1 January 2026, the situation has changed. Your customers in the EU will now ask you for the embedded carbon emissions of your product based not on estimates, but on verifiable data. A manufacturer that cannot provide this is either penalised with high default values or ends up at a price disadvantage on the shelf. Companies that prepared early, meanwhile, have already started obtaining this data from the systems they already have.


Summary –What CBAM requires in 2026 is not buying new carbon software, but integrating your existing production data correctly. Much of the data you need – product recipes, production orders, energy consumption, cost centres – is already scattered across your ERP system. Those who do not provide the data will carry a permanent cost burden from 2028 onwards, with default value mark-ups of up to 30%. In this article, we look at what CBAM changes in the definitive period, how carbon data is fed from ERP production data, and how you can prepare in 5 steps.


Contents
  • What has changed in CBAM in this period?
  • Why is the “default value” expensive for you?
  • Carbon data is actually inside your ERP system
  • A practical 5-step roadmap
  • Conclusion: The cost of delay keeps rising
What has changed in CBAM in this period?

First, let’s clarify the timing, because there is still confusion in the market:

  • The definitive period began on 1 January 2026. It currently covers six sectors: cement, iron and steel, aluminium, fertilisers, electricity and hydrogen — as well as certain downstream products in these sectors.
  • The first surrender of certificates, covering emissions from goods imported in 2026, will take place in 2027 and must be completed by 30 September 2027.
  • Under the Omnibus simplification regulation (EU Regulation 2025/2083), importers whose annual net imports remain below 50 tonnes are exempt from all CBAM obligations. Electricity and hydrogen are excluded from this threshold.

For full details of the regulation and the current timetable, see the European Commission’s official CBAM page.

The critical point for the Turkish manufacturer: The obligation lies with the importer in the EU, but the data is with you. The regulation applies to EU importers; however, importers can request information from all parties in the supply chain in order to meet these obligations. In other words, your EU customer will ask you for installation-specific, verified emissions data.

Why is the “default value” expensive for you?

There are two options: provide actual (verified) emissions data, or use the default values published by the Commission. The second may look attractive because it requires less effort — but it comes at a high price.

For non-electricity goods, the default values include mark-ups intended to reflect the likely underestimation of emissions; these mark-ups will be applied from 2028 onwards, rising to up to 30% for most CBAM goods. In other words: if you do not provide the data, the system calculates with a high estimate that penalises you.

To be able to use actual emissions data, companies have to undergo third-party verification — including an on-site inspection in the first year, and an assessment against a strict 5% materiality threshold. The only way to pass this verification is with traceable data that is collected regularly. This is where ERP comes in.

Carbon data is actually inside your ERP system

The embedded emissions calculation that CBAM requires is not built from scratch; it is built on top of your existing production data.

CBAM calculations go far beyond simple emission factors: importers must define system boundaries, track precursor emissions, distinguish production routes and prepare data rigorously so that it is ready for verification. Each of these elements has a counterpart in your ERP system:

Product structure and bill of materials (BOM). A product’s embedded emissions consist of the emissions of the materials that go into it. The multi-level BOM structure in abas ERP or Odoo forms the natural basis for tracking precursors — information on which semi-finished product goes into which end product is already recorded.

Production orders and production route data. CBAM benchmark values can vary by production route — for example, they differ for natural gas-based DRI and electric arc furnace (EAF) steel. The work order and operation routing data in your ERP system shows which route was used.

Energy and material consumption. The purchasing (MM) and production (PP) modules of the ERP system record the quantity of energy and raw materials consumed. An IIoT layer such as Prodaso IIoT adds the actual energy consumption per machine and verifies this data with measurements — real figures instead of estimates.

Cost accounting (CO). CBAM reporting requires a logic similar to a cost breakdown per product. If your cost centres are already set up, the basic structure for allocating emissions is ready. We covered the role of these modules in cost control in our article on production costs in abas ERP.

A practical 5-step roadmap

Before acquiring “carbon software” from scratch, get the existing system ready for use in this order:

1. Define the scope. Which of your products fall under the CN codes covered by CBAM? Since 1 January 2026, certain CBAM-related codes have to be declared in EU import declarations. The data your customer will ask you for relates to exactly these products.

2. Map the data sources. Determine from which field in the ERP system you will take each emission component (material, energy, process). Fill in what is missing (e.g. machine-level energy) with IIoT.

3. Define the system boundary. Which process steps will be included in the calculation? The bill of materials (BOM) and production route data clarify this.

4. Prepare for calculation and verification. Compile the data according to the CBAM methodology. The verification process assesses not only the final figures, but also how the data was collected, managed, stored and included in the calculations. That is why traceable data from the system, not manually prepared Excel sheets, is vital.

5. Set up the data flow to the customer. Create a process that can deliver regular, verifiable emissions data in the format your EU importer will request.

Conclusion: The cost of delay keeps rising

Companies that delay setting up robust data and supplier processes run the risk of higher costs based on default values becoming permanent; uncertainty, meanwhile, makes planning and budgeting harder.

The goods you export in 2026 form the basis of the certificate calculation in 2027 — in other words, the data you collect today determines next year’s cost.

The good news is this: most of this data already exists in your ERP system. What is missing is the structure that connects this data the way CBAM requires. At MindDX, we work with manufacturing companies that build this bridge by combining abas ERP and Odoo production data with IIoT and Carbon Management Suite layers.

Let’s assess together whether you have products that fall under CBAM and how much of your existing ERP data can be used.Free CBAM data readiness assessment →

▶ Climate Change: Your carbon footprint explained - BBC News

Talk to MindDXAsk the AssistantAll articles on MindDX Blog

Start your project with a measurement, not an estimate.

Talk to MindDX