Understanding Scope 3 Category 11
Use of sold products covers emissions from customers using the products your organization sells. According to the GHG Protocol Scope 3 Standard, Category 11 includes emissions from:- Direct use-phase emissions: Emissions from the use of products that directly consume energy or fuels
- Indirect use-phase emissions: Emissions from the use of products that indirectly consume energy (e.g., clothing that requires washing)
When Does Category 11 Apply?Category 11 is most relevant for organizations that sell energy-consuming products — anything that uses electricity, burns fuel, or consumes water during its use phase. If your products don’t consume energy during use (e.g., passive building materials, textiles), Category 11 emissions are typically zero or negligible.For many manufacturers, Category 11 is the largest Scope 3 category — often exceeding 50% of total emissions for products with long lifespans or high energy consumption.
Prerequisites
Before starting, ensure you have:- Dcycle API credentials (get them here)
- Completed Step 1: Company Structure
- Product data: what you sell, where, and how many units per period
- Use-phase data: energy consumption of your products during their lifetime (from product specs, testing, or LCA studies)
Data Map: Use of Sold Products Requirements Overview
How It Works
Dcycle calculates Category 11 emissions using a product-centric approach with four layers of data:1
Create a Sold Product
Register each product or product family your organization sells
2
Define Reporting Periods
Add date ranges for when sales data applies (e.g., 2024-01-01 to 2024-12-31)
3
Add Country Sales
Record how many units were sold in each country during the period
4
Configure Use-Phase Consumption
Define what the product consumes during its lifetime: electricity, fuel, and/or water
5
Automatic Calculation
Dcycle calculates total use-phase emissions:
Units sold × Consumption per unit × Lifespan × Country-specific emission factor
Country-Specific Emission FactorsDcycle applies country-specific emission factors for electricity consumption. A product sold in France (low-carbon grid) will have lower use-phase emissions than the same product sold in Poland (coal-heavy grid). This is why country-level sales data matters.
Calculation Methodology
Step 11.1: Create a Sold Product
📋 Data Map: Sold Product
📋 Data Map: Sold Product
Where to get this data:
- Product catalog: Your product management system or ERP
- Naming: Use consistent names across periods (one product record per product family)
The name identifies the product in your organization, trimmed and matched exactly (
compressor x200 is a different
product from Compressor X200): sending a name that already exists adds the periods to that product instead of
creating another one. Use product families rather than individual SKUs when products have similar use-phase
consumption profiles.POST /v2/sold-products (up to 1,000 products per request). The emissions
are calculated when you send each period’s use in Step 11.4, so this answer is immediate (201 Created): each product
with the periods written and their id, the period_id you need in that step.
Step 11.2: Define Reporting Periods
📋 Data Map: Reporting Period
📋 Data Map: Reporting Period
Constraints:
- Periods for the same product cannot overlap, the dates of both included
- A period cannot end in the future (tomorrow in UTC at the latest)
- Each product must have at least one period (you cannot delete the last period)
- Reporting cycle: Typically annual, aligned with your GHG Protocol reporting year
periods array. Periods define the timeframe for which
sales data applies. You don’t need to check for overlaps first: a period that overlaps one the product already has is
rejected with PERIOD_OVERLAPS and the id of that period, and nothing in the request is written. To add the next
year, send the same product name with the new period.
Step 11.3: Add Country Sales Data
📋 Data Map: Country Sales
📋 Data Map: Country Sales
Constraints:
- Only countries the Dcycle app offers (
COUNTRY_NOT_SUPPORTEDotherwise): send each country, not a region such asRoW - One entry per country per period (
DUPLICATE_SALEotherwise) - All sales within the same period use the period’s
unit_id - Send every country of a period in the same request: a later request cannot add countries to an existing period
- Sales system / ERP: Units sold by country by period
- Distribution records: Shipping destinations, invoicing addresses
- Market reports: Regional sales breakdowns
sales array of each period, as in the request of
Step 11.1, and the 201 answer returns them with their ids.
Step 11.4: Configure Use-Phase Consumption
📋 Data Map: Use-Phase Consumption Data
📋 Data Map: Use-Phase Consumption Data
Then at least one of these blocks. Leave out the ones the product does not consume.
electricity (if applicable):combustion (if applicable):water (if applicable):fugitive (refrigerant leaks, if applicable):Frequency options:
daily, weekly, monthly, yearly, all_lifeThe unit_id of each block is listed in Units.POST /v2/use-of-sold-products (up to 5,000 periods per
request, one record per period_id). The emissions are calculated in the background: the answer is 202 Accepted with
an ingest job. Follow it with GET /v2/ingest-jobs/{id} until its status is no
longer processing, or receive the ingest_job.finished webhook.
Step 11.5: View Emissions Results
Once the job has finished, read the results of each period with Period Emissions:Emission Statuses
🏢 Typical Data Sources
🏢 Typical Data Sources
Automation options:
- CSV upload → Upload country sales data via the Dcycle App
- API → Push products and sales from ERP/CRM with
POST /v2/sold-products, and the use phase withPOST /v2/use-of-sold-products - Product specs → Use-phase data typically comes from R&D or product engineering
Examples by Industry
Industrial Equipment Manufacturer
Industrial Equipment Manufacturer
Product: Industrial Compressor X200
Total use-phase emissions = (250 + 180) × 8,000 kWh/year × 15 years × country EFs
Gas Boiler Manufacturer
Gas Boiler Manufacturer
Product: Residential Gas Boiler Pro
Total use-phase emissions = 5,000 × (150 kWh elec + 12,000 kWh gas)/year × 12 years × EFs
Household Appliance Manufacturer
Household Appliance Manufacturer
Product: Washing Machine EcoWash 9kg
Total use-phase emissions = (15,000 + 3,000) × (200 kWh + 10 m³)/year × 10 years × country EFs
Updating Use-Phase Data
If product specifications change or you have more accurate data, send the period’s use again withPOST /v2/use-of-sold-products. A period has one use: the new record
replaces the stored one whole, so send every block the product consumes, not only the fields that changed.
Automatic RecalculationReplacing the use of a period recalculates all its emissions in a new ingest job. You don’t need to manually
re-trigger calculations. To remove the use of a period and its emissions, keeping the period and its sales, use
Delete Use of Sold Products (v2).
Connection with LCA
If you have detailed Life Cycle Assessment (LCA) data for your products, you can use Dcycle’s LCA module to build a complete cradle-to-grave model. The LCA module uses the ecoinvent database and provides more granular impact categories beyond just climate change. Category 11 and LCA complement each other:- Category 11 (this guide): Estimates use-phase emissions from sales volumes and product specs — ideal for GHG Protocol reporting
- LCA module: Detailed product-level environmental impact across the full lifecycle — ideal for EPDs, product design, and ecodesign
LCA Overview
Build complete life cycle assessments
Resource Manager
Manage materials and processes for LCA
Next Steps
Sold Products API
Full API reference for sold products endpoints
Create Use of Sold Products (v2)
Full reference for the use-phase records, units and errors
Category 1: Purchased Goods
Track upstream emissions from purchases
Custom Emission Factors
Use supplier EPDs and PCFs for upstream data
GHG Protocol Scope 3
Return to the Scope 3 overview