21 CFR Part 210 makes lot identity a history key—not a release decision

The identifier points to history

The direct answer in 21 CFR 210.3 is that a lot number, control number, or batch number is a key for reconstructing history. The definition reaches manufacture, processing, packing, holding, and distribution. A useful record therefore connects the identifier to the manufacturing order, material and product identities, equipment and location context, dates, quantities, status changes, packaging, holding, shipment, corrections, and the source records that support each step.

The identifier is not the history itself. Printing a code on a container or loading it into an ERP field does not establish that every relevant record can be found, is complete, belongs to the same defined lot, or preserves the version that existed when an action occurred. Buyers should test retrieval across production, laboratory, warehouse, quality, serialization, and distribution systems, including a split lot, rework, correction, and downstream return.

Batch and lot are related but not always identical

Part 210 defines a batch as a specific quantity produced according to one manufacturing order during the same manufacturing cycle. It defines a lot as a batch or an identified portion of a batch and gives a continuous-process alternative based on a defined time or quantity. A data model that treats every batch, lot, sublot, campaign, and continuous-run interval as one interchangeable field can erase the relationship the record is meant to preserve.

A representative demonstration should begin with the organization's controlled definitions and follow one batch into multiple identified portions, or one continuous process into defined lots. The system should show parent-child relationships, permitted merges or splits, unit and quantity reconciliation, status inheritance, sampling and test association, label generation, distribution linkage, and the effect of a correction without silently rewriting earlier evidence.

Acceptance remains a separate decision record

The same section defines acceptance criteria as product specifications and acceptance or rejection criteria, including an associated sampling plan, necessary to decide whether a lot, batch, or other subgroup should be accepted or rejected. That definition keeps identity and disposition separate. A valid identifier can point to a rejected, quarantined, under-investigation, recalled, expired, or released lot; the code alone does not resolve which state applies.

Quality-system and manufacturing buyers should require a governed disposition record that names the applicable specification and version, sample and test evidence, deviations and investigations, responsible quality unit, decision, timestamp, restrictions, and downstream effects. Search, genealogy, and barcode performance are valuable, but they cannot substitute for the accountable acceptance or rejection decision.

Applicability and current status still need qualified review

Part 210 states that applicable CGMP parts supplement rather than supersede one another unless a rule expressly says otherwise, and that the more specific regulation controls when applicable provisions conflict. It also limits a person's duties to the covered operations in which that person engages. Teams should therefore connect each identifier and control to the relevant product, operation, establishment, and current authority rather than apply a generic lot template without scope analysis.

This source establishes definitions and general federal drug-CGMP context; it does not approve a lot, prescribe one software architecture, validate a sampling plan, or decide how another jurisdiction or product class applies. Qualified quality, manufacturing, laboratory, regulatory, validation, supply-chain, and legal owners should determine the operative requirements and retain their rationale. Technology should make that evidence traceable without presenting the presence of a lot number as a release verdict.

Enterprise buyer test

Translate this change into the exact population, record type, workflow stage, decision owner, effective date, and evidence that could be affected. Ask current or prospective providers to demonstrate the named workflow with representative data and an exception—not a polished feature tour. Record what official documentation establishes, what a provider states, what the team observes, and what remains unresolved.

A defensible review also identifies the dependency outside the product. Authority interpretation, policy configuration, data quality, integrations, human judgment, approval rights, release governance, training, and retained evidence may remain customer or service responsibilities. The evaluation should preserve those boundaries instead of treating a technology claim as the complete operating model.

What we will watch next

RegQuality Review will watch the named source and affected market records for later evidence that changes status, scope, availability, implementation timing, workflow consequence, or the limits of the initial report. A later announcement does not silently overwrite this dated account; the change ledger preserves the sequence.