The starting point.
The customer is a specialty chemicals producer whose downstream customers had started asking for product carbon footprints inside tender responses. Calculations were being commissioned ad hoc through external consultants for a few high-priority SKUs, with turnaround times that did not fit a normal sales cycle. The producer wanted to bring the work in house and standardise it across the catalogue.
The brief.
A cradle-to-gate PCF for every active SKU, aligned to ISO 14067. Calculations close enough to source data that procurement and assurance can both read them directly. A workflow that keeps up with new formulations and reformulations without consultant lead times.
How we set it up.
1. Bill-of-materials as the source of truth.
Noa imported the bill of materials for each active SKU from the producer’s ERP, including supplier identifiers for upstream materials. Process inputs were captured from the manufacturing execution system, with energy data drawn from utility meters and invoices. Where direct supplier data was unavailable, regional emission factors filled the gap with provenance attached.
2. ISO 14067-aligned calculation pipeline.
PCFs were calculated under the ISO 14067 methodology, with allocation rules declared explicitly and applied consistently across the catalogue. Reformulations and new SKUs run through the same pipeline, so a new product carries a defensible PCF from launch.
3. Outputs procurement and assurance can both use.
Each SKU has a structured PCF record with calculation summary, evidence chain and methodology notes. Sales teams pull this directly into tender responses. External assurance reads the same record with the right scope.
What runs on Noa today.
PCFs run continuously for every active SKU in the producer’s catalogue. New formulations enter the pipeline at launch. Sales and procurement work from the same dataset, and external assurance reads the evidence chain directly.
The outcome.
Before
- Per-SKU PCFs commissioned ad hoc from external consultants
- Lead times that did not fit a normal sales cycle
- Inconsistent allocation rules between calculations
- No standing evidence trail for assurance to read
With Noa
- Every active SKU carries a current cradle-to-gate PCF
- New formulations enter the pipeline at launch
- Allocation rules declared once and applied consistently
- Sales, procurement and assurance read from the same record
Per-product carbon stops being a project the moment it becomes part of how new SKUs are launched.
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.