GHG PRODUCT STANDARD · WBCSD / WRI

The GHG Protocol Product Standard is the other main way to count a product's footprint.

Same intent, different heritage. Pick the one your buyer names in the contract.

Runs on your public disclosures. Nothing from you.

Deadline: Buyer-driven, request-based In scope: Any product a buyer asks to account for GHG emissions on Penalty: RFP loss, contract requirement gap
This is for

You are the Product Manager or Head of Sustainability at a manufacturer whose customer references GHG Protocol by name. A US-based customer asked for a product-level GHG number under the WBCSD/WRI Product Standard. You reply with ISO 14067 and get pushed back.

The answer

The GHG Protocol Product Life Cycle Accounting and Reporting Standard (2011) is the WBCSD/WRI-published methodology for quantifying the GHG emissions associated with a specific product. It is one of the two dominant product-level accounting standards, the other being ISO 14067. Both use Life Cycle Assessment as the foundation. Both cover cradle-to-grave by default with cradle-to-gate as an allowed subset. They are compatible; contracts sometimes name one specifically.

What GHG Product Standard actually is

The scope is one product studied along its full life cycle. Every stage (material acquisition, production, distribution, use, end-of-life) is quantified in CO2 equivalent per functional unit.

The Product Standard sits under the GHG Protocol umbrella alongside the Corporate Standard (for organisation-level accounting) and the Scope 3 Standard. It is designed to feed both product-level buyer disclosures and Scope 3 Category 11 (use of sold products) calculations.

The standard requires assurance, by a first party or a third party. Third-party assurance is optional, but US buyers and Fortune 500 customers often ask for it when the product number goes into their own Scope 3 reporting.

Why now

Many US corporates now cite the GHG Protocol Product Standard in supplier data requests as they build their Scope 3 numbers for SBTi targets, CDP and California's SB 253. A number under one standard translates to the other with methodological notes.

WHAT BREAKS

What breaks when your carbon number is not defensible.

Three common reasons a GHG Product Standard number gets sent back.

FAILURE 01

Different standard than the buyer asked for

Buyer names GHG Protocol Product Standard. Supplier delivers under ISO 14067 without a reconciliation note. Buyer procurement rejects.

FAILURE 02

Life-cycle stages omitted

The use phase and end-of-life stages skipped in the calculation. The Product Standard requires cradle-to-grave unless a cradle-to-gate cut is justified.

FAILURE 03

Data quality unnamed

The Product Standard requires a statement on data sources and data quality for every significant process. Leave it out and the buyer sends the report back.

HOW CARBON-OS ANSWERS

Three moves that make GHG Product Standard defensible.

ANSWER 01

Both standards, one workflow

Carbon-OS builds the product footprint once, tagged to either standard. Whichever the buyer names, the delivery matches.

ANSWER 02

Full life-cycle scoping

Cradle-to-grave by default, cradle-to-gate as an explicit choice with justification captured in the report.

ANSWER 03

Data-quality per input, on record

Every input carries a data-quality tag (representativeness, completeness, temporal alignment). The buyer sees the assessment, not just the number.

See where your GHG Product Standard number stands. Free scan.

Run the free Carbon X-Ray →
FAQS

What people ask, straight.

Do we do GHG Product Standard or ISO 14067?

Do the one your buyer specifies. If neither is named, ISO 14067 is safer internationally. GHG Protocol Product Standard is safer for US-domiciled buyer relationships.

Are the two standards interchangeable?

With the same data and choices they usually land close. Differences come from allocation, end-of-life, biogenic carbon and boundary rules, so add a short reconciliation note when you switch.

Is verification required?

ISO 14067 makes verification optional. The GHG Protocol Product Standard requires assurance, either by an independent internal team or an outside firm. For public claims or a buyer's Scope 3, expect an outside check either way.

How does this feed Scope 3?

A product-level number is the input to Scope 3 Category 1 (upstream, for the buyer) and Category 11 (use of sold products, for you). A product number gives your buyer real data for their Category 1, and gives you the base for your own Category 11 where the product uses energy or fuel.

What data do we collect for a first calculation?

Bill of materials, energy use in production, transport distances, packaging materials, use-phase energy or fuel, and end-of-life route. Suppliers provide their upstream numbers.