Lot Attribute

Most inventory systems carry two layers of data about a material: the item master, which describes what the material generically is (its code, description, unit of measure, default supplier, standard cost), and the lot or batch record, which describes a specific, physically identifiable quantity of that material produced or received at a particular time. A lot attribute lives on the second layer. It is a fact that is true of this lot — this delivery of vitamin C powder, this fermentation batch of probiotic blend, this reel of label stock — and is not assumed to be true of every other lot of the same item code.

The commonest lot attributes in manufacturing and warehouse operations fall into a handful of families. Potency or assay values record how much of the active or labelled constituent the lot actually contains, expressed against a specification range rather than a single number — a vitamin premix might carry an assay of 102.3% of label claim on one lot and 98.7% on the next, both passing, but materially different inputs to a formulation calculation. Expiry and retest dates record how long the lot may be used or how long it may sit before it must be re-tested and re-dated; these two concepts are related but distinct, and conflating them is a common source of inventory errors. Status fields record where the lot sits in a disposition lifecycle — commonly something like quarantine, released, rejected, or on hold — and gate whether the lot is even visible to picking, production issue, or shipping logic. Country of origin records where the material was grown, synthesised, or last substantially transformed, which can matter for tariff classification, country-of-origin labelling, or customer-specific sourcing restrictions. Allergen flags record whether the lot contains, or was produced on a line shared with, a declared allergen, which can differ lot to lot even for the same item code if a supplier changes a sub-ingredient or a shared line runs a different product between cleans.

The attribute set is not fixed by any single regulation; what counts as a lot attribute for a given material is a function of what that material's specification requires and what downstream processes need to know before they touch the lot. A vitamin concentrate might carry potency, moisture, heavy-metal results, and a retest date. A packaging substrate might carry only a supplier batch reference and a visual-inspection pass/fail. A blood or tissue product, at the far end of the spectrum, carries donor eligibility and screening status as inseparable lot-level facts. The common thread is that all of these are attributes of the lot, not the item, and a system that only stores them at item level cannot represent the difference between two deliveries of the same material.

First-Expired, First-Out picking logic only works if the system can see an expiry or retest date on every eligible lot and compare it reliably across lots of the same item. If that date lives only on a paper certificate of analysis or a handwritten label, a picker has no automated way to know which of three lots on the shelf is closest to expiry, and FEFO collapses into whatever order the lots happen to be arranged in on the rack — which in practice tends to default to FIFO by receipt date, or worse, to whichever lot is physically easiest to reach.

Making FEFO work operationally means the expiry or retest date has to be captured as a structured lot attribute at receipt — read from the supplier's certificate of analysis or label, keyed or scanned into the lot record — and then made visible to the picking logic as a sortable field, not just a printed note. Pick-list generation, allocation, and put-away slotting can then all reference that attribute: a warehouse management system can direct a picker to the lot with the nearest date without the picker needing to compare dates by eye, and can block allocation of a lot whose date has already passed its usable window.

The same lot-attribute mechanism also supports the less visible case of a conditional or shortened date — a lot that passed its original specification but was assigned a tighter internal retest date because of a marginal stability result, or a lot held under an internal shelf-life policy stricter than the supplier's labelled date. None of that nuance is representable if the system only stores a single generic "item default" shelf life; it depends on the date being a property of the lot.

Many formulated products — nutritional premixes, animal feed additives, active pharmaceutical ingredients, flavour and fragrance concentrates — are formulated to deliver a target amount of an active constituent, not a target weight of raw material. If a lot of an active ingredient assays at 97% of label claim rather than the nominal 100%, dispensing the standard recipe weight of that lot under-delivers the active by roughly 3%, which can be enough to fail a finished-product specification depending on the margin built into the formulation.

Potency-adjusted dispensing (also called assay-adjusted or strength-adjusted dispensing) uses the lot's recorded assay value as an input to a weighing calculation, scaling the quantity dispensed so that the amount of active constituent delivered matches the target regardless of which specific lot is pulled. This only works if the assay result is attached to the lot being weighed — a bulk container of the ingredient — rather than stored as a generic item-level figure, because the whole point is that different lots of the same nominal material carry different actual potency.

Getting this wrong in either direction has consequences: dispensing by nominal weight against a lot that assayed low under-delivers the active and risks an out-of-specification finished product; dispensing by nominal weight against a lot that assayed unusually high can push a formulation toward an upper specification limit, or in some categories, toward a safety or regulatory ceiling. Capturing and using the lot's actual assay as a dispensing input is the mechanism that keeps the finished batch on target across lot-to-lot raw-material variability, rather than only after the fact at finished-product testing.

The status attribute is what turns a lot record into something a quality team can govern. A newly received lot of a component is typically not immediately usable; it sits in a quarantine or "on hold" status until testing or supplier certificate verification confirms it meets specification, at which point quality control personnel change its status to released. If testing shows a specification is not met, or some other deviation occurred, the lot can instead be moved to rejected, or held pending a documented disposition decision.

This pattern has a direct regulatory anchor for dietary supplement manufacturers in 21 CFR 111. Section 111.113 requires quality control personnel to conduct a material review and make a disposition decision whenever a specification is not met, a batch deviates from its master manufacturing record, an unanticipated occurrence could adulterate a component or product, calibration issues raise doubt about prior results, or a product is returned — and the regulation requires that components, in-process material, or finished product be rejected unless quality control approves a specific treatment, in-process adjustment, or reprocessing instead 1. That disposition decision is exactly what a status attribute is built to record and enforce: the lot cannot move to a released state in the system until the documented review has happened.

