Why Product-Level Carbon Accounting Changes Everything

For nearly two decades, the global carbon accounting regime has been anchored to a single unit of analysis: the facility. Corporations disclose the total greenhouse gas emissions of their factories, refineries, and power plants. CDP questionnaires ask for site-level Scope 1 and 2 figures. The Greenhouse Gas Protocol provides guidance for rolling those numbers up into a corporate inventory. And sustainability reports present the result — a single number, often in millions of tonnes of CO2 equivalent, that purports to describe an entire company's climate impact.

That era is ending. A convergence of regulatory mandates, buyer requirements, and market mechanisms is forcing a fundamental shift in how emissions are measured, reported, and valued. The new unit of analysis is not the facility. It is the product.

1. The Shift from Facility to Product

Facility-level GHG reporting served an important purpose. It established the discipline of corporate emissions measurement, built the institutional infrastructure for third-party verification, and created the data foundations for national and international climate policy. Frameworks like CDP, the GHG Protocol, and the EU ETS were designed around facilities because that was the tractable unit — a refinery has a fence line, metered energy inputs, and stack emissions that can be quantified with reasonable accuracy.

But facility-level accounting has a critical limitation: it tells you nothing about the carbon intensity of individual products. A petrochemical cracker producing ethylene, propylene, butadiene, and a dozen co-products reports a single facility emissions number. A refinery processing crude oil into gasoline, diesel, jet fuel, LPG, naphtha, and asphalt reports one aggregate figure. A steel mill producing hot-rolled coil, rebar, and wire rod bundles everything into a single disclosure.

The market has recognized this gap. Regulators now require product-level data. The EU's Carbon Border Adjustment Mechanism (CBAM) does not ask importers for facility-level emissions. It asks for the specific embedded emissions per tonne of product — steel, aluminium, cement, fertiliser, hydrogen, and electricity. That is a fundamentally different question, and answering it requires a fundamentally different approach to carbon accounting.

Buyers are moving in the same direction. Apple requires its suppliers to report the carbon footprint of specific components. BMW demands product-level emissions data from steel and aluminium suppliers. Volvo has committed to publishing the lifecycle carbon footprint of every vehicle model. These are not voluntary disclosures; they are procurement requirements that determine whether a supplier keeps or loses the contract.

2. What Product-Level Carbon Intensity Actually Means

Product-level carbon intensity (CI) expresses the greenhouse gas emissions attributable to one unit of a specific product. It is typically measured in kilograms of CO2 equivalent per kilogram of product (kgCO2e/kg), per tonne (tCO2e/t), or per unit of energy output (gCO2e/MJ). The concept is straightforward. The execution is not.

Calculating product-level CI requires answering three questions that facility-level accounting never had to address:

• Scope allocation: How do you attribute Scope 1 (direct combustion and process emissions), Scope 2 (purchased electricity and heat), and Scope 3 (upstream supply chain) emissions to individual products that share the same production infrastructure?
• Allocation methodology: When a single process produces multiple products simultaneously — as in refining, petrochemical cracking, or metals smelting — what method do you use to divide the total emissions among co-products?
• Temporal resolution: Do you calculate CI as an annual average, a monthly figure, or a per-batch measurement tied to actual operating conditions at the time of production?

The Allocation Challenge

The allocation problem is where product-level carbon accounting gets genuinely difficult. Consider a steam cracker at a petrochemical complex. The cracker takes a single feedstock — naphtha, ethane, or a mixture — and produces ethylene, propylene, mixed C4s (butadiene, butylene, butane), pyrolysis gasoline, and fuel gas, all from the same thermal process. The furnace burns the same fuel regardless of product slate. The energy input is shared. The emissions are joint.

Three primary allocation methods exist, each with different implications:

