PACT Compliant Carbon Accounting: Pathfinder Framework v2.0 Explained
PACT (Partnership for Carbon Transparency) defines the Pathfinder Framework v2.0 for exchanging verified Product Carbon Footprint data across supply chains. This guide covers the PCF data model, DQR scoring, industry adoption, and what PACT compliance requires in practice.
What Is PACT?
The Partnership for Carbon Transparency (PACT) is an industry-led initiative co-governed by the World Business Council for Sustainable Development (WBCSD). Its central output is the Pathfinder Framework, a technical specification for calculating and exchanging Product Carbon Footprints (PCFs) across value chains using a standardized data model and API protocol.
PACT does not issue compliance certificates or audit individual products. Instead, it establishes the methodology and data schema that software solutions must implement so that PCF data produced by one system can be consumed, verified, and acted upon by another — regardless of industry sector or geography.
The current version, Pathfinder Framework v2.0, was published in early 2023 and supersedes v1.0. Implementations that have not migrated to v2.0 are increasingly unable to exchange data with counterparts on updated platforms.
How PACT Differs from ISO 14067
ISO 14067:2018 governs the quantification and communication of the carbon footprint of products (PCF). It is a measurement standard. PACT's Pathfinder Framework layers an exchange protocol on top of ISO 14067's calculation rules:
| Dimension | ISO 14067 | PACT Pathfinder v2.0 |
|---|---|---|
| Scope | Quantification methodology | Methodology + data model + API |
| Output | Study report | Machine-readable PCF data record |
| Interoperability | None specified | Defined JSON schema + REST API |
| Data quality | Referenced from ISO 14044 | Explicit DQR scoring schema |
| Assurance | Optional critical review | Conformance claims by software providers |
A PCF calculated per ISO 14067 is a valid input to a Pathfinder-compliant system, but the Pathfinder Framework additionally specifies exactly which fields are required, how uncertainty must be represented, and how data is transmitted between business partners.
The PCF Data Model
The core unit in Pathfinder is the ProductFootprint object, a JSON record with versioned fields. Key mandatory fields in v2.0 include:
- pcfExcludingBiogenic and pcfIncludingBiogenic: GHG emissions in kg CO2e per declared unit, split to isolate biogenic carbon flows (per GHG Protocol Land Sector guidance)
- declaredUnit and unitaryProductAmount: the functional unit basis
- referencePeriodStart / referencePeriodEnd: temporal boundary of the study
- geographyCountryOrRegion: geography of production, used for electricity grid factor selection
- primaryDataShare: percentage of activity data that is primary (measured or supplier-provided) versus secondary (database proxies)
- dqi: the Data Quality Indicators block, which carries scores for the five pedigree matrix dimensions
- exemptedEmissionsPercent: share of the value chain excluded from calculation, capped at 5% per ISO 14044
- crossSectoralStandardsUsed: enumerated list (e.g., GHG Protocol, ISO 14067)
- productOrSectorSpecificRules: PCR references (e.g., PCR 2019:14 for construction products, automotive sector PCRs)
Optional but strongly recommended fields include fossilGhgEmissions, biogenicCarbonContent, and landUseEmissions — the latter becoming mandatory as TNFD-linked disclosure grows.
DQR Scoring in Pathfinder
Data Quality Rating (DQR) in Pathfinder v2.0 is derived from the ISO 14044 pedigree matrix but expressed as a numeric score per dimension:
| Dimension | Abbreviation | Score range (1 = best, 5 = worst) |
|---|---|---|
| Technological representativeness | TeR | 1-5 |
| Temporal representativeness | TiR | 1-5 |
| Geographical representativeness | GeR | 1-5 |
| Completeness | C | 1-5 |
| Reliability | R | 1-5 |
An overall DQR is computed as the arithmetic mean of these five scores. Pathfinder v2.0 requires the five individual scores plus the composite; it does not specify a mandatory DQR threshold for conformance, but downstream buyers in automotive and chemicals sectors have begun setting contractual DQR maxima (typically DQR <= 2.5 for Tier 1 suppliers).
Software tools that do not capture pedigree metadata at the activity-data entry level cannot produce conformant DQR blocks without post-hoc estimation — a common gap in legacy tools.
Primary vs. Secondary Data
Pathfinder distinguishes sharply between:
- Primary data: activity data collected directly from the operations under study (energy meter readings, purchase invoices, process measurements). Counted toward primaryDataShare.
- Secondary data: generic factors drawn from background databases such as ecoinvent, GaBi, or industry average datasets. These fill gaps where primary data is unavailable.
The primaryDataShare field is a percentage (0.0–100.0). Buyers often impose contractual minimums — automotive OEMs such as BMW and Volkswagen have signaled expectations of >50% primary data for direct materials within three years.
This distinction drives the core challenge of PACT compliance: suppliers must move from pure secondary-data LCAs to hybrid studies where their own energy consumption, logistics data, and manufacturing inputs are measured and reported.
Industries Adopting PACT
Automotive
The automotive sector has the most mature PACT deployment. The Drive Sustainability and CATENA-X consortia have mandated Pathfinder-compatible PCF exchange for Tier 1 and Tier 2 suppliers. BMW, Stellantis, Mercedes-Benz, and Volkswagen Group have all published supplier requirements referencing Pathfinder v2.0. The CATENA-X marketplace uses the Pathfinder API to enable automated PCF ingestion across the supply chain.
Chemicals
BASF, Evonik, Covestro, and others in the Together for Sustainability (TfS) initiative have adopted Pathfinder as the standard for sharing PCFs with downstream customers. Chemical products often have complex co-product allocation scenarios; Pathfinder v2.0's allocation fields accommodate both physical and economic allocation, with a mandatory declaration of the method used.
Steel and Metals
The ResponsibleSteel standard and the SteelZero initiative are converging on Pathfinder-compatible data exchange. Steel has high primary data availability (energy use at mills is metered) but complex scrap allocation challenges. Pathfinder v2.0's allocationRulesDescription field allows documentation of the chosen approach.
Consumer Goods and Retail
Retailers including IKEA and H&M have begun requesting Pathfinder-formatted PCFs from product suppliers. This is less mature than automotive but growing rapidly as CSRD and the EU Green Claims Directive create disclosure obligations.
What "PACT Compliant" Means in Practice
There is no third-party PACT certification body. "PACT compliant" has two distinct meanings:
- Software conformance: A solution provider self-declares that its API implementation conforms to the Pathfinder API specification (OpenAPI schema, authentication, versioning). WBCSD maintains a list of conformant solutions that have passed the interoperability testing protocol.
- Data conformance: A PCF data record contains all required fields, values within permitted enumerations, and a DQI block with scores for all five dimensions. A conformant record can be validated against the published JSON schema.
Neither meaning implies that the underlying LCA study is independently verified. Data accuracy remains the responsibility of the producing organization and its chosen LCA practitioner.
PACT Compliance Checklist
Use this checklist to assess readiness for PACT-conformant PCF production:
- Methodology alignment: Confirm your LCA study follows ISO 14067 and GHG Protocol Product Standard. Document cross-sectoral standards in the data record.
- PCR identification: Identify the applicable Product Category Rule. If no sector-specific PCR exists, document use of the Pathfinder Framework as the governing rule.
- System boundary documentation: Define cradle-to-gate or cradle-to-grave boundary; Pathfinder supports both. Declare exempted emissions and confirm they are below 5%.
- Primary data collection plan: Identify which activities require primary data. Implement measurement protocols for energy, materials, and logistics at your facilities.
- DQR scoring: For each input, assign pedigree scores across all five dimensions. Ensure your LCA software captures this metadata per activity, not just at aggregate level.
- Biogenic carbon split: Separate biogenic CO2 flows from fossil flows. Confirm your background database disaggregates these (ecoinvent 3.9+ does; some older versions do not).
- Data record construction: Map all required Pathfinder fields to your LCA outputs. Validate the resulting JSON against the v2.0 schema.
- API implementation: If you are a software provider or operate a supplier portal, implement the Pathfinder REST API (OAuth 2.0 authentication, /footprints endpoint, pagination).
- Interoperability testing: Use the PACT Conformance Testing service to validate API responses against published test cases.
- Version management: Implement record versioning; Pathfinder v2.0 requires version and updated fields and supports a status field for superseded records.
How ClimatePoint Supports PACT Compliance
ClimatePoint's LCA platform captures primary data shares, pedigree scores per activity, and biogenic carbon flows natively — producing Pathfinder-conformant data records without manual field mapping. The DQR dashboard surfaces per-dimension scores so practitioners can identify weak data points before finalizing a PCF exchange record.
Ready to produce PACT-conformant PCFs for your supply chain? Book a demo at climatepoint.com to see the Pathfinder data model in action with your product data.
