Product carbon footprint: how to read, calculate, and use PCF data
Understand product carbon footprint boundaries, units, calculation, and verification, then model supplied PCF data for reliable product catalogs.
A product carbon footprint (PCF) is useful only when the record around the value is clear. 2.4 kg CO₂e could describe one item, one kilogram, a factory gate, or an entire life cycle. Those are different claims.
Product-data and sustainability teams need a practical way to carry a supported value into a structured catalog. Catalog's role starts after a supplier or qualified practitioner has produced the result. We preserve provenance and distribute the supplied fact. We do not calculate or certify it.
What is a product carbon footprint?
A product carbon footprint measures the greenhouse-gas emissions and removals attributable to a defined product system over a stated part of its life cycle. It is expressed in carbon-dioxide equivalents (CO₂e). ISO 14067 applies life-cycle-assessment principles to the climate-change impact category, so a PCF does not describe every environmental impact of a product.
A PCF usually answers a question such as:
How many kilograms of CO₂e are associated with one defined quantity of this product, across this stated lifecycle boundary, for this period and geography?
The number needs its context. A usable PCF record includes:
| Field | Example | Why it matters |
|---|---|---|
| PCF value | 2.4 | The calculated climate impact needs the fields around it. |
| Unit and quantity | kg CO₂e per 1 item | A value per kilogram cannot be compared directly with a value per item. |
| Lifecycle boundary | cradle-to-gate | The boundary determines which stages are counted. |
| Period and geography | 2025, Germany | Energy, suppliers, transport, and waste systems change by place and time. |
| Method and evidence | PACT V3, third-party verified | Users need to understand how the result was built and reviewed. |
The value does not make a product “green,” “low carbon,” or “carbon neutral” by itself. Those claims require a documented comparison, reduction accounting, or other evidence beyond one PCF result.
Lifecycle boundaries determine the result
A lifecycle boundary states where the accounting starts and stops. Two products can have identical values and very different levels of coverage if their boundaries differ.
| Lifecycle stage | What it can include |
|---|---|
| Materials and preprocessing | Raw-material extraction, purchased inputs, packaging materials, and processing before production |
| Production | Energy, fuel, process emissions, waste, and transformation into the finished product |
| Distribution and storage | Transport and storage within the defined stages, plus separately reported outbound logistics where required |
| Use and maintenance | Energy, consumables, repairs, and other emissions while the customer uses the product |
| End of life | Collection, reuse, recycling, treatment, and disposal |
A cradle-to-gate PCF covers the product from raw materials through a defined production gate. The PACT calculation guide focuses on material acquisition and preprocessing, production, and distribution and storage for cradle-to-gate exchange. It also describes when outbound logistics should be reported separately up to the handover point.
A cradle-to-grave PCF continues through customer use and end of life. ISO 14067 supports full cradle-to-grave analysis and partial footprints, including cradle-to-factory-gate studies. Other boundaries include gate-to-gate and cradle-to-customer. Use the exact boundary name and list the included stages in the product record.
Do not compare a cradle-to-gate value with a cradle-to-grave value as if they describe the same product journey. A catalog should store the boundary as a field, not bury it in a PDF or a free-text note.
Units answer “per what?”
The standard unit is a mass of CO₂e, usually kilograms, tied to a declared unit or functional unit.
- A declared unit describes the quantity being reported, such as one item, one kilogram of material, one litre, or one tonne.
- A functional unit describes the service or function delivered, such as one square metre of flooring for a stated service life. It lets users compare products that provide the same function when the assumptions match.
Examples make the difference clear:
3.1 kg CO₂e per one insulated jacketdescribes one product.0.8 kg CO₂e per kg of polymerdescribes a mass of material.12 kg CO₂e per square metre of flooring over a stated service lifedescribes a function and duration.
Keep the quantity represented with the value. If a supplier gives 480 kg CO₂e for a batch of 200 units, the record needs the batch quantity and the method used before anyone derives a per-item value. Do not silently divide, round, or convert a result when the declared quantity is unclear.
CO₂e combines the climate effects of relevant greenhouse gases and removals using the global-warming-potential rules selected by the method. Preserve the reported unit and methodology version. A conversion can change the meaning if it changes the reference quantity, gas treatment, or boundary.
How a product carbon footprint is calculated
1. Set the goal and scope
Identify the product, variant, market, reporting period, intended use, declared or functional unit, geography, boundary, and calculation method. Choose an industry rule or product-category rule when one applies. This is where the team decides what the result is intended to represent.
The GHG Protocol Product Standard provides product-level life-cycle accounting and reporting guidance. ISO 14067 provides another foundation. PACT Methodology V3 adds practical guidance for calculating and exchanging cradle-to-gate PCFs. Record the selected standard and version rather than storing only “calculated with standard methodology.”
2. Build the life-cycle inventory
List the activities attributable to the product and assign an owner and source to each data point. Depending on the boundary, the inventory can include:
- bills of materials, component footprints, packaging, material quantities, and processing steps;
- electricity, fuel, heat, refrigerants, process emissions, production waste, and co-products;
- inbound and outbound transport, warehousing, storage, customer use, maintenance, replacement parts, collection, recycling, treatment, and disposal.
Primary data comes from the supplier's or manufacturer's own activity or emissions records. Secondary data comes from databases, industry averages, proxy products, or other published factors. PACT tracks data reliability with metrics such as Primary Data Share and Data Quality Ratings. More primary data does not guarantee a correct result. The source mix should be visible.
3. Apply emission factors
For each activity, multiply the activity data by an appropriate emission factor. For example:
activity data × emission factor = emissions in CO₂eThe calculation then sums emissions across the included processes and converts relevant greenhouse gases to CO₂e under the chosen rules. Emission-factor geography, technology, year, and unit must match the activity data closely enough for the result to be defensible.
4. Allocate shared processes
A factory, transport route, or energy system can serve several products. The calculation must assign a fair share to each product. Avoid allocation where the method allows a physical subdivision or another approach. When allocation is necessary, document the chosen basis, such as mass, energy, economic value, or another method required by the applicable guidance.
The allocation choice can change the result. Keep the basis and any product-category rule with the value so another team does not mistake an allocated estimate for a direct measurement.
5. Assess quality, uncertainty, and verification
Review data completeness, representativeness, assumptions, proxy use, allocation, cut-offs, and uncertainty. Then follow the verification requirements for the chosen method or programme.
Verification is a review of the result and its supporting information against stated criteria. It is separate from calculation. The PACT eight-step guide treats verification and data exchange as distinct steps. A PCF may be unverified, internally reviewed, or independently verified. Store the exact status, reviewer or verifier, programme, date, and scope. Do not turn an unverified value into a “certified” claim.
How to read and compare a PCF
Before using a value in a product page, feed, procurement decision, or Scope 3 workflow, answer these questions:
- Which product and variant does it represent? Match the result to a SKU, component, batch, or supplier identifier.
- What quantity and lifecycle stages does it represent? Record the declared or functional unit, quantity, boundary, and included stages.
- What period and geography apply? A 2025 factory result for one country does not describe every future production site.
- Which method and data support it? Preserve the methodology version, allocation, primary-data share, secondary sources, proxies, assumptions, and quality indicators.
- Who reviewed it, and where is the evidence? Link the source document, verifier statement, programme record, or supplier declaration.
Two PCFs are comparable only when their units, function, boundaries, stages, geography, reference period, methodology, allocation, and data quality are sufficiently aligned. If one result is per kilogram and another is per item, start by resolving the unit. If one includes use and end of life and the other stops at the factory gate, do not rank them.
A PCF is also not a reduction claim. A lower result can reflect a different boundary, product function, production mix, allocation choice, or data quality. Publish the documented result and context rather than an unsupported sustainability label.
PCF compared with related terms
These terms often appear together in sustainability and product-data work. They answer different questions.
| Term | What it measures or contains | Relationship to a PCF |
|---|---|---|
| Corporate Scope 1, 2, and 3 inventory | An organisation's emissions from operations, purchased energy, and other value-chain activities during a reporting period | It uses organisational boundaries and scope categories. A supplier's cradle-to-gate PCF can improve a buyer's upstream Scope 3 estimate, but the records are not interchangeable. See PACT's explanation. |
| Life Cycle Assessment (LCA) | A method for assessing environmental impacts across a product or service life cycle | A PCF applies LCA principles to climate change. A full LCA can cover water, land, resource use, toxicity, and other categories. |
| Environmental Product Declaration (EPD) | A verified and registered document reporting quantified impacts under a product-category rule and programme requirements | An EPD normally contains multiple impact categories and may report global warming. A PCF is the climate-focused result, not the full EPD. The EPA EPD guide explains PCRs, units, and verification. |
| Product Environmental Footprint (PEF) | The European Commission's LCA-based method for quantifying and communicating multiple product impacts | PEF is a broader environmental method, not a synonym for PCF. See the Commission's PEF method. |
| Ecolabel | A mark or claim awarded under a programme's environmental criteria | It communicates that a product meets specified criteria. It is not a numeric PCF or a substitute for evidence. |
| Digital Product Passport (DPP) | A digital container for product, component, or material information, potentially including environmental performance, composition, repairability, and circularity | A DPP can carry a PCF value or link to an EPD. It is a broader product-information container. The European Commission's DPP overview describes its scope. |
Model PCF data as a typed product attribute
A product catalog should treat PCF data as a structured, machine-readable environmental attribute with provenance. Do not paste the value into a description and expect downstream systems to interpret it correctly.
At minimum, store:
| Data group | Fields to preserve |
|---|---|
| Identity | Product ID, variant ID, SKU, supplier, facility, component, or batch reference |
| Result | PCF value, CO₂e unit, declared or functional unit, quantity represented, and gases or removals covered |
| Boundary | Lifecycle boundary, included stages, cut-offs, geography, and handover point |
| Method | Standard or methodology, version, industry rule or PCR, allocation approach, emission-factor sources |
| Reliability | Primary or secondary data, primary-data share, quality rating, assumptions, uncertainty, and calculation date |
| Review and provenance | Verification status, verifier or programme, review date and scope, source document or URL, supplier revision, valid-from date, and expiry or re-review date |
An illustrative record might look like this:
{
"product_id": "SKU-4812-BLUE",
"pcf": {
"value": 2.4,
"unit": "kg CO2e",
"declared_unit": "1 item",
"boundary": "cradle-to-gate",
"included_stages": ["materials", "production", "distribution_and_storage"],
"geography": "DE",
"reference_period": "2025",
"methodology": "PACT Methodology V3",
"data_profile": "supplier-specific",
"verification": {
"status": "third-party verified",
"verifier": "Example Assurance Body",
"date": "2026-03-15"
},
"source_document": "https://supplier.example/pcf/SKU-4812-BLUE.pdf",
"supplier_revision": "r2"
}
}This is an example shape, not a universal PCF schema. Use the data model required by your methodology, supplier exchange, or destination. The important design choices are explicit units, boundaries, versions, evidence, and product identity.
How Catalog fits into the workflow
The calculation belongs with the supplier, manufacturer, LCA practitioner, or sustainability system that owns the activity data and method. Verification belongs with the independent reviewer or programme required by that method.
Catalog's role is the product data layer after that work. We attach a supplied PCF to the correct variant, preserve its unit, boundary, methodology version, evidence, verification status, and revision history, and map supported fields into structured product data, feeds, search, marketplaces, and AI shopping surfaces where the destination accepts them.
We do not calculate a PCF, select emission factors, resolve allocation, verify a supplier's evidence, certify a product, or infer a value from an industry average. If the source does not support a field, the field stays unknown. If two results are not comparable, the catalog should preserve both contexts rather than invent a ranking.
This is the same discipline required for other sensitive product facts. Catalog's product data quality guide covers accuracy, completeness, validity, freshness, and provenance. A PCF needs all five, plus a clear environmental boundary.
A practical implementation sequence is:
- Identify the record. Match the result to the exact product, variant, component, supplier, and facility it describes.
- Ingest and validate the evidence. Store the source document, revision, calculation date, verification statement, unit, quantity, boundary, stages, period, geography, methodology, and data-quality fields.
- Preserve history. Keep prior versions and expiry or re-review dates. Never overwrite a newer supplier result with an older import.
- Distribute supported facts. Map the typed attribute to the destination's schema and publish only the claims the evidence supports.
- Monitor changes. Track supplier revisions, methodology updates, feed errors, and product-variant changes.
That workflow makes a PCF useful to sustainability teams without turning a product catalog into an unverified calculator.
FAQ
Can a PCF replace an EPD?
No. A PCF is a climate-impact result. An EPD is a verified and registered environmental declaration that usually reports several impact categories under a product-category rule. A PCF can be one value inside an EPD, and either record can be linked from a broader product data system.
Can a Digital Product Passport contain a PCF?
Yes, where the applicable product rules require or allow that data. A DPP is a broader digital container that can include carbon, environmental, material, repair, safety, and circularity information. A PCF remains the specific climate-impact record inside that container.
If your teams already have supplier-provided environmental data, Catalog can keep it structured, traceable, and ready for the product channels that use it. Talk to Catalog.
