As climate reporting matures, more suppliers are stepping up with Product Carbon Footprints (PCFs)[ra1] , a welcome shift toward primary data for Scope 3.1 (purchased goods and services). These footprints offer product-level insights that can elevate the precision of a company’s emissions inventory and even inform supplier selection or design decisions.
But here’s the catch: not all PCFs are created equal.
Without clear validation protocols, companies risk embedding flawed or inconsistent data into their GHG inventories. Misaligned system boundaries, unclear functional units, and unverifiable emission factors can seriously distort a Scope 3.1 profile, eroding trust with regulators, investors, and internal stakeholders.
In this blog, we walk you through a practical validation checklist to help you assess the quality and reliability of supplier-provided PCFs, ensuring that your Scope 3.1 emissions accounting remains accurate, auditable, and fit for decision-making.
PCFs are gaining traction as the gold standard for product-level emissions, but premature adoption without scrutiny poses risks:
Robust validation is your safeguard. It ensures that supplier data not only “looks right” but is accurate, from both a technical and reporting standpoint.
Start with the system boundary. For Scope 3.1, the PCF should reflect a cradle-to-gate boundary, covering:
Many suppliers mistakenly provide gate-to-gate or site-level footprints that exclude major upstream emissions. These may reflect energy use at the final manufacturing site only, missing most of the carbon impact.
Checklist: Ask suppliers to clearly specify the boundary used and whether it includes upstream value chain stages.
A PCF must be reported per a defined functional unit, such as:
Also, confirm that the PCF corresponds to the specific product or material your company buys, not a generic category.
Example: A PCF for “flexible plastic packaging” is insufficient if you’re procuring “BOPP multilayer film, 250-micron, 3-layer, from India.”
Checklist: Ensure unit consistency and product matching with your procurement records.
Ask for detailed documentation on how the PCF was calculated. Look for transparency around:
Checklist: Confirm alignment with internationally accepted calculation frameworks.
Emissions profiles change over time with updates in energy mix, manufacturing processes, or supplier operations.Using a PCF from 2015 based on coal-heavy electricity no longer reflects current emissions if the site transitioned to renewables in 2023.
Checklist:
While not mandatory, third-party verification strengthens credibility. Common reviewers include:
Where third-party assurance isn’t available, request a self-declaration checklist showing internal QA procedures.
Checklist: Ask whether the PCF has undergone:
The integrity of a PCF depends heavily on the quality of its emission factors. Red flags include:
Checklist: Ensure emission factors come from traceable, publicly available sources, such as:
If you receive PCFs from multiple suppliers for similar products, do a sanity check:
If Supplier A reports 1.2 kg CO₂e/kg for aluminium sheet and Supplier B reports 4.8 kg CO₂e/kg for an identical spec, ask why.
Checklist:
Want to simplify Scope 3.1 supplier reporting?
The rise of supplier-provided PCFs signals a major evolution in Scope 3.1 data maturity. But quality must always accompany quantity. Without systematic validation, you risk undermining the very benefits primary data promises.
Use this checklist as a gatekeeper. It helps you accept only those PCFs that are methodologically sound, boundary-aligned, and product-specific, ensuring your GHG inventory is both accurate and defensible.
As your program evolves, embed PCF validation into supplier onboarding, procurement contracts, and internal data governance policies. This not only strengthens your emissions accounting but also builds trust across your value chain.
No, but it adds credibility and reduces validation effort. If missing, request QA documentation or adherence to standards like ISO 14067.
Ask for clarification. If the footprint does not include cradle-to-gate impacts, do not use it for Scope 3.1.
It’s risky. Instead, work with the supplier to correct or update the data. Always document any adjustments clearly.