Industrial procurement has long relied on documents: material certificates, inspection reports, declarations, audit reports and certificates of origin. These remain useful. The change is that customers and regulators increasingly ask how each document connects to a specific product and supply-chain event.
A certificate can be authentic and still be irrelevant to the delivered batch. A supplier can be approved while an undisclosed sub-tier performs the critical process. A database can be tamper-resistant while storing an unsupported input. The emerging requirement is not simply “more documents”; it is a more granular evidence chain.
What an evidence chain contains
A practical manufacturing evidence chain connects four elements:
- Identity: product, part, model, revision, material lot, facility and legal entity.
- Transaction: purchase, receipt, transfer, subcontract and shipment records.
- Transformation: what process converted the input, where, when and under which specification.
- Claim or result: composition, conformity, origin, emissions, test result or other statement supported by records.
Each link needs a scope. Does a certificate cover one heat, one furnace load, one batch, one model or an entire facility for a period? Without scope, readers may apply evidence more broadly than it supports.
Chain of custody is not one universal model
ISO 22095:2020 establishes general terminology and models for chain of custody across materials and products. ISO — ISO 22095:2020 In March 2026, ISO announced new standards ISO 22095-2 and ISO 22095-3 concerning mass balance and book-and-claim models. ISO — New standards bring clarity to chain of custody
These references underline an important procurement distinction: physical segregation, controlled mixing, mass balance and certificate trading do not make the same claim. Buyers should identify which chain-of-custody model a scheme uses and whether that model is acceptable for the legal, customer or engineering purpose.
A mass-balance claim, for example, should not be described as proof that a specific physical unit contains a particular source unless the applicable model supports that statement. Conversely, physical unit tracing may be unnecessary where a legitimate programme expressly uses another model.
Traceability is moving from facility-level to product-level questions
Traditional supplier qualification often asks whether a factory has a certified management system. Newer questions may ask which facility made the item, which material batch was used, what transformation occurred, who supplied the input and which evidence supports a sustainability or origin claim.
Regulatory developments such as CBAM, forced-labour controls and Digital Product Passports illustrate different reasons for this shift. They should not be merged into one compliance checklist: each has its own scope, actors, evidence rules and dates. Their common operational need is the ability to connect upstream information to the product or transaction.
NIST's IR 8536, *Supply Chain Traceability: Manufacturing Meta-Framework*, was issued as a second public draft on 31 July 2025. NIST describes it as a cross-sector manufacturing traceability meta-framework; its draft status must remain visible and it should not be presented as a binding standard. NIST — IR 8536 Second Public Draft
Technology follows data discipline
Barcodes, QR codes, ERP systems, shared platforms and distributed ledgers can improve retrieval and integrity. They cannot establish whether the initial data was accurate or whether a supplier omitted an operation.
NIST's publication on blockchain and related technologies for manufacturing traceability examines technical and non-technical challenges and emphasises the need to understand traceability objectives and system context. NIST — IR 8419 overview
Before buying a platform, define:
- what question the traceability system must answer;
- the smallest required traceable unit;
- the events and transformations to record;
- who creates, checks and corrects each field;
- evidence-retention and access rules;
- how identifiers survive processing and repacking; and
- how data from different suppliers will interoperate.
If these rules are unclear, technology digitises ambiguity.
Design traceability according to consequence
Full unit-level tracing can be expensive or physically impossible for some bulk materials. A risk-based design selects the required granularity: unit, batch, heat, load, purchase order, facility or reporting period.
The selection should consider safety, regulatory obligation, customer contract, material mixing, process variability and the cost of containment if something fails. A low-risk standard item may need supplier and lot records. A safety-critical custom part may need material heat, serial identity, special-process load and individual inspection results.
State where traceability legitimately ends. An honest limitation is more useful than an unsupported “fully traceable” claim.
Test the chain with retrieval and reconciliation
Choose a delivered item and trace backward to material and processors, then choose an incoming lot and trace forward to finished shipments. Reconcile quantities, identities and dates. Record missing links and the time required.
This bidirectional test reveals common weaknesses:
- one certificate reused across unrelated batches;
- labels removed during cleaning or finishing;
- supplier names changed between local and English records;
- subcontract operations absent from the route;
- mixed inventory with no allocation method;
- spreadsheet claims with no source method; and
- valid records that cannot be retrieved within a decision deadline.
The corrective action may be better identifiers, controlled containers, document indexes, supplier notification, retained source records or a narrower claim. Blockchain is not the default answer.
Procurement checklist
- What business, quality or regulatory question must traceability answer?
- What is the required traceable unit?
- Are product, revision, batch, facility and legal-entity identities controlled?
- Are transactions and transformations recorded, not only final certificates?
- Does every claim identify its evidence, method, scope and date?
- Is the chain-of-custody model stated accurately?
- Are quantities and yields reconciled across transfers?
- Can identifiers survive subcontract processes?
- Are corrections and superseded records preserved?
- Can the chain be traced backward and forward within the required time?
- Are confidentiality and access rights controlled?
- Are limitations disclosed instead of hidden behind “fully traceable” language?
What this means for procurement
Supplier evaluation is moving from document possession to evidence connectivity. Buyers should not abandon certificates; they should ask what each certificate proves and how it connects to the delivered item. A modest, well-tested lot-level system is often more credible than a sophisticated dashboard with unclear inputs.
Morning Sunlight Asia can help map China-side suppliers, processes, lots and documents into an order-level evidence chain. Submit Your Requirements to define the traceability question and the practical granularity before selecting tools.