Traceability as a procurement requirement.
Traceability in procurement means being able to show where an item came from, who handled it, and under what conditions it moved, at every handover between the manufacturer and your receiving dock. It fails as a requirement when it is written as an adjective rather than a list of documents. A tender that says goods must be traceable without naming the records it expects will receive exactly what it asked for: a promise.
Traceability gets treated as a quality-department concern that procurement merely restates in the purchase order. That is how it ends up as a single line at the bottom of a specification, satisfied by a supplier's assurance, and discovered to be worth nothing the first time a lot has to be located quickly.
This piece covers what the requirement should actually name, where records reliably break down, and how to write it so replies can be compared. If you are still defining the requirement itself, how to scope a medical product inquiry comes first.
What traceability actually asks for
Strip the word back and it is four questions. What is this item, specifically. Where did it come from. Who has held it since. And what were the conditions while it moved. A record set that answers all four is traceable; one that answers two is a packing list.
The depth required depends on what the item is and where it is going, which is why the requirement belongs in the same section as the specification rather than in a general terms appendix. A consumable and an item with a defined shelf life under specific storage conditions do not ask for the same records, and a public-sector buyer usually has reporting obligations that a private purchaser does not.
Batch-level and unit-level are different promises
Batch-level traceability lets you identify every unit sharing a lot number. Unit-level traceability follows an individual item through its life. Unit-level is a materially heavier requirement and is generally driven by regulation or by items where individual identification matters — it should be demanded deliberately, not inherited by accident from vague wording.
The records worth naming
Name documents, not qualities. Each of these is something a supplier either produces or does not, which makes replies comparable instead of merely persuasive.
| Record to require | What it proves |
|---|---|
| Lot or batch number, with expiry or best-before where the item has one | The key every other record hangs from. Without it, none of the documents below can be tied to what you actually received. |
| Manufacturer or authorised source identification | Where the item came from, unambiguously rather than inferred from packaging. |
| Certificate of analysis or conformity tied to the lot supplied | That this consignment was assessed, not that the product line in general once was. |
| Storage and handling conditions recorded for the journey | That the stated conditions held, with any excursion noted rather than smoothed over. |
| Chain-of-custody record showing each party that held the goods, with dates | That possession is unbroken — the document that makes the rest provable. |
| Product identifiers as they appear on the unit | That what arrived matches what was ordered, item for item. |
Where the record breaks
Traceability rarely fails at the factory. It fails at handovers, because each one is a moment where custody changes and nobody owns the continuity. Ranked by how often the chain actually snaps:
- Consolidation, when goods from several sources are combined and the original identifiers are no longer sufficient on their own.
- The transition from origin to international transit, where documentation is often reissued and lot references can drift.
- Customs and regulatory inspection, where packages are opened, resealed, or held long enough for records to fall behind events.
- Arrival and staging, where a consignment is broken down and put away before anyone has reconciled what arrived against what was recorded.
- Internal distribution onward to the point of use, where the last link is frequently the least documented.
Each of those is a place to ask specifically about in the RFQ rather than in a general enquiry. The handover that worries you is the one to name.
Writing it so it is enforceable
Traceability that sits in the specification has to be scored, otherwise every reply claims it. Put it in the evaluation criteria with a stated weighting, ask for a specimen of each named record, and make clear that an inability to produce them is a material gap rather than a documentation detail.
Three things make the difference between a requirement and a wish: naming the documents, asking for examples before award, and stating what happens when a record is missing. That last one matters more than the first two — a supplier told what a missing record costs will tell you up front which records it can and cannot produce, which is exactly the information you wanted.
Where the requirement carries regulatory weight for the destination, say so in the brief and link the relevant guidance directly rather than paraphrasing it. Our medical and regulatory disclaimer sets out the boundary between this site's general guidance and advice from a qualified professional.
Why procurement owns this
Quality can specify what a record should contain, but only procurement decides whether a supplier without it still gets the business. That trade-off is made during evaluation, before anything ships, and it is made once. Making it afterwards means choosing between goods you have already paid for and records you cannot produce.
It also compounds. A buyer with a documented, comparable record set can move on supply questions quickly, and can answer a challenge about a consignment with documents rather than recollection. Whether that extends to formal public-sector reporting obligations depends on the programme — government contracting is where those obligations usually arrive.
Start with the categories you actually buy. Which product categories we source is a reasonable place to see how differently the six of them answer this question — traceability for a diagnostic device and traceability for a PPE consumable are not the same conversation.
Straight answers.
What does chain-of-custody documentation need to show?
That the goods you received are the goods described: the lot or batch identifier, the source, each party that held the consignment with dates, and the conditions maintained while it moved. Anything short of that identifies the product in general without proving anything about the specific units in front of you.
Is batch-level traceability enough?
For most consumables, yes — it lets you find every unit sharing a lot number, which is what a recall or a quality question requires. Unit-level traceability follows an individual item through its life and is a heavier requirement, generally driven by regulation or by items where individual identification matters.
Where should traceability appear in an RFQ?
In the specification section with the records named individually, and again in the evaluation criteria with a stated weighting. Asking for a specimen of each record before award is what separates suppliers who can evidence the requirement from suppliers who can describe it.
What should we do if a supplier cannot produce a record?
Establish whether the record can be produced at all or was simply not prepared for this consignment, and price the difference into your evaluation rather than discovering it after award. A missing record is material information about the supplier and the route, and it should change the decision rather than be waived quietly.
