The Carbon Stack Is Splitting Into Data, Calculation and Reporting Layers: What It Means for Scope 3 Teams in 2026

A Scope 3 team measuring suppliers or portfolio companies can now buy calculation as an API from several directions, so the figure is only as useful as the data it runs on. Verdantix expects the carbon stack to separate into data, calculation and reporting layers, with reporting platforms keeping governance.
What is changing in the carbon management stack?
In From APIs To Agents: The Next Disruption In Carbon Management? (1 June 2026), Alessandra Leggieri describes embedded calculation reaching broader enterprise software. A large software vendor made an emissions API generally available in late April 2026 so firms can embed emissions calculations in their own systems, and developer-first providers have offered the same through APIs since 2021.
Verdantix says the carbon stack is gradually separating into data, calculation and reporting layers, and points to a problem in the bottom one:
"Emission factors remain fragmented across multiple sources, with different structures, levels of detail and update cycles." Alessandra Leggieri, Senior Analyst, Verdantix
Specialist providers are working on aggregating and standardising that factor data beneath calculation engines.
What does the data layer need to hold for Scope 3?
LayerWhat it holdsThe question to askCompany emissions dataReported GHG inventories, and service and product-level carbon footprints, for named organisationsHow many of the organisations I buy from or invest in are covered before any request goes out?Supplier-specific (primary) emissionsFigures calculated for a named organisation at spend, activity and product levelWhat share of my baseline sits here, and what share on a generic factor?Generic emission factorsPublished factors applied to a category, such as a rate per unit of spendWhere in the order of methods is it reached?
Aggregating and standardising factors improves the third row. Every serious platform holds a large library of published factors, DitchCarbon included, and ours draws on ecoinvent, CEDA, EPA, DEFRA and EXIOBASE, so library size is table stakes. The first two rows separate platforms. DitchCarbon holds verified emissions data for over 2 million organisations, built on primary emissions data wherever it exists, so a generic factor is the last method reached on any line.
How can a buyer test the data layer?
Ask any vendor to show, on your own list, how many lines rest on a sector average. At DitchCarbon each organisation records which method produced its figure, the method is a filterable column, and the headline figure toggles between organisation-specific and industry factors, so the share is a number you can read on that list. A platform that cannot produce it is telling you something by not having it.
Does a separate data layer replace the reporting platform?
Verdantix expects the opposite: a hybrid architecture in which reporting platforms keep a central role in governance, consolidation and reporting. Where a team already runs a system of record for the inventory and the disclosure, DitchCarbon becomes the data layer feeding it: the emissions, the score, the target status and the source behind each figure arrive as data the platform can read.
Run on its own, DitchCarbon is the platform: it measures, engages suppliers, forecasts each organisation against its own target trajectory and tracks progress.
Calculation can be embedded anywhere in the stack. DitchCarbon calculates on product data, activity data and supplier-specific spend, and only when all else fails, industry-level spend.

