Food stock control software tracks every pallet, case and unit of food stock by location, batch and expiry date, so the right stock ships first and short-dated product does not reach a customer by accident. Most search results for this phrase describe restaurant stock control, which links stock to EPOS sales and recipe costing. That is a different job. This guide is for food manufacturers, food distributors and food 3PLs who hold stock in a warehouse and need to rotate, hold and trace it.
If you run a kitchen or restaurant, an EPOS-linked tool is the right starting point. If you run a chilled, frozen or ambient warehouse for other businesses, the questions change. Which batch went where? How many days does each pallet have left? Has a customer’s minimum shelf life been met before stock is picked?
What is food stock control?
Food stock control is the discipline of knowing what stock you hold, where it sits, its batch and date data, and whether it is free to allocate. In a warehouse, every receipt, put-away, move, hold and pick is recorded against a specific unit of stock, not against a product line on a spreadsheet.
The gaps usually show up in three places. Counts drift from the floor because movements are recorded late or not at all. Expiry dates live on a clipboard, so nobody notices a pallet turning short until a customer rejects it. And when a recall or complaint arrives, tracing a batch means phoning around. Software closes those gaps by making the transaction itself the record.
The operational detail in this guide comes from Mat Buttar, a Clarus implementation consultant with nearly 25 years in warehouse operations, including fresh produce and chilled distribution. His account of how the system handles each control is set out in the sections below.
FIFO, FEFO and the rotation rule that decides what ships next
FEFO, first expired, first out, means the stock with the earliest expiry date is allocated and picked first, whatever order it arrived in. It is the usual rule for chilled, frozen and dated ambient food. A GMP compliance summary of WHO guidance sets out the same principle for medical products: stock should be rotated so the first expired is the first out.
FIFO, first in, first out, uses the order of receipt. It suits stock with no date control, but it can send out a batch received last week while a batch received yesterday expires sooner. The two rules are not interchangeable, and the difference matters most when deliveries of the same product arrive on different dates.
| Rule | Allocates by | Suits | Main risk |
|---|---|---|---|
| FIFO | Date the stock record was created | Products with no expiry control | Ships a newer batch with less life left |
| FEFO | Earliest expiry or sell-by date | Chilled, frozen and dated ambient food | Needs accurate date capture at receipt |
| FEFO with batch control | Expiry date, then batch | Food businesses that may need a recall | Slower picking if batch data is incomplete |
Clarus WMS supports FIFO, LIFO and FEFO rotation, and you can set the rule per client or per product. A chilled line and a dry goods line in the same warehouse can therefore run different logic. Clarus treats FIFO as the stock record creation date, to the millisecond. Expiry-based picking is a separate pick rule set on the account. Keeping the two apart means a dated product is picked by expiry, not by the day it arrived.
Rotation rules only work if the oldest stock can be reached. In deep bulk stacks, the oldest pallet is often at the back, under pallets of newer stock. Keep dated lines in pallet-accessible racking rather than bulk stacks, or the rule exists on screen only.
Shelf life and the minimum-life rules your customers set
Use-by dates are a safety limit, and best-before dates describe quality. Den Food Standards Agency advises that food should not be sold or eaten after its use-by date. The Food Information Regulations 2014 set the rules for date marking on pre-packed food, and WRAP’s food date labelling guidance covers how those dates are applied in practice. Your warehouse often has to meet a stricter test than the label, though. A retailer or distributor may refuse stock with less than a set number of days left, and each customer can set a different figure. One accepts product with five days on it, another only with three.
Batch, sell-by and best-before control can be switched on at account level and overridden per product. When a product has date control, the handheld screens ask for the batch and date, and a wrong batch triggers a warning. Products without date control skip those screens. That matters when a site holds dated food alongside packaging or dry goods that do not need the same checks.
When you assess a system, ask how a minimum remaining life is enforced at three points: receipt, allocation and picking. A system that stores an expiry field but cannot stop a short-dated pallet being allocated to the wrong customer leaves the risk where it was. For more on how expiry dates are captured and reported, see Clarus expiry and best-before tracking, and for picking logic built around shelf life, see how to automate shelf-life picking.
Batch control, traceability and recall
Batch control turns a recall from a week of phone calls into a query. Clarus supports batch and lot control, serial number capture where a product needs it, and an audit trail of every action and stock movement. Suppliers often put GS1 labels on each pallet. The GS1 UK guidance on the SSCC explains that this serial shipping container code identifies logistic units. A handheld can be set to read the barcodes already on a supplier’s label, so batch and quantity are captured by scanning rather than typing.
Traceability standards expect the same thing. The BRCGS best practice guideline on traceability describes linking a product back from the final customer to its original materials. Edge Transport, a food and 3PL business, reached 99% stock accuracy and can now produce full BRCGS traceability in minutes. Campeys of Selby, a food business, cut product recalls to under five minutes and secured BRC Double-A accreditation.
When a recall lands, Mat’s sequence is the one to follow. First, find what went where: this works only if dispatch data, including the order and the vehicle, was captured when stock left. Second, put the stock still on the shelf on hold from the stock list, which takes seconds, so nothing can be allocated to another order. Third, check stock already sitting on orders that have not yet left, stop those picks, and reallocate them to a good batch. Finally, hold whatever remains.
Quarantine and QC holds
A QC hold stops stock being allocated until someone releases it. In Clarus this is an automation rather than a separate module. Put the affected products in a group, create a quarantine location, and set an automation on the account so that stock put away there goes on hold automatically. Stock on hold cannot be allocated to any task, and the hold, its reason and the person who placed or released it are recorded.
Reason codes can be enforced or optional. They typically mirror the codes your customer uses for damage, customer request or quality, so the record makes sense to the business that owns the goods. Damaged stock can be received as a separate damaged quantity and held there, and later transferred back once repaired.
Mat describes one animal feed manufacturer whose product needed veterinary sign-off before release. Received straight into a 3PL, it was placed on hold automatically, so nothing could be picked until the sign-off was recorded. The system records the hold. It does not test the product, and it cannot see what happens once a load leaves the back door.
Stock accuracy and counts
Stock accuracy underpins every other control. If the system says a batch is in the rack and it is not, shorts appear at picking, customers receive the wrong quantities, and the hold process rests on an inaccurate base.
Cycle counting is the practical method. Rather than closing the warehouse for a full stock take, you count a sample each week, measure the error rate on that sample and apply that rate to the rest of the stock. A full stock check means stopping operations, paying overtime or counting on a night shift, which is why rolling counts are common.
JODA Freight, a refrigeration logistics 3PL, reached 99% stock accuracy by year two, and its stock takes went from weeks in Excel to one day. For the counting workflow, see Hvordan gjennomføre strukturerte lageropptellinger.
Clarus does not have temperature mapping or a built-in HACCP module. Temperature and hygiene checks are captured as typed fields in the handheld flow and timestamped against each transaction. That gives you a record of what was checked and by whom, but not a live temperature reading. Plan your temperature monitoring separately.
Food stock control software, WMS and MRP: which system does what
Many food manufacturers run stock planning in an ERP or MRP system and add a warehouse management system where stock is physically handled. An ERP or MRP tracks stock value and plans what to buy and make. A WMS controls each movement inside the building: where a pallet is put away, which batch is picked, what is held and which vehicle it leaves on.
The two should exchange data. The ERP needs accurate stock quantities to plan, and the WMS needs orders and planning data to pick against. If the warehouse system is weak, the ERP’s figures drift away from the floor. Clarus integrates with common ERPs and inventory systems, including Sage 200, Microsoft Dynamics and SAP. For a fuller explanation, read our ERP vs WMS comparison.
Food manufacturing inventory management software is a broad category, so the table below is a useful checklist before you shortlist any product. Use it with a vendor and ask for a demonstration of each row.
| Requirement | What to check with the vendor | Why it matters |
|---|---|---|
| Rotation rule per product | Can FEFO apply to chilled lines and FIFO to dry goods on one site? | Mixed ranges need mixed rules |
| Shelf life at receipt | Can you capture the date and hold stock that fails a set minimum? | Stops short-dated stock entering the pick face |
| Batch and recall | Can you trace a batch to every order and vehicle? | Recall speed depends on dispatch data |
| Quarantine | Does receipt into a hold location stop allocation automatically? | Manual holds get forgotten |
| Stock counts | Does the system support sample-based cycle counts? | Full stock takes stop the site |
| Integrasjon | Does it connect to your ERP and carriers without re-keying? | Re-keyed data creates errors |
For food warehouses that also need shelf-life picking, batch and hold controls in one place, the Clarus inventory management features og lagerrotasjon 101 cover the mechanics in more depth. The Clarus food and beverage solution sets out how these controls fit a food operation.
Snakk med en lageransvarlig
If you’re evaluating your options and want to see how a purpose-built WMS handles FEFO, batch and holds in practice, Clarus is worth a conversation. We work with food manufacturers, distributors and 3PLs across the UK to implement warehouse management software that fits the way you operate, not the other way around.
Ta kontakt med teamet vårt å snakke gjennom dine krav.