The starting point.
The customer is a global FMCG producer with a long catalogue of consumer-facing brands. Retailer requests for PCF data were growing in volume and consistency, with the largest grocers asking for cradle-to-gate carbon at SKU level for every product they stocked. The producer’s in-house calculations had been built for a handful of flagship SKUs, with the rest filled by category averages.
The brief.
Bring cradle-to-gate PCFs to ISO 14067 across the active catalogue. Make per-product emissions available at the moment a new product launches. Keep the workflow inside the systems procurement and R&D already run on.
How we rolled out.
1. Bill-of-materials at SKU level.
Noa imported the bill of materials for every active SKU, with supplier identifiers for upstream materials. Process inputs were drawn from manufacturing systems, energy data from utility meters and invoices, and transport assumptions calibrated against logistics planning. Direct supplier data was used where available, with regional emission factors filling gaps with provenance attached.
2. Launch-day PCFs for new products.
The pipeline was wired into the product launch workflow so that a new SKU enters the catalogue with a current cradle-to-gate PCF. R&D and procurement see the carbon profile of a formulation before it goes to market, and category teams can plan against it.
3. Retailer-ready outputs.
Each SKU carries a structured PCF record with calculation summary, methodology notes and evidence chain. Retailer responses pull from the same record, with no separate workbook required per request.
What runs on Noa today.
PCFs run continuously for every active SKU across the catalogue. New products enter with a launch-day PCF. Retailer requests are served from the same dataset, and category teams use per-product emissions inside the workflow they already use for planning.
The outcome.
Before
- PCFs maintained for a handful of flagship SKUs
- Category averages filling the rest of the catalogue
- Retailer requests handled one workbook at a time
- New products arriving without a defensible PCF
With Noa
- Cradle-to-gate PCFs across the active catalogue
- Launch-day PCFs as part of the new-product workflow
- Retailer responses served from a single source
- Category teams planning against per-product emissions
When PCF data lives inside the systems that launch the products, the disclosure question shifts from "can we produce a number" to "what is the number telling us this quarter".
Customer details have been generalised. Outcomes described reflect deployments as scoped and may not be representative of all engagements. References to third-party products are descriptive of prior states only.