FEFO vs FIFO: Choosing the Right Allocation Method

If you manage inventory with expiry dates, whether that's food ingredients, finished goods, pharmaceuticals, or chemicals, you've probably encountered the terms FEFO and FIFO. They sound similar, but they solve different problems. Choosing the wrong one can lead to unnecessary waste, customer complaints, or compliance issues.

This article explains both methods, when to use each, and why the distinction matters more than you might think.

What Is FIFO?

FIFO (First In, First Out) means you dispatch or consume stock in the order it was received. The oldest stock (by receipt date) gets used first.

Example: You receive 100 units of flour on Monday and another 100 units on Wednesday. When production needs flour, FIFO says: use Monday's delivery first, because it arrived first.

FIFO is the default allocation method in most general inventory systems. It's simple, logical, and works well for non-perishable goods where receipt date is a reasonable proxy for "use this first."

FIFO is ideal for:

• Non-perishable goods (hardware, electronics, building materials)
• Products where all batches have the same shelf life
• Situations where receipt order genuinely reflects the priority for use

What Is FEFO?

FEFO (First Expiry, First Out) means you dispatch or consume stock based on expiry date, not receipt date. The batch closest to expiring gets used first, regardless of when it was received.

Example: You receive Batch A of cream cheese on Monday (expires 15 March) and Batch B on Wednesday (expires 10 March). FEFO says: use Batch B first, because it expires sooner, even though it arrived later.

This might seem like a subtle difference, but in practice it's critical for food manufacturers and anyone dealing with perishable inventory. Effective batch allocation depends on having proper batch tracking software that records expiry dates at every stage of your supply chain.

Why the Difference Matters

Scenario: Supplier Delivers Shorter-Dated Stock

Your regular supplier delivers 500kg of butter every week. Usually it has 6 weeks of shelf life remaining. But this week, they send butter with only 3 weeks left, perhaps clearing older stock from their cold store.

Under FIFO: This delivery sits at the back of the queue behind last week's delivery, which has 5 weeks of shelf life remaining. By the time you get to this week's butter, it might be expired or too short-dated to use.

Under FEFO: This delivery jumps to the front of the queue because it expires soonest. You use it in production this week, and last week's delivery (with longer shelf life) gets used next week. No waste.

Scenario: Customer Shelf-Life Requirements

Major retailers in New Zealand typically require a minimum remaining shelf life on delivered products, often 75% of total shelf life. If your product has a 12-week shelf life, the retailer wants at least 9 weeks remaining on delivery.

Under FIFO: You might dispatch stock based on when it was produced, not when it expires. If production batch dates don't perfectly align with expiry dates (which they often don't, due to varying raw material shelf lives), you could ship shorter-dated stock when longer-dated stock is available.

Under FEFO: The system always picks the shortest-dated stock first, but you can configure minimum shelf-life thresholds. Stock that doesn't meet the customer's requirements gets flagged before it's allocated, not after it's been shipped and rejected.

Scenario: Multiple Storage Temperatures

Some products have different shelf lives depending on storage conditions. Frozen stock might have 12 months, while chilled has 4 weeks. If you transfer stock between temperature zones, the receipt date becomes meaningless. What matters is the expiry date.

Under FIFO: The system doesn't account for the fact that a batch moved from frozen to chilled storage now has a much shorter effective shelf life.

Under FEFO: Expiry dates are updated when storage conditions change, and allocation is always based on the current expiry date.

What About LIFO?

LIFO (Last In, First Out) is a third allocation method where the most recently received stock is used or dispatched first. While LIFO is common in accounting contexts (particularly in the United States for tax purposes), it is rarely used as a physical stock allocation method in New Zealand, and for good reason.

Why LIFO Is Rarely Used in NZ

• It causes waste. For perishable goods, using the newest stock first means older stock sits at the back of the warehouse, ageing towards its expiry date. This is the exact opposite of what food manufacturers need.
• NZ tax rules don't incentivise it. In the US, LIFO is popular because it can reduce taxable income during periods of rising costs (you expense higher recent costs first). New Zealand's tax framework under the Income Tax Act 2007 does not permit LIFO for tax purposes. IRD requires either FIFO, weighted average cost, or specific identification methods.
• It contradicts food safety principles. MPI expects food manufacturers to demonstrate effective stock rotation. LIFO fundamentally undermines this by deprioritising older stock.

LIFO does have a narrow practical application in physical warehousing: when goods are stored in deep racking or stacked pallets where only the front/top is accessible, the most recently placed stock is physically easiest to retrieve. But this is a warehouse layout constraint, not an allocation strategy, and it should be addressed through better racking design or pick-face replenishment, not by accepting LIFO as policy.

For NZ food manufacturers, LIFO should be considered a non-option. FIFO is the minimum standard, and FEFO is the best practice.

Real Warehouse Scenario: Switching from FIFO to FEFO

To make this concrete, here is how a mid-sized NZ food manufacturer producing chilled ready meals with a 21-day shelf life experienced the switch from FIFO to FEFO.

