Warehouse Operations Guide

FEFO vs. FIFO: Lot and Expiration Control for 3PL Warehouses

Choose the lots that can fulfill the order before you decide which one to pick first. FIFO sends the earliest received eligible stock first, using the receipt event your team has agreed to record. FEFO sends the eligible lot with the earliest applicable expiration or other approved reference date first. Both methods depend on the same initial checks for ownership, item identity, inventory status and the customer's requirements. Stock that has passed its applicable shipping cutoff stays out of the pick list.

Consider a warehouse with two lots of the same shelf-stable product. The pallet received last week might expire before the pallet received two weeks ago. Add a buyer who requires three weeks of remaining shelf life at delivery, and the pick can change again. This guide covers physical fulfillment of ambient, prepackaged goods for U.S. third-party logistics providers (3PLs) and their food, beauty and household goods clients. Accounting FIFO concerns inventory cost. Pharmaceutical distribution, cold chain and formal recalls follow their own procedures.

A warehouse worker checks the date area on a plain carton beside two separated bins of matching products.
Verify the lot on the goods before releasing them to picking.

What is the difference between FIFO and FEFO?

Use receipt order for FIFO. Use the applicable date for FEFO. Write down the receipt event that governs FIFO, especially when a transfer between sites or a return can create a new transaction. A bin move changes location. Keep the original receipt information unless the approved policy defines a different receipt event for that stock. For FEFO, use the reference date agreed for the product and order. If the rule uses an expiration date, an earlier eligible expiration wins. FEFO can deliberately send a lot with less remaining shelf life than another eligible lot.

CheckFIFOFEFO
Primary sortOldest agreed receipt firstEarliest applicable date first
DataReceipt event, owner, item, stock status; other order fields when requiredSame identity and eligibility checks, plus verified date type and value
Typical fitStock managed by receipt orderDate-sensitive stock with differing verified dates
Main riskNew receipt can expire before an old receiptWrong or ambiguous dates can lead to the wrong pick
ExceptionPreserve receipt history, hold failed checksExclude failed or unknown lots and apply an agreed tie breaker

Choose a method that fits the agreement and the data you have. A brand can use FIFO for a SKU whose age is managed by receipt order while applying a separate date gate where relevant. For a SKU with varying expiration dates and a reliable source for those dates, FEFO can help rotate the stock the buyer can actually accept. Write a tie breaker for identical dates, such as original receipt timestamp followed by the internal receipt or lot ID. Location can help break ties only when the agreed policy allows it. Comparing the next two picks after a replenishment is a simple way to catch a location preference overriding the rule. DCL Logistics on FEFO · Savino Del Bene on FIFO and FEFO

If one client changes methods, test the receipts where the new sort gives a different result. Keep the old and new rule versions and choose an effective time. Decide whether the switch applies only to newly allocated lines or also to orders already picked. A supervisor can reconcile open work before the next release. A change in sort order should not silently recalculate the underlying receipt or product dates.

Case 1. A later receipt expires first

Assume the planned handoff date is November 16, 2026. For the same owner and SKU, lot A arrived November 1, 2026 and expires January 15, 2027. Lot B arrived November 10, 2026 and expires December 16, 2026. Both lots pass all order checks. Subtract the handoff date from each expiration date without counting the handoff day as an extra day. A has 60 calendar days remaining at handoff and B has 30. FIFO picks A. FEFO picks B. Putting the oldest receipts at the front works for FIFO only if people and systems preserve that receipt order, and it cannot establish the expiration sequence. Give the picker a lot ID and verify the lot when it leaves the bin.

Lot A received November 1 and expires January 15. Lot B received November 10 and expires December 16. FIFO chooses A and FEFO chooses B when both qualify.
Hypothetical Case 1. Receipt and expiration produce different pick orders.

Record the lot and the source of its date

The SKU identifies the item in the owner's catalog. The manufacturer's lot code identifies a production batch in its own context. An internal lot record tells the warehouse how the stock was received and where it can be found. Start with the owner, warehouse, SKU, raw lot code, internal record ID, date type, date value, original receipt date, quantity, unit, location, stock status and source. Retain a production date when available and record the stop-pick date separately. If the same manufacturing lot comes in on different receipts, preserve the receipt layers where FIFO needs them. A bin can hold part of a lot and a lot can span bins. Keep both relationships queryable.

