FIFO (First In, First Out) Stock Rotation in Regulated Manufacturing
A practical guide to stock eligibility, selection order and reviewable FIFO decisions without confusing receipt order with expiry order.

On this page · 11 sections
- 1What FIFO actually is
- 2Physical rotation versus accounting cost layers
- 3The US drug distribution rule and its scope
- 4When FIFO fits: a receipt-order worked case
- 5When expiry order changes the decision
- 6From receipt to issue: the operational lifecycle
- 7Evidence that explains a pick and supports traceability
- 8System handoffs and recovery from changed stock status
- 9Where FIFO breaks and how controls expose it
- 10Measuring adherence without misleading denominators
- 11Implementation and review checklist
How does FIFO 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 FIFO actually is
FIFO (First In, First Out) is a stock-rotation method that selects the earliest-entered eligible inventory before later-entered eligible inventory. In physical inventory management, it governs which stock is selected for movement or use, rather than merely how inventory appears on a report.
Entered refers to the inventory-entry event the site chooses to establish stock age. That could be receipt into the site's inventory, supported by a goods receipt note. The chosen event is distinct from manufacture, expiry and quality-status timestamps: each answers a different question. FIFO terminology alone does not prescribe a universal age basis. A useful operating definition names the event and identifies the record that carries it.
Eligibility means the site's applicable selection conditions, such as suitable quality status, material identity, storage condition and order-specific restrictions. Age ranks candidates after eligibility has been assessed; it does not replace that assessment. The oldest stock physically present may therefore differ from the oldest stock available for a particular issue.
| Term | Selection basis | Practical purpose | Boundary |
|---|---|---|---|
| Physical FIFO | Earliest inventory-entry event among eligible stock | Rotate stock by entry age | Does not establish eligibility |
| FEFO | Earliest expiry date among eligible stock | Use shorter-dated stock first | Not permission to issue expired stock |
| LIFO | Latest inventory-entry event among eligible stock | Select newest-entered stock first | Describes order, not suitability |
| Accounting FIFO | Earliest cost layers assigned first | Value inventory and issues | Does not prove physical movement |
| Lot traceability | Lot identity and linked movement records | Follow stock history and destination | Does not choose picking priority |
FEFO means First Expired, First Out. Operationally, it selects the earliest expiry date among eligible stock—not the earliest receipt. A later receipt can therefore take priority if it expires sooner. Despite its name, FEFO is not permission to issue expired stock; eligibility still governs the candidate pool. Expiry-driven FEFO addresses remaining shelf life, whereas FIFO addresses entry age. The two methods produce the same sequence only when those orderings align; neither term is a synonym for the other.
02Physical rotation versus accounting cost layers
Physical FIFO answers a warehouse question: which stock unit actually moved? Accounting FIFO answers a different question: which inventory cost layer was assigned to an issue? These are separate operational and accounting concepts; using FIFO costing does not demonstrate FIFO picking.
For example, assume an older receipt and a newer receipt belong to different physical lots of the same item. The financial system assigns the older receipt’s cost layer to a sale, while the warehouse ships stock from the newer lot. The cost assignment can describe the expense recognised as cost of goods sold (COGS), but it does not identify the lot shipped. A costing report alone therefore cannot reconstruct the physical selection or explain why that lot was chosen.
A practical reconciliation connects separate records rather than treating either as a substitute:
- Physical movement identity: item, lot and, where tracked, container or pallet, with origin and destination.
- Quantity moved and its unit of measure.
- Transaction reference linking the warehouse issue to the financial posting.
- Valuation-layer reference identifying the cost assignment.
Use WMS movement records to establish what moved and perpetual inventory records to reconcile stock changes; compare those references with valuation records separately.
03The US drug distribution rule and its scope
For US drug-product distribution under 21 CFR 211.150, written procedures must be established and followed: "Written procedures shall be established, and followed, describing the distribution of drug products." This is a binding obligation within the US drug-product framework, not a general FIFO rule for every regulated manufacturer. See the broader 21 CFR 211 context.
For US drug products, 21 CFR 211.150(a) states: "A procedure whereby the oldest approved stock of a drug product is distributed first. Deviation from this requirement is permitted if such deviation is temporary and appropriate."
For US drug products under this provision, the operative wording is oldest approved stock—not earliest receipt, earliest manufacture or earliest expiry. The permission to deviate for US drug products is conditional: the deviation must be both temporary and appropriate, rather than an unrestricted alternative selection policy.
Eligibility and exceptions are different decisions
As a suggested site practice, determine eligibility before ranking candidates. Excluding stock that is on hold removes it from consideration; bypassing an older eligible candidate is a different decision that deserves an explanation. A convenient picking location is not itself evidence that older stock was ineligible.
Suggested exception controls are to record the reason, identify the responsible reviewer, and define the closure condition for returning to normal selection. Consider recurring exceptions through change control rather than allowing an informal workaround to become the operating rule. These are proposed site controls, not additional quoted legal duties or agency guidance.
| Jurisdiction and product | Reference or applicability question | Operational boundary |
|---|---|---|
| US drug-product distribution | 21 CFR 211.150(a), discussed above | Oldest approved stock first; deviation permitted if temporary and appropriate. |
| US drug warehousing | Check the current text of 21 CFR 211.142 for scope. | Assess warehousing separately from distribution selection. |
| US foods | Check the current text of 21 CFR 117.93 for scope. | Do not import the US drug distribution rule. |
| Supplements, devices, chemicals and other jurisdictions | Identify the applicable product classification, market and rules. | Establish the legal basis before selecting a rotation policy. |
Keep authority separate from implementation
In the site's applicability review, distinguish binding law from official guidance and local practice. Treat guidance according to its stated authority; do not relabel site recommendations as agency expectations. Treat software support as implementation support, not legal authority or proof of compliance. Keep review, approval and release decisions with responsible people.
04When FIFO fits: a receipt-order worked case
Receipt-based FIFO is a practical candidate when stock is interchangeable for the intended use, the same age basis applies to every candidate, and no competing expiry or customer condition changes eligibility. The following hypothetical case illustrates an operational choice, not a prescribed handling unit or regulatory exception.
Assumptions and selection
Alpha and Beta are named stock units, each a sealed drum. Their item and specification match the request, and both have the site's assumed eligible status for this issue. Receipt establishes stock age consistently; Alpha entered inventory before Beta. The requested issue can be fulfilled from Alpha without opening or splitting the drum. Neither expiry nor a customer-specific condition excludes either candidate or gives Beta priority.
- Identify candidates: include Alpha and Beta because both match the requested item and specification. Do not restrict the candidate set to whichever drum is easiest to reach.
- Assess eligibility: confirm the assumed eligible state applies to each drum for the intended issue. This assessment establishes which stock can participate in the ranking.
- Compare receipt age: use the receipt values associated with each stock-unit identity, such as those linked to a goods receipt note. Alpha ranks ahead of Beta.
- Select Alpha: the earlier eligible receipt can fulfill the request, so Alpha is the receipt-order FIFO choice.
Convenience does not change the ranking
Suppose Beta is already at the pick face, while Alpha is less convenient to retrieve. That location advantage does not make Beta the earlier receipt. Selecting Beta instead is a different decision to evaluate against the site's procedure, not a silent redefinition of FIFO.
Useful decision evidence comprises the selected receipt-based policy, both stock-age values, each candidate's eligibility state at selection, the candidate set, and Alpha's selected stock-unit identity. Together, these explain why Alpha was chosen rather than merely showing what left storage.
05When expiry order changes the decision
Assume both lots are eligible for the intended issue under the site's defined conditions, the item and specification match, and the handling unit is a sealed case. Expiry dates are known and reliable. Either lot can satisfy the request without opening a case. This hypothetical comparison isolates the selection policy; it does not establish release criteria or legal permission to distribute.
| Lot | Receipt order | Expiry order | Selection outcome |
|---|---|---|---|
| Cedar | Arrived earlier | Expires later | Receipt-based FIFO candidate |
| Birch | Arrived later | Expires earlier | Expiry-based FEFO candidate |
Receipt-based FIFO selects Cedar because it arrived first. Expiry-based FEFO selects Birch because its expiry comes first. Selecting Cedar leaves the earlier-expiring Birch in storage; selecting Birch leaves the earlier-received Cedar. Neither comparison changes either lot's eligibility under the assumptions. The conflict is between ranking rules, not between acceptable and unacceptable stock.
As an operational design recommendation, define which consideration takes precedence for this item and intended use, with a tie-breaker where relevant. An expiry-driven selection policy can put Birch first, while receipt order can resolve equal expiry dates. Document that hierarchy in the picking procedure rather than leaving the choice to an undocumented picker preference. The decision should be explainable from the policy and lot attributes, not merely from whichever case was easiest to reach.
Operational suitability and legal authorization remain separate questions. For the US drug-product boundary, refer back to the regulatory section above; do not treat this FEFO example as a standing exception to that rule.
If an expiry date is unavailable, ambiguous or disputed, the assumptions no longer hold. Use the site's defined escalation or restriction process to resolve the uncertainty before relying on expiry ranking. In expiry date management, an unknown date should remain visibly unresolved—not silently become the longest remaining life. Otherwise, the apparent ranking conceals a data problem rather than supporting a deliberate stock-rotation decision.
06From receipt to issue: the operational lifecycle
The following proposed warehouse sequence separates stock identification, selection and execution. It is an operating model, not a universal regulatory workflow. Site procedures define the authoritative records, permitted actions and escalation routes at each decision point.
Workflow: identify receipt → establish eligibility → rank candidates → reserve stock and create task → verify pick and recheck eligibility → post movement or escalate.
- Identify the receipt. During inbound receiving, associate the material, lot, quantity, location and handled-unit identity. A lot identifies a production grouping; a pallet or container identifies a physical stock unit. Several units may belong to the same lot. Assign the stock-age event defined by the site’s rotation procedure and retain its timestamp against the relevant stock record.
- Establish eligibility. Consult the authoritative quality and inventory states defined by the site, including any applicable inspection disposition, holds, location restrictions and available quantity. Receipt alone does not establish an approved condition. Where incoming inspection informs disposition, use the resulting authorised status rather than treating arrival or label creation as permission to issue.
- Rank eligible candidates. Apply the defined FIFO age reference only after eligibility filtering. Use the configured tie-break reference when needed; detailed handling of equal timestamps belongs in the FAQ. Preserve a candidate snapshot as described in the evidence section below.
- Reserve and create the task. Treat the ranked result as a recommendation until a reservation commits the intended quantity against identified stock. Create the warehouse task with the allocated lot, handled unit, source location, quantity and destination. Reservation does not confirm physical movement; see the evidence section for that distinction.
- Verify before completing the movement. Warehouse personnel compare the picked stock with the allocated identity and quantity, then perform a final eligibility check using current authoritative states. A mismatch or unsuitable state stops routine completion and goes to the assigned reviewer. Neither a prior recommendation nor an existing reservation substitutes for this check.
- Post the physical issue. Warehouse personnel confirm execution and record the actual movement, quantity, identities and time. Keep the posted issue distinct from the recommendation and reservation so the record distinguishes intended activity from completed activity. Approval authority stays with people, as noted in the authority-boundary section above.
- Define scopeSelect the policy and inventory population.
- Identify stockConnect physical units to their age events.
- Check eligibilityApply the site's current selection conditions.
- Rank CandidatesOrder eligible units using the defined basis.
- Reserve StockRetain the candidate snapshot and allocation.
- Verify pickConfirm identity and recheck relevant status.
- Record movementPost the issue and link exception decisions.
07Evidence that explains a pick and supports traceability
A selection policy answers why particular stock was chosen. Genealogy and movement records answer where identified material actually went. A FIFO allocation can explain the intended pick without proving that the allocated stock was issued, consumed or shipped. Connecting those records supports both decision reconstruction and bin-level lot genealogy, while preserving their different purposes.
Illustrative evidence model
The following is a proposed record design, not a prescribed database structure or a description of product features. Its relationship chain is: receipt → stock unit → allocation → executed issue → manufacturing consumption or shipment, as applicable.
| Record | Illustrative fields |
|---|---|
| Receipt and identity | receipt_id, lot_id, stock_unit_id, received_at |
| Selection decision | decision_id, policy_version, age_basis, age_value, decision_at |
| Candidate snapshot | decision_id, stock_unit_id, eligibility_state, available_qty, uom, exclusion_reason |
| Allocation | allocation_id, decision_id, stock_unit_id, allocated_qty, uom, actor_id, exception_ref |
| Executed movement | movement_id, allocation_id, stock_unit_id, from_location, to_location, moved_qty, uom, executed_at, actor_id |
| Downstream connection | movement_id, consumption_id, manufacturing_batch_id, shipment_id, destination_id |
Preserve the candidate snapshot at decision time, including eligible alternatives and excluded stock with reasons. Record the age basis explicitly: a timestamp alone does not explain whether the policy ranked receipt, manufacture or another defined event. Keep the applicable policy version retrievable rather than merely naming the current policy.
Link allocations to executed movements without treating them as interchangeable. Partial issues, splits and reversals benefit from separate movement records with quantities and units. For production, connect those movements to material consumption postings; for distribution, connect them to shipments and destinations. Retain the responsible actor and any exception reference alongside the relevant decision or action.
For warehouse recall execution, rotation history provides context, not the downstream population. Reconstruct affected movements from actual lot-linked consumption and shipment records, rather than assuming the stock that should have moved was the stock that did move.
RotationPolicy
Defines the selection basis.
- policy_id
- scope_id
- age_basis
- tie_break_rule
- effective_at
- policy_version
Lot
Identifies shared material attributes.
- lot_id
- material_id
- manufacture_at
- expires_at
- quality_status
StockUnit
Locates individually distinguishable inventory.
- stock_unit_id
- lot_id
- location_id
- stock_age_at
- received_at
- quantity
- uom
Allocation
Preserves the selection context.
- allocation_id
- stock_unit_id
- order_line_id
- candidate_set_id
- policy_version
- allocation_status
StockEvent
Records traceable inventory changes.
- event_id
- stock_unit_id
- event_type
- occurred_at
- source_event_id
- actor_id
RotationException
Connects rationale and review.
- exception_id
- allocation_id
- reason_code
- rationale
- reviewer_id
- decision_at
- closure_state
08System handoffs and recovery from changed stock status
Treat system boundaries as implementation responsibilities, not assumed product integrations. A practical division for MES–ERP integration and MES–WMS integration is:
- ERP: maintain material and order context and receive inventory postings.
- Warehouse system: track stock units, locations and available quantities; manage allocations and picking tasks.
- Quality-status source: maintain authoritative disposition and hold status, with decisions controlled by authorised people.
- Production or shipping execution system: confirm the actual consumption or shipment event against the selected stock identity.
Define handoff data explicitly: material and lot identifiers, stock-unit identity, status, location, quantity, unit of measure, event time and source-event reference. Agree which system owns each field and how acknowledgements, delayed messages and duplicate events are handled. Arrival order alone is a poor basis for resolving conflicting status updates.
Worked case: a hold arrives before picking
Assume the handling unit is a pallet. Its stock unit was eligible when allocated, but a hold-status update arrives before picking. No physical issue has occurred. Proposed recovery is:
- Stop the affected task so the stale allocation cannot drive picking.
- Reconcile the authoritative status and affected stock identity through the agreed container-status controls.
- Cancel or revise the stale allocation, retaining its original event reference.
- Refresh eligible candidates and apply the configured rotation rule.
- Record the replacement selection, reason and links to the hold and superseded allocation without erasing the original history.
This is routine re-selection after eligibility changes, not a discretionary bypass of an eligible candidate. For a bypass, use the exception governance covered above. Software can provide configured assistance for data exchange, ranking and recordkeeping; it does not transfer approval authority from people, consistent with the authority boundary above.
09Where FIFO breaks and how controls expose it
A FIFO rule can rank records correctly while warehouse data misrepresents the stock. The following are plausible failure modes and proposed operational controls, not prescribed compliance tests. Diagnose the ordering inputs and execution evidence before treating a younger-stock pick as an operator error.
| Failure mode | Observable symptom | Preventive control | Review evidence |
|---|---|---|---|
| Administrative transaction overwrites age | An older pallet moves behind newer receipts after a transfer or record correction. | Explicitly control the age basis; preserve event lineage rather than substituting the latest transaction timestamp. | Original receipt event, change history, and ranking before and after the transaction. |
| Aggregation hides receipt-age groups | A lot total contains separate receipts, but the picker sees only one age. | Maintain stock-unit-level visibility and retain receipt-age groups through consolidation. | Stock-unit receipt records compared with the aggregated balance and pick candidates. |
| Stranded reservations exclude older stock | Older stock remains reserved against a cancelled or completed demand while newer stock is issued. | Reconcile reservations with demand status and review reservation ownership before clearing them. | Reservation owner, linked demand status, allocation history, and disposition. |
| Physical labels drift from system identity | A scanned pallet or bin label resolves to a different lot or stock unit. | Reconcile physical identity with system identity and control relabelling. | Scan results, label history, and physical stock reconciliation. |
| Inconsistent time-zone handling | Receipt order reverses between screens or exports displaying the same events. | Apply consistent timestamp interpretation, retaining offsets and distinguishing event time from posting time. | Underlying timestamps, offsets, and interface conversion rules. |
| Quantity units do not match | An older stock unit appears insufficient because allocation and stock balances use different units. | Use controlled unit mappings and explicit conversion and rounding rules. | Source units, mapping versions, and converted allocation quantities. |
Use FIFO pick enforcement to frame selection checks and bin-level lot genealogy to investigate identity discrepancies. After correction, compare the reconstructed candidate order with the recorded pick decision; a changed balance alone does not explain the original failure.
10Measuring adherence without misleading denominators
A proposed FIFO adherence measure is conforming assessed selections divided by assessed selections. Before calculating it, define the scope: products, locations, review period, selection event, ordering key and treatment of ties. Specify whether equally ranked eligible lots all count as conforming.
Assess each decision against the candidate set and eligibility state at selection time—not today’s inventory. Use contemporaneous selection records and the process event log to reconstruct what could actually have been selected.
Keep justified departures and unexplained bypasses separately visible within assessed decisions; neither counts as FIFO conformity. Report decisions lacking enough evidence as unassessable, alongside the assessed denominator and total reviewed decisions. Reconcile those counts so missing evidence cannot disappear through denominator exclusions or be mistaken for successful rotation.
For management review, examine aging eligible stock, blocked allocations and recurring exception reasons qualitatively. Ask whether patterns reflect access constraints, status delays or selection behaviour. These proposed management measures support investigation; they are not statutory metrics, regulatory thresholds or proof of compliance.
11Implementation and review checklist
Use this suggested readiness checklist before introducing FIFO or changing an established rotation policy. It supports site governance rather than serving as an exhaustive legal checklist.
- Assign a policy owner and define the inventory scope: materials, products, locations and movement types covered.
- Document the age basis, who controls stock eligibility, the selection hierarchy and who authorizes and closes exceptions.
- Test normal selection against the receipt-order worked case and conflicting expiry order against the expiry-order worked case above; record expected and observed decisions.
- Challenge stale status, inaccessible stock and incomplete decision evidence. Confirm how each condition is detected, contained and resolved before the affected movement proceeds.
- Reconcile recorded issues, transfers and reversals with physical movements; investigate mismatches rather than treating allocation records as proof of execution.
- Keep unresolved exceptions visible through assigned owners, disposition status and supporting evidence for exception-based review.
- Review changes to policy configuration or master data through change control, including their effect on selection and whether affected tests need repeating.
As before, people retain approval and release authority; system behavior and recorded evidence inform, not replace, that review.
Frequently asked questions
Q.What should happen when eligible stock units have the same recorded receipt time?+
A practical tie-break rule uses a stable secondary identifier, such as the original receipt transaction sequence or container identifier. Apply it consistently rather than letting operators choose whichever pallet is easiest to reach. If the timestamp reflects a bulk upload, consult the underlying goods receipt note before assuming the units arrived together. Document the tie-break logic in the site's FIFO picking procedure, and keep genuine ties distinguishable from missing or unreliable receipt data.
Q.How should an opened container be positioned relative to sealed stock from the same lot?+
An opened container commonly needs a separate suitability check before its picking priority is decided. Consider its opening history, closure condition, storage exposure and any established in-use restriction. Where continued use is acceptable, a documented partial-container-first rule can reduce unnecessary openings without redefining the lot's receipt age. Connect partial container handling with container status tracking, so an accessible part-pack is not mistaken for an eligible one. Record consumption against the actual container used.
Q.Can a customer's minimum remaining-shelf-life condition change a FIFO pick?+
Yes, as an order-eligibility condition, not a replacement for the rotation rule. For the US drug-product distribution requirement and its deviation condition, see the regulatory section above. In practice, record the customer's condition and why older stock is unsuitable; retain it for suitable demand. This differs from FEFO, which ranks by expiry rather than receipt age, as defined above.
Q.How should returned stock be considered for re-entry into the FIFO sequence?+
A practical approach keeps returned units outside the pickable sequence while designated personnel assess identity, condition, custody and storage history. Use returns quarantine to separate that assessment from routine allocation. If re-entry is approved, preserve the original stock-age reference where it remains reliable, while recording the return receipt separately. Treating the return date as a fresh original receipt can conceal ageing stock. Uncertain history calls for a disposition decision, not an arbitrary position in the queue.
Q.Should consignment ownership affect the physical FIFO sequence?+
Ownership commonly defines which stock is available to a particular order, rather than how old that stock is. Establish the eligible ownership pool from the consignment agreement and allocation rules, then apply FIFO within that pool. Adjacent pallets belonging to different owners are not necessarily interchangeable. Client segregation helps explain this distinction operationally. An ownership change can be recorded as a commercial event without resetting physical receipt age; unresolved allocation rights belong with the responsible commercial personnel.
Q.How should an intersite transfer preserve the stock age used for FIFO?+
A practical transfer record carries both the established FIFO age reference and the destination receipt time. The destination timestamp describes arrival there; it need not replace the earlier age reference. Reconcile identifiers, quantities and receipt history between dispatch and receipt, using the stock transfer receipt advice where applicable. Preserve links through pallet splits or relabelling with bin-level lot genealogy. The site's procedure should explain which age reference governs allocation across its warehouse network.
Q.How can opening inventory be evaluated when legacy receipt records are incomplete?+
Start with a physical reconciliation of identity, quantity and location, then assess which age references can be supported by receiving, supplier or transfer records. A practical migration approach distinguishes known dates from estimates and unresolved dates rather than assigning every unit the system start date. Use the inventory accuracy review to identify discrepancies, and document approved corrections through a stock adjustment process. A physical count establishes presence, not historical receipt order; uncertain sequencing needs an explicit allocation decision.
Q.What can recurring FIFO overrides reveal about purchasing and pack-size decisions?+
Repeated overrides can indicate a mismatch between purchased pack sizes and actual consumption, rather than a picking problem alone. Group exceptions by material, supplier pack, demand pattern and stated reason. Frequent selection of smaller, newer packs may justify reviewing purchase quantities, dispensing arrangements or partial-pack handling. Compare these patterns with MRP assumptions before changing replenishment settings. Treat the pattern as a hypothesis: purchasing and warehouse personnel can test whether revised order quantities address the underlying cause.
Primary sources
Explore this topic
FIFO sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.
GS1 identifiers, barcodes, ASNs and the rules that require lot-level traceability.
Material requirements planning, BOM explosion, net requirements, scheduling and demand signals that drive what the floor makes next.
Want to see how FIFO could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
