For most contractors, an embodied-carbon figure is built backwards. The materials arrive, the job proceeds, and weeks later someone assembles what was bought from delivery tickets and invoices, then hunts down an emissions factor for each line. Travis Perkins, the UK builders’ merchant group, is now attacking that sequence from the other end: its Connect platform attaches a carbon dioxide equivalent (CO2e) value to products on orders and delivery records, so the number arrives with the goods instead of being reconstructed after them.
The group says it has mapped product weights in tonnes and kilograms and applied a CO2e figure to more than 120,000 products, and it is expanding Connect across five of its distribution businesses — Travis Perkins, CCF, Keyline, BSS, and Travis Perkins Managed Services. Connect began at CCF, the group’s interiors business; the October announcement is the group-wide rollout and the newly reported mapping scale. This is a British merchant’s platform in a British rollout. Nothing about it is on sale in the United States — what travels is the pattern.
The human stake is in the number the group’s announcement keeps returning to. Phil Monkman, who led the CCF team that built Connect, describes the old way in the announcement: “Up to now, the only way to get really accurate carbon data has been for the subcontractor to download delivery tickets and invoices and manually input the information, line-by-line. For some this could mean inputting up to 3,000 data points a month, just for carbon reporting.” That figure is one supplier’s description of some subcontractors’ burden, not a measured saving — but anyone who has assembled a Scope 3 inventory from a subcontractor’s spreadsheet knows the workload it names.
Three thousand hand-keyed data points a month is not just slow. It is where carbon reporting quietly goes wrong: a transposed digit, a quantity entered in the wrong unit, a factor grabbed from the wrong table at 11 p.m., a gap filled with a plausible number because the filing was due. Attaching the factor at the merchant’s end does not exhort that weakest link to try harder; it removes the link. The transcription step disappears, and with it an error surface that came free with every line.
What it proves — and what it doesn’t
What the delivery-attached number genuinely proves is provenance. Each line carries the product, quantity, weight, and the factor applied, on a transaction record that already exists for commercial reasons. An auditor, a client’s sustainability team, or your own assurance provider can walk that chain line by line. A month-end estimate cannot offer the same walk; it can only be believed or doubted as a whole. For data heading toward assurance — which California’s SB 253 builds in as its Scope 3 requirements phase in from 2027 — provenance is most of the game.
What it does not prove is precision, and the distinction lives in the factor library. Travis Perkins says its factors come from manufacturers’ environmental product declarations — EPDs — where those exist, and from recognized industry datasets everywhere else. Those are two different grades of evidence. An EPD is a manufacturer-specific, independently verified declaration with defined life-cycle boundaries. A generic dataset value is an average for a product class: a reasonable estimate wearing a uniform. A delivery total that blends the two is only as strong as its mix, and the group does not publish what share of its 120,000 mapped products is declaration-backed.
The boundary matters
The boundary matters as much as the grade. A product-level figure describes the material — typically manufacture up to the merchant’s gate. It is not a life-cycle assessment of the building: transport to site, installation, replacements across decades of use, and end of life sit outside the frame unless someone adds them. Nor does one merchant’s platform cover a project. Materials bought from any other supplier arrive the old way, numberless, and a contractor reporting on the whole job still has to reconcile covered and uncovered piles without double-counting.
The group’s own customer accounts hint at why the trade is still worth making. In one account the company tells, a contractor’s earlier estimate came in roughly 60 percent below the figure the delivery data later produced — a supplier-told story, not a validated error rate. But the direction is familiar to anyone who has compared a first-pass estimate with a counted inventory: hand-built numbers drift, usually downward, because the person building them is tired, rushed, and missing half the tickets.
The questions to ask your own merchants
So the useful response for a US or Canadian contractor is not envy of a UK platform; it is a set of questions for your own merchants and distributors, because the pattern is now demonstrably buildable. Which of my regular lines can you attach carbon data to, and which of those factors are declaration-backed rather than generic? What share of my tonnage does each grade cover? How often is your factor library updated, and are past deliveries restated when a factor changes? And can I have the data line by line, in a file my reporting system can ingest — or only as a printed total I have to re-key — rebuilding the weakest link this pattern exists to remove?
The delivery record was always the most trustworthy document on a construction job. It is signed, priced, and argued over; nobody invents one for fun. What is changing — in this UK rollout first, and in the questions it teaches buyers to ask everywhere else — is that the record now carries the carbon alongside quantity and price. When it does, the argument about your Scope 3 number moves from whether you counted at all to what grade of evidence you counted with. That is a better argument, and it is the one assurance providers, clients, and California’s filing calendar are about to have with you.
