V5 Ultimate
Ultimate
PricingResourcesCompany
English (original)العربيةDeutschΕλληνικάEspañolFrançaisItalianoעברית日本語한국어NederlandsPolskiPortuguêsSvenska
Talk to us Log in Start free trial
Food & Beverage
  • Bakery & Confectionery
  • Food Processing
  • Ingredients & Dry Mixes
  • Sausage & Meat Products
  • Produce Packing
  • Pet Food & Pet Supplements
  • Dairy & Chilled Foods
  • Beverages & Liquid Manufacturing
  • Infant Formula
Pharma & Life Sciences
  • Radiopharmaceuticals
  • Pharmaceutical
  • Medical Devices
  • Veterinary Pharmaceuticals
  • Blood & Tissue
  • Diagnostics & IVD Kits
  • Reference Materials & Standards
  • OTC Topical Creams & Gels
Supplements & Personal Care
  • Dietary Supplements
  • Cosmetics & Personal Care
  • Cannabis & Hemp Manufacturing
  • Fragrances & Perfumery
  • Soaps & Personal Hygiene
  • Botanical Extracts & Essential Oils
Chemicals & Materials
  • Plastics & Resins
  • Agricultural Chemicals
  • Specialty & Industrial Chemicals
  • Printing Inks, Pigments & Construction Chemicals
  • Lubricants & Metalworking Fluids
  • Coatings, Adhesives & Sealants
Other Manufacturing
  • Consumer Products
  • Electronics & Electrical Assembly
  • Textiles & Nonwoven
  • Contract Manufacturing & Co-Packing
  • Packaging & Food-Contact Materials
  • Regulated Warehousing & Distribution
Explore all industries
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Why V5? Product & Features
Why V5?Product & Features
  • Warehouse & TraceabilityReceive, store, pick and trace
  • Production & PlanningPlan jobs and guide production
  • Quality & LaboratoryTest, investigate and review
  • Documents & TrainingControl procedures and qualifications
  • Equipment & PerformanceMaintain assets and measure losses
  • Orders & IntegrationsConnect customers, suppliers and systems
  • Outputs & InsightsReports, KPIs and label design
Explore all industries
    • Bakery & Confectionery
    • Food Processing
    • Ingredients & Dry Mixes
    • Sausage & Meat Products
    • Produce Packing
    • Pet Food & Pet Supplements
    • Dairy & Chilled Foods
    • Beverages & Liquid Manufacturing
    • Infant Formula
    • Radiopharmaceuticals
    • Pharmaceutical
    • Medical Devices
    • Veterinary Pharmaceuticals
    • Blood & Tissue
    • Diagnostics & IVD Kits
    • Reference Materials & Standards
    • OTC Topical Creams & Gels
    • Dietary Supplements
    • Cosmetics & Personal Care
    • Cannabis & Hemp Manufacturing
    • Fragrances & Perfumery
    • Soaps & Personal Hygiene
    • Botanical Extracts & Essential Oils
    • Plastics & Resins
    • Agricultural Chemicals
    • Specialty & Industrial Chemicals
    • Printing Inks, Pigments & Construction Chemicals
    • Lubricants & Metalworking Fluids
    • Coatings, Adhesives & Sealants
    • Consumer Products
    • Electronics & Electrical Assembly
    • Textiles & Nonwoven
    • Contract Manufacturing & Co-Packing
    • Packaging & Food-Contact Materials
    • Regulated Warehousing & Distribution
PricingResourcesCompany
Start free trial Log in Talk to us
HomeGlossaryFEFO
Inventory & traceability · The complete guide

FEFO (First Expired, First Out): Meaning, Rules and 21 CFR 211.150

In short

FEFO (First Expired, First Out) is a stock-rotation rule that selects eligible stock with the earliest expiry date first.

