Reagent Lot Traceability
Connect finished diagnostic kit lots to the materials actually used, the evidence supporting their use, and the recipients of shipped units—without confusing plans, identity, and acceptance.

On this page · 9 sections
- 1What reagent lot traceability establishes
- 2The regulatory anchors—and their boundaries
- 3Build identity relationships from actual events
- 4Fictional example: a substitution, merge, and split
- 5Separate qualification, dating, and permission to use
- 6Trace uncertainty without overstating causation
- 7Common mistakes and practical trade-offs
- 8Assign record ownership across systems and teams
- 9A practical implementation checklist
How does Reagent Lot Traceability apply to your shop floor?
Pick your industry and scale — Ask V5 rewrites the definition in your context, gives a worked example, and shows what V5 does on day one.
01What reagent lot traceability establishes
Reagent Lot Traceability is the record chain connecting a diagnostic reagent or finished kit lot backward to its actual material inputs and forward to subsequent batches, kits, and shipments. It combines identity relationships, quantities, and supporting evidence so that a question about one lot can be followed in either direction.
A bill of materials describes what a product is intended to contain. A planned issue identifies what production expects to use. Neither proves what entered a particular batch. Genealogy comes from actual consumption and transformation records, including substitutions, splits, merges, returns, and losses. Kit assembly adds another relationship: which filled reagent, control, calibrator, and other in-scope component lots entered each kit lot.
Identity and qualification answer different questions. A lot can be identifiable while testing remains pending; an accepted lot can still be unsuitable for a particular use. The record designs and implementation suggestions below are educational practice, not universal legal requirements. For broader context, see the diagnostics and IVD manufacturing guide.
02The regulatory anchors—and their boundaries
U.S. Labeling and Quality-System Law
Subject to the applicability qualifications in paragraph (a), 21 CFR 809.10(a)(9)(9)) calls for an identified lot or control number from which the product's complete manufacturing history can be determined. For multiple-unit products, it must permit tracing individual-unit identity; for instruments, all functional subassemblies. For included units used together as a system, the provision says all units should bear the same lot or control number, if appropriate, or another suitable uniform identification. This is not a standalone list requiring a separate lot number for every consumable or printed component.
QMSR scope under § 820.1 concerns the methods, facilities, and controls for finished devices intended for human use. A manufacturer performing only some covered operations need comply with the requirements applicable to those operations. Paragraph (a)(2) excludes manufacturers of components or parts of finished devices from this part's provisions, while encouraging appropriate consideration of them. A finished reagent device and a material supplied as a component therefore need distinct applicability assessments.
Section 820.35(c) requires recording the UDI for each medical device or batch of medical devices. Separately, § 820.45 addresses labeling and packaging procedures, accuracy examination before release or storage where applicable, documented labeling release for use, and documented inspection before use to prevent mix-ups. Recording a UDI, releasing labeling for use, and releasing finished product are not interchangeable events.
EU Party Identification and UDI Records
IVDR Article 22 requires distributor and importer cooperation on device traceability. Economic operators must be able to identify their direct suppliers, direct economic-operator recipients, and directly supplied health institutions or healthcare professionals to the competent authority for the referenced period. These are supply-chain party relationships, not a universal component-genealogy specification.
Article 24(7) separately requires manufacturers to maintain an up-to-date list of assigned UDIs within technical documentation. Article 24(8) makes economic-operator UDI storage conditional on devices belonging to categories or groups determined by the referenced measure. Do not turn that conditional storage provision into a blanket requirement to upload every stored UDI to EUDAMED.
03Build identity relationships from actual events
In a practical record design, preserve the supplier's material and lot identifiers alongside the internal identifier. A supplier lot string alone may not be unique across suppliers or materials. Separate receipts or containers can have distinct internal identities while retaining the same supplier-lot parent. Renaming or splitting material should not erase that relationship.
Record issued quantities separately from actual consumption, returns, samples, and losses. For a merge, retain every contributing parent and its quantity. For a split, identify each child and reconcile quantities in compatible units. Do not allocate a suspect parent's influence to selected children merely by its percentage in a mixed bulk.
| Relationship or evidence | Useful practice fields | What it establishes |
|---|---|---|
| Supplier lot → internal receipt | Supplier, material, supplier lot, internal lot, container, quantity and unit | Identity across receiving and production |
| Input lot → transformation → output lot | Actual input/output IDs, quantities, units, event time, returns and losses | What was actually consumed and produced |
| Lot → qualification evidence | Test or evaluation reference, decision, intended use, approver and effective time | Basis for use—not material ancestry |
| Component → kit lot | Actual assembly consumption, substitutions, relevant labeling revision and physical print lot where in scope | Lot-specific assembly history |
| Kit lot → shipment | Recipient, ship-to location, shipment reference, quantity and subsequent disposition | Direct distribution and its known limits |
Supplier lot
Maps to one or more internal receipt identities.
- Supplier + material + supplier lot
Internal material lot
Is consumed by a transformation event; retains its supplier-lot mapping.
- Internal lot
- Receipt/container IDs
Transformation event
Links each actual input lot to identified output lots.
- Input/output IDs
- Quantities and units
- Event time
Qualification evidence
References a material or output lot and supports a use decision; it is not an input lot.
- Evidence reference
- Decision and intended use
- Effective time
Finished kit lot
Links to component lots actually consumed during assembly.
- Assembly reference
- Component consumption
Labeling evidence
References the kit lot and applicable labeling; remains distinct from finished-product disposition.
- Revision
- Inspection record
- Labeling release reference
Shipment line
References a finished kit lot and a direct recipient, not an assumed downstream user.
- Ship-to identity
- Quantity
- Shipment reference
Define trace scope deliberately. Include materials and labeling identities needed to explain manufacturing history and investigate relevant failures. Artwork revision and physical printed-component lot are different facts. A lot-specific production record should preserve the applicable relationships rather than reproduce only the nominal recipe.
04Fictional example: a substitution, merge, and split
This fictional example isolates one reagent branch, not a complete kit dossier. A production plan names enzyme lot RM-E215, which remains pending. A documented substitution instead records accepted lot RM-E214, mapped to supplier lot S-E61, as the actual issue. RM-E214 has 36.0 mL available; 30.0 mL is issued and consumed, leaving 6.0 mL. The planned RM-E215 contributes nothing.
| Actual event | Inputs or starting quantity | Accounted output |
|---|---|---|
| Form bulk PB-318 | 30.0 mL RM-E214 + 270.0 mL diluent RM-D052 | 300.0 mL bulk |
| Fill and split PB-318 | 300.0 mL bulk | FV-318A: 170 × 1.0 mL vials; FV-318B: 110 × 1.0 mL vials; 12.0 mL retained; 8.0 mL documented loss |
| Assemble K-472 | 170 vials FV-318A; one vial per kit | 170 kits |
| Assemble K-473 | 110 vials FV-318B; one vial per kit | 110 kits |
The bulk balance is 170 + 110 + 12 + 8 = 300 mL. The kit balance is 170 + 110 = 280 kits. Both fill lots inherit both bulk-input relationships; the enzyme's 10% volume contribution does not mean only 10% of kits contain that parent.
- Actual enzyme identityRM-E214 / S-E61: 36.0 mL available; 30.0 mL consumed and 6.0 mL remains.
- Accepted for this use
- Planned RM-E215: pending, zero consumed
- Merge into PB-31830.0 mL RM-E214 plus 270.0 mL RM-D052 produces 300.0 mL.
- Both parent IDs retained
- Split into fill lotsPB-318 produces FV-318A: 170 vials and FV-318B: 110 vials, each 1.0 mL.
- 12.0 mL retained
- 8.0 mL documented loss
- Assemble kit lotsFV-318A → K-472: 170 kits; FV-318B → K-473: 110 kits.
- One vial per kit
- 280 kits total
- Distribute and retainK-472 and K-473 total 195 shipped kits and 85 on-hand kits.
- Direct recipient records below
- Distributor onward recipients not established
| Kit lot | Direct shipments | On hand | Reconciliation |
|---|---|---|---|
| K-472 | Lab A: 58; Distributor B: 72 | 40 | 58 + 72 + 40 = 170 |
| K-473 | Lab C: 65 | 45 | 65 + 45 = 110 |
| Total | 195 | 85 | 195 + 85 = 280 |
A concern about S-E61 therefore identifies both kit lots, 195 shipped kits, 85 on-hand kits, the 6.0 mL enzyme remainder, and the retained bulk sample. Distributor B's 72 kits are a known direct shipment, not proof of their present location or end users. These are genealogy findings, not a final recall decision.
05Separate qualification, dating, and permission to use
21 CFR 809.10(a)(5)–(6)(5)) addresses reagent storage instructions protecting stability, including applicable instructions for reconstituted or mixed product. Paragraph (a)(6) provides for one or more label means of assurance at use: an expiration date based on stated storage instructions, an observable indication of alteration, or instructions for a simple method to determine whether appropriate standards are met. It does not make expiration dating the sole means.
As practice, retain applicable dating and storage evidence alongside identity, without treating a date as permission. An in-date lot with pending qualification is not thereby accepted. A qualification decision does not by itself establish remaining shelf life or authorize every application. Preserve the decision effective when material was used, rather than relying only on today's status.
Define when a material change needs additional evaluation based on the assay, material role, existing evidence, and risk. Where a lot comparison is chosen, link the evaluated and comparator lots, criteria, results, and use decision. A new critical lot should not automatically trigger an invented universal bridging protocol.
A shortest-input-date rule may be a chosen conservative control; it is not the rule stated in paragraph (a)(6). Finished-kit dating needs a documented product-specific basis. Keep that dating decision distinct from material acceptance, permission to consume, labeling release, and finished-product disposition.
06Trace uncertainty without overstating causation
For a complaint, first establish the reported product and lot identity, including transcription uncertainties. Trace backward through actual assembly and bulk events, then forward from potentially relevant parents. Include remaining material, retained samples, intermediate stock, finished stock, shipments, and known returns where relevant to the investigation.
A practical trace report separates confirmed links, possible links caused by missing or conflicting evidence, and exclusions supported by records. A blank join is not evidence that material was absent. If an assembly record is missing, report the unresolved boundary and investigate it; do not silently substitute the planned bill of materials.
Complaints sharing an input lot can support a hypothesis, but do not prove that input caused the problem. Failure to find a shared input does not rule out a material or process cause, especially when records are incomplete. Traceability informs containment and investigation; it cannot guarantee a narrowly limited recall. Evidence gaps, distribution uncertainty, and the nature of the hazard may leave the relevant scope broader than the confirmed genealogy.
07Common mistakes and practical trade-offs
| Mistake | Why it misleads | Practical response and trade-off |
|---|---|---|
| Treating a planned issue as consumption | A substituted or returned lot can create false ancestry | Capture actual use; accept additional transaction detail |
| Overwriting supplier identity with an internal code | Separate receipts can become impossible to reconcile | Maintain a durable cross-reference; manage duplicate identifiers |
| Flattening merged bulk to one parent | Other contributing lots disappear from forward traces | Retain all parents; review more complex relationships |
| Equating pending, accepted, and in-date | Identity, qualification, and dating answer different questions | Keep distinct dated states; reconcile conflicting decisions |
| Assuming shipment proves current possession | A distributor may have moved units onward | Request downstream evidence; retain an explicit unknown boundary |
| Tracking every packaging detail indiscriminately | Volume can obscure the evidence needed for a specific failure | Choose and justify scope; narrower capture leaves some questions unanswerable |
Finer container or sublot detail can support more precise reconstruction, but increases reconciliation work. Coarse lot-level records are simpler, yet may not distinguish separate handling or consumption histories. Choose granularity deliberately rather than promising precision the records cannot support.
08Assign record ownership across systems and teams
Whether records reside on paper, in spreadsheets, or across MES, LIMS, and distribution systems, define who owns each identity and event. Production may own actual consumption, the laboratory qualification evidence, and distribution shipment and return records. Agree how identifiers, corrections, and status decisions are exchanged; do not infer capabilities from a software category name.
Useful evaluation questions are concrete: Can the team reconstruct a substituted input, an amended shipment, and a split lot without overwriting earlier evidence? Are quantity units and time-effective decisions unambiguous? Can missing relationships be distinguished from confirmed absence? The IVD manufacturing record dossier offers a related way to organize the supporting record set.
09A practical implementation checklist
Use this as a practice checklist tailored to the product and operations, not as a statutory inspection schedule.
- Define trace scope, identity granularity, and owners for materials, assembly, qualification, labeling, and distribution.
- Preserve supplier-to-internal identifier mappings, including partial receipts and container identities where needed.
- Capture actual consumption and reconcile splits, merges, returns, samples, and losses in explicit units.
- Keep qualification status, dating, permission to use, labeling release, and finished-product disposition distinct.
- Link relevant component and labeling evidence at assembly; address substitutions and corrections explicitly.
- Reconcile lot-specific shipments, remaining stock, and known returns without assuming downstream possession.
- Exercise both backward and forward reconstruction using a realistic exception; document unknowns, responsibilities, and corrective follow-up.
For assembly-specific context, see medical device kitting. A useful trace ends with an evidence-backed answer and a clear statement of what remains unknown.
Frequently asked questions
Q.Is a finished kit lot number enough?+
No. The identifier needs resolvable links to actual manufacturing inputs and relevant distribution records. A number without those relationships identifies a label, not a usable genealogy.
Q.Must every consumable and printed component have its own tracked lot?+
The cited lot-history provision is not a universal item-by-item list. Define the necessary trace scope for the product and applicable obligations. Distinguish labeling revision from physical printed-component lot identity.
Q.Does every new reagent lot require a bridging study?+
Do not assume a universal trigger or protocol. Define evaluation decisions using the material's role, assay risks, and existing evidence. If a comparison is performed, preserve its lot identities and decision basis.
Q.Can a pending lot be treated as accepted because it is in date?+
No. Dating and qualification are different facts. In the practical model described here, permission to use comes from the applicable documented decision, not from the absence of an expired date.
Q.Does UDI replace component genealogy?+
No. A recorded device identifier does not establish which actual input lots were consumed. Maintain the applicable UDI records and the manufacturing relationships as distinct, connected information.
Q.Can a complete trace guarantee a narrowly limited recall?+
No. It can establish confirmed relationships and distribution quantities, but causal uncertainty, missing downstream records, and the hazard itself can affect decisions. Genealogy is evidence, not a recall-scope guarantee.
Primary sources
- eCFR — 21 CFR 809.10, selected IVD labeling provisions; Title 21 display dated 15 October 2026
- eCFR — 21 CFR Part 820, selected QMSR scope, UDI-record, and labeling provisions; Title 21 display dated 15 October 2026
- EUR-Lex — Regulation (EU) 2017/746, Articles 22 and 24; consolidation dated 10 January 2025
Further reading
- IVD Manufacturing Record DossierRelated context for organizing manufacturing records and supporting evidence.
- Medical Device KittingExplore the assembly context in which component identities become finished-kit relationships.
- Diagnostics and IVD Manufacturing GuideBroader background on diagnostic manufacturing and its quality-system context.
Want to see how Reagent Lot Traceability could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
