ZeroCarbon is PACT conformant: what it means for your product carbon footprints
ZeroCarbon passed the PACT v3.0 conformance tests. What PACT is, what was tested, and what it changes for suppliers asked for product carbon footprints.
Akshit Tiwari
3 min read
Key takeaways
- ZeroCarbon is now a PACT conformant solution, listed in the PACT Network for Technical Specifications v3.
- PACT is an initiative hosted by WBCSD that sets one methodology and one data-exchange standard for product-level carbon footprints.
- Our production PACT API passed every mandatory test case in the v3.0 conformance suite: authentication, footprint listing and filters, and the request and publish events.
- For a supplier, it means one footprint, calculated from its own ledger, can answer every customer who connects through a PACT conformant solution.
On 27 October 2026 PACT confirmed that ZeroCarbon passed its conformance tests, and ZeroCarbon is now listed in the PACT Network as a PACT conformant solution. We have written up the announcement separately. This post explains what PACT is, what the tests checked, and what changes for a company that is asked for the carbon footprint of its products.
What PACT is
The Partnership for Carbon Transparency (PACT) is an initiative hosted by the World Business Council for Sustainable Development (WBCSD). It publishes two things that work together: the PACT Methodology, which says how to calculate a product carbon footprint (PCF) consistently, and the PACT Technical Specifications, which say how software systems exchange those footprints through a common data model and API.
The point is interoperability. Without a shared standard, every buyer asks for footprints in its own spreadsheet, and every supplier answers the same question many times in slightly different ways. With PACT, a footprint calculated once can move between any two conformant solutions without re-keying.
What the conformance tests checked
PACT runs its conformance testing tool against a live solution's API and records the results. For Technical Specifications v3.0 the suite has 41 test cases, two of them optional. Our production API passed every mandatory case:
- Authentication. Tokens are issued only for valid credentials, and requests without a valid token are refused.
- Footprints. Listing footprints, fetching one by ID, pagination, and a proper error for an ID that does not exist.
- Filters. By product, company, geography, classification, validity dates and status, combined with AND and OR, including queries that must return nothing and a malformed query that must be rejected.
- Events. A customer asks for a footprint and receives it asynchronously, or receives a rejection for an unknown product, and partners are notified when a footprint is published.
- Transport. Every endpoint refuses plain HTTP.
What changes for suppliers
If you sell to companies that track Scope 3 emissions, you are likely to be asked for product-level footprints, and the request will often name PACT. In ZeroCarbon the path is short:
- Your bills, invoices and production records become a verified emissions ledger, with each figure linked to its source document.
- ZeroCarbon calculates the footprint of each product from that ledger under the PACT Methodology v3.0, recording how plant-level emissions were allocated to products.
- You publish the footprint and grant access to the customers who should see it. Nothing is shared without a grant.
- Customers using any PACT conformant solution can fetch it, or ask for it through a PACT event, and ZeroCarbon answers automatically.
The same works in the other direction: you can request footprints from your own suppliers in the PACT format, in place of spend-based estimates for purchased goods. How to calculate a product carbon footprint under PACT works through the method with numbers.
What it does not change
PACT is a standard for product footprints across value chains. It does not replace regulatory schemes with their own rules. EU CBAM, for example, defines embedded emissions and its reporting format in its own regulation, and ZeroCarbon handles CBAM separately. The underlying ledger is shared, so the same verified records support both.
Thank you
Thank you to the PACT team at WBCSD for the specifications, the conformance testing service and their help through the process. If a customer has asked you for a PACT footprint, tell us who is asking and we will help you answer it.
Frequently asked questions
What does PACT conformant mean?+
That a software solution has passed PACT's conformance tests for a version of the PACT Technical Specifications, so it can exchange product carbon footprints with other PACT conformant solutions. ZeroCarbon is conformant with version 3.0.
Is PACT conformance a certification of my emissions?+
No. It tests that the software exchanges data correctly. The accuracy of a footprint depends on the data used to calculate it.
Can my customer receive my footprint if they use different software?+
Yes, if their software is also PACT conformant. Both sides use the same data model and API, so the footprint moves between them without re-keying.
Sources
- 1.ZeroCarbon in the PACT Network · PACT, WBCSD
- 2.PACT Technical Documentation · PACT, WBCSD
- 3.PACT v3.0 conformance test cases and expected results · PACT, WBCSD
- 4.Partnership for Carbon Transparency · WBCSD
This article is general information, not legal or tax advice. Regulations change; check the primary source before acting.