4,093 words · ~19 min read
FEFO stock picking: a warehouse worker in PPE scans an ingredient container at the front of an organised storage shelf
First Expired, First Out (FEFO) means selecting eligible stock with the earliest expiry, not simply the front container.
On this page
  1. 01What FEFO means—and what it does not decide
  2. 02FEFO vs FIFO: one order, two different picks
  3. 03When expiry-led rotation is the right policy
  4. 0421 CFR 211.150 and EU GDP: wording and scope
  5. 05From receiving to dispatch: the picking lifecycle
  6. 06Overrides: ineligibility is not the same as bypass
  7. 07Records that reconstruct selection and distribution
  8. 08Cold chain: temperature status before expiry ranking
  9. 09ERP, warehouse and quality-system handoffs
  10. 10Seven FEFO failure modes and targeted controls
  11. 11Measure selection behaviour, not just write-offs
  12. 12An implementation and review checklist
On this page · 12 sections
  1. 1What FEFO means—and what it does not decide
  2. 2FEFO vs FIFO: one order, two different picks
  3. 3When expiry-led rotation is the right policy
  4. 421 CFR 211.150 and EU GDP: wording and scope
  5. 5From receiving to dispatch: the picking lifecycle
  6. 6Overrides: ineligibility is not the same as bypass
  7. 7Records that reconstruct selection and distribution
  8. 8Cold chain: temperature status before expiry ranking
  9. 9ERP, warehouse and quality-system handoffs
  10. 10Seven FEFO failure modes and targeted controls
  11. 11Measure selection behaviour, not just write-offs
  12. 12An implementation and review checklist
AI · Explain it for MY operation

How does FEFO 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.

Your scale

01What FEFO means—and what it does not decide

FEFO (First Expired, First Out) is a stock-rotation convention that selects eligible stock with the earliest expiry date first. The phrase “first expired” names the ordering convention; it is not an instruction to distribute stock that has already expired. In operational terms, the question is which eligible lot reaches its expiry date soonest—not which lot has already passed it.

Eligible stock is the candidate population established by the site's documented selection policy. That policy determines which stock may enter the selection process; FEFO then ranks the candidates. This is an operational definition, not a universal legal rule for every product or warehouse.

The boundary matters: ranking cannot approve a lot, reverse a hold, extend an expiry date or substitute for an authorised person's disposition. Keep stock sequencing separate from batch release. A lot's position at the front of a pick list answers an ordering question, not whether that lot is acceptable for distribution.

Expiry is the primary FEFO ranking key. It is distinct from the receipt date, manufacturing date and approval date: those describe arrival, production and approval events, respectively. Expiry date management should preserve that distinction so the selection policy uses the intended lot date rather than treating these different events as interchangeable measures of stock age.

02FEFO vs FIFO: one order, two different picks

FEFO, FIFO and LIFO are stock-selection conventions, not interchangeable regulatory requirements. Their difference is the ranking key: expiry date or entry sequence. For this comparison, FIFO’s entry event is warehouse receipt, so “first in” means first received—not first manufactured or first to expire.

Rotation rulePrimary ranking keyWhat the rule does not establish
FEFOExpiry date: earliest expiry firstWhich lot entered stock first
FIFODefined entry sequence: earliest receipt first in this exampleWhich lot expires first
LIFODefined entry sequence: most recent entry firstWhich lot expires first

Worked case 1: a 100-carton order

Assume two eligible lots of the same product, interchangeable cartons, no existing reservations and an order for 100 cartons. Selection takes place before either lot expires. All quantities below are cartons.

LotReceivedExpiresAvailable
A2 January 202730 September 202780
B9 January 202731 July 202760
  • FEFO selects B first because it expires earlier: 60 from B + 40 from A = 100 cartons. Remaining stock: A has 40; B has 0.
  • Receipt-based FIFO selects A first because it arrived earlier: 80 from A + 20 from B = 100 cartons. Remaining stock: A has 0; B has 40.