• Mass allocation divides emissions in proportion to the mass of each product. Simple and reproducible, but it treats a tonne of ethylene (high-value) the same as a tonne of fuel gas (low-value), which distorts economic signals.
• Energy allocation divides emissions based on the energy content (calorific value) of each product. Better for energy carriers like fuels and gases, but less meaningful for chemical products valued for their molecular properties, not their heating value.
• Economic allocation divides emissions based on the market value of each product. Reflects commercial reality, but introduces price volatility into what should be a physical measurement. When ethylene prices spike, ethylene's CI rises even though nothing changed in the furnace.

The choice of method is not academic. For the same facility operating under the same conditions, different allocation approaches can yield CI figures that vary by 30% or more for a given product. This is why regulators are increasingly prescriptive about methodology — CBAM's implementing regulation (CDR 2023/1185) specifies mass-based allocation as the default, with limited exceptions. ISO 14067 and the Product Environmental Footprint (PEF) framework provide additional guidance, but significant methodological discretion remains.

3. Why It Is Hard: The Data Problem

The single largest barrier to product-level carbon accounting is not methodology. It is data. Specifically, it is the gap between where the data lives and where the calculation needs to happen.

In a typical industrial facility — a refinery, a petrochemical plant, a mine, a smelter — the operational data required for CI calculation is scattered across a patchwork of systems that were never designed to talk to each other:

• SCADA and DCS systems capture real-time process data: flow rates, temperatures, pressures, equipment status. This data sits in the operational technology (OT) domain, behind firewalls, in proprietary formats, often stored in historians like OSIsoft PI or Honeywell PHD.
• ERP systems (SAP, Oracle) contain production volumes, material movements, and energy procurement data. This is the IT domain — different teams, different access controls, different data models.
• Laboratory information management systems (LIMS) hold feedstock and product quality data, which determines emission factors for process emissions.
• Energy management systems track electricity, steam, and fuel consumption by unit, but often at aggregated levels that do not map cleanly to individual product lines.
• Emissions monitoring systems (CEMS) measure stack emissions, but at the point of release, not at the point of product attribution.

The result is a data landscape that is fragmented by system, fragmented by organizational boundary (plant engineers own the OT data, sustainability teams own the reporting obligation), and fragmented by time (some data is real-time, some is monthly, some is entered manually on an annual basis).

In practice, most companies today bridge this gap with spreadsheets. A sustainability analyst sends an email to the plant manager requesting production data. The plant manager asks a process engineer to pull numbers from the DCS historian. Those numbers get pasted into an Excel workbook. Emission factors are applied. Allocation is performed manually. The result is reviewed by a consultant, adjusted, and eventually submitted — months after the reporting period ended.

This process is slow, expensive, and error-prone. It produces annual averages at best. It cannot support the per-batch, per-shipment CI claims that CBAM and buyer mandates require. And it scales linearly: every additional product, every additional facility, every additional reporting framework requires more manual effort. For a multi-product refinery exporting to the EU, the current approach is not just inadequate. It is unsustainable.

4. The Regulatory Push

The regulatory landscape is converging rapidly on product-level emissions data. This is not a trend to be monitored. It is a compliance reality that is already generating financial obligations.

CBAM: Embedded Emissions Per Product

The EU's Carbon Border Adjustment Mechanism entered its definitive phase in January 2026. Importers of covered goods — iron and steel, aluminium, cement, fertilisers, hydrogen, and electricity — must now purchase CBAM certificates corresponding to the embedded emissions of each imported product. The price of those certificates is linked to the EU ETS carbon price, currently fluctuating between 55 and 75 euros per tonne.

The critical detail: CBAM requires actual embedded emissions per installation and per product, calculated according to the methodology laid out in CDR 2023/1185. Default values (based on averages from the exporting country or worst-performing benchmarks) apply when actual data is not available — and those default values are significantly higher than what efficient producers actually emit. A steel producer in the Middle East using best-available technology might have a CI of 1.6 tCO2/t steel, but the CBAM default value could be 2.3 or higher. The difference, multiplied by export volume and the EU carbon price, translates directly into millions of euros in excess costs.

