If you're new to product carbon footprinting, start with our guide on Decoding Product Carbon Footprints: Methodologies and Benefits, which covers what a PCF is and how to choose the right methodology standard for your business.
This post picks up from there and walks through the actual steps of running a calculation.
Every PCF calculation comes back to the same basic equation used in corporate GHG inventories, just applied at the product level:
ghgEmissions = activityData x emissionFactor x GWP
A quick refresher on each variable:
You'll use this formula repeatedly, once for every process in your product's lifecycle, then sum the results.
Before you can calculate anything, you need a reference quantity to measure emissions against. This is called a functional unit, such as one bottle of shampoo or one pair of running shoes.
If you're doing a partial (cradle-to-gate) footprint, this reference is usually called a declared unit instead, typically a defined mass or volume, like one kilogram of packaged coffee.
Every process in your calculation gets measured relative to this single unit, which is what makes the final number comparable across products or against a benchmark.
Your system boundary determines which lifecycle stages you're including. The five main stages are:
Most companies start with a cradle-to-gate boundary (everything from raw material extraction through your factory gate) before expanding to a full cradle-to-grave analysis that includes downstream use and disposal.
For a deeper look at how these boundaries work, see the boundary-setting section in our core PCF guide.
Once your boundary is set, map out every process your product touches within it. For each process, identify what flows in (materials, energy) and what flows out (product, waste, byproducts).
For example, a packaging step might have cardboard and electricity flowing in, and a sealed box flowing out. Each of these flows becomes a data point you'll need to collect activity data for.
This is where PCF calculations diverge from company-level GHG inventories. At the corporate level, you might count all the electricity used at a factory. At the product level, you only count the share of that electricity tied to producing one functional unit of your specific product.
A few practical sourcing tips:
For each activity data point, apply the appropriate emission factor. These can come from:
Multiply by GWP to convert non-CO2 gases into CO2e, unless the factor is already expressed on a CO2e basis.
Once every process has an emissions figure, sum them all to get your total CO2e per functional unit. This is your PCF.
From here, the number becomes a tool: use it to identify emissions hotspots, evaluate design trade-offs, respond to customer or regulator data requests, or benchmark against competitors.
For guidance on choosing the methodology standard that determines how this number gets verified and shared, revisit the methodology selection section of our core guide.
What's the difference between a functional unit and a declared unit?
A functional unit describes a product in terms of the function it performs, such as one wash cycle's worth of detergent, and is used for full cradle-to-grave comparisons.
A declared unit is a simpler reference quantity, like one kilogram or one liter, used when a full functional comparison isn't possible or necessary, such as in a cradle-to-gate footprint.
What data do I need to calculate a PCF?
At minimum, you need activity data (energy use, material quantities, transport distances) for every process within your system boundary, along with matching emission factors for each.
The more of this data comes from your own operations and suppliers rather than industry averages, the more defensible and specific your footprint will be.
How is a PCF different from a corporate carbon footprint?
A corporate carbon footprint (CCF) totals emissions across an entire company's operations over a reporting period. A PCF isolates the emissions tied to a single product, measured against one functional or declared unit, and often draws on the same underlying activity data allocated down to the product level.
Do I need third-party verification for my PCF?
It depends on your use case. Internal hotspot analysis generally doesn't require verification. Footprints used for regulatory compliance, on-product claims, or shared with customers under frameworks like PACT typically benefit from or require third-party verification against a standard like ISO 14067.
How long does it take to calculate a PCF?
Timelines vary based on product complexity, data availability, and whether you're building your first process map from scratch. A well-scoped first cradle-to-gate PCF for a single product can often be completed in a matter of weeks, particularly with existing supplier data and the right tooling in place.