Both rules fulfil exactly 100 cartons and leave 40 cartons in stock. They select different lot quantities because receipt order and expiry order diverge: the later receipt, B, has the earlier expiry. The example demonstrates a selection difference, not a measured reduction in waste, write-offs or recalls.

For a warehouse comparison, check the dates that drive expiry-led selection against the entry event used for FIFO pick enforcement. In this case, changing the ranking key changes the pick even though the product, eligible stock and order quantity stay the same.

03When expiry-led rotation is the right policy

Use expiry-driven FEFO where expiry order provides a useful basis for selecting stock. Before adopting it, assess four implementation criteria—not statutory prerequisites:

  • Meaningful lot-level expiry: the date belongs to the lot being selected and has a defined meaning for its use.
  • Comparable stock: the candidate lots can serve the same demand; do not rank unlike materials or presentations together merely because they have dates.
  • Defined eligibility: a documented policy identifies which stock may enter the selection pool.
  • Operational purpose: consuming earlier-expiring stock first addresses a stated need, such as reducing stock left unused at expiry.

For pharma, supplements, food, devices and chemicals operations, make this assessment by product and workflow. Treat the chosen rotation policy separately from applicable product, jurisdiction and customer requirements. Check the current product-specific rules before adopting or changing the policy; these sector labels are not a basis for applying one pharmaceutical rule across every operation.

Keep expiry_date, retest_date and other labelled date concepts in distinct fields where used. The expiry versus retest date distinction should remain visible in the selection design. Establish an explicit policy before using any non-expiry date as a ranking key, and name that policy accurately rather than silently calling every date-based sequence FEFO.

0421 CFR 211.150 and EU GDP: wording and scope

For US drug-product distribution, the introduction to 21 CFR 211.150 states: “Written procedures shall be established, and followed, describing the distribution of drug products. They shall include:” The stock-rotation wording below belongs within that written-procedure requirement. It should not be replaced with the shorthand “FEFO required.” For broader context, see 21 CFR 211.

Jurisdiction and product contextAuthority typeStated wordingOperational boundary
US drug-product distributionBinding regulation: 21 CFR 211.150(a)“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.”“Oldest approved stock” and “earliest expiry date” are different expressions. This provision does not state an explicit expiry-ranking algorithm.
US components, drug product containers and closuresBinding regulation: 21 CFR 211.86“Components, drug product containers, and closures approved for use shall be rotated so that the oldest approved stock is used first.”Addresses approved materials used in manufacture, rather than finished-product distribution.
EU medicines distributionOfficial guidance: EMA GDP overview, stock-turnover bullet“an adequate turnover of stored medicines takes place;”An official stock-turnover statement, not a quotation of a detailed FEFO algorithm.
Ingredients used in medicines productionOfficial guidance: EMA GDP overview, paragraph beginning “GDP also applies”“GDP also applies to the sourcing, storage and transportation of active pharmaceutical ingredients and other ingredients used in the production of the medicines.”Identifies ingredient scope; this sentence does not specify an additional rotation rule.

The EMA overview and a site's operating policy serve different purposes. The overview supplies the quoted turnover expectation and ingredient scope; the site policy specifies how expiry-led selection will operate. Keep that distinction visible when describing EU GDP, rather than attributing local sorting rules, tie-breakers or exception fields to the overview.

Recommended site controls—not additional quoted requirements

A practical distribution procedure should explain how the site's FEFO policy relates to oldest-approved-stock sequencing, especially where the two produce different selections. Define the date fields used, identify who can authorise an exception, and document its reason and temporary scope. These are recommended implementation controls, not a claim that paragraph (a) prescribes those particular fields or an approval workflow.

For GDP deviation management, keep the regulatory wording separate from the site's supporting justification and authorisation process. Do not borrow laboratory-control or production-deviation requirements merely because they also discuss deviations. If a separate obligation governs a particular activity, identify that provision and its scope explicitly. This keeps the procedure precise: the legal wording remains intact, while the operating controls explain how authorised people apply and review the site's policy.

