Supplier carbon data portal guide for requesting and reviewing evidence
A machined flange sits beside a green binder and notebooks. The laptop displays a generic dashboard without identifiable supplier or footprint information.
Diagram text description
A supplier carbon data portal gives buyers and suppliers a shared process for requesting emissions information, recording the response, reviewing its evidence and tracking what the buyer can use. Start with the decision the data should support. A purchasing estimate for one component needs a different request from a supplier engagement review across a whole business.
A useful record starts with the product or activity, unit, period and boundary. The reviewer then checks the method, supporting records and any gaps. Only after those checks should the buyer accept a value for a named use. The portal can keep that decision visible and notify the owner when a product or source changes.
This guide includes a reusable request and a fictional record that arrives with the wrong freight boundary. It shows what to ask the supplier to correct, how to convert the revised value to the purchased item and which uses stay on hold. Use those checks to judge whether a portal improves the evidence available to your team.
Start with the decision the data must support
Name the decision before choosing a form. A procurement team may want a first estimate for its purchased-goods inventory, a product designer may want to compare material inputs and a supplier manager may want to understand whether a business has measured its emissions. Those decisions work with different objects and data.
| Decision | Data to request |
|---|---|
| Supplier engagement or corporate reporting maturity | Organisation-wide inventory and its covered entities, scopes, period and review status |
| Estimate purchased-goods category emissions | Physical purchase quantities or other suitable activity data and factors representative of the category and boundary |
| Model the purchased component | A product carbon footprint, or PCF, for the specific item, site, version and period, with a declared unit and matching boundary |
Table 1, shown one row at a time. Every field is retained.
Row 1
- Decision
- Supplier engagement or corporate reporting maturity
- Data to request
- Organisation-wide inventory and its covered entities, scopes, period and review status
Row 2
- Decision
- Estimate purchased-goods category emissions
- Data to request
- Physical purchase quantities or other suitable activity data and factors representative of the category and boundary
Row 3
- Decision
- Model the purchased component
- Data to request
- A product carbon footprint, or PCF, for the specific item, site, version and period, with a declared unit and matching boundary
For supplier engagement, request the organisation inventory and its coverage. For purchased goods, match activity to suitable category factors. For an item-level model, request the matching item, site, revision, period and boundary.
Diagram text description
A supplier’s organisation-wide total can inform engagement. Assigning a share to a component requires a defensible allocation and evidence that the included processes fit the purchase. A product factor may be more specific, but a value for a different material grade or production site could be less useful than a documented proxy.
Write the intended use into the request and acceptance record. If a team later wants to reuse a value in a different inventory, report or public comparison, ask a reviewer to check whether the original evidence still applies.
Prioritise the supplier requests worth making
Start with categories likely to contribute materially to the inventory. Use the best available screen, such as purchase quantities with representative average factors, and record its uncertainty. Spend can help identify a category to investigate. High spend alone may reflect a premium price or purchasing volume rather than the activity with the largest emissions.
Ask where better supplier evidence could change a decision. A high-volume component with two possible production routes may warrant a focused request because the route affects both the estimated footprint and the choice of supplier action. A lower-volume service with a stable estimate might stay on the existing method until a refresh would change the decision. Give each invitation a reason the buyer can explain to the supplier.
Rows distinguish lower and higher likely emissions. Columns distinguish lower and higher value of better evidence. A high–high case enters the first cohort. A high-emissions case with lower decision usefulness can be screened. A lower-emissions case with high usefulness can receive a targeted request.
Diagram text description
Build the first cohort around a few suppliers and a small number of items. Check who can answer for the actual plant, and whether a smaller supplier needs a worked example or a call to explain the fields. The US EPA’s supplier engagement guidance recommends clear questions and support for suppliers with fewer resources.
Review how many answers became usable for the stated decision. If responses commonly omit the site or boundary, improve the request before adding suppliers. A large response count is useful only if the buyer can act on the evidence.
Send a request suppliers can answer
Tell suppliers which purchase the request covers, what the buyer will do with the response and who can see it. Use the fields below as a reusable form. Prefill what the buyer already knows and ask the supplier to confirm or correct it. Give the supplier a way to mark an item unknown and say what it can provide instead.
| Field to complete | What to enter |
|---|---|
| Product or service identity | Supplier item code, buyer SKU, revision, producing site and any production mix |
| Declared unit and activity | Quantity and unit the value describes, such as one item or one kilogram. Include matching purchase mass or other activity if needed |
| Reporting period | Period represented, applicable lots and the periods of significant datasets |
| Boundary and exclusions | Included stages, where transport stops, packaging treatment and material omissions |
| Method and allocation | Calculation method and version, factor sources and how shared processes were assigned |
| Supporting evidence | Original files, activity records, evidence of source quality and scope of any assurance |
| Owner and due date | Buyer requester, supplier contact, response deadline and person who can resolve an exception |
| Review status and intended use | Requested, received, clarification, accepted for named use or superseded, with owner and date |
Table 2, shown one row at a time. Every field is retained.
Row 1
- Field to complete
- Product or service identity
- What to enter
- Supplier item code, buyer SKU, revision, producing site and any production mix
Row 2
- Field to complete
- Declared unit and activity
- What to enter
- Quantity and unit the value describes, such as one item or one kilogram. Include matching purchase mass or other activity if needed
Row 3
- Field to complete
- Reporting period
- What to enter
- Period represented, applicable lots and the periods of significant datasets
Row 4
- Field to complete
- Boundary and exclusions
- What to enter
- Included stages, where transport stops, packaging treatment and material omissions
Row 5
- Field to complete
- Method and allocation
- What to enter
- Calculation method and version, factor sources and how shared processes were assigned
Row 6
- Field to complete
- Supporting evidence
- What to enter
- Original files, activity records, evidence of source quality and scope of any assurance
Row 7
- Field to complete
- Owner and due date
- What to enter
- Buyer requester, supplier contact, response deadline and person who can resolve an exception
Row 8
- Field to complete
- Review status and intended use
- What to enter
- Requested, received, clarification, accepted for named use or superseded, with owner and date
The request identifies product and revision, unit, boundary, period, method and evidence. The reviewer checks the actual item, site and processes, tests the source and its provenance, and documents the intended use.
Diagram text description
Where the supplier has activity data but no product result, request the quantities and their coverage. The buyer’s analyst can then decide whether a documented factor is suitable. Use plain examples for units and boundary descriptions and provide a secure route for confidential attachments. Confirm which fields the supplier can share before requiring the same level of detail from every participant.
Keep every response in a visible state
Use status to show what happened and what needs to happen next. Preserve the supplier submission before adding the buyer’s review notes. Give each response its own version so a clarification can be linked to the earlier value and its decision.
| State | What it means | Responsible role |
|---|---|---|
| Invited | The request has a named purpose, scope, contact and deadline | Buyer requester |
| Received | The original response and files have been recorded | Supplier contact and intake owner |
| Incomplete or clarification | A required field is absent, inconsistent or ambiguous | Buyer reviewer names the gap and supplier contact resolves it |
| Under review | The reviewer is checking identity, boundary, units, period and evidence | Method reviewer |
| Accepted for a named use | The reviewer has documented the permitted use and any limits | Designated approver |
| Superseded | A new version or changed purchase scope has replaced the record for a specified use | Product record owner |
Table 3, shown one row at a time. Every field is retained.
Row 1
- State
- Invited
- What it means
- The request has a named purpose, scope, contact and deadline
- Responsible role
- Buyer requester
Row 2
- State
- Received
- What it means
- The original response and files have been recorded
- Responsible role
- Supplier contact and intake owner
Row 3
- State
- Incomplete or clarification
- What it means
- A required field is absent, inconsistent or ambiguous
- Responsible role
- Buyer reviewer names the gap and supplier contact resolves it
Row 4
- State
- Under review
- What it means
- The reviewer is checking identity, boundary, units, period and evidence
- Responsible role
- Method reviewer
Row 5
- State
- Accepted for a named use
- What it means
- The reviewer has documented the permitted use and any limits
- Responsible role
- Designated approver
Row 6
- State
- Superseded
- What it means
- A new version or changed purchase scope has replaced the record for a specified use
- Responsible role
- Product record owner
Name the decision in the request, preserve the file at receipt and review identity, boundary, unit, period and source. Accept a fitting version only for the named use. Route a gap to clarification or a labelled proxy where allowed. Keep the source, open gap and review trigger with the decision and retain superseded records.
Diagram text description
Keep a status history with the person, decision date and reason. Avoid overwriting the received value with a converted one. Store the original and derived values separately so a later reviewer can identify who made the conversion and on what basis.
Acceptance belongs to a defined use and version. If a buyer approved a result for an internal screening estimate, another team should see that restriction before trying to export the number for a customer report. Where evidence is unresolved, keep the affected use on hold and route the next question to the person who can answer it.
Check whether the number fits the purchase
Start with identity. Match the supplier item, revision, facility and period to the goods actually bought. Then read the boundary. A cradle-to-gate result ends at the stated production gate. A delivered or full-life result can include other stages. Confirm where freight and packaging enter before inserting the number into a purchase estimate.
Next check the denominator. A factor expressed per kilogram can be converted to a per-item value only when the item mass represents the same material or product that the factor describes. The diagram uses fictional values. For a factor of 2.40 kg CO₂e per kilogram of finished collars and a matching mass of 0.25 kg per collar, multiply to get 0.60 kg CO₂e per collar.
The factor applies to one kilogram of the matching finished collar. Each collar weighs 0.25 kilograms. Multiplying the two gives 0.60 kilograms of carbon dioxide equivalent per collar. A scope or period mismatch needs a separate resolution.
Diagram text description
Keep the original factor, mass record and conversion. A packaging-inclusive shipping weight would need reconciliation before it could be used with a factor for the unpacked item. If a factor represents two sites, check which site supplied the shipment or record how the mix was established. If a period does not match, ask which production data changed and whether the value still represents the purchase.
A unit conversion can fix the denominator. A scope mismatch needs a separate resolution, such as a supplier breakdown or a revised result. Do not remove freight by guesswork just to make the fields align.
Judge evidence, not just a completed form
Treat the completed form as the start of evidence review. Read how the value was made, including which data are specific to the product and which are estimates. Keep the source and version beside the value so a reviewer can determine whether the evidence covers the same item and period.
| Evidence check | What the reviewer looks for |
|---|---|
| Product and stages | Exact item and site, included processes, exclusions and treatment of freight |
| Method and factors | Method version, allocation choices, source references and fit of the factors |
| Primary-data share | How the share was defined, which stages it represents and where secondary datasets remain |
| Uncertainty | Significant proxies, assumptions, time or geographic gaps and the sensitivity of the intended decision |
| Verification | What was reviewed, by whom, and which product, method, boundary and period were within scope |
Table 4, shown one row at a time. Every field is retained.
Row 1
- Evidence check
- Product and stages
- What the reviewer looks for
- Exact item and site, included processes, exclusions and treatment of freight
Row 2
- Evidence check
- Method and factors
- What the reviewer looks for
- Method version, allocation choices, source references and fit of the factors
Row 3
- Evidence check
- Primary-data share
- What the reviewer looks for
- How the share was defined, which stages it represents and where secondary datasets remain
Row 4
- Evidence check
- Uncertainty
- What the reviewer looks for
- Significant proxies, assumptions, time or geographic gaps and the sensitivity of the intended decision
Row 5
- Evidence check
- Verification
- What the reviewer looks for
- What was reviewed, by whom, and which product, method, boundary and period were within scope
An assurance statement for a supplier’s organisation can sit alongside a component value without covering that value. Ask for the assurance scope and check it against the specific claim the buyer plans to make. If the supplier has no documented percentage of primary data, record the known measured processes and secondary inputs, and leave the percentage unresolved.
Review fitness for the named use. A record with a disclosed secondary upstream factor may support an internal estimate if the uncertainty is understood. A comparison may need equivalent function, methods and evidence across both products.
Work through gaps and changed products
Give the supplier a precise clarification request. Instead of asking for a “better PCF,” identify the field that blocks the decision. For example, request the supplier-gate subtotal and the description of the delivery leg when a submitted number ends at your warehouse. Record the reason for the hold and what evidence would resolve it.
If the supplier cannot provide the information in time, use a documented secondary proxy where your method allows it. Link the proxy to the item, scope, date and source version, and tell reviewers which use it supports. Keep the original response alongside it. A blank record should stay visible if no defensible estimate is available.
Reopen an accepted record when a relevant fact changes. A new revision can change the mass, a site change can affect the energy supply and a new factor or reporting period can make the old result less representative. Ask the supplier which changes apply. Keep the prior accepted version for the period and use it covered, and document when the new version takes effect.
Track repeated problems. If several suppliers send a delivered figure when the request calls for the supplier gate, add a clear example of the stopping point. Reduce avoidable clarification work before broadening the collection.
Separate internal collection from data exchange
A private portal can collect questionnaires and attachments for the buyer’s own workflow. Interoperability concerns whether separate systems can exchange structured information using agreed technical rules. PACT’s Technical Specifications describe a product footprint data model and an API for exchange. PACT describes the exchange as direct between participating host systems, with no central PACT database holding supplier values.
| Buyer need | What to assess |
|---|---|
| Manage supplier requests | Invitations, responses, evidence files, permissions, clarification and review |
| Exchange a structured PCF with a partner | Compatible technical specification version, authorisation and a tested exchange between the two systems |
| Use an exchanged figure in a decision | Product mapping, declared unit, boundary, method, data quality and permission for the named use |
Table 5, shown one row at a time. Every field is retained.
Row 1
- Buyer need
- Manage supplier requests
- What to assess
- Invitations, responses, evidence files, permissions, clarification and review
Row 2
- Buyer need
- Exchange a structured PCF with a partner
- What to assess
- Compatible technical specification version, authorisation and a tested exchange between the two systems
Row 3
- Buyer need
- Use an exchanged figure in a decision
- What to assess
- Product mapping, declared unit, boundary, method, data quality and permission for the named use
A private portal manages requests, responses, attachments and review. Standards-based exchange transfers structured PCF data between systems. Check the interface version and the received record’s fitness for use.
Diagram text description
A portal and a PACT-conformant exchange interface can coexist. A supplier might respond through a form while another partner shares a structured PCF from its own system. In both cases, the buyer still needs to map the record to its product and review the evidence. A successful transmission establishes that the systems exchanged data. Review of the footprint calculation and approval for use are separate decisions.
If exchange is part of the procurement requirement, ask which version the software has been tested against. Use an agreed partner and test dataset to confirm what each side can send and receive, what happens when permissions are missing and how a replacement record is handled.
A buyer checklist for portal selection
Test the portal with real tasks from both sides before committing. Use a small sample with one straightforward response, one incomplete submission, a duplicate request and a product revision. Give the supplier a chance to show where the terminology or data entry creates extra work.
| Test | What to look for |
|---|---|
| Supplier usability | Prefilled identifiers, clear units, reusable answers, simple corrections and a way to flag missing evidence |
| Bulk import | Validation for missing columns and inconsistent units, with clear errors and traceable source files |
| Product linkage and duplicate handling | Distinct supplier, site, period and revision, with duplicates flagged before sending |
| Review and audit trail | Separate received and accepted states, decision owners and an accessible record of changes |
| Permissions and export | Appropriate access to confidential files and an export that retains source, version, status and restrictions |
Table 6, shown one row at a time. Every field is retained.
Row 1
- Test
- Supplier usability
- What to look for
- Prefilled identifiers, clear units, reusable answers, simple corrections and a way to flag missing evidence
Row 2
- Test
- Bulk import
- What to look for
- Validation for missing columns and inconsistent units, with clear errors and traceable source files
Row 3
- Test
- Product linkage and duplicate handling
- What to look for
- Distinct supplier, site, period and revision, with duplicates flagged before sending
Row 4
- Test
- Review and audit trail
- What to look for
- Separate received and accepted states, decision owners and an accessible record of changes
Row 5
- Test
- Permissions and export
- What to look for
- Appropriate access to confidential files and an export that retains source, version, status and restrictions
Run the test through to export. Check whether a second analyst can reproduce a conversion and tell which scope was approved without asking the original reviewer. Try a correction to a supplier record and inspect which users see it and whether affected calculations can be identified.
If the team needs exchange with another system, test that separately from bulk import. Record any manual steps that remain and who will own them. Use the results to choose the tool that fits the workflow and supplier capacity.
Review a corrected supplier carbon record
Consider this fictional example. Fenmere Assembly buys a finished metal collar from Norbeck Components. Its internal estimate separates the supplier-gate product value from inbound freight. The supplier’s first file contains a delivered value that already includes the trip to Fenmere. All names, values and evidence references below are invented.
| Record field | Filled entry |
|---|---|
| Purchase and period | Fenmere SKU FC-25 revision C, Norbeck item NB-250 from the fictional Alder plant, 2025 production |
| Requested boundary and unit | Supplier gate, per kilogram of finished collars, with delivery to Fenmere handled separately |
| First response and issue | NC-25 v1 gives 2.70 kg CO₂e per kg to Fenmere’s receiving point, including inbound freight |
| Clarification and correction | Procurement asks for the supplier-gate result. NC-25 v2 separates the journey and gives 2.40 kg CO₂e per kg for the matching item and period |
| Buyer conversion | Batch specification shows 0.25 kg per finished collar. The buyer calculates 2.40 × 0.25 = 0.60 kg CO₂e per collar |
| Evidence and remaining gap | Supplier note explains measured forming energy and its allocation. Upstream metal uses a secondary dataset whose period is unresolved |
| Decision and owner | Inventory reviewer accepts v2 for Fenmere’s internal purchased-goods estimate only. Procurement requests the missing dataset period |
| Review trigger | Reopen when the supplier provides the dataset period, or when the item, site, method or purchase period changes |
Table 7, shown one row at a time. Every field is retained.
Row 1
- Record field
- Purchase and period
- Filled entry
- Fenmere SKU FC-25 revision C, Norbeck item NB-250 from the fictional Alder plant, 2025 production
Row 2
- Record field
- Requested boundary and unit
- Filled entry
- Supplier gate, per kilogram of finished collars, with delivery to Fenmere handled separately
Row 3
- Record field
- First response and issue
- Filled entry
- NC-25 v1 gives 2.70 kg CO₂e per kg to Fenmere’s receiving point, including inbound freight
Row 4
- Record field
- Clarification and correction
- Filled entry
- Procurement asks for the supplier-gate result. NC-25 v2 separates the journey and gives 2.40 kg CO₂e per kg for the matching item and period
Row 5
- Record field
- Buyer conversion
- Filled entry
- Batch specification shows 0.25 kg per finished collar. The buyer calculates 2.40 × 0.25 = 0.60 kg CO₂e per collar
Row 6
- Record field
- Evidence and remaining gap
- Filled entry
- Supplier note explains measured forming energy and its allocation. Upstream metal uses a secondary dataset whose period is unresolved
Row 7
- Record field
- Decision and owner
- Filled entry
- Inventory reviewer accepts v2 for Fenmere’s internal purchased-goods estimate only. Procurement requests the missing dataset period
Row 8
- Record field
- Review trigger
- Filled entry
- Reopen when the supplier provides the dataset period, or when the item, site, method or purchase period changes
NC-25 v1 includes delivery. After clarification, NC-25 v2 reports the supplier-gate factor for the matching item and period. Use v2 only for the internal purchased-goods estimate, account for inbound freight separately and reopen the decision when the upstream dataset period arrives.
Diagram text description
Retain both versions and the clarification. Use the gate figure in the purchased-goods estimate and keep the inbound journey in the separate freight calculation. The first file stays visible as the record received. The corrected file carries the accepted scope and the open upstream gap.
The reviewer has approved a bounded internal use. The case does not provide independent assurance or a basis for a public product comparison. If another buyer wants the value, its own item, route, period and review purpose need to be checked.
Prepare the product and supplier records
Prepare the product record before inviting the supplier to respond. Link the buyer’s SKU and revision to the supplier item and production site. Where the purchase becomes part of a bill of materials, identify which component quantity and unit belong to the finished product. That makes it possible to use a returned factor for the right item instead of applying it to a product family.
If two sites make the same catalogue item, keep the versions and applicable batches distinguishable. If procurement changes suppliers under the same buyer code, preserve the previous mapping with its period and the calculation that used it. Where the mass changes, attach the source record rather than overwriting the old value.
Give procurement responsibility for the mapping, give the analyst responsibility for the unit and boundary checks and give the reviewer authority to decide the permitted use. The product file prepares evidence for the review. The review still needs the original supplier submission, its method and the reasons any gap remains open.
Make supplier engagement part of the system
Start with one purchasing category and a small group of suppliers. Tell them which decisions the buyer will make from the data and give them a clear request, a contact for questions and a reasonable deadline. At the first review, trace one accepted value back to the supplier’s submission and note where a clarification or proxy was needed.
Measure how many responses can support the intended use, how much effort the request took and which fields need better examples. Share useful feedback with the suppliers who contributed. For the collar case, follow up on the upstream dataset period before extending use. Expand the process when the team can preserve the original data, resolve discrepancies and explain why an accepted value belongs in its calculation.
SKU, BOM & supplier data