The Problem

The manufacturer was using a general inventory system with FIFO allocation. Their warehouse team picked stock in receipt order, which worked well when all suppliers delivered ingredients with consistent shelf lives. But as they scaled from two to five product lines and added new ingredient suppliers, problems emerged:

• Supplier A delivered cream with 14 days of shelf life remaining. Supplier B delivered cream with 8 days remaining (sourced from a longer supply chain). Under FIFO, Supplier A's cream (received first) was always used first, while Supplier B's shorter-dated cream sat in the chiller.
• Over three months, the manufacturer wrote off $12,000 of expired cream, cheese, and fresh herbs. This was stock that had been pushed to the back of the queue by longer-dated deliveries received earlier.
• Two customer complaints about short-dated finished goods led to a retailer audit, which flagged inadequate stock rotation as a non-conformance.

The Switch

The manufacturer migrated to Frostbyte Pro and enabled FEFO allocation. The transition involved:

1. Data cleanup (2 days). The warehouse team audited existing stock and recorded accurate expiry dates for every batch in the chilled and frozen stores.
2. System configuration (1 day). FEFO was enabled as the default allocation method for all batch-tracked products. Minimum shelf-life thresholds were configured for each major retail customer.
3. Team training (half day). Warehouse pickers were shown how pick lists now ordered batches by expiry date rather than receipt date. The key message: trust the system's suggested batch, don't default to grabbing the nearest pallet.

The Result

Within two months of switching:

• Expired stock write-offs dropped from $4,000/month to under $500/month
• No further customer complaints about short-dated deliveries
• The retailer audit non-conformance was closed at the next review
• Warehouse pickers reported that the new pick lists were actually easier to follow, because the system made the decision for them

When FIFO Falls Short

FIFO breaks down when any of these conditions exist:

1. Suppliers deliver stock with varying shelf lives. Not every delivery has the same expiry window.
2. You receive the same product from multiple suppliers. Different suppliers may provide different best-before dates.
3. Stock moves between temperature zones. Shelf life changes with storage conditions.
4. Production batches have different raw material inputs. The finished product's expiry depends on which raw materials were used.
5. Customers have minimum shelf-life requirements. You need to allocate based on expiry, not receipt order.

If any of these apply to your operation (and for food manufacturers, most of them will), FEFO is the right choice.

Implementing FEFO in Practice

Recording Expiry Dates

FEFO only works if expiry dates are captured accurately at the point of receipt. When raw materials arrive:

1. Record the batch number from the supplier's label
2. Record the expiry date (or best-before date)
3. If the product is manufactured internally, calculate the expiry based on production date + shelf life

This needs to happen for every batch, every time. It's one of the reasons barcode scanning at goods receipt is so valuable: it forces the data capture step and reduces manual entry errors.

Allocation Rules

A good FEFO system should:

• Automatically suggest the shortest-dated batch when picking for production or sales orders
• Respect minimum shelf-life thresholds so that stock too short-dated for the customer's requirements is never allocated
• Handle split picks by taking what's available from one batch and moving to the next shortest-dated batch when quantity falls short
• Alert on near-expiry stock with proactive notifications before stock expires, giving you time to act

Stock Rotation Discipline

FEFO in software is only half the story. Your warehouse team needs to physically rotate stock to match the allocation. This means:

• Labelling. Every pallet or location should show batch number and expiry date
• Physical arrangement. Shortest-dated stock should be most accessible
• Regular checks. Periodic stock takes that verify physical stock matches system records, including expiry dates

Integration with Production

For manufacturers, FEFO allocation should extend into production. When a production order consumes raw materials, the system should allocate the shortest-dated batches first. This ensures:

• Raw materials are used before they expire
• The finished product's expiry date accurately reflects its raw material inputs
• Traceability is maintained, so you know exactly which raw material batches went into each production batch

FEFO and Compliance

For New Zealand food manufacturers, FEFO isn't just good practice. It directly supports MPI (Ministry for Primary Industries) compliance:

• Traceability: FEFO systems track which batches were used in production and which were dispatched to customers, maintaining a complete chain of custody.
• Recall readiness: If a raw material batch is found to be contaminated, you can instantly identify every finished product batch that used it, and every customer that received those batches.
• Waste reduction: By minimising expiry-related waste, FEFO contributes to your food safety management plan's requirement for effective stock control.

Making the Switch

If you're currently using FIFO (or no systematic allocation at all), switching to FEFO involves:

1. Clean up your batch data. Ensure every current batch in your system has an accurate expiry date recorded.
2. Enable FEFO allocation in your inventory system. In Frostbyte Pro, FEFO is the default allocation engine and it's always on for batch-tracked products.
3. Train your warehouse team. Explain why picking order might change and how to read the system's allocation suggestions.
4. Configure alerts. Set up expiry notifications at appropriate lead times (e.g., 7 days before expiry for chilled goods, 30 days for ambient).