05From receiving to dispatch: the picking lifecycle

Use the following as a proposed operating design, not a universally mandated field list. Its purpose is to turn trustworthy lot information into a controlled physical pick, then close the transaction against dispatched and remaining stock.

  1. Receive and identify. Capture product, lot, quantity, unit of measure, storage location and labelled expiry. Resolve unreadable or inconsistent date information before using it as a ranking key; do not let a guessed date determine selection. Maintain the location-to-lot relationship through bin-level lot genealogy.
  2. Build the eligible candidate set. Apply the recorded disposition, product identity, available quantity and order-specific eligibility before sorting. A lot outside this set should not become selectable merely because its expiry is earlier.
  3. Rank deterministically. Sort eligible candidates by earliest expiry. Equal expiry dates belong to the same primary ranking cohort; use a documented tie-breaker, such as receipt timestamp followed by lot identifier, to make the resulting selection reproducible.
  4. Reserve and present. Configure the warehouse system to reserve the selected quantity and present the expected lot to the picker. Keep the allocation explicit rather than displaying only a product-level instruction that leaves lot choice open.
  5. Check the physical pick. Compare the scanned lot with the allocation. For FEFO pick enforcement, configure a mismatch to stop the transaction or route it for resolution—not silently replace the allocated lot.
  6. Recheck and confirm. Re-evaluate eligibility before confirmation when relevant status changes occur. Confirm the actual picked quantities against the allocation; do not assume that an earlier reservation establishes continuing eligibility.
  7. Dispatch and reconcile. Link the confirmed dispatched quantities and lots to their destination, then reconcile remaining stock and outstanding reservations. Keep any unresolved quantity difference visible for investigation rather than treating the planned pick as the completed movement.

This diagram summarises the proposed lifecycle; it does not represent automatic approval or release. Disposition and release decisions remain with authorised people.

A proposed FEFO picking workflow
  1. 1
    ReceiveRecord lot, quantity, location and labelled expiry.
  2. 2
    Confirm statusApply the disposition recorded by authorised personnel.
  3. 3
    Build candidatesFilter by product, availability and order-specific eligibility.
  4. 4
    RankSort by expiry, then the defined tie-breaker.
  5. 5
    Resolve exceptionsRoute departures for a bounded, authorised decision.
  6. 6
    Confirm pickMatch the scanned lot and quantity to allocation.
  7. 7
    Record dispatchLink shipped lots and destinations; reconcile remaining stock.
Eligibility precedes ranking; authorised people retain disposition and exception decisions.

06Overrides: ineligibility is not the same as bypass

Worked case 2: customer shelf life changes eligibility

Assume both lots are otherwise eligible, each contains 10 cartons, and the order is for 10 cartons. At planned delivery, lot A has 45 calendar days remaining and lot B has 90. The customer's agreed minimum is 60 calendar days: A is 60 − 45 = 15 days short; B exceeds the minimum by 90 − 60 = 30 days. Selecting 10 cartons from B is selection from the eligible set, not bypassing an eligible earlier-expiring lot. The 60-day threshold is hypothetical, not a regulatory limit.

Record departures without removing safeguards

For the site's rotation procedure, define a genuine bypass as choosing a later-expiring lot while an earlier-expiring candidate remains eligible under the same policy. Classify that departure separately from eligibility filtering so that routine customer restrictions do not obscure actual overrides.

A proposed exception record, linked to the site's applicable deviation-management process, should contain:

  • Affected order and lots.
  • Reason for departing from the selection policy.
  • Decision-maker and authorised scope.
  • Validity boundary, such as the named order or a defined period.
  • Resulting selection.

As proposed SOP controls, use documented justification, bounded authorisation by an authorised person and follow-up exception-based review. These controls are distinct from the regulatory wording covered above, not additional words in 211.150(a). The exception mechanism should not itself erase the eligibility restrictions established earlier: permission to change ranking is not permission to make restricted stock eligible.