SEC Climate Disclosure and Scope 3

The SEC's climate disclosure rules require large public companies to report material Scope 3 emissions. For industrial producers, Scope 3 Category 1 (purchased goods) and Category 11 (use of sold products) are the dominant categories. Meaningfully reporting these requires product-level granularity. You cannot calculate the downstream emissions of sold petroleum products without knowing the carbon intensity of each product grade. You cannot estimate the Scope 3 impact of sold polyethylene without a product-level CI that accounts for feedstock, cracking, and polymerization.

CSRD/ESRS: Value Chain Emissions at Product Level

The Corporate Sustainability Reporting Directive (CSRD) and its European Sustainability Reporting Standards (ESRS) require companies to disclose Scope 3 emissions across the value chain. ESRS E1 (Climate Change) specifically calls for emissions intensity metrics that, for industrial companies, must be calculated at the product or activity level to be meaningful. Starting in 2026, tens of thousands of EU and non-EU companies fall under CSRD's scope.

Customer Mandates

Beyond regulation, major industrial buyers are imposing their own product-level requirements. Apple's Supplier Clean Energy Program requires component-level carbon data. BMW has committed to halving supply chain CO2 per vehicle by 2030 — achievable only with product-level supplier data. The Responsible Steel certification standard requires product-level GHG intensity reporting. Maersk asks container shipping customers for product-level embedded emissions to calculate and offset transport footprints.

5. How Agentic AI Solves This

The product-level carbon accounting problem is, at its core, a data integration and continuous computation problem. The methodology exists. The regulatory requirements are defined. What is missing is the operational capability to execute — to continuously collect data from disparate industrial systems, apply allocation algorithms at the batch level, detect and resolve data quality issues, and produce outputs that auditors and regulators can trust.

This is where agentic AI represents a genuine architectural shift, not an incremental improvement over existing tools.

Forward-Deployed Engineering

Traditional sustainability software asks plant operators to export data and upload it to a cloud platform. This is a manual, periodic process that breaks at every step. Agentic AI takes the opposite approach: it deploys agents directly into the OT/IT environment. These agents connect to SCADA historians, DCS systems, ERP databases, and LIMS directly. They ingest data at the source, in real time, without requiring plant engineers to change their workflows or sustainability analysts to understand process control systems.

Continuous Ingestion and Calculation

Once connected, agents perform CI calculations continuously — not quarterly, not annually, but as production happens. When a batch of ethylene leaves the cracker, the agent has already computed its CI based on the actual feedstock composition, actual furnace energy consumption, actual electricity grid carbon intensity, and actual co-product yields from that specific run. The result is a per-batch CI score with a complete data provenance trail.

Automated Allocation at Scale

Agents execute allocation algorithms automatically, following the methodology prescribed by the applicable framework (CBAM, ISO 14067, PEF, or customer-specific requirements). When a refinery runs 20 product streams simultaneously, the agent applies mass-balance allocation across all streams for every production period. When methodology changes — as regulators update implementing regulations — the agent can recalculate historical periods under the new rules.

Anomaly Detection and Data Quality

One of the most valuable capabilities of agentic AI in this context is automated data quality assurance. Industrial data is noisy. Flow meters drift. Sensors fail. Manual entries contain transcription errors. Lab results arrive late. Agents detect anomalies in real time — a sudden spike in reported energy consumption, a mass balance that does not close within tolerance, a feedstock composition that falls outside the expected range — and flag them for resolution before they propagate into CI calculations. This catches errors that annual audits would only find months later.

Machine-Verifiable Outputs

The final piece is auditability. Agentic AI produces outputs that are machine-verifiable: every CI score comes with a complete computation trace from raw sensor data through normalization, allocation, and calculation to the final figure. Every data point is blockchain-anchored, creating an immutable audit trail. When a third-party verifier reviews a CI claim, they do not need to re-derive the number from scratch. They can inspect the automated computation chain and verify that the methodology was applied correctly to validated inputs.

