"Send us your carbon data" can mean three quite different things. Your customer might want your organisation's overall footprint, structured Scope 3 supplier data for their own value-chain calculations, or the carbon footprint of a specific product you supply them. Sending the wrong one wastes your time and still leaves the request unanswered. This page helps you work out which one it is, then routes you to exactly what to prepare.
Read the request again before you start calculating anything. Look for whether it names a specific product, references "supplier data" or a Scope 3 programme, arrives as a structured form covering more than just emissions, or simply asks for "your carbon footprint" with no further detail. That wording usually tells you which of the four categories below applies.
The request simply asks for "your carbon footprint" or "your emissions" with no product or supplier-programme language. This is your whole-company Scope 1 and 2 total (and sometimes relevant Scope 3), not tied to a specific item you supply.
What to send for an organisational footprint →The request mentions "supplier emissions," a CDP or EcoVadis survey, or your customer's own Scope 3 reporting. They need the emissions tied to your relationship with them, not necessarily your whole company footprint.
What to send for a Scope 3 request →The request names a specific product, SKU or service and asks for its carbon footprint per unit — often for a product carbon footprint (PCF), EPD or lifecycle assessment. This is the most detailed and time-consuming of the four, so only prepare it if this is explicitly what's being asked for.
See the product footprint checklist below ↓The request arrives as a structured form, portal or scorecard covering policies, targets and emissions together — not a single carbon figure on its own. Carbon data is only one part of what you need to complete.
What to send for a sustainability questionnaire →Not sure which applies? Other common request formats have their own dedicated guides: a tender or procurement carbon requirement, or a request that specifically needs traceable, audit-ready evidence behind the figures.
This is the most detailed of the four data types, so use it only when the request explicitly names a product or asks for a per-unit figure. Your customer wants the carbon attributable to that specific product or service, so they can slot it into their own Scope 3 supply chain inventory — a functional unit (per product, per kg, per service delivery), a stated boundary, and enough methodology detail that they don't have to come back and ask.
Usually mandatory: the product carbon footprint in kg or tonnes CO2e per functional unit, the system boundary (cradle-to-gate, gate-to-gate, or cradle-to-grave), the reference year, and the calculation standard used. Usually optional but strengthens your response: a lifecycle-stage breakdown, third-party verification, and your reduction initiatives.
A complete response covers each of these — missing any one usually triggers a follow-up question from the customer's sustainability team.
Whichever data type your customer needs — organisational, supplier or product-level — most of the effort goes into applying the right emission factors consistently, keeping the boundary and methodology documentation aligned with the figures, and formatting the output so your customer's system can actually use it. GreenKPO keeps your activity data and current UK emission factors in one place, so the same calculation approach applies every time a customer asks. It doesn't set your system boundary or verification strategy for you; it removes the calculation and formatting work behind the response, so putting one together is a matter of hours rather than days.
Whichever data type your customer needs, get it calculated, documented and formatted for their system — ready to reuse the next time they ask.