07Records that reconstruct selection and distribution

For drug products, 21 CFR 211.150(b) requires: "A system by which the distribution of each lot of drug product can be readily determined to facilitate its recall if necessary." This binding provision does not prescribe a particular database schema.

Separately, the EMA GDP overview's tracing paragraph states: "The distributor should also put in place a tracing system to enable finding faulty products and an effective recall procedure." This is a guidance statement, not a prescribed FEFO decision-record format.

A proposed six-entity record model

Use these linked entities as an implementation design, not a regulatory field list. Field names are illustrative. Retain quantity units wherever quantities are recorded, including requested, available, selected and shipped quantities.

EntitySuggested relationship and fields
Product lotlot_id identifies product and lot; links to stock positions.
Stock positionposition_id links lot_id to location, quantity and unit.
Order lineorder_line_id identifies requested product, quantity and unit.
Pick decisiondecision_id links order_line_id to selected positions, quantities and units.
Exceptionexception_id links decision_id to a departure reason and authorised person's approval.
Shipment allocationallocation_id connects decision_id, lot_id and order_line_id to shipment, destination, shipped quantity and unit.

Two different evidence questions

"Where did this lot go?" is the distribution question supporting recall readiness. The proposed shipment allocation connects each dispatched quantity to its lot and destination; multiple allocations can explain a split shipment or an order fulfilled from several lots.

"Why was this lot chosen then?" needs decision-time context. Preserve the applicable policy version, candidate ranking, exclusion reasons and relevant status snapshot with the pick decision. Link that record to bin-level lot genealogy where location history matters. Today's inventory balance alone cannot explain which alternatives were available or excluded at selection time. These are recommended reconstruction records, not a universal statutory field list.

A proposed selection and distribution model

Product Lot

Lot identity, expiry and disposition.

  • lot_id
  • product_id
  • expiry_date
  • quality_status

Stock Position

Available inventory at a location.

  • position_id
  • lot_id
  • location_id
  • available_quantity
  • unit

Order Line

Demand and customer eligibility.

  • order_line_id
  • product_id
  • requested_quantity
  • unit
  • min_shelf_life_days

Pick Decision

Selection and contemporaneous ranking.

  • decision_id
  • order_line_id
  • position_id
  • selected_quantity
  • unit
  • policy_version

Exception

Reason and bounded authorisation.

  • exception_id
  • decision_id
  • reason
  • approved_by
  • valid_until

Shipment Allocation

Shipped quantity and destination.

  • allocation_id
  • decision_id
  • order_line_id
  • lot_id
  • destination
  • shipped_quantity
  • unit
Illustrative records connect stock, selection, authorisation and shipment; identifiers match the table above.

08Cold chain: temperature status before expiry ranking

For drug products subject to US drug CGMP requirements, 21 CFR 211.142(b) requires storage under appropriate conditions of temperature, humidity and light so that identity, strength, quality and purity are not affected.

Worked case 3: held stock stays outside the allocation

Assume the site's operating policy excludes stock placed on hold pending a temperature-excursion assessment. Quantities are measured in cartons. The earliest-expiring lot contains 30 cartons and is on hold; the next eligible lot contains 50 cartons. The order requires 40 cartons.

Allocate all 40 cartons from the eligible lot: 50 − 40 = 10 cartons remain there. All 30 held cartons remain outside the candidate set. Under this assumed policy, the allocation reflects an eligibility filter, not a discretionary bypass of eligible earlier-expiring stock. The example assumes no temperature threshold, excursion duration or assessment outcome.

Connect the event to its disposition

As an operational control, link the temperature-monitoring event to the affected inventory and the authorised disposition record. Keep the event, inventory hold and assessment decision distinguishable so reviewers can follow what happened to the affected cartons. A sensor event, elapsed time or FEFO ranking should not itself be treated as the disposition or as an instruction to return held stock to the picking pool.

09ERP, warehouse and quality-system handoffs