Before any of that, 21 CFR 111.75 requires that a component's identity be verified — at minimum one appropriate identity test for a dietary ingredient, unless an exemption has been separately petitioned and granted — and that other component specifications be confirmed either by in-house testing or by relying on a qualified supplier's certificate of analysis 2. Operationally, that verification step is also what a status attribute gates: a lot cannot reasonably carry a released status until its identity has been confirmed and its other specification results have been checked against the limits set under 111.70 3.

Holding itself has its own baseline requirement: 21 CFR 111.455 requires that components, dietary supplements, packaging, and labels be held under conditions of temperature, humidity, and light that do not affect identity, purity, strength, or composition, and under conditions that prevent mix-up, contamination, or deterioration 4. A quarantine status attribute, paired with physical segregation or a system-enforced hold on picking and shipping, is the practical way a warehouse keeps an unreleased lot from being mixed into stock that is fit to use while it is still being held under those conditions.

For purchased components, lot attributes typically originate on the supplier's certificate of analysis (CoA) — the document in which the supplier reports the results of its own testing against an agreed specification for that specific lot. Getting those values from a PDF or paper document into a usable, structured lot record is the step where a lot attribute either becomes a reliable operational input or stays a filed-away document nobody actually reads before picking.

21 CFR 111.75 explicitly allows a manufacturer to rely on a supplier's certificate of analysis to confirm non-identity component specifications, but only on conditions: the manufacturer must first qualify the supplier by establishing the reliability of its certificates through confirmation of the supplier's own testing results, and must periodically re-verify that reliability 2. That qualification step is what gives a receiving team the basis to key a supplier's reported assay, moisture, or heavy-metal figures straight into the lot record as trusted attributes, rather than re-testing every lot in-house — but it also means the CoA-to-lot-record pathway is not simply a data-entry exercise; it depends on an underlying supplier qualification decision being current.

Operationally, the flow usually looks like: a lot arrives with its CoA; receiving captures identity confirmation per 111.75(a)(1); quality or receiving staff transcribe or scan the CoA's reported values — assay, moisture, microbial counts, heavy metals, country of origin if stated, the supplier's own lot number — onto the internal lot record, cross-referencing the supplier's lot number to the internal lot number so the two can be traced against each other later; and the lot's status is set to quarantine pending any additional checks the manufacturer's own specification requires, then moved to released once the review under 111.113 is complete. Each of those transcribed CoA values becomes a lot attribute precisely because it is now attached to this lot's record rather than sitting only in the supplier's document.

Manual transcription is also where attribute data most commonly goes wrong — a mistyped assay value, a retest date read off the wrong line of a densely formatted CoA, a unit mismatch between the supplier's reporting basis and the internal specification. Because downstream decisions (potency-adjusted dispensing, FEFO picking, release) depend directly on these values, errors introduced at this step do not stay contained to a paperwork record; they propagate into formulation calculations and shipping decisions made against the lot.

The quarantine-to-released status pattern described for dietary supplements under 21 CFR 111 is a specific instance of a much more general GMP concept: that material moving through a regulated manufacturing process should carry an explicit, auditable status reflecting its disposition at every stage, and that systems and procedures should prevent material from being used, shipped, or further processed while that status is not yet "released" or equivalent. This article opened and verified the Part 111 text directly; the parallel material-status provisions in other regimes — such as pharmaceutical cGMP under 21 CFR 211 or 21 CFR 820 for devices, or EU GMP Annex-level guidance — were not opened for this review, so this section describes the general, widely documented shape of that concept across industries rather than quoting specific clause numbers from those other regulations.

In practice, this means the same lot-attribute architecture — a status field, an expiry or retest date, identity and specification results, and a documented chain from receipt through disposition — tends to recur across food, dietary supplement, pharmaceutical, and medical device manufacturing environments even though the specific regulatory citations differ. What varies by sector is the detail of what must be tested, who must sign the disposition decision, and how long the records must be kept; what stays constant is the underlying requirement that a lot's status and supporting attribute data be captured at the lot level, kept current, and consulted before the lot moves further.

Allergen status is a useful illustration of how the same architecture extends beyond classic identity/purity attributes. An allergen flag on a lot record is not typically a result of the lot's own assay testing; it more often derives from the formulation or supplier declaration associated with that specific lot — for example, a supplier substituting a sub-ingredient, or a shared production line's last-run product before changeover. Representing that as a lot attribute, rather than a static item-level allergen statement, allows a system to reflect that two lots of the same nominal material can carry different allergen exposure, which matters directly for label accuracy and for segregation decisions in a shared facility.

A recurring failure mode is storing an attribute that should vary by lot as a fixed value on the item master instead — a single "standard shelf life" or "standard assay" applied to every lot regardless of what its own CoA actually says. This defeats FEFO logic, potency-adjusted dispensing, and status-based release all at once, because the system has no way to distinguish lots that should be treated differently.

Another is treating the lot attribute as a document reference rather than a structured value — attaching a scanned CoA to the lot record without extracting the specific figures into searchable, sortable fields. A scanned PDF satisfies a record-keeping requirement but does not let a picking or scheduling system act on the data inside it.

A third is losing the link between an internal lot number and the supplier's own lot or batch number once the CoA values have been transcribed — which makes it harder to trace a quality issue back to the supplier's original lot if a recall or investigation surfaces later, and harder to re-verify a supplier's certificate reliability as required for continued reliance on their CoAs.

Finally, conflating expiry date and retest date in a single field causes downstream confusion: an expiry date generally means the material should not be used past that point, while a retest date means the material must be re-evaluated against specification before further use or extension, and may still be usable afterward if it passes. Systems and procedures that store only one date field, and apply it inconsistently as either concept depending on the material, make both FEFO logic and release decisions less reliable.