Product and supplier data review
One product dataset that answers customer questions.
This is for you if product records, EPDs and supplier answers live across PDFs, inboxes, spreadsheets and separate systems, so every customer question starts again.
- Defined scope
- Evidence recorded
- Usable output
What we do
Who this is for and when. For manufacturers, merchants and procurement teams with a catalogue, bill of materials, product category or supplier group whose EPDs and supplier responses need to be usable for procurement, reporting or a tender.
When product and supplier information sits across records, emails, PDFs and separate systems, every customer question and tender answer is rebuilt from scratch and the answers do not match. This work produces one structured dataset for the agreed scope, with each record's evidence, status, owner and next action set out, and a request routine that keeps it current.
- Agree the catalogue, bill of materials, product category or supplier group in scope.
- Consolidate existing product records, EPDs and supplier responses against a fixed set of fields.
- Assess what counts as usable, current or missing evidence for procurement, reporting and tender use.
- Flag missing, expired and conflicting entries, with an owner and next action against each.
- Rebuild the supplier request template and follow-up routine around that structure.
What you receive
- An organised dataset for the agreed scope, recording product reference, supplier, evidence URL, EPD status and expiry, declared and functional unit, source, owner, evidence status and next action
- A gap and inconsistency list with named owners and next actions
- Supplier request templates and a maintenance guide for your team
What we need from you
The range in scope, exports of the product data you hold, recent supplier responses and a contact in product, technical or procurement.
Provenance: every figure is logged with its source and method, marked measured, estimated or supplier-provided, and recorded with any assumption behind it. Status: each figure is then rated on currency, completeness and any conflict, and anything missing or expired is flagged rather than relied on.
What is not included
We organise and check the information you hold and request what is missing. We do not verify supplier claims independently and we do not produce EPDs. A wider supplier engagement programme can be scoped separately.
Proof
How this work is structured.
A preview of the format used on this service. The records shown are generic samples created for illustration.
Product and supplier data schema
Swipe to see all columns
| Group | Fields | Example entry | Why the group exists |
|---|---|---|---|
| 1 Identity | product_id, supplier_id, product_name | P02 | S01 | Example insulation product | Stable IDs keep names and documents linked. |
| 2 Evidence | document_id, programme_operator, source_url, version, valid_to | Example supplier document v2; source link pending | Keep a separate evidence record; do not invent an EPD ID. |
| 3 Comparison basis | declared_unit, modules, function, technical_performance, service_life | Unit recorded; performance evidence pending | Store the basis alongside the value, not in a footnote. |
| 4 Result record | indicator, value, unit, scenario, method_version | No value entered: review incomplete | One result per indicator, module and scenario; never treat missing as zero. |
| 5 Maintenance | status, data_owner, checked_on, next_action, due_date | Needs review | Product data owner | Confirm performance | Make responsibility and currency part of the dataset. |
Same records, one at a time
1 Identity
- Fields
- product_id, supplier_id, product_name
- Example entry
- P02 | S01 | Example insulation product
- Why the group exists
- Stable IDs keep names and documents linked.
2 Evidence
- Fields
- document_id, programme_operator, source_url, version, valid_to
- Example entry
- Example supplier document v2; source link pending
- Why the group exists
- Keep a separate evidence record; do not invent an EPD ID.
3 Comparison basis
- Fields
- declared_unit, modules, function, technical_performance, service_life
- Example entry
- Unit recorded; performance evidence pending
- Why the group exists
- Store the basis alongside the value, not in a footnote.
4 Result record
- Fields
- indicator, value, unit, scenario, method_version
- Example entry
- No value entered: review incomplete
- Why the group exists
- One result per indicator, module and scenario; never treat missing as zero.
5 Maintenance
- Fields
- status, data_owner, checked_on, next_action, due_date
- Example entry
- Needs review | Product data owner | Confirm performance
- Why the group exists
- Make responsibility and currency part of the dataset.
Illustrative structure using synthetic example records. No declaration identifier is invented: evidence is held as its own record, with status and owner beside it.
Download the product dataset schema example (PDF, one page) Illustrative structure using synthetic records, not a client document.
Questions about this service
Do you need our data in a particular format?
No. We work from the exports and records you already hold, and agree one structure for the scope as part of the work.
Do you verify supplier claims?
We organise and check what you hold and request what is missing. Independent verification of supplier claims is a separate appointment.
How is the dataset kept current?
You receive supplier request templates, an owner and next action against each record, and a maintenance routine your team can run.
Discuss the catalogue or supplier group in scope
Tell us the catalogue, bill of materials, category or supplier group you need organised. We agree the inputs, outputs, scope and review points in writing before work starts.