Treat FEFO integration as an authority agreement, not simply a data feed. ERP, warehouse and quality systems are possible participants—not a required architecture. The following proposed ownership model assigns one accountable owner and authoritative record to each selection-critical field.

DataProposed accountable ownerPossible authoritative record
Lot identityMaster-data teamERP lot master
ExpiryQualityApproved lot record
DispositionQualityQuality-system status record
Available quantityWarehouse inventory controlWarehouse inventory ledger
ReservationsOrder-allocation teamOne designated allocation ledger
Customer shelf-life rulesCommercial order managementERP customer/order rules

Document who may change each field and how downstream copies receive updates. Keep reservation ownership explicit across warehouse integration boundaries: two systems should not independently promise the same quantity.

For message handling, use unique event identifiers to detect duplicates and per-record versions to detect stale or out-of-order updates. Track acknowledgements and pending events to expose delayed delivery. Ignore already-applied duplicates; investigate version gaps rather than letting arrival order determine the current record. When an expiry or status change affects a reservation, route it for re-evaluation and flag conflicting copies until reconciled. These are data-integrity design controls, not release decisions.

Example outage recovery design—not a universal legal requirement: pause affected work, identify orders touched during the interruption, reconcile physical picks against recorded movements, and resolve disputed inventory. Obtain the required human decisions under site procedures before resuming the normal queue; reconnecting an interface alone is not the recovery acceptance criterion.

10Seven FEFO failure modes and targeted controls

Use this diagnostic table to investigate unexpected FEFO selections. The controls are implementation recommendations, not regulatory requirements, an inspector-mandated checklist or claims about how frequently these failures occur. Start with the observable symptom rather than assuming the expiry-ranking rule itself is wrong.

Failure modeObservable symptomTargeted control
Missing or malformed expiryStock cannot be ranked by expiry, or its date fails parsing.Route affected stock records for data review; do not silently assign a default expiry.
Stale disposition messagesConnected systems show inconsistent candidate sets for the same selection.Monitor event age and sequence at the disposition handoff; investigate delayed or out-of-order updates.
Incompatible quantity unitsAllocated quantities differ when expressed in cases versus individual units.Check the configured unit conversion at the transaction boundary, including the units on both sides.
Ambiguous pallet identityThe physical pallet cannot be matched unambiguously to the selected lot.Reconcile physical labels with inventory identity before confirming the selection.
Stale reservationsEarlier-expiring stock remains reserved while later-expiring stock is allocated.Review aged reservations and resolve obsolete commitments through the designated reservation process.
Manual substitutionConfirmed picks differ from shipment allocations without a linked explanation.Compare confirmed scans with shipment allocations and investigate unmatched substitutions.
Inconsistent site configurationsIdentical inputs produce different rankings at different sites.Compare policy versions using a shared test set; distinguish intended local rules from configuration drift.

Use FEFO pick enforcement when investigating selection mismatches and MES–QMS integration when investigating disposition handoffs. Keep diagnostic ownership specific: identify the affected record, message, conversion or configuration rather than recording only “FEFO failed.”

11Measure selection behaviour, not just write-offs

Use a proposed operational metric to assess FEFO pick enforcement, not as an agency-defined compliance measure:

FEFO-conforming pick rate (%) = (confirmed pick decisions whose complete allocation conforms ÷ all confirmed decisions evaluated) × 100. The unit is the whole pick decision, and conformity is quantity-aware: walk the eligible candidates in expiry order and check that the allocation takes the available quantity of each earlier cohort before taking anything from a later one.

Equal-expiry lots form one cohort, so selecting any eligible lot within it conforms. A decision that draws from a later cohort conforms only when every earlier cohort was exhausted at decision time. Publish the denominator and exclusions alongside the percentage so readers can see which decisions the rate represents.

