Choosing FIFO or FEFO stock rotation for a real item
Delpack Logistics
October 26, 2026
10 min read
Decide whether receipt order or expiration order controls each eligible lot when the older receipt expires later than a newer batch.
Two batches of the same product are ready to pick. Batch A entered the warehouse first, but its printed expiration date is later. Batch B arrived last week and expires sooner. If the picker follows receipt order, A leaves first. If the picker follows expiration order, B leaves first. Choosing FIFO or FEFO stock rotation requires deciding which of those facts controls selection for this item, then making sure the warehouse can identify and release the correct stock.
FIFO means first in, first out: stock received earlier is selected ahead of stock received later under the defined receipt or aging record. FEFO means first expired, first out: eligible stock with the earliest expiration date is selected first. The two rules often point to the same batch, which can make an untested process look sound. The crossed-date example reveals the difference. The right answer depends on the product’s handling obligation, valid date data, customer requirements, and the system’s ability to enforce the choice. This guide addresses that selection rule, not a broad inventory-accuracy metric or the physical putaway process.
Identify the product obligation before ranking stock
Start with the item and the rules that govern its release. Does the product carry an expiration date, use-by date, retest date, or another controlled date? Must stock have a minimum remaining shelf life when it ships or reaches the customer? Does the supplier, customer, contract, quality program, or applicable regulation set a specific rule? Do not infer one from the fact that the package contains a date. A printed date may have a meaning that needs confirmation, and a product without a controlled expiry may still need rotation to avoid aging in storage.
State the requirement in operational language. For example: “Among eligible lots that satisfy the customer’s remaining-life requirement, select the earliest expiration date.” That is more precise than “use FEFO.” Another item might require the oldest received eligible stock first, with no expiration-based ranking. Eligibility comes before ranking. A batch that is held for quality review, recalled, damaged, or unable to meet the order’s conditions cannot be chosen simply because its receipt or expiry date makes it first in the list.
Record whether the decision applies to each SKU, lot, license plate, or location. A warehouse can say it uses FEFO while its scan workflow cannot distinguish two lots in the same bin. The rule then exists only on paper. Choosing FIFO or FEFO stock rotation begins by tying a specific item and unit of selection to a verifiable obligation.
Know what the receipt date actually represents
For FIFO, the date used to order stock must be defined. It could be the date an item first entered the warehouse, a lot receipt timestamp, or an aging date carried with a license plate. Those are not always interchangeable. A transfer between bins should not necessarily make old stock “new”; a rework or return may need a separate status before it can rejoin available inventory. Define the date field that represents the business’s intended entry order and confirm how it behaves when stock moves.
Receipt date evidence should survive normal warehouse movements. Microsoft’s Dynamics 365 documentation describes a location-aging FIFO strategy that uses aging dates associated with warehouse inventory, including license plates and locations, to find the oldest stock. That is a product-specific implementation example, not a guarantee about every inventory system. In a local process, trace one unit from receipt through relocation and verify that the FIFO ranking still reflects the intended original age.
Check whether the item is tracked at a level fine enough to apply the rule. If a single bin combines physically indistinguishable units from several receipts, a location-level “oldest” label may not prove which unit a picker takes. Separation, labeling, scan controls, or a different pick method may be needed. A rule that sorts system records but cannot direct a person to the corresponding physical stock will not provide reliable rotation.
FIFO can be useful where expiration dates are not available or do not control the item. Microsoft notes that its location-aging FIFO strategy can be especially useful for non-batch-tracked inventory that lacks expiration dates for sorting. That observation does not make FIFO a universal default. The product’s requirements decide whether receipt order is enough.
Use the expiration date that governs FEFO
FEFO needs an accurate, meaningful date tied to the stock being selected. Confirm the date type, its source, and its link to each lot or serial unit. A manufacturing date is not automatically an expiration date. A date entered from a supplier label may need format validation and a check against the physical package. When products are relabeled or retested under an authorized process, record which current date is valid and preserve the earlier value for traceability.
Expiration date ranking applies only after ineligible stock is removed from consideration. A lot that already expired, lacks the customer’s required remaining life, or is under hold should not be released merely because its date is earliest. Microsoft’s Business Central documentation describes FEFO picking as selecting the earliest expiration dates first and explains that settings such as item tracking and strict expiration posting affect the behavior. The local system configuration therefore matters: the letters FEFO on a procedure do not show that the pick transaction enforces it.
Pay attention to ties. Two lots can share an expiration date while differing in receipt date or location. Decide the tie-breaker in advance, provided it does not conflict with the governing requirement. A consistent tie rule can reduce confusion, but it is secondary to eligibility and expiration. If the product has multiple date fields, such as manufacture date and best-before date, document which field drives selection and why. Otherwise, one screen may appear to show “oldest” stock while another shows a different date entirely.
For a lot-controlled item, test the route from the printed date to the electronic lot record and then to the pick confirmation. If the picker can scan the wrong lot and still close the task, the rule is not enforced at the final handoff. Choosing FIFO or FEFO stock rotation requires a usable chain from item label to release decision.
Work the crossed-date example without assuming the answer
Imagine Batch A was received on March 2 and expires on October 30. Batch B arrived on March 15 and expires on September 20. Both batches are otherwise available. Under FIFO, A is first because it entered the warehouse earlier. Under FEFO, B is first because its expiration date comes sooner. The example is deliberately simple; a real order may add minimum remaining-life rules, allocation commitments, quality holds, or lot restrictions.
If the item’s approved process requires FEFO, verify that B still meets the customer’s remaining-life requirement. If it does, B is the first eligible batch by expiry. If it does not, do not ship it just to obey a superficial “earliest date” rule. The order may need another lot, a customer exception under the applicable policy, or a controlled hold. If the approved process requires FIFO and expiry is not a release constraint, A may be the selected batch. If expiry is a release constraint even under FIFO, check that A is eligible before ranking it.
The example also shows why receiving order is a poor proxy for expiration order. The later shipment can contain older product or a shorter-dated production run. A picker who simply takes the front pallet may accidentally follow either rule depending on how putaway placed the stock. Test the intended rule against crossed-date cases in the actual inventory record, then check that the physical pick can follow the result.
Record the chosen lot and the reason. “Batch B picked because it is the earliest eligible expiration date” is auditable. “Batch B was in front” says nothing about policy compliance. If the choice differs from the system suggestion, investigate before shipping rather than treating the override as an ordinary shortcut.
Handle missing date data as a controlled exception
Missing date data can defeat both rotation rules. If a receipt timestamp is missing or was reset during a transfer, FIFO ranking is uncertain. If a lot’s expiration date is absent, FEFO ranking is uncertain. Do not fill the field with a convenient estimate or treat a blank as the newest date without an approved rule. Identify the affected stock, keep it from being selected under a false ranking, and find the source evidence that can establish the correct value.
Possible evidence may include the original receiving record, supplier documentation, physical lot label, production record, or a traceable system history. The appropriate source depends on the item and the date being recovered. A worker should not infer expiry by adding a shelf-life interval to an unverified manufacture date unless an authorized procedure permits that calculation. If the date cannot be established, the quality or inventory owner should decide the item’s status under the applicable policy.
Missing data can be hidden by software behavior. Microsoft’s Business Central FEFO guidance notes that a warehouse pick can still populate a serial or lot number for inventory posted without an expiration date in certain circumstances. That example underscores a practical point: a completed pick does not prove the date-based rule had sound inputs. Review records with blank, implausible, or conflicting dates before relying on FEFO reports.
Fix the upstream cause once found. If suppliers omit lot dates, receiving needs an exception path. If scans allow a lot to be entered without its controlled date, the transaction or validation rule needs attention. If a transfer overwrites aging history, test and repair that mapping. The immediate lot decision and the shared data defect have different owners, but both must be closed for rotation to remain credible.
Configure the physical and system pick to agree
A rotation policy has two parts: the system identifies eligible stock in the correct order, and the worker can select exactly that stock. Check location labels, lot separation, scan prompts, replenishment movement, and pick-confirmation controls. If two lots occupy one pick face, verify that the picker can distinguish them without searching through cases or moving product unsafely. If that is impractical, use a different storage arrangement or selection method.
Test three cases before treating the setup as reliable. First, use a routine pair where earlier receipt and earlier expiry agree. Second, use crossed dates like the A/B example. Third, include a held, expired, or missing-date lot that should not be released. Watch the actual suggested pick and the scan confirmation. A configuration that passes only the easy first case may be applying FIFO while staff believe it is FEFO, or vice versa.
Microsoft’s warehouse documentation describes separate FIFO location-aging and FEFO batch-reservation strategies. Its Business Central guidance also lists conditions for FEFO behavior, including item tracking setup and bin types in certain warehouse configurations. Those details are specific to Microsoft products. The transferable lesson is to validate the real software and physical workflow rather than assuming a strategy name guarantees the outcome.
Consider replenishment too. A reserve lot that should be selected next must reach the active pick position without burying shorter-dated stock or mixing labels. This is not an article about how to perform putaway; it is a check that movement after receipt does not break the selected rotation rule. Keep the same lot identity and date evidence through that move.
Review exceptions and measure whether the rule is working
Rotation exceptions should be visible. Track picks that override the suggested lot, expired or short-dated stock found in available inventory, missing date fields, and cases where the chosen lot cannot be located. Review the cause rather than counting overrides as worker error by default. A bad date import, mixed bin, inaccessible pallet, or customer restriction may be the actual reason.
For an override, retain the item, lot, order, original recommendation, selected lot, reason, and authorized decision where required. If the override was necessary because the first lot was held, update the stock status so the system stops recommending it. If staff repeatedly bypass a physically inaccessible lot, the location arrangement may need correction. This evidence is more useful than a broad stock-accuracy percentage, which can be correct while the wrong lot is shipped.
Revisit the rule when the product changes. A new package may add an expiration date, a customer may set a remaining-life condition, or supplier lot labeling may improve. Conversely, a discontinued date field can make an old FEFO configuration unreliable. Review the specific item’s obligation and data before changing the pick priority; switching system codes across all products to solve one exception can create new errors elsewhere.
Readers exploring adjacent logistics topics can use the driver guide hub , and those considering field roles can review the Fort Wayne driver careers page . For the stock decision itself, the closing question is concrete: can a worker show why this eligible lot was picked ahead of another? Choosing FIFO or FEFO stock rotation is complete when the answer follows the item’s rule, the recorded dates, and the physical unit that leaves the warehouse.
Continue with Delpack
Review the Fort Wayne career overview or contact Delpack with a question about the company.
Topics
Browse Topics
All Guides
346
Job Search, Applications & Offers
79
Role Types & Job Fit
83
Schedules, Policies & Work-Life
40
Route Operations & Performance
91
Logistics & Warehouse Operations
53
Delpack Logistics Delpack Logistics is an Amazon Delivery Service Partner and last-mile logistics company serving the Fort Wayne market. Explore Welcome Meet Delpack Fort Wayne Delivery Driver Careers Driver Resources Contact Delpack Delpack News Legal Terms of Service Privacy Policy SMS status Contact info@delpacklogistics.com 260-306-5806 View market and mailing address © 2026 Delpack Logistics . All rights reserved.