FEFO Pick Enforcement: Meaning, Evidence and Controls
A practical guide to deciding which stock can be picked, explaining why it wins, and preserving the evidence behind exceptions.

On this page · 11 sections
- 1What FEFO pick enforcement controls
- 2US regulatory scope: stock age is not expiry order
- 3From demand to confirmed pick
- 4The data needed to explain a selection
- 5Decision matrix: eligibility before expiry ranking
- 6Separate reallocation, substitution and override
- 7Worked cases: show why the selected lot wins
- 8Integrations, concurrent picks and recovery
- 9Retest-controlled stock and other date boundaries
- 10Challenge the rules and their evidence
- 11Implementation and review checklist
How does FEFO Pick Enforcement 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 FEFO pick enforcement controls
FEFO pick enforcement is the application of configured rules at allocation and picking to select the earliest-expiring eligible stock and control departures from that selection.
Eligible comes first: establish which stock can satisfy the particular demand, then compare the applicable expiry dates within that candidate set. Eligibility commonly considers material identity, quality status, accessible location, existing reservations and customer acceptance conditions. An earlier expiry does not make otherwise unsuitable stock selectable.
| Term | Question answered | Boundary at picking |
|---|---|---|
| FEFO principle | Which eligible stock takes priority? | FEFO orders stock by expiry; the principle alone does not control execution. |
| FEFO pick enforcement | Does this selection follow the configured rules? | Applies eligibility and ranking rules to the actual pick and handles departures. |
| FIFO | Which stock entered inventory first? | FIFO pick enforcement follows stock age, not expiry order. |
| Expiry-versus-retest assessment | What does the controlling date mean? | Distinguishes expiry from a retest trigger; date assessment is not authorization to use stock. |
| Quality release | Is stock authorized for its intended use or distribution? | Provides a disposition input; it does not rank eligible lots by expiry. |
This article covers allocation, reservation, physical picking, confirmation and related exception handling. These are separate decision points: reserving a lot does not establish that the same lot was physically picked. Enforcement connects the intended selection to execution through configured checks and exception records. Detailed shelf-life assignment belongs in expiry date management; quality-release procedures remain outside this article’s boundary.
02US regulatory scope: stock age is not expiry order
For US drug products under 21 CFR 211, 21 CFR 211.150 requires written distribution procedures to be established and followed. This is a procedural obligation, not a specification for warehouse software.
For US drug products under 21 CFR 211, 21 CFR 211.150(a) requires a procedure for distributing the oldest approved stock first and permits deviations that are temporary and appropriate. Do not equate that stock-age wording with an earliest-expiration mandate. In operational practice, expiry-driven FEFO uses expiration order; a local procedure should explain how that selection rule relates to stock-age rotation when the orders differ.
For US drug products within the scope of 21 CFR 211.137, 21 CFR 211.137(d) requires expiration dates on labeling in accordance with § 201.17. Keep that labeling duty separate from picking-algorithm design.
| Product and jurisdiction | Authority category | Provision or scope check | Picking-design implication |
|---|---|---|---|
| US drugs | Binding regulation | 211.150(a); 211.137(d), within scope | Separate stock rotation from labeling. |
| US dietary supplements | Product-specific regulation | Check current 21 CFR 111.470 for scope. | Do not transfer the drug provision. |
| Food, devices, chemicals; other jurisdictions | Applicable product and market framework | Check relevant distribution obligations. | Establish the applicable basis locally. |
| Relevant product and market | Official guidance | Distinguish recommendations from binding law. | Identify recommendations separately. |
| Site and order | Local procedures; customer conditions | Document rotation and acceptance rules. | Explain additional eligibility filters. |
| Configured implementation | Software support | Document intended behaviour. | Treat blocking and approval settings as design choices. |
For implementation, distinguish the legal basis from local controls: neither a universal FEFO rule nor a scan-blocking or electronic-signature specification should be attributed to these US drug provisions. Document the rationale for such controls separately.
03From demand to confirmed pick
In a typical FEFO workflow, an order or production demand starts the selection process; it does not itself identify stock that can be picked. The workflow below separates planning, commitment and execution.
| Workflow stage | Business event |
|---|---|
| Demand → candidate retrieval | Identify stock potentially able to satisfy the requested item and quantity. |
| Eligibility screening → expiry ranking → suggested allocation | Exclude ineligible candidates, then propose stock from the ranked eligible set; a suggestion does not commit inventory. |
| Reservation commitment | Commit a quantity against the demand under the site's reservation rules; no physical movement is implied. |
| Physical selection → pick confirmation | Select stock at its location, then record the item, lot and quantity actually moved to the picking destination. |
Configurable decision checkpoints can sit at allocation, reservation commitment, lot or location selection, and final confirmation. Define what each checkpoint rechecks and whether a mismatch warns, blocks or routes an exception. A location scan need not perform the same checks as a lot scan. Competing demands belong in the allocation arbitration design.
At the point of work, show the picker the selected item, lot, location, quantity, relevant restriction and an intelligible exception route: what failed, whom to contact and how to pause safely. Keep task completion separate from authorization for downstream use or distribution. Responsible quality or other designated approvers retain human approval and release decisions; a completed pick merely advances the pick-pack-ship workflow.
- Resolve demandLoad item, quantity, destination and shelf-life policy.
- Capture stateRead quality, location, stock, reservations and policy versions.
- Screen EligibilityExclude candidates failing applicable eligibility gates.
- Rank CandidatesApply expiry ordering and the configured tie-breaker.
- Commit ReservationResolve conflicting commitments before presenting the selection.
- Confirm or routeRecheck relevant changes and route exceptions.
- Record and reconcileRetain inputs, reasons, outcome and downstream acknowledgements.
04The data needed to explain a selection
A practical FEFO data model separates the following input groups. Assign each field an authoritative owner through master data governance; replicated values should retain their originating record and version. These are operational design recommendations, not universal regulatory requirements.
| Input group | Meaningful fields | Suggested authoritative owner |
|---|---|---|
| Item policy | item_id, policy_version, ranking basis, stock unit, date interpretation | Master-data steward; quality approves eligibility rules |
| Lot disposition | lot_id, quality_status, expiry_date, retest_date, disposition version | Quality-controlled lot register |
| Inventory position | location_id, available_qty, quantity unit, inventory version | Warehouse inventory ledger |
| Demand constraints | order_line_id, requested quantity/unit, remaining-shelf-life rule, reference event/date | Order management, using agreed customer requirements |
| Reservation state | reservation_id, reserved quantity/unit, linked demand, reservation version | Allocation service or reservation ledger |
| Decision evidence | decision_at, candidate_snapshot_id, selected quantity/unit, exclusions, input-version references | Pick-decision record custodian |
Define available_qty consistently, including whether reservations are already deducted, to avoid subtracting them twice. Link each lot attribute to its authority rather than treating matching field names as matching meanings.
For customer remaining shelf life, calculate the interval from an explicitly agreed reference event—such as dispatch or planned receipt—to the interpreted expiry boundary. Record the customer rule, reference event and date, calculation units, rounding convention, and date interpretation. Define how date-only values differ from timestamps, including time-zone and boundary treatment; do not assume a universal acceptance threshold.
Missing dates, conflicting date sources, incompatible units and inconsistent location identifiers need explicit routing: for example, suspend allocation for resolution or apply an approved fallback. Unresolved inputs should not silently rank last.
Current master data describes now; the historical decision snapshot describes what the picker’s selection used. Preserve the candidate population, exclusion reasons, selected quantity, policy_version and relevant state versions. candidate_snapshot_id can reference retained inputs or reconstructable versioned records, provided those references remain resolvable. A selected-lot identifier alone cannot explain competing candidates. Corrections should retain the previous value, replacement, author, reason and effective time without rewriting the historical pick inputs.
Pick Policy
Versioned eligibility, ranking and exception configuration.
- item_id
- policy_version
- date_basis
- tie_break_rule_id
- exception_route_id
Lot Disposition
Separate quality decisions, expiry and retest.
- lot_id
- quality_status
- expiry_date
- retest_date
- disposition_version
Stock Position
Location-level quantity and concurrency state.
- lot_id
- location_id
- on_hand_qty
- available_qty
- stock_version
Demand Reservation
Order constraints and committed stock.
- order_line_id
- shelf_life_rule_id
- reference_event_at
- reservation_id
- lot_id
- reserved_qty
- reservation_version
Pick Decision
Historical inputs, selection and exception evidence.
- decision_id
- candidate_snapshot_id
- policy_version
- selected_lot_id
- decision_reason_code
- actor_id
- decision_at
05Decision matrix: eligibility before expiry ranking
A practical FEFO design separates exclusion gates from ranking preferences. Build the candidate set from stock positions that pass every applicable eligibility gate; only then order them by expiry. An earlier date cannot authorize held, incompatible or otherwise ineligible stock. The following is an operational design pattern, not a universal regulatory rule.
| Decision stage | Input | Passing condition | Failure or exception route | Evidence retained |
|---|---|---|---|---|
| Identity gate | Requested item; substitution rules | Exact item or authorized substitute | Exclude; seek substitution authorization | Item match; authorization |
| Quality gate | Current disposition | Status permits intended use | Exclude; quality review | Status and effective version |
| Location gate | Position; access permissions | Position permitted for this pick | Exclude; authorized relocation | Location; permission rule |
| Quantity gate | Free issuable balance plus quantity already reserved to the current demand (counted once); issue unit | Positive quantity issuable to this demand | Exclude empty positions; evaluate shortfall | Balance, own-reservation quantity and calculation |
| Reservation gate | Owner; reserved quantity | Reservation owned by the current demand, or free balance | Stock reserved to other demands excluded pending authorized release | Owner; reservation changes |
| Date gate | Date type; validity; disposition | Applicable date basis valid for use | Exclude ambiguity; quality decision for retest eligibility | Date basis; quality decision |
| Customer gate | Shelf-life rule; reference event | Remaining life meets applicable agreement | Exclude; authorized commercial review | Rule version; calculation inputs |
| Expiry ranking | Eligible stock positions | Earliest applicable expiry first | Later candidate remains lower-ranked | Ordered candidate set |
| Equal-date ties | Secondary and final keys | Documented deterministic ordering | Resolve missing keys | Key values; resulting order |
| Exception classification | Proposed selection; reason | Normal selection or authorized departure | Route by exception category | Reason; decision authority |
| Decision replay | Inputs; rules; selected quantities | Selection reproducible from historical state | Investigate unexplained difference | Snapshot; rule version; outcome |
Evaluate quantity relative to the demand being picked. A position whose whole balance is reserved to this order has no uncommitted balance, yet it remains issuable to this order. Count that own reservation once: if the configured available figure already includes it, do not add it again. A useful test fixture is a position with zero free stock and a reservation equal to the full line quantity for the current demand; the expected result is that the position passes the quantity and reservation gates and is ranked by date like any other eligible candidate.
Current-demand reservations remain available to that demand; another demand’s reservation does not become available merely because its expiry is earlier. Define reservation priority, release authority and reallocation explicitly through allocation arbitration, rather than hiding them inside the expiry sort.
Within eligible equal-expiry stock, use a documented secondary key, such as receipt sequence, followed by a stable unique stock-position identifier. This produces an explainable tie result from identical inputs. For quantity splitting, consume eligible positions in expiry order using the permitted unit of issue. If a unit constraint prevents fulfillment, expose the shortfall rather than silently skipping stock. Splitting the same item across lots is not substitution; changing item identity invokes the substitution rule.
Configure enforcement by decision point: advisory message, required confirmation, blocked action or exception routing. Interlock logic should distinguish an ineligible candidate, an eligible but lower-ranked candidate, insufficient available quantity and an authorized ranking departure. Record the applicable category rather than a generic override. Neither blocking every scan nor obtaining a signature for every override is inherent to FEFO; controls depend on the approved workflow.
06Separate reallocation, substitution and override
As an operational design practice, distinguish four routes. Recalculation reruns selection after inputs change. Reservation replacement releases an existing commitment and assigns another. Substitution replaces the requested item or proposed lot with an authorized alternative. An override deliberately departs from the applicable ranking rule. A changed lot alone does not establish an override; reservation replacement or substitution may still respect that rule.
- Does the original selection remain eligible? If not, remove it from consideration and recalculate using current inputs. Preserve why eligibility changed. If it remains eligible, identify why a different selection is proposed.
- Is the alternative authorized for the affected demand? Check the applicable substitution and reservation permissions. If authorization is absent, stop that route rather than treating availability as permission.
- Does the alternative bypass the applicable ranking rule? If not, record the recalculation, reservation replacement or substitution. If it does, use the configured override route before confirming the departure.
Capture proposed and selected stock identifiers, affected demand, reason code, explanatory context, actor, decision time, policy version and any approval reference called for by the procedure. Specify approval or signature behavior in the configuration specification; neither is inherent to every override.
Keep ranking-override authority separate from quality-disposition authority. Design the route so a generic FEFO override cannot silently change quality status or make ineligible stock selectable.
Structured codes support grouping; narrative explains the particular constraint and why the alternative was chosen. Review repeated generic reasons and unexplained manual selections for hidden rule bypasses. Where prior approval is prescribed, approval after physical picking is not equivalent: preserve the actual sequence and assess it through the applicable deviation process, rather than backdating authorization.
07Worked cases: show why the selected lot wins
These worked cases use fictional lot labels and sealed cartons as the issue unit. Each eligible candidate has enough available cartons to satisfy the whole demand; no split pick is needed. Expiry relationships are explicitly ordered, without calendar dates. Customer shelf-life pass/fail results are evaluated inputs at the agreed reference event, not invented thresholds. Unless stated otherwise, stock is released, accessible, unreserved and satisfies the demand constraints. These are illustrative operating policies, not regulatory requirements.
Protected reservations: Cedar wins
Assume other-order reservations are protected: this demand cannot consume their cartons. Expiry order is Alder before Birch before Cedar before Dogwood. Apply eligibility first, then expiry-driven ranking. A demand-constraint pass below includes the evaluated customer shelf-life condition; it does not cancel a hold or reservation exclusion.
| Lot | Relative expiry order | Quality state | Reservation state | Demand constraints | Decision reason |
|---|---|---|---|---|---|
| Alder | Earliest | Quality hold | Unreserved | Pass | Excluded: quality hold prevents selection. |
| Birch | After Alder | Released | Fully reserved for another order | Pass | Excluded: protected reservation leaves nothing available. |
| Cedar | After Birch | Released | Unreserved | Pass; accessible | Selected: earliest-expiring eligible lot. |
| Dogwood | After Cedar | Released | Unreserved | Pass; accessible | Eligible, but expires later than Cedar. |
Cedar wins without an override. Alder and Birch never enter the eligible ranking; Dogwood enters but loses. Record Dogwood as eligible but not selected, rather than assigning it a false rejection condition. Reserve Cedar’s required cartons against this demand.
Shelf-life eligibility and an equal-expiry tie
Elm expires before Fir and Grove; Fir and Grove share the next expiry. All are released and accessible. Fir already has a valid reservation covering this demand. The stated tie rule prefers an existing same-demand reservation, but only among eligible candidates sharing the earliest eligible expiry.
| Lot | Shelf-life result at agreed reference event | Reservation | Outcome |
|---|---|---|---|
| Elm | Fail | Unreserved | Excluded despite earlier expiry. |
| Fir | Pass | Valid for this demand | Selected by equal-expiry tie rule. |
| Grove | Pass | Unreserved | Eligible; loses tie to Fir. |
Retain Fir’s reservation through confirmation. Its reservation would not rescue a shelf-life failure or give it precedence over an earlier-expiring eligible lot. Capture both the shelf-life result and its reference event so the exclusion of Elm remains explainable.
Changed quality state before confirmation
Return to the Cedar selection. Before confirmation, Cedar changes to quality hold. Under this example’s revalidation policy, stop the original confirmation and recalculate from current state. If Alder remains held, Birch remains protected and Dogwood remains eligible with sufficient quantity, select Dogwood. Remove this demand’s reservation from Cedar, reserve Dogwood and confirm only after its revalidation succeeds. This is reallocation after changed eligibility, not a ranking override: Cedar no longer competes in the eligible set.
Keep the decision replayable
Connect each decision in the process event log: demand identifier and carton quantity; candidate snapshot with expiry relationships, status, location, availability and shelf-life results; policy version; rejected candidates and reasons; eligible losers; selected lot; reservation transition; and final confirmation outcome. For the changed-state case, preserve the original Cedar selection, stopped confirmation and subsequent Dogwood decision as linked events. Reproducing Cedar’s original selection uses its historical inputs and policy. Running the demand against today’s data is a new decision, not a replay.
08Integrations, concurrent picks and recovery
As an operational design practice, map responsibilities across the systems actually used: order constraints, quality disposition, stock position, reservation commitment and physical execution each need a named authority. For MES–ERP integration and MES–WMS integration, define boundary payloads rather than assigning ownership by system label. Exchange order constraints and revisions; lot disposition and effective status; location, quantity and unit; reservation identity and commitment result; and executed lot, quantity and transaction identity.
Reading available stock does not secure it. Another picker may commit that stock before the first request commits. Define how commitment detects changed availability or status, reports an unsuccessful attempt and triggers recalculation against current eligible stock. Do not treat the original selection as a successful reservation. The conflict-control mechanism depends on the implementation.
Use transaction identities to distinguish retries from new movements. Specify duplicate-message handling and status checks after delayed acknowledgements so retries do not double-post. Cancellation handling should establish whether execution has begun; partial completion should distinguish consumed reservation quantity from the outstanding remainder. After disconnection, establish what physically moved and what each system recorded before retrying or cancelling.
Adopt this recovery invariant: reconcile physical movement, inventory balance and reservation state before representing the transaction as complete. Define offline authorization, stale-data tolerance and manual fallback explicitly, including who resolves discrepancies and how temporary records enter the reconciled history.
09Retest-controlled stock and other date boundaries
As an operational control design, keep expiry and retest dates in separate fields. Expiry marks the end of assigned shelf life; retest identifies a point for reassessing eligibility. Neither field substitutes for the other. See expiry versus retest date for the broader distinction.
Route retest-due material to an authorized quality decision before further selection. A passed test, changed calendar date or system calculation is not automatic renewal. Record the decision, its supporting assessment and the resulting eligibility and date basis; preserve the previous values.
Bring retest-controlled material into selection through an approved policy that explicitly identifies its ranking basis. Where candidates have different date types, define separate selection groups or an approved comparison rule. Do not silently sort retest dates alongside expiry dates as equivalent shelf-life endpoints.
For reworked, repacked or returned stock, retain traceable identity, disposition and approved date provenance. Record the relationship to the original stock and the authority for any date change. A handling event alone does not establish a fresh expiry; link returned-stock decisions to the restocking process.
For a temperature excursion or another condition concern, make the resulting disposition control eligibility. Keep unresolved stock outside the eligible pool pending assessment; an unchanged expiry date does not establish acceptability.
10Challenge the rules and their evidence
As a practical validation approach, build a test matrix around the configured decision gates and policy branches. Record assumptions, input state, expected selection or non-selection, expected reason and observed result. Link cases to intended behavior through a CSV traceability matrix.
| Challenge | Expected decision under the test policy |
|---|---|
| Earlier-expiring held stock | Exclude held lot; rank eligible stock. |
| Another demand’s reservation | Exclude protected quantity; explain unavailable stock. |
| Missing date basis | Route to exception; prevent silent fallback. |
| Failed customer remaining shelf life | Exclude failing lot; retain calculation inputs. |
| Equal-expiry lots | Apply documented tie-break; explain winner. |
| Unauthorized substitution | Reject substitution authorization; preserve attempted change. |
Define each fixture’s policy explicitly; these expected decisions are test assumptions, not universal legal rules. Between allocation and confirmation, introduce quality-state updates, stock depletion, reservation conflicts and policy-version changes. Check whether the configured response re-evaluates, suspends or rejects the pick, and detects stale reservations rather than confirming obsolete availability.
Exercise advisory, confirmation and blocking modes separately: verify the warning, required acknowledgement or prevented transaction specified for that branch. Do not judge every configuration against blocking behavior.
Correct master data after a completed test, then replay the original decision using its historical inputs and policy version. Check that corrections leave original evidence intact. Reconcile successful and failed transaction outcomes, including rejected attempts; flag overrides lacking an explanation. Capture mismatches in a validation deviation report, linking each failure to its corrective control and retest result.
11Implementation and review checklist
Use this operational checklist and measurement scheme as practice recommendations, not regulatory thresholds.
- Approve the decision policy; assign field ownership and customer-rule maintenance.
- Document reservation behavior, exception authority and recovery procedures.
- Retain test evidence; name the review owner and follow-up owners.
| Measure | Population and exclusions |
|---|---|
| Eligible-ranking departures | Completed selections with ranked eligible alternatives: count departures; exclude permitted ties and policy-compliant reallocations. |
| Quality-related exclusions | Candidate evaluations: count quality-status rejections; exclude candidates rejected solely for non-quality reasons. |
| Customer shelf-life exclusions | Quality-eligible candidate evaluations: count customer-rule rejections; exclude quality-blocked stock. |
| Reservation conflicts | Reservation attempts: count competing-allocation failures; exclude failures unrelated to reservation ownership. |
| Unexplainable decisions | Confirmed picks: count decisions not reconstructable from retained inputs and policy; exclude cancelled attempts. |
Keep legitimate reallocation outside override counts. Use a consistent review period and counting unit for each measure.
During decision-record review, ask: do repeat reasons indicate bad master data? Assign corrections to field owners. Are reservations released correctly? Assign investigation to operations and system owners. Were policy changes evaluated through change control? Assign impact assessment to quality and system owners; track follow-up to closure.
Frequently asked questions
Q.Why can a later-expiring lot be the correct FEFO pick?+
FEFO ranks eligible stock, not every lot physically present. An earlier-expiring lot may be on quality hold, reserved to another order, in an excluded location, or unsuitable for the requested product configuration. A later-expiring lot can therefore be the earliest eligible choice without an override. The decision record should distinguish each exclusion from the date ranking, rather than merely recording that the selected lot was available. See allocation arbitration for competing demands on stock.
Q.How should a customer shelf-life condition change the selection when the earliest lot is otherwise eligible?+
Treat the agreed customer condition as an order-specific eligibility filter before ranking the remaining lots. Define whether remaining shelf life is assessed at dispatch, expected delivery, or another agreed event; those bases can produce different results. Exclude a lot that fails that condition even if it is otherwise released and available. Record the condition and calculation basis with the allocation. A changed delivery assumption should trigger reassessment under the procedure, not a silent change to expiry data.
Q.What should happen when an earlier-expiring lot becomes available after an order is reserved?+
Apply the defined reservation policy rather than silently replacing the selected lot. A procedure can preserve a valid reservation or rerank eligible stock at a specified checkpoint, such as pick-task release. In either design, a new quality hold or other disqualifying change calls for separate eligibility reassessment. If reranking changes the allocation, retain the previous reservation, the triggering event, and the replacement decision. Coordinate any physical replenishment through the forward-pick and reserve process.
Q.Can retest-controlled material enter the same selection queue as expiry-controlled stock?+
It can share an operational queue only where the procedure preserves the different date meanings and defines a defensible comparison rule. A retest date is not an expiry date, and a new test result should not automatically renew eligibility. For retest-controlled material, selection should depend on a documented quality decision covering its intended use. Preserve the date type, decision reference, and applicable restrictions; do not simply sort both date fields as interchangeable deadlines. See expiry versus retest date.
Q.When is changing the selected lot a reallocation rather than a FEFO override?+
A change is ordinarily a reallocation when the selection rules are reapplied and the replacement is the highest-ranked eligible lot under those rules. Examples include releasing a reservation or excluding stock after a status change. An override deliberately departs from the applicable ranking while an earlier-ranked candidate remains eligible and available. Record the original selection, changed inputs, replacement, and reason so the distinction can be reconstructed. Whether either event also needs a deviation record depends on the governing procedure.
Q.Does FEFO pick enforcement require a hard block at every scan or a signature for every exception?+
As an operational control, FEFO enforcement does not prescribe a single scan or approval design. A control specification can assign warnings, blocks, reallocation paths, and approval steps to different events according to risk and applicable obligations. Distinguish bypassing the date ranking from attempting to use stock that fails eligibility: permission for the former should not authorize the latter. Define who may resolve each exception and what evidence is retained in the configuration specification, rather than assuming every scan behaves identically.
Q.What evidence explains a historical pick after quality status, reservations or expiry data have changed?+
Retain the decision-time inputs, not just the lot's current master record. A useful replay includes the order condition, candidate lots, quantities available after reservations, quality and location status, date values and types, exclusion reasons, tie-break rule, selected quantity, and rule version. Link subsequent corrections to the original decision without overwriting its context. Where a person changed the result, retain the reason and any approval required by the procedure. A process event log can organize this chronology.
Q.Does the US drug provision in 21 CFR 211.150(a) establish a universal FEFO mandate?+
No. For US drug products subject to 21 CFR 211.150(a), the requirement is a procedure whereby the oldest approved stock is distributed first; deviation is permitted if temporary and appropriate. That wording does not establish earliest expiry as the selection key or a universal FEFO rule. Operationally, distinguish stock-age ordering from expiry ordering and document how the applicable procedure resolves conflicts between them. FIFO pick enforcement addresses the stock-age side of that distinction.
Primary sources
Want to see how FEFO Pick Enforcement could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.