The transition is usually straightforward. The biggest challenge is ensuring your existing batch data is clean and complete.

Software Implementation: How Frostbyte Pro Handles Both Methods

Understanding how allocation methods work in software helps clarify why the choice between FIFO and FEFO matters at a practical level.

Dual-Mode Allocation

Frostbyte Pro supports both FIFO and FEFO simultaneously across your product catalogue. The allocation method is determined automatically based on whether a product is batch-tracked with expiry dates:

• Products with expiry dates (batch-tracked raw materials, perishable finished goods) use FEFO by default. When a sales order or production order requires allocation, the system queries all available batches, sorts them by expiry date (ascending), and allocates from the shortest-dated batch first.
• Products without expiry dates (packaging materials, labels, non-perishable components) use FIFO. The system sorts by receipt date and allocates from the oldest received batch first.

This means you do not need to choose one method for your entire operation. Perishable ingredients and finished goods get FEFO protection, while your cartons, films, and labels follow standard FIFO, all managed within the same system.

How Allocation Works Step by Step

When a sales order is confirmed or a production order is released, the allocation engine runs through the following logic:

1. Identify available stock. Query all batches of the required product across the specified warehouse location(s), excluding quarantined or reserved stock.
2. Sort by allocation method. For FEFO products, sort batches by expiry date ascending. For FIFO products, sort by receipt date ascending. If two batches share the same expiry date (under FEFO), fall back to FIFO as a tiebreaker.
3. Apply shelf-life constraints. If the customer has a minimum remaining shelf-life requirement configured, exclude any batches that do not meet the threshold. This prevents allocation of stock that would be rejected on delivery.
4. Allocate quantity. Starting from the first eligible batch, allocate as much quantity as available. If the batch does not have enough to fill the order, take what is available and move to the next batch (split pick).
5. Generate pick list. The warehouse team receives a pick list showing exactly which batches to pick, in which quantities, from which locations, with batch numbers and expiry dates clearly displayed.

Handling Edge Cases

Real warehouse operations produce edge cases that simple allocation rules cannot cover:

• Manual override. Sometimes a warehouse supervisor needs to override the system's allocation. For example, they may want to use a batch that is about to expire for an internal order rather than a customer order. Frostbyte Pro allows manual batch selection with an audit trail recording the override reason.
• Quarantine and holds. If a quality issue is identified with a specific batch, it can be placed on hold, removing it from the allocation pool immediately. This prevents the batch from being picked for any order until the hold is released.
• Location-specific allocation. For operations with multiple warehouses, allocation can be restricted to specific locations, ensuring that a dispatch from your Auckland warehouse does not accidentally allocate stock sitting in your Christchurch facility.

Impact on Financial Reporting and Stock Valuation

The choice between FIFO and FEFO affects more than warehouse operations. It has direct implications for how your inventory is valued on the balance sheet and how cost of goods sold (COGS) flows through your profit and loss statement.

Stock Valuation Under FIFO

Under FIFO valuation, the cost of goods sold is calculated using the cost of the oldest stock first. If ingredient prices are rising over time, FIFO results in a lower COGS (because you are expensing older, cheaper stock) and a higher closing inventory value (because remaining stock reflects newer, higher prices). This is the standard valuation method accepted by IRD and NZ IFRS (International Financial Reporting Standards as adopted in New Zealand).

Stock Valuation Under FEFO

FEFO is a physical allocation method, not an accounting valuation method. However, when your FEFO allocation aligns with your accounting treatment (which it usually does when FEFO and FIFO produce similar results), your financial statements accurately reflect the physical flow of goods through your operation.

Where FEFO and FIFO diverge (for example, when a shorter-dated batch received later is consumed before an older batch), the cost assigned to COGS may differ from a pure FIFO valuation. Most NZ food manufacturers handle this by using weighted average cost valuation in their accounting system, which smooths out the per-batch cost variations and avoids the need to track exact batch cost sequences.

Practical Implications for NZ Food Manufacturers

• IRD compliance. New Zealand's tax rules permit FIFO, weighted average cost, or specific identification for inventory valuation. LIFO is not permitted. If you use FEFO for physical allocation, ensure your accounting valuation method (in Xero or your accounting system) is configured to an IRD-accepted method.
• Write-off visibility. FEFO reduces expired stock write-offs, which directly improves your gross margin. Tracking write-offs by category (expiry, damage, quality) in your inventory system provides the data your accountant needs for accurate financial reporting.
• Audit readiness. Both financial auditors and MPI auditors expect your physical stock to match your system records. Using FEFO for allocation and maintaining accurate batch-level cost data means your stock valuation report can be reconciled to the physical stock count, and both align with your Xero accounts.

Summary

For food manufacturers, FEFO isn't a luxury. It's the baseline for effective stock management. Any inventory system designed for food manufacturing should support it natively, not as an afterthought.

Frostbyte Pro includes FEFO allocation as standard across all plans. Start a free trial or explore all features to see how it works for your operation.