FIFOFirst In, First Out

FIFO is a consumption rule. When a SKU has multiple lots available, FIFO picks the lot that was received earliest. The lot's expiry date is ignored — receipt date is the sort key. For materials where age does not change fitness for use (corrugate cartons, screws, labels, bottle caps, durable spare parts), FIFO is the right rule because it matches consumption to receipt sequence, prevents indefinite ageing of working stock, and aligns physical movement with the cost-flow assumption finance is already using. For materials where age does change fitness for use — drugs, supplements, food ingredients, reagents, refrigerated finished goods, biologics — FIFO is the wrong rule, and FEFO (First Expired, First Out) replaces it.

The reason this distinction is worth a full page is that FIFO is the historic default in most ERPs and many warehouse systems. A site that ships a new SKU usually inherits FIFO until somebody actively configures FEFO for that SKU. If nobody does, perishables silently age out on the shelf — the loss shows up only at the next cycle count, by which point the financial damage is locked in and the regulatory exposure (dispensing a near-expiry lot when a longer-dated lot was on hand) is non-trivial. The fix is to make per-material rule selection an explicit decision at SKU creation, not a default that nobody owns.

FIFO is two disciplines wearing the same name. Conflating them is the source of most disagreements between operations and finance.

They can diverge without anybody noticing for months. A warehouse can be physically running LIFO (operators grab the front pallet because it's closer) while the ERP serenely relieves cost from the earliest layer, producing a financially clean FIFO report and an operationally broken FIFO process. The cycle count catches it eventually — old lots show up in odd corners with values nobody recognises — but by then the financial restatement window is already open.

Auditors split the same way. A GMP inspector wants to see that the lot the operator just picked is the oldest available, and they will sample a dispense or a putaway live to prove it. An external financial auditor wants to see that the inventory carried on the balance sheet is the latest receipts and the COGS is the earliest layers; they will rebuild the cost flow from the ERP. Both can pass; both can fail; and a site can pass one and fail the other. V5 Ultimate enforces physical FIFO at the kiosk pick — the lot proposal is the oldest, deviations require an override reason that is logged in the batch record — and emits accounting events that an ERP can consume to keep its own cost-flow layer aligned.

FIFO is the right default for any material where the following five conditions hold.

1. No meaningful expiry. The supplier does not issue an expiry date, the material is not subject to potency loss in normal storage, and microbial drift is not a concern. Corrugate, hardware, durable consumables, packaging films, non-perishable additives all fit this category.
2. Receipt order is a reasonable proxy for sequence of use. The earliest received lot is also the lot that has been exposed to warehouse conditions longest, so consuming it first naturally limits working-stock ageing.
3. Lot identity does not affect downstream traceability beyond standard genealogy. The customer does not require a specific lot for a contract or a recall window.
4. Physical and accounting FIFO can be aligned with reasonable effort. Mixed-lot pallets at line-side are the chief obstacle here; if they are unavoidable the site needs an explicit mitigation (see 'common failures' below).
5. The downstream consumption process can be paused or reorganised without batch-record consequences when the FIFO lot is unavailable (under-quantity, on hold, in another zone). For perishables this last condition is almost never true — running out of FEFO lot mid-batch is a deviation — and that is one of the structural reasons FEFO is treated more strictly.

Where any of the five conditions break, the right answer is either to switch the SKU to FEFO or to add the missing capability (lot-level expiry capture, mixed-pallet decomposition, explicit override workflow) before relying on FIFO for compliance.

FIFO degrades silently and predictably when applied to any of the following material classes. The damage shows up in writeoffs, in cycle-count surprises, and — most painfully — in regulatory findings tied to dispensing a near-expiry lot when a longer-dated lot was on hand.

• Pharma APIs, excipients and drug products — FEFO is the universal expectation under 21 CFR 211.150 and EU GMP §5.10. FIFO is acceptable only for materials with no assigned shelf life, which is rare.
• Dietary supplements regulated under 21 CFR 111. Botanicals, vitamins and minerals all have potency-loss curves; 111.415 requires storage conditions that prevent deterioration, and FEFO is how the rotation rule operationalises that.
• Food ingredients and finished food. ISO 22000 §8.5 and FSMA require stock rotation; in practice this means FEFO for anything with an issued shelf life, FIFO for non-perishables.
• Lab reagents and analytical standards, where expiry is tied to specification — out-of-spec reagent invalidates the test method.
• Refrigerated and frozen products, where the gap between received-first and expires-first is sometimes weeks because cold-chain history differs between deliveries.
• Cell and gene therapy components, biologics, and short-dated diagnostics — where FEFO is augmented further by individual unit-level tracking.
• Any SKU where the supplier issues a remaining-shelf-life guarantee (e.g. '12 months minimum on delivery'); the customer is implicitly relying on FEFO downstream.

1. Receipt timestamps are day-only. Two lots received on the same day have no defined order; the WMS picks arbitrarily. Fix: capture receipt to the second, and break ties on PO line then on container ID.
2. Mixed-lot pallets at line-side. The operator picks whatever container is on top — usually the most recently moved, which is the newest. Fix: prohibit mixed-lot pallets at the line, or treat them as decomposed into individual lot-tagged units the WMS can still address.
3. Re-received lots take the new receipt date. Returned, repacked or re-tested lots that re-enter inventory with a new receipt date jump the queue. Fix: preserve the original-receipt date as a separate field and sort on it.
4. Cycle counts not regular. Book-and-bin diverge over months; the FIFO lot in the system is not the lot physically in the bin. Fix: cycle-count cadence proportional to lot churn, with reconciliation events that re-anchor receipt dates.
5. ERP-side accounting FIFO assumed but physical movement uncontrolled. Finance reports clean FIFO; warehouse runs by feel. Fix: physical pick audit trail exported to ERP nightly for reconciliation.
6. Multiple receiving doors with separate receipt clocks. Lots from dock 1 and dock 2 received minutes apart may sort wrong because of clock skew. Fix: single canonical receipt timestamp source.
7. FIFO applied to perishables because nobody configured the SKU to FEFO. Silent ageing on the shelf. Fix: SKU-creation workflow forces a rule selection — there is no default; an unselected SKU cannot be received.
8. Override on pick allowed without reason capture. Operator skips the FIFO lot 'because the next one was closer.' No audit trail of why. Fix: every deviation from the system-proposed lot requires a reason from a controlled list, an e-signature, and an entry in the batch record.

Lot-level FIFO is the foundation of forward and backward traceability. When a recall lands — a supplier-side issue on lot X received on date D — the question 'which finished batches did lot X go into?' depends on accurate dispense records that name the lot. If FIFO selects the lot at the kiosk and the operator confirms, the dispense record is authoritative. If FIFO is overridden silently the dispense record is still authoritative for the actual lot picked, but the original FIFO selection that was bypassed is invisible — so the supervisor cannot tell whether the wrong lot was picked deliberately or by error, and the override-reason trending data is corrupted.

The same logic runs the other way. When a customer reports a defect on a finished batch, the backward trace from finished-batch → dispense records → consumed lots → supplier receipts must reconstruct the consumption sequence exactly. Mixed-lot pallets, silent overrides and book-and-bin divergence all degrade this trace. The compliance test is: pick a finished batch at random from twelve months ago, and produce the full dispense list with lot IDs, override reasons and operator e-signatures inside the audit window the regulator allows (typically minutes, not hours). If that test fails, FIFO is not being run as a controlled process; it is being run as folklore.

Accounting FIFO is the cost-flow assumption defined by IAS 2 and FASB ASC 330: when inventory is sold or consumed, the cost relieved is from the earliest layer. In rising-cost periods FIFO reports a lower COGS and a higher ending inventory than LIFO would; in falling-cost periods the reverse. FIFO is permitted under both IFRS and US GAAP; LIFO is permitted under US GAAP only. Most regulated manufacturers use FIFO or weighted-average; LIFO is rare outside specific US industries (oil and gas, some commodity processing) because the operational disconnect is too sharp.

The platform's job is to make accounting FIFO match physical FIFO without manual reconciliation. The mechanism is the dispense event: at the moment of pick the system knows the lot, the received-cost layer, the quantity, the operator, the work order and the override reason. Exporting that event as an accounting transaction (relieve N units from cost layer L, charge to WO W) keeps the two sides aligned in near-real-time. The historical alternative — month-end reconciliation between a WMS report and an ERP cost-layer report — is where most divergences hide; if the reconciliation is a separate ritual rather than a continuous emit, divergences accumulate.

FIFO is not named in regulations; stock rotation is. The regulations require that materials be rotated and that the rotation rule prevent the use of deteriorated material. FIFO is one of two acceptable implementations; FEFO is the other. The auditor's job is to verify that whichever rule is documented is the rule that is actually being run.

• 21 CFR 211.150(a) — pharma distribution procedures must assure 'that the oldest approved stock of a drug product is distributed first.' For raw materials with assigned shelf life, FEFO is the universal interpretation; for materials without assigned shelf life FIFO satisfies the rule.
• 21 CFR 111.415(e) — supplement holding operations must protect against contamination and deterioration; in practice this means FEFO for any component with a potency-loss curve.
• EU GMP Part I, Chapter 5 §5.10 — 'Stocks should be rotated according to the principle of first expiry / first out.' EU has codified FEFO as the default; FIFO is acceptable for materials without expiry.
• ISO 22000:2018 §8.5 — operational PRPs require stock rotation; FEFO for perishables, FIFO acceptable for shelf-stable.
• FSMA 117.80(c) — food manufacturing controls include rotation to prevent contamination; FEFO/FIFO selection is a documented operational control.
• 21 CFR Part 11 / Annex 11 — the pick rule, the proposed lot, the picked lot, the override reason and the e-signature are all audit-trail events with timestamp and signer.
• ICH Q9(R1) — quality risk management. The rule selection per material is a documented risk decision; the override workflow is the controlled exception path.

• FIFO compliance rate — picks where the system-proposed lot was the lot picked ÷ total picks. World-class: 98%+. Below 90% means the override path is being used as the default.
• Override-reason distribution — share of overrides by reason code. A clean distribution means operators are documenting real reasons; a single reason dominating means the reason list is being clicked through.
• Mean inventory age by SKU — older average means the rule is running; consistent ageing means the rule is broken or demand is below replenishment.
• Write-off / expired-stock rate — share of received volume written off due to age. For FIFO SKUs (no expiry) write-off should be near zero; spikes signal mis-classified perishables.
• Book-vs-bin variance at cycle count — divergence between system-of-record lot and physical lot in the bin. Should trend toward zero with a healthy cycle-count cadence.
• Physical-to-accounting reconciliation gap — value of inventory adjustment at month-end attributable to FIFO divergence. Should trend toward zero with continuous emit; persistent gaps mean reconciliation is happening manually.
• Pick cycle time for FIFO vs override picks — overrides usually take longer because the operator must select a reason. Sharp parity means the reason list is being clicked through without thought.
• Audit findings on 211.150 / 111.415 / EU GMP §5.10 stock rotation — mature sites: zero. Any finding here is a structural process gap, not a one-off.

1. SKU creation requires a rule choice. There is no default. The choices are FIFO, FEFO, or FEFO with minimum-remaining-shelf-life policy. A SKU without a rule cannot be received.
2. Receipt captures lot ID, received timestamp to the second, supplier expiry date (mandatory for FEFO SKUs, optional for FIFO), supplier CoA reference and inbound QC status. Receipt clocks across docks are reconciled to a single canonical source.
3. Putaway directs the lot to a bin. Mixed-lot pallets at the line are flagged at putaway with a decompose workflow; pallets that arrive mixed are decomposed to lot-tagged units before line-side.
4. At dispense, the kiosk proposes the lot. For FIFO SKUs the proposal is the oldest receipt with sufficient quantity, in the closest available zone, not on hold. The proposal includes the reasoning ('oldest receipt, zone A, 240 kg available, no hold').
5. If the operator picks the proposed lot the pick is one tap. If the operator deviates, a reason list is presented (customer-required lot, FEFO lot on hold, FEFO lot in distant zone, FEFO lot quantity short, supervisor-directed). A free-text 'other' option is allowed but flagged for review. The override e-signs, the reason lands in the batch record, and the supervisor dashboard surfaces the override for trend review.
6. The dispense event emits to the accounting layer immediately. The cost layer relieved matches the lot picked. The ERP-side cost flow stays aligned with the physical pick without month-end reconciliation.
7. Forensic queries — 'show every override on this SKU in the last 90 days with reason and supervisor sign-off' — run from the audit-trail explorer in seconds, not days.
8. Cycle-count cadence is configurable per SKU class and proportional to lot churn. Reconciliation events re-anchor receipt dates only with sign-off; silent re-receipt date changes are blocked.