Use the inventory owner and item identity in every lookup. Two clients can both use a short SKU and the same printed lot code. A match on those strings alone could pull another client's inventory into a decision or a report. Keep the raw string, including leading zeros, and link it to the internal record. If the chosen owner and SKU still match more than one production context for that code, find a reliable distinction with the brand, such as a verified manufacturer or receipt record. Carry the unit of measure with quantity so a case count is not converted into an each count by default.

Date text and date meaning need separate fields. Keep the printed wording and value, plus the normalized date used by the order rule and the evidence that supports it. For example, USDA Food Safety and Inspection Service guidance describes Best if Used By as a quality date in its food dating context. Apply the brand's documented product-specific requirements and relevant rules before deciding what a particular date permits. A manufacturing date alone gives the date of production. Calculate any operational reference date from it only with the brand's documented method and the necessary verified inputs. If a month-only stamp or an ambiguous format cannot be interpreted under the approved rule, hold the affected stock and ask for confirmation. Preserve the label and the receipt record when correcting a verified data entry error. USDA FSIS date terms

Test the scan with real sample labels. An ordinary product barcode often identifies the item but does not carry its lot or date. For labels that encode GS1 Application Identifiers, (10) is the batch or lot number, (15) is the best-before date, and (17) is the expiration date. Verify what the label encodes, what the scanner outputs and how the warehouse software maps each field. The presence of a printed date near a barcode does not make it part of the scan. For manual entry, retain the label image or source document and use a second check when the interpretation affects release. GS1 Application Identifier registry · Warehouse labeling guide

Decide who can approve a date correction and how open orders are reviewed afterward. If a supplier confirms that a printed date was transcribed incorrectly, keep the previous value, the label image and the approval. Find allocations made using that value and recalculate them before release. When a carton and its inner units disagree, isolate the affected quantity and check which labeling level the brand specifies. Changing data merely to make the order pass can spread the error to every allocation that follows.

Decide whether the lot can reach the customer with enough time left

Start with three dates or rules that can coexist on one order. The product has an applicable date and quality controls. The brand, channel or receiving customer may require a minimum remaining shelf life at receipt. The facility can also have a stop-pick lead time to keep certain inventory off the floor. Treat these as separate checks. The facility cutoff can block a lot that otherwise passes a transit calculation. A lot that passes the warehouse cutoff can still fail a particular customer's delivery requirement. Define the event each rule uses, its comparison operator and the order of precedence when requirements overlap. Escalate an unresolved conflict before allowing a pick.

One planning calculation is expected remaining days at delivery = agreed reference date minus planned handoff date minus planned transit days minus buffer days. In the examples below, subtract dates in calendar days, then subtract transit and buffer in the same unit. In a system driven by business days, first convert the planned shipment and delivery into actual calendar dates, accounting for the relevant weekend and holiday schedule. If starting from pick date, account for time waiting to hand off as well. If a retailer measures at a receiving appointment or after check-in, use the event in its agreement. The calculation estimates order eligibility under the selected assumptions. Product quality and safety follow their own applicable requirements.

Build the order rule from the customer's terms and your shipping plan. Record the warehouse and destination calendar, how you choose the transit estimate, the buffer, and who can approve changing the plan. A salesperson's promise and a carrier estimate are different inputs. Use the later relevant planning event if the receiving facility works by appointment and the handling time is part of your rule. If the label channel gives an estimate in business days, saving the number alone loses the calendar it depends on. Keep the service assumption or planned delivery date with the allocation so the dock can tell when to recompute it.

Define a stop-pick boundary just as carefully. A date stored as the first blocked day should not be treated as the last allowed day. Check a sample the day before the boundary, at the boundary and after it. If an overnight shift uses a different date from the order-planning system, choose the agreed warehouse time zone and record the event. Tell the dock which changes require another check even after the parcel is sealed.

Check owner and SKU, stock status and verified dates, remaining life and available quantity. Hold or escalate a failed check, then rank eligible stock.
Pass each order check before ranking lots.

Case 2. The earliest date fails the delivery requirement

