Knowing a supplier's name is different from knowing where a material came from. Traceability connects a product or batch to records of its origin, movement and transformation. Procurement needs to understand what those records can demonstrate, where they stop and what happens when the evidence is incomplete.
The WOP archive interview with Circulor co-founder Doug Johnson-Poensgen explores traceability, responsible sourcing and the changing role of procurement. The episode description discusses databases and distributed ledgers. This companion develops the practical buying questions around those themes. Vendor roles, customers and technology descriptions in the interview refer to its recording period.
Begin with the claim you need to support.
A team may need to know the origin of a particular material, understand an emissions calculation or investigate a responsible-sourcing concern. Those are different evidence problems. Define the decision before asking a supplier for “full transparency”. That phrase can produce an impressive dashboard without a clear standard for accepting the information.
Describe the unit being traced. It might be an item, a batch or a quantity of material. Ask how that unit is identified and what happens when materials are mixed, split or transformed. A record tied to a supplier account does not automatically establish the history of every product bought from that account.
Make the boundary explicit. First-tier coverage can be useful while leaving important upstream activity unknown. Record which tiers, sites and transformations are included, and where the information depends on supplier declarations rather than independently checked evidence.
A durable ledger cannot repair a false input.
The technology used to store a record matters, but the quality of the original observation matters too. A record can be securely preserved while still describing the wrong batch or relying on an unsupported declaration. Ask who creates the record, how they know the fact and what checks connect it to the physical material.
Compare the system's treatment of routine records and exceptions. What happens if a supplier submits incomplete data? If two records conflict? If an upstream participant refuses to provide information? A useful traceability process has a way to investigate, correct and explain those cases.
Ask about access and ownership. Which participants can see which information, who can correct it and what remains available if a supplier or technology provider leaves? Procurement needs evidence it can use throughout the relationship, including when a dispute makes access uncomfortable.
Connect sourcing decisions to the evidence.
Decide which information is required before selection and which will be supplied during delivery. Put responsibilities, timing and verification arrangements into the buying process. Involve technical, sustainability and operational colleagues in defining what an acceptable record looks like.
Avoid asking for data that no one will use. If the team cannot explain how a field affects a decision, consider whether collecting it imposes more effort than value. Equally, do not accept a missing field simply because the dashboard looks complete. The evidence should support the specific claim the business wants to make.
Use proportionate escalation. A missing upstream record may require investigation, additional evidence or a sourcing decision. The response depends on the material, exposure and alternatives. Assign an owner for the decision rather than leaving the exception indefinitely marked red in a system.
A hypothetical battery-material purchase.
Imagine a buyer needs evidence about a material's origin and processing history. The immediate supplier provides a traceability report covering several batches. Procurement asks how the purchased batch is linked to the report, which transformations were recorded and which participants supplied the underlying information.
The team then identifies a point where physical batches were combined. The report may still be useful, but the nature of the claim needs to reflect the tracking model. The technical owner explains that limitation, the sourcing team determines what further evidence is needed and the supplier receives a clear request.
This is a better outcome than treating the report as a universal certificate. The business can describe what it knows and where uncertainty remains, while procurement has a route to improve the evidence with the supplier.
Keep the data useful after onboarding.
Traceability changes as suppliers, sites and materials change. Agree when records need updating and which events trigger a review. A new processing site or a changed upstream source can matter more than the annual anniversary of an onboarding form.
Link the records to actual purchases and supplier reviews. Otherwise the traceability programme can sit beside the buying process while business decisions continue to rely on old assumptions. Check that the people placing orders and managing changes know where the relevant evidence lives.
What a useful demonstration should show.
Bring a representative item or batch and ask the provider to walk backwards through the records. Include a mixed-material case and a missing-data case. Ask for the source of each material claim, the correction process and the available export.
The interview invites procurement to engage with the supply chain beyond the immediate commercial relationship. The practical next step is to define one claim, trace its evidence and understand its limits. That provides a firmer foundation for responsible sourcing than buying a platform and assuming visibility has been solved.