Worked comparison: an order line needs 100 cartons. Lot B (earliest expiry) has 60 eligible cartons and lot A (next expiry) has 400. Allocating 60 from B and 40 from A conforms, because B was exhausted before A was used. Allocating 50 from B and 50 from A does not conform, even though B was touched, because 10 eligible B cartons were left while later-expiry stock was taken. Allocating 100 from A without an authorised bypass also does not conform.

  • Report authorised bypasses separately; permission to depart does not make a later-expiry selection conforming.
  • Report unauthorised substitutions separately from authorised bypasses.
  • Report decisions with insufficient ranking data separately, making their exclusion from the rate explicit rather than treating them as successful picks.

Review results by policy version or operation before combining them. The example rules in this article are not universal benchmarks.

Expiry write-offs measure inventory lost to expiry; remaining shelf life at dispatch measures time left when goods leave. Neither answers whether selection followed the eligible expiry ranking. A high picking score does not prove legal compliance or predict a particular financial result.

12An implementation and review checklist

Use this practical acceptance checklist alongside the earlier operational explanations.

  • Approve policy scope and owner.
  • Document date-field meanings, eligibility inputs and deterministic ranking.
  • Name human exception authorities.
  • Link selection decisions and shipment records for recall readiness.
  • Define integration recovery and metric denominators.

Test normal picks, equal expiries, missing dates, partial quantities, changed dispositions, simultaneous reservations and interrupted interfaces. Record expected and actual selections and the authorised review outcome; document discrepancies in a configuration test deviation report. Passing does not certify compliance.

Edge-case policy decisions (month-only dates, mixed pallets, returns, retesting, cross-site candidate scope, shortages, policy comparison and late holds) are answered in the FAQs below; record the site's approved answer to each as an acceptance criterion before go-live.

Cover of The Regulated Warehousing & Distribution Guide
For regulated warehousing & distribution

Putting FEFO into practice

It shows how expiry-first picking, quarantine status and lot holds work in a regulated warehouse.

The Regulated Warehousing & Distribution Guide · 24-page guide

Get the guide See the industry page

Frequently asked questions

Q.What should happen when no eligible lot meets the customer's remaining shelf-life requirement?+

Treat the order as a fulfilment exception rather than silently relaxing the shelf-life filter. A practical procedure is to confirm the customer's requirement, its reference point—dispatch or expected delivery—and the dates used in the calculation. Then seek suitable replenishment, propose a revised delivery, or obtain an authorised agreement to change the commercial requirement where permitted. Record the decision before reallocating. Expiry-driven FEFO should rank eligible stock; it should not conceal an unmet order condition.

Q.How should a pallet containing several lots or expiry dates be represented during picking?+

Represent the pallet as a handling unit containing separately identifiable stock lines, rather than assigning one convenient expiry date to its entire contents. Each line should retain its lot, quantity, expiry information and eligibility status. For partial picks, specify which line and quantity the picker must take, then update the remainder. This recommended design keeps the relevant lot attributes visible and preserves bin-level lot genealogy when stock is split, moved or consolidated.

Q.What should be checked before returned stock re-enters the selection queue?+

For drug products subject to 21 CFR 211.204, returned products must be identified as such and held. As a practical return-to-stock review, reconcile identity and quantity, assess storage and transport history, inspect product and packaging condition, and confirm the authorised disposition. Relevant cold-chain records can inform that assessment. Keep queue eligibility separate from physical receipt: receipt alone should not reverse a hold or substitute for an authorised batch-release decision.

Q.How should a month-and-year expiry label be represented without inventing an unsupported day?+

Preserve the labelled month and year and record that the date has month-level precision. If software requires a complete calendar date, use a documented interpretation approved for the applicable product and market; do not let a default silently become the authoritative expiry. Where the interpretation is unresolved, flag the stock for review rather than making a day-specific shelf-life promise. A practical expiry date management design retains both the original label value and any derived selection value.

Q.Should a local warehouse select stock from another site solely because it expires sooner?+