Keep the November 16 handoff for A and B. Add lot C, received October 28, 2026, with an expiration of November 26, 2026. The fictional customer requires at least 21 calendar days remaining at expected receipt. Plan seven calendar days for transit and hold two more days as a buffer. Starting from 60, 30 and 10 days at handoff, A has 60 − 7 − 2 = 51 days, B has 30 − 7 − 2 = 21 days, and C has 10 − 7 − 2 = 1 day. In this example the rule includes equality, so A and B pass and C fails. Assuming the other gates pass, choose B under FEFO. The planned transit and buffer are exercise inputs, and the minimum is this customer's example term.

LotReceipt dateExpiration dateDays at handoffDays at delivery after bufferMeets 21 days?
A2026-11-012027-01-156051Yes
B2026-11-102026-12-163021Yes
C2026-10-282026-11-26101No
Illustrative handoff November 16, 2026, seven calendar transit days and two buffer days. A has 51 days, B 21 days and C one day at planned receipt.
The 21-day minimum includes equality. FEFO chooses B after C fails.

If the truck leaves a day late with the same transit and buffer, B falls to 20 days and must be checked again. Under the illustrated rule it now fails, even though it was correctly allocated earlier. Reallocate to eligible stock such as A if there is enough and the revised shipment still meets the order. Changing the route for C to two calendar days gives 10 − 2 − 2 = 6 days, still short. After a delay, order hold, address change, service change or revised promised date, recompute using the current plan before release. When two orders have different minimums, make the decision by order. An account-level setting can be a useful baseline if the warehouse has another way to enforce any stricter order requirement.

Carry the lot from receiving to carrier handoff

Assign a decision owner and a record to every change in custody. At receiving, the receiving lead compares the advance notice or purchase order with the carton or unit label, records the original wording and identifies any date or quantity conflict. The brand or supplier confirms ambiguous source data. Finish by reconciling the lot and unit count to the receipt and releasing accepted quantities to the proper stock state. Put unresolved stock in a clearly identified hold state and location. Keep the evidence and the approval that explains why a discrepancy was corrected. Warehouse receiving process

At putaway and replenishment, the inventory team scans or records both source and destination, with the owner, item, lot, quantity and unit. Preserve the lot when breaking a case into eaches. Mark inner units or put them in an identified container if they would otherwise lose the connection. Complete the move by matching the count and identifiers at the destination to the posted transaction. Two lots can share a location only when the brand permits it and the physical separation or labels and scan workflow allow reliable identification under normal work. If different lots become indistinguishable, block that location for review. Warehouse replenishment guide

At allocation, the planner or WMS excludes locked, expired under the applicable rule, owned by another client, or otherwise ineligible stock. Use available quantities net of other reservations and confirm any single-lot requirement before promising enough. Apply the rotation rule to the candidates that remain. The allocated record should show the rule version, date assumptions, selected lot and required quantity. If the required quantity cannot be assigned, create an exception with the reason, review owner and next decision time. The floor should never switch to a more convenient lot because it is already in the pick face.

At picking and packing, check the physical lot against the allocated task as well as the SKU. Record the actual lot and quantity in each parcel. The shift lead resolves any mismatch before packing can finish. If a substitution is authorized, recheck available stock, timing and customer criteria and update the reservation and actual packing record. Reconcile the original units before releasing them for another order. For split cartons, the pack confirmation needs a line for each lot and actual package allocation. A valid SKU scan by itself cannot prove that the correct lot entered the box.

At handoff, the shipping lead checks that today's collection, order holds and route match the allocation assumptions. Review aging orders and changes before physically releasing them. Confirm the packed contents to the package ID and label, then associate the dock handoff evidence. If a truck misses its cutoff, keep affected parcels in the proper staged state and review their dates before the next pickup. Finish when the physical cartons released agree with the handoff record and exceptions are assigned. A created label supplies a tracking identifier. The departure needs its own evidence.

ShipHero illustrates where configuration fits. Its help describes client-level setup by the 3PL, a setting to choose FIFO or FEFO, a configurable period before expiration when picking is disabled, and optional lot verification during picking. The documentation says to turn on lot tracking for the individual products and describes active and inactive lots in picking. These controls belong to ShipHero. Test your own client configuration, actual dates, scans and orders end to end, especially whether the customer's remaining-at-delivery condition needs a separate calculation. Keep unresolved dates off the released stock record. ShipHero lot tracking setup · ShipHero lot management