6. The Business Case

Product-level carbon accounting is often framed as a compliance cost. This framing is incomplete. For industrial producers who get it right, product-level CI is a revenue driver, a market access enabler, and a source of operational intelligence.

Green Premiums

Verified low-carbon industrial products already command price premiums. Low-carbon aluminium trades at a 5-15% premium over standard-grade. Certified low-CI hydrogen attracts premiums of 20-30% in markets with clean fuel standards. Green steel — steel produced with verified CI below defined thresholds — commands premiums of 10-25% from automotive and construction buyers willing to pay for decarbonized supply chains. These premiums are not theoretical. They are being captured by producers who can substantiate their claims with auditable, product-level data.

Market Access

CBAM non-compliance means one of two outcomes: paying tariffs based on default values that significantly overstate actual emissions, or losing access to the EU market entirely. For producers in the Middle East, Asia, and North America exporting steel, aluminium, cement, fertiliser, or hydrogen to the EU, the ability to report actual product-level emissions is not a competitive advantage. It is a market access requirement. The gap between actual CI and the default value, multiplied by volume and the EU carbon price, can represent tens of millions of euros annually.

Investor Pressure

ESG ratings agencies — MSCI, Sustainalytics, CDP — are increasingly evaluating companies on the granularity and quality of their emissions data. Facility-level reporting satisfies baseline requirements. Product-level data signals operational maturity, strategic seriousness, and reduced transition risk. For publicly traded industrial companies, this translates into improved ESG scores, lower cost of capital, and stronger positioning with institutional investors integrating climate criteria.

Operational Efficiency

Continuous product-level CI calculation reveals operational inefficiencies that aggregated annual reporting obscures. When you can see that a specific batch of polyethylene had 18% higher CI than the facility average, you can trace the cause: higher-carbon grid electricity during a specific shift, a suboptimal furnace firing profile, or a feedstock quality issue. CI optimization and energy optimization are, in most industrial processes, the same thing. Companies deploying product-level CI systems consistently report that the operational insights alone justify the investment, independent of compliance value.

7. From Compliance Burden to Strategic Asset

The most forward-looking industrial companies are not treating product-level carbon accounting as a regulatory obligation to be minimized. They are treating it as a strategic asset to be developed.

Product-level CI is, functionally, an environmental attribute — a quantified, verified characteristic of a physical product that has independent market value. This is the same concept that underpins Environmental Attribute Certificates (EACs) in electricity markets, where renewable energy certificates (RECs) and guarantees of origin (GOs) are traded separately from the physical electricity they represent.

The industrial products market is moving toward the same model. Low-carbon steel certificates, verified hydrogen CI scores, and certified green aluminium are becoming tradeable attributes. A producer who invests in the measurement infrastructure to generate auditable, continuous, product-level CI data is building a factory for producing environmental attributes — not just products.

This inversion — from compliance cost to attribute production — changes the economics fundamentally. The compliance investment is not a sunk cost. It is the infrastructure for a new revenue stream. Companies that move first capture the premium. Companies that wait pay the tariff.

The shift from facility-level to product-level carbon accounting is not optional, and it is not gradual. CBAM's definitive phase is live. SEC disclosure requirements are being implemented. Buyer mandates are arriving in procurement contracts today. The question for industrial producers is not whether to build product-level carbon accounting capability, but how to build it fast enough — and whether to build it as a manual, periodic exercise that satisfies minimum requirements, or as an automated, continuous system that generates competitive advantage.

The answer, for any producer operating at scale across multiple products and jurisdictions, is clear. Manual processes cannot keep up with the velocity, granularity, and auditability that the new regime demands. Agentic AI — forward-deployed, continuously operating, machine-verifiable — is the architecture that matches the ambition of the regulation and the opportunity of the market.