SDAI Insights
Product carbon footprints need versioned methods, not static formulas
A product carbon footprint is increasingly incomplete without the method version behind it.
Event date
Thesis
A product carbon footprint is increasingly incomplete without the method version behind it. As ISO 14067 enters revision, product-footprint systems should be designed so methodology can change without forcing teams to rebuild the underlying inventory or lose the history of how an earlier result was calculated.
What changed
ISO is developing a second edition of ISO 14067, the standard for quantifying the carbon footprint of products. The current project, ISO/WD 14067.2, is intended to replace ISO 14067:2018 while remaining aligned with the ISO 14040 and ISO 14044 life-cycle framework. The 2026 working-draft study closed its comment period on May 25. The project is still under development. The significance is not that a new set of final rules has already arrived, but that one of the core product-carbon standards is moving again.
Analysis
A PCF number is difficult to interpret when it arrives without its calculation context. Two footprints for the same product can differ because of operational performance, but they can also differ because the studies used different allocation rules, electricity treatments, data vintages, exclusions or reporting methods. If those choices are not stored explicitly, a future method update can make historical results difficult to reproduce or compare. Methodology therefore needs to be treated as versioned configuration, not hidden logic.
Engineering implications
The product system and the reporting method should be separate objects. The foreground model should retain the physical and operational data needed to calculate the footprint. A method profile should define how that inventory is interpreted and reported. At minimum, a reproducible PCF record should preserve: - activity data and units, - emission factors and dataset versions, - allocation choices, - treatment of biogenic carbon, - electricity-accounting method, - exclusions and cut-off rules, - uncertainty and data-quality information, - method and reporting version. That separation makes it possible to rerun the same inventory when methodology changes and identify whether a result moved because the factory changed or because the accounting rules changed.
What to watch next
LCAgo should treat method profiles as versioned objects rather than a static compliance checkbox. A user should be able to rerun the same product inventory under a revised method and compare the two results side by side, with a clear explanation of which assumptions changed. That is a more useful form of standards support than simply labeling a model "ISO-aligned."
Primary source
ISO/WD 14067.2 remains under development. This analysis uses publicly available ISO project information only and does not describe final requirements or reproduce restricted draft text.
ISO/WD 14067.2Related work
See the research and case studies behind SDAI's technical analysis.