What FEFO and FIFO actually mean in a food manufacturing context
FIFO is simple. The batch that arrived first ships first. It assumes that older stock should move before newer stock, which is true for non-perishable goods or raw materials with long shelf lives.
FEFO adds a critical dimension: expiry dates. The batch expiring soonest ships first, regardless of when it arrived. This matters when you receive two shipments of the same ingredient a week apart, but the second shipment has a shorter remaining shelf life because it sat longer at the supplier's warehouse or spent more time in transit.
In a manual warehouse, FIFO is easier to implement. You stack pallets in order and pick from the front. FEFO requires checking dates, which in practice means either a clipboard system that your team maintains manually or an ERP system that tracks expiry dates against every lot and generates pick instructions automatically.
When FIFO is enough
FIFO works for:
Dry goods with long shelf life. Flour, sugar, spices, canned goods. If your shortest shelf life is measured in months and you turn stock regularly, FIFO is fine because the arrival order and expiry order are effectively the same.
Non-food raw materials. Packaging, labels, cleaning chemicals, maintenance supplies. No expiry pressure means FIFO keeps things simple.
Finished goods with uniform shelf life. If every batch has the same production and expiry date because you produce and ship the same day, FIFO and FEFO produce identical results. This is common in bakeries and fresh-daily operations.
When NZ food manufacturers need FEFO
FEFO becomes necessary when any of these apply to your operation:
You hold multiple batches of perishable ingredients at the same time. Dairy, fresh produce, meat, seafood, sauces, anything chilled or frozen. Different batches from different deliveries have different remaining shelf life. Without FEFO, your warehouse team is guessing which pallet to pick, and they will get it wrong under time pressure.
Your customers specify minimum remaining shelf life. Supermarket buyers in NZ routinely require 60% or 75% of shelf life remaining at delivery. Foodstuffs and Woolworths both enforce this. If your product has a 90 day shelf life and a retailer requires 75% remaining, you can only ship product with at least 67 days of life left. FEFO ensures you ship the batch that meets their requirement while still being the closest to expiry. FIFO might ship a batch with 80 days remaining while a batch with 70 days remaining (still compliant) sits in the warehouse and eventually becomes non-compliant because nobody picked it first.
You manage multiple storage conditions. A single ingredient might exist in your warehouse at three temperatures: ambient, chilled, and frozen. Each has a different shelf life. FEFO across storage conditions ensures the right unit gets picked regardless of where it is stored.
MPI traceability applies to your operation. Under the Food Act 2014 and the Animal Products Act 1999, you need to be able to trace product forward and backward by batch. FEFO with lot tracking makes this straightforward because every pick is recorded against a specific lot with a known expiry date. FIFO without lot tracking means your traceability records are incomplete.
You export. Export markets, especially Australia, Asia, and the EU, have strict date requirements. A shipment rejected at port because the remaining shelf life does not meet the importing country's rules is an expensive mistake. FEFO at the warehouse level prevents this by ensuring you always ship the optimal batch.
What goes wrong without FEFO: the scenarios your team deals with
The forgotten pallet
A delivery of 6 pallets of cream cheese arrives on Monday. Your team puts 4 pallets in the main pick location and 2 in overflow racking at the back. Over the next two weeks, they pick from the main location using FIFO. By the time someone checks the overflow racking, those 2 pallets have 5 days of shelf life remaining. They cannot be shipped to any retail customer. They become waste, or you scramble to find a food service customer who will take short-dated stock at a discount.
With FEFO, the system knows those overflow pallets exist and their expiry dates. When pick instructions are generated, it directs the operator to the overflow pallet first because its expiry date is earliest, not because of where it was stored or when it arrived.
The customer rejection
You ship a pallet of finished product to a Foodstuffs distribution centre. Their goods-in team checks the dates and finds the product has 55% of shelf life remaining. Their requirement is 60%. The pallet is rejected. You now have a pallet in transit back to you, a credit note to issue, a replacement order to fulfil urgently, and a buyer who is questioning your reliability.
With FEFO and customer-specific shelf life rules, the system would not have allowed that lot to be picked for that customer. The warehouse operator would have been directed to a newer lot that met the 60% threshold. The short-dated lot would have been picked for a different customer with a lower threshold, or flagged for food service channels where shelf life requirements are more relaxed.
The recall nightmare
A supplier notifies you that a batch of flour may contain an undeclared allergen. You need to identify every finished product that used flour from that supplier lot, and every customer who received those products. With FIFO and no lot tracking, you are pulling delivery notes, cross-referencing purchase orders, and trying to reconstruct which flour went into which production run based on dates and assumptions. This takes days. MPI expects hours for high-risk recalls.
With FEFO and full lot tracking, you enter the supplier lot number and the system returns every production batch that consumed it, every finished product lot that resulted, every customer shipment that included those lots, and the exact quantities. The trace is complete and auditable.
How Business Central with Yaveon handles FEFO in practice
Microsoft Dynamics 365 Business Central with the Yaveon food and beverage extension manages FEFO as a core part of daily warehouse operations, not a reporting afterthought.
Every lot carries its own expiry data from day one
When ingredients arrive, each lot is recorded with its supplier lot number, your internal lot number, production date, and expiry date. Yaveon extends standard BC lot tracking with additional attributes: allergen flags, country of origin, quality status, storage condition requirements, and any other data points your operation needs. These attributes travel with the lot through every transaction.
Quality holds prevent premature picking
Not every lot that arrives is immediately available. Yaveon's quality management creates inspection orders automatically when goods are received. A lot of raw milk powder might need a certificate of analysis verified, or a microbial test result confirmed, before it can be used in production. Until the quality team releases the lot, it exists in the system but cannot be picked. FEFO only considers lots that have passed quality and are genuinely available.
Warehouse picks are generated by expiry, not location
When a sales order or production order needs 500kg of an ingredient, the system generates a pick instruction. Yaveon's warehouse management sorts available lots by expiry date and directs the operator to the lot expiring soonest. If you use handheld scanners (Yaveon integrates with Tasklet Mobile), the operator scans the lot barcode to confirm they picked the correct one. No clipboard, no guessing, no relying on someone remembering which pallet arrived first.
Customer shelf life rules are enforced automatically
You configure minimum remaining shelf life per customer. When the system generates picks for a sales order, it filters out any lot that does not meet that customer's threshold. A lot with 50% remaining shelf life will not be suggested for a customer requiring 60%. It will be suggested for a customer requiring 40%, or flagged for alternative channels. This happens at the pick instruction level, before anyone touches a pallet.
FEFO for picking, FIFO for costing
A common question from finance teams: does FEFO affect how we value inventory? No. Yaveon allows you to run FEFO for physical warehouse operations (which lots get picked) while running FIFO or weighted average for financial costing (how inventory is valued on the balance sheet). These are independent settings. Your warehouse operates on expiry dates. Your accountant reports on cost flows. Both are correct for their purpose.
Reporting shows what is at risk
Beyond daily picks, the system provides visibility into stock approaching expiry. You can see which lots are within 30 days of expiry, which have already passed customer shelf life thresholds (and therefore have limited channels available), and which are at risk of becoming waste. This lets you proactively push short-dated stock into food service, staff sales, or other channels before it becomes a write-off, rather than discovering it during a stock count.
Making the decision
For most NZ food manufacturers, the answer is FEFO for warehouse picking, FIFO for cost valuation. This gives you the safety and compliance benefits of expiry-based inventory rotation while keeping your financial reporting straightforward.
If you are currently running on spreadsheets or a system that only supports FIFO, the transition to FEFO is one of the highest value changes you can make. It reduces waste, prevents customer rejections, simplifies recall responses, and gives your warehouse team clear instructions instead of relying on their memory of which pallet arrived when.
The businesses that get the most value from this are those handling 20 or more ingredient lots at any given time, serving customers with shelf life requirements, or operating under MPI compliance obligations. If that sounds like your operation, FEFO is not a nice-to-have. It is how modern food manufacturing runs.
Equerra implements Dynamics 365 Business Central with Yaveon for NZ food manufacturers. See our food manufacturing ERP page for how we handle batch tracking, FEFO, allergen management, and MPI compliance. Or book a discovery call to talk through your specific requirements.