The GHG Protocol is in the middle of its first significant revision to the Corporate Value Chain (Scope 3) Standard since 2011. A Phase 1 Progress Update has been published, and a final revised standard is expected around 2027, according to Certainty Software's analysis of the revision. The GHG Protocol Working Group has reportedly held 42 meetings since September 2024; verify revision status and timeline specifics directly at ghgprotocol.org before acting on any specific provision.
The direction is consistent across multiple interpretations: tighter supplier data requirements are coming for Category 1 (Purchased Goods and Services). For mid-market manufacturers, the regulation itself is not the immediate problem. Their large customers are.
Why This Is a Supplier Qualification Problem, Not a Sustainability Problem
Scope 3 Category 1 covers the emissions embedded in a company's purchased goods and services. For a large industrial OEM or multinational manufacturer, that category can represent the majority of their reported carbon footprint. Normative.io estimates that Scope 3 emissions typically account for 70–90% of a company's total footprint — a widely cited industry figure, not a normative GHG Protocol measurement.
When a large customer must disclose Scope 3 Category 1 emissions — under CSRD, an SBTi commitment, or California SB 253 — they need data from their suppliers to do it. Most currently rely on spend-based proxies: purchase spend multiplied by an emissions factor from a public database. Fast, but imprecise. The GHG Protocol revision reportedly moves away from accepting spend-based allocation for many supplier categories, pushing toward primary or activity-based data instead.
Vendor analyses from Certainty Software and Normative.io describe proposed provisions including coverage floors, data quality tier labeling, and restrictions on spend-based allocation. These specific provisions have not been confirmed against primary GHG Protocol documentation, which is not yet publicly final. Treat them as the direction of travel, not locked requirements.
What is confirmed: three separate regulatory and voluntary frameworks are already creating customer-side disclosure pressure.
Three Customer-Side Frameworks Creating Real Pressure Now
CSRD (EU Corporate Sustainability Reporting Directive): Under ESRS E1, large companies covered by CSRD must disclose Scope 3 emissions where climate is identified as a material topic, per Normative.io's regulatory summary. A proposed EU Omnibus I amendment reportedly narrows CSRD coverage to approximately 5,000 firms, down from the original ~50,000 scope — confirm that figure against European Commission documentation before using it in customer-tier planning. At 5,000 firms, those remain the largest multinational companies in Europe. If you supply one, you are in their Category 1 inventory.
SBTi (Science Based Targets initiative): Companies with SBTi commitments must set Scope 3 targets when value chain emissions exceed 40% of their total footprint, per Normative.io — confirm against primary SBTi documentation at sciencebasedtargets.org. The directional point holds regardless: SBTi-committed customers have a structural incentive to collect better data from their suppliers, and that incentive flows directly to supplier qualification criteria.
California SB 253 (Climate Corporate Data Accountability Act): This law requires large companies doing business in California with over $1 billion in revenue to report Scope 3 emissions on a phased schedule beginning in 2026. U.S.-headquartered large manufacturers and distributors are in scope. If your customer is a California-based company above that threshold, they carry a legal obligation, not a voluntary one.
The SEC climate disclosure rule, which was withdrawn and did not include a Scope 3 requirement, is not a factor here.
Where the Qualification Risk Lives in Your Operation
The risk is not abstract. It surfaces in three places:
- Supplier qualification and re-qualification cycles. Large customers periodically re-qualify their supply bases. Emissions data capability is increasingly an evaluation criterion alongside quality certifications and financial stability.
- RFP addenda and sustainability questionnaires. RFQs from CSRD- or SBTi-exposed customers increasingly include sustainability data sections. If you cannot respond with primary or activity-based data, you may score lower than a competitor who can.
- Contract renewals. Multi-year supply agreements are beginning to include data provision clauses tied to the customer's ESG reporting obligations.
The problem most mid-market manufacturers face is not unwillingness to provide emissions data — their systems cannot produce it. ERP supplier master records typically capture vendor name, address, payment terms, and lead time. They do not capture emissions intensity by material, process type, or product line. Procurement spend data exists, but it is organized around cost centers and vendor accounts, not the activity types or process steps needed for emissions calculations.
What Your Procurement Process and Systems Need to Support
If a customer requests Scope 3 Category 1 data for your products today, the gap is predictable across most mid-market manufacturers:
- No documented emissions factor by product or process in the ERP product master
- No supplier-facing data collection workflow in the procurement onboarding process
- No reporting layer that aggregates activity-based emissions by supplier or material category
- No supplier qualification form capturing carbon data fields alongside ISO certifications or financial references
Closing this gap does not require a full sustainability platform. It starts with procurement process changes and ERP configuration decisions that operations and IT leaders can scope without a dedicated ESG team.
What to Audit Before the Next RFP Cycle
Run these checks before a customer requirement formalizes:
- Customer relationship review. For your top 20 customers by revenue, determine whether any are subject to CSRD, have SBTi targets, or are California-domiciled companies above the $1B SB 253 threshold. This is a two-to-three hour research task.
- Active RFPs and open contracts. Review all active and pending RFPs and contract renewals for sustainability, ESG, or emissions data clauses. The absence of one so far is not a guarantee the next one is clean.
- Supplier qualification forms. Pull your current supplier onboarding questionnaire. Does it include fields for emissions data, environmental product declarations (EPDs), or carbon intensity figures? For most mid-market manufacturers, the answer is no.
- ERP supplier and product data. Determine whether your ERP purchasing module and product master can store, report, or export activity-based emissions data at the SKU or process level. If it cannot, that is a configuration gap, not a platform replacement decision.
- Top 10 Category 1 suppliers by spend. Do any already provide EPDs or activity-based emissions data? If so, you have a starting point for your own Category 1 reporting if a customer requests it.
What to Watch in the Next 12 Months
The GHG Protocol revision is not final. Before treating any specific provision — including the widely cited 95% coverage floor — as a confirmed requirement, check ghgprotocol.org directly for the Phase 1 Progress Update and any open public comment period.
The more immediate signal to track is your own customer base:
- Sustainability questionnaire sections appearing in RFQs from large industrial customers
- SBTi target announcements from any customer above $500M in revenue
- California SB 253 phased reporting deadlines beginning in 2026, which will push large California-headquartered customers to formalize supplier data requests
- CSRD implementation guidance from the European Commission clarifying which firm categories remain in scope post-Omnibus I
Manufacturers who build a documented primary emissions data capability before customers demand it will have a cleaner qualification story. Those who wait will be answering an RFP requirement with a procurement system that was never designed to produce that answer.