Traceability is often described as a property of a supplier. It is not. It is a chain that runs from an analytical document, through a lot identifier, through an inventory row, to a work record — and it exists only where every link in that chain is intact at the same time. A supplier can publish flawless records and a laboratory can still have no traceability at all, because the chain broke on a shelf three weeks after delivery. This page is about holding the chain together on the buyer's side.
The chain, and where it is weakest
Each link has a different owner. The supplier owns the document and the lot assignment. The courier owns a period during which neither party can observe the material. Your receiving officer owns the moment the physical object and the paperwork meet. Your records system owns everything afterwards, which is by far the longest stretch and the one with the most staff turnover.
Predictably, the weakest link is the last one. Documents are rarely lost at the point of supply; they are lost eighteen months later when nobody can work out which downloaded file corresponds to which inventory row. That is a filing problem, not an analytical one, and it is solvable without any specialist system.
Store the document, not a link to it
A portal reference is not a record. Portals change, links rot, and the question you will eventually need to answer is what the document said on the day you accepted the material — not what a live lookup returns today. Download the record and store the file itself in your own repository, then keep the portal reference alongside it as a convenience rather than as the primary artefact. VaultLabs publishes per-lot records where they have been uploaded, and they can be reached through COA verification and the COA area, but your copy is the one that matters to your audit trail.
Name files so a stranger can use them
Most retrieval failures are naming failures. A file called "coa final (2).pdf" is unfindable by anyone except the person who saved it, and that person will leave. A filename that carries the SKU, the lot identifier, and the issue date can be matched to an inventory row by someone who has never seen the order. Adopt one pattern, write it into the receiving procedure, and do not allow exceptions — an inconsistent convention is barely better than none. Supporting material for this practice is collected in the documentation centre, with the concept defined at audit trail.
Record the absence as carefully as the presence
A receiving log that only records documents when they are found tells you nothing about the lots where nothing was found. Those are exactly the entries that matter later. Write down that a check was performed, what was entered, and what came back — including "no published record at this date". An explicit negative is a finding. A blank field is an unanswered question that will be read, years later, as though nobody looked.
Retention outruns the material
Set the retention period for records against how long results derived from the material will remain relevant, not against how long the vial lasted. The vial is consumed in weeks; the questions arrive in years. If your institution has a records retention schedule, map analytical documents onto it explicitly rather than assuming they are covered. Where a consolidated set of records is needed for a review, the documentation pack route is the appropriate request channel.
What a reviewer actually asks for
In practice the request is narrow and predictable. A reviewer wants to see, for one named lot: the document, the receiving entry, the storage record, and the work that used it. If those four can be produced in a few minutes for any lot chosen at random, your traceability is real. If producing them requires a search, a phone call, and someone's memory, it is not — regardless of how good the supplier's records are. The framework VaultLabs publishes around this is described at the Vault Standard.
FAQ
Is a supplier's published record enough on its own?
No. It establishes what the lot was at analysis. Your own receiving entry, storage record, and usage log establish everything that happened afterwards, and traceability requires both halves.
What if a record is uploaded after we have already received the material?
Attach it to the existing lot entry and note when it was obtained. The sequence is part of the record; backdating it is not.
How do I link a record to a specific vial rather than an order?
Through the lot identifier, which is the only field common to the document and the container. The reasoning is set out in how to read a COA.
Does documentation change what the material may be used for?
No. Records support traceability and internal qualification. The catalogue is positioned research-use-only and all material is supplied for in vitro laboratory research only.