Not solely on that basis. A practical selection policy first defines the eligible fulfilment locations, then applies expiry ranking within that scope. Consider whether a transfer is authorised and feasible, whether transport conditions can be maintained, and whether the stock can arrive with the required remaining shelf life. If central planning chooses an intersite transfer, record it as a separate fulfilment decision. Pick-pack-ship instructions should identify the actual dispatch location, not merely the earliest date across the network.

Q.How should a retest result be handled when the lot also has a recorded expiry date?+

Keep the retest result and the recorded expiry as separate controlled information. As a conservative operating practice, a passing retest should not automatically overwrite the expiry or restore picking eligibility. Route any proposed dating change to authorised personnel under the applicable material procedure, retaining the decision and its basis. Configure the selection rule to use the approved date and status rather than whichever date is later. The expiry-versus-retest distinction is useful when defining those separate fields.

Q.How can a spreadsheet and a warehouse system be tested for equivalent lot-selection decisions?+

Use a controlled test dataset and an independently approved expected result for each case. Include different receipt and expiry orders, tied expiry dates, held stock, insufficient shelf life, partial quantities, missing dates and location restrictions. Feed identical inputs and selection rules into both tools, then compare selected lots, quantities, exclusions and tie-breaking results. Agreement alone is insufficient if both implement the same mistake. This practical test connects FEFO pick enforcement with data integrity by design.

Q.What should happen when a hold or recall instruction arrives after allocation but before dispatch?+

A practical workflow should stop affected stock from progressing to dispatch and identify allocations, picked containers and staged shipments that contain it. Preserve the original allocation history, apply the instruction through an authorised process, and reconcile the physical stock with its recorded status. Reallocate only from stock that remains eligible; do not treat an earlier reservation as permission to ship. Linking recall readiness to perpetual inventory helps define where those status changes and quantity movements must be reconciled.

Primary sources

  • eCFR 21 CFR Part 211
  • EMA: Good distribution practice

Explore this topic

FEFO sits inside 2 overlapping topic clusters in our glossary. Every neighbour is one click away.

Identification, Traceability & EDI
13 related entries

GS1 identifiers, barcodes, ASNs and the rules that require lot-level traceability.

GTINSSCCGS1-128UDIEDI 856DSCSAFSMA 204KDECTEFIFOISO 13485Supplier Risk ManagementSupply Chain Risk Management
Planning & MRP
17 related entries

Material requirements planning, BOM explosion, net requirements, scheduling and demand signals that drive what the floor makes next.

MRPMRP IIBOMBOM ExplosionPhantom BOM ExplosionNet RequirementsRoutingWOBackward SchedulingForward SchedulingFinite Capacity SchedulingDemand ForecastingEconomic Order Quantity (EOQ)Days of Supply (DOS)Fill RateBackflush ConsumptionFIFO
Talk to us about FEFO

Want to see how FEFO could fit into your own records and workflows? Explore the related V5 pages or talk to our team about what applies to your operation.

Start free
Back to glossary
Where this term comes up
Regulated Warehousing
Inside V5
  • → Score your compliance gap — then download the validation pack.
  • → Document control — one version in force, every change signed and explained.
  • → QMS — quality records next to the work they concern.
Related terms
  • → FIFO
  • → GTIN
  • → SSCC
  • → GS1-128
  • → UDI
  • → EDI 856
  • → DSCSA
  • → FSMA 204
  • → KDE
  • → CTE
  • → ISO 13485
  • → Supplier Risk Management
  • → Supply Chain Risk Management
  • → MRP
  • → MRP II

Next Step

Try V5 with your own records, or ask a question first. Ask V5 opens with an editable question; nothing is sent until you choose to.

Start your free trial Browse All Features

Showing the site for the United States. Local spelling, dates and prices are applied automatically; change the language at the top of the page.

V5 Ultimate
Ultimate

Warehouse, quality and manufacturing software for regulated operations.

ProductIndustriesPricingResourcesSecurity & TrustCompanyLegal Centre

© S.G. Systems, LLC