"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 sits in calculation, documentation and formatting. GreenKPO handles that layer so a response takes hours, not days.
Activity data and current UK emission factors stay in one place, so the same calculation approach applies every time a customer asks.
Boundary and methodology notes stay linked to the figures, so your customer can use the output without chasing clarifications.
Output is formatted so their system can actually ingest it — without rebuilding the spreadsheet from scratch each time.
GreenKPO doesn't set your system boundary or verification strategy — it removes the manual calculation and formatting work behind the response.
Ask the customer to clarify if you're not sure, or default to your organisational Scope 1 and 2 footprint — it's the most commonly requested baseline and rarely wrong to lead with.
Not always. If verification is pending or you haven't obtained it, say so clearly and give a timeline if you have one — an honest "not yet verified" is better than an unclear claim.
That's a reasonable starting point — state the primary-versus-secondary split clearly so your customer can judge data quality, and improve the mix over time as you collect more primary data.
Ask your customer which they need for their Scope 3 category. Cradle-to-gate is more common for upstream supplier data; cradle-to-grave is used when the use-phase or disposal falls within their reporting.
A human-readable PDF summary alongside a machine-readable CSV covers most customer systems, including CDP Supply Chain and similar platforms.
Whichever data type your customer needs, get it calculated, documented and formatted for their system — ready to reuse the next time they ask.