When the earliest eligible lot is in reserve, give replenishment a task with that lot named and a due time. If the floor cannot get the stock safely before cutoff, ask the planner to compare another eligible lot or reset the shipping plan. Record why the exception happened. Repeat exceptions on one SKU may signal a replenishment or slotting issue, even if every individual package met the customer rule.

Keep component lots visible in a kit

Treat a parent SKU as the kit's sales identity. For each necessary component, check applicable dates, condition, owner, availability and order criteria. Next calculate the number of complete kits each component can support given its units per kit, rounding down, and select the smallest result. If the customer allows mixed lots, record the actual quantity from each lot. If a customer requires one lot on an order or in each carton, apply the scope it specified. Enough aggregate stock may still be impossible to pack under a single-lot requirement. For prebuilt kits, use an assembly batch or equivalent record linking actual component lots to finished units or groups that the warehouse can identify. Kitting fulfillment guide

Case 3. The order asks for 120 kits and only 90 can be built

Each gift box needs one X and one Y. The warehouse physically has 160 X and 140 Y. After checking the same customer's terms and others' reservations, 110 X and 90 Y remain eligible and available. With other conditions satisfied and no additional component constraints, min(110, 90) = 90 kits. The order is short 30. A list showing that the warehouse has more than 120 of each item cannot authorize the remaining kits. The brand can wait for qualifying stock, approve partial fulfillment with the original terms enforced, or follow its order exception agreement. Changing the required date or using a different owner's stock is outside the original authorization.

For an approved partial build, reserve 90 of each component and keep the remaining 30 kits open. If two batches of X feed the same build, distinguish which finished package received them, or preserve the actual boundaries of identifiable finished groups and map those to packages. The operator checks the component consumption and packed quantities against the work order. The brand supplies any applicable kit dating or labeling instructions. Recalculate the remainder when new stock arrives or the shipping date changes. ShipHero's product documentation specifically directs users to track lots at component level for its kit SKUs. ShipHero kit limitation

Before building ahead, decide what granularity the brand needs on a later hold. If several component lots are loaded into one undifferentiated assembly run, the entire run may be the smallest group you can identify. Label smaller finished groups when the promise calls for narrower traceability. Check how the record survives repacking or a partial request. Use the actual material consumption and packaging record as evidence for the order.

Find the affected goods and parcels when a lot goes on hold

Begin with the owner, SKU and lot ID, then follow the physical and digital trail from stock location and quantity to order line, actual package and tracking number. Treat a unit on the shelf, a picked unit on a cart, a packed unit at the dock, a handed-off unit and a returned unit pending inspection as different current states. Use a snapshot time and reconcile movements after that time. Avoid counting a reservation as a second unit on top of on-hand stock. Keep returns out of pickable stock until the applicable review and disposition are documented. Order, shipment, package and label guide

The supervisor records the time, lot scope and person who requested the hold. Block the affected inventory and open work in the system and tell the floor where to secure the goods. Check carts and sealed parcels against the dock load. Where the records cannot distinguish which cartons contain a lot, state the affected range explicitly and review the potentially affected cartons before release. A voided label does not move a carton off a pallet or stop someone from handing it over. Confirm physical control at the station or dock before closing the action. For departed parcels hand the supported records and unresolved gaps to the authorized brand contact. That owner decides communication, replacement, return or other action under the applicable instructions.

Case 4. Reconcile the location of 200 units

Assume the states are mutually exclusive, with no loss or returns. Of 200 units, 120 are still on shelves. Another 30 are in 10 packed parcels with three affected units in each, waiting for handoff. The other 50 have departed in 50 parcels with one affected unit each. Reconcile 120 + 30 + 50 = 200. Investigate and control the shelf units, locate all 10 staged packages and confirm the physical stop, then export the actual records for the 50 departed packages. The 80 packed units are in 60 parcels across two different handoff states. The example does not supply an order count.

Of 200 affected units, 120 are on shelves, 30 are packed in 10 parcels awaiting handoff, and 50 have departed in 50 parcels.
Hypothetical Case 4. Count units and parcels separately at the time of the hold.

If the pick record identifies the planned lot but the pack record has only a SKU and tracking number, report that distinction. Show which quantities and locations are confirmed and which outbound records are candidates that still need a check. Verify system timestamps against handoff records and preserve the snapshot plus the resolution. A brand can decide with explicit uncertainty while the warehouse reconstructs the missing link. Use one row for each actual lot and package pairing, with order-line and quantity fields. If two lots of the same SKU enter one package, store two rows under the same package ID. Avoid copying the complete order quantity into both rows.

Ask a second staff member to reconcile the hold before releasing unaffected cartons. Start from the units found and subtract only states supported by real movements. See the cycle counting guide for reconciling counts across a cutoff. Check whether a stale staging line represents a carton waiting at the dock or one that has departed. If you later find a mislabeled carton, correct the current status and retain the earlier snapshot so the brand can see which information changed.

Start with a few SKUs and a reviewable pilot

Begin with a few products and one clear client agreement. Compare printed labels, the receipt record and the WMS export for real sample units before enabling the rule. Define the reference date, order minimum, stop-pick date, tie breaker and mixed-lot permission with the brand. Make the responsible shift lead complete a pick, a package record and a handoff check. Retain results and correct the rule or physical layout before expanding. If the workflow starts with spreadsheets, assign one controlled record for updates, version it, and reconcile it with the floor at every shift that uses it.

Define the pilot exit criteria before opening live work. Check whether rejected units stay off pick tasks, correct lots flow from receipt to carton, and a supervisor can find staged and departed parcels from a lot query. Run at least one case in which you physically withdraw a staged carton. Keep evidence of the expected and actual result, and give every discrepancy a specific owner and retest date.

Test scenarioExpected warehouse action
Later receipt expires firstConfirm FEFO picks the earlier date among eligible stock
Date missingKeep required date unknown, hold and request evidence
Conflicting datesContain affected units and obtain documented resolution
All lots ineligibleStop allocation and escalate the order without an automatic substitute
Same lot code under two ownersReturn only the right owner’s units and records
Delay after allocationRecalculate before release and update the pick if needed
Kit component shortageCap kits to eligible availability and seek partial-ship approval
Hold after packingLocate and physically stop staged cartons, reconcile dock records

Use the rules worksheet as the approval and release reference. The trace worksheet shows one order line divided into two lot records within one packed carton. Keep tracking and parcel IDs separate, and document evidence for handoff. A missing scan or an unresolved quantity is an exception to investigate. The editable sheets include sample data and room for your own entries. Download the customer rules worksheet · Download the lot-to-package worksheet · Download the pilot checklist

Compare costs by volume and role. For example, time how long receiving spends on a new lot, how much picking adds per order, and how many holds require a supervisor. Record documented write-offs and retailer rejections by reason. Use the same definitions before and after the change so a change in reporting does not look like a change in loss.

Measure the additional work for data entry, segregated storage, scan verification, resolving exceptions and updating rules. Compare those labor and space costs with write-offs, rework and reshipment costs observed over a comparable volume and time period. Record the reason for each loss, including cases attributable to other changes. A reasonable pilot starts with observed differences and leaves unknown categories open. Once the warehouse clears the goods, use the sealed parcel dimensions, weight, destination and tender plan to compare available services. EasyShippingX supports labels through its portal, Excel upload or API according to account and shipment eligibility, with tracking for supported services. EasyShippingX shipping calculator · EasyShippingX features

FIFO and FEFO FAQ

FIFO sorts eligible stock by the agreed receipt event. FEFO sorts eligible stock by the applicable expiration or approved reference date.

No. Check the applicable cutoff and order requirements first. Then select the earliest date among the lots that pass.

Yes. Keep receipt and date fields separately so the order can follow the agreed method.

Use the actual customer, product and channel criteria. Include shipping and receiving time in the calculation if the agreement requires it.

Yes if the customer allows it. Record the quantity from each lot in each actual package.

Only when the label and capture process also identify the lot. Test the encoded data and field mapping with sample units.

Keep the component lots and quantities linked to identifiable finished goods and their actual packages.

Hold or escalate the order. Review replenishment, revised timing or partial shipment with the authorized decision maker.

Sources and methodology

Sources reviewed November 15, 2026. The examples use fictional orders and lot records. Date differences use calendar days. Product requirements and account settings apply within their documented scope.