Inventory Management Software for the Food Industry
A generic stock app counts units. Inventory management software for the food industry has to track batches, expiry dates and allergens, drive first-expired-first-out picking, and trace one-up and one-down for a recall. This guide covers what food inventory software must do differently, and the right-sized owned alternative to bending your business around a heavy food ERP.
Inventory management software for food industry businesses records stock by lot, date, temperature condition and allergen profile, not just by product code and quantity. Whether you produce, distribute, wholesale or cater, it has to show where each lot came from, where it went, how much safe life it has left and what it contains.
The practical problem is that this information is usually spread across delivery notes, picking sheets, fridge logs and supplier specification files. That works on an ordinary day. It struggles when a supplier reports a problem lot, a customer asks for ten days of life on a chilled delivery, or a reformulation adds an allergen to a product already in your cold room.

Every delivery in or out of a food warehouse is a traceability record waiting to be made. Illustrative photograph from a US food bank warehouse, not an OpsMavix project.
Image credit: U.S. Department of Agriculture, Public Domain Mark 1.0. No edits.
Key Takeaways
- GB food businesses must identify their suppliers and business customers, so record the lot at goods in and despatch.
- Food past its use-by date is deemed unsafe; best before is about quality.
- FEFO picking should also respect each customer’s minimum remaining life.
- Temperature checks and allergen data are most useful when linked to the lot.
- A recall is faster and smaller when despatch records name the lot, not just the product.
- Choose a system approach by testing your own lots, customers and recall scenario.
In this guide:
- 1. Know Your Place in the Food Chain
- 2. Trace Lots One Step Back and One Step Forward
- 3. Treat Use By and Best Before Dates Differently
- 4. Allocate Stock by Expiry and Customer Rules
- 5. Keep Temperature Records With the Stock
- 6. Carry Allergen Information Through the Chain
- 7. Be Ready for a Withdrawal or Recall
- 8. Choose a System Approach That Fits
- Frequently Asked Questions
- How OpsMavix Can Help
1. Know Your Place in the Food Chain
Different businesses, the same core records
Much of the food industry never makes anything: it buys, stores, moves and serves food made by others. A chilled distributor, a contract caterer and a farm shop with a wholesale arm all hold dated, lot-coded stock, but the pressure points differ.
| Business type | Typical stock | Where control usually breaks |
|---|---|---|
| Producer or grower | Raw materials, packaging, finished lots | Linking input lots to output lots |
| Distributor or wholesaler | Finished goods by the case or pallet | Recording lots on picks and despatches |
| Caterer or food service | Ingredients across kitchens and sites | Transfers between sites and opened containers |
| Retailer with trade customers | Mixed consumer and trade sales | Separating business customers from consumer sales |
If you make food, our guide to food manufacturing inventory management software covers recipes, catch weights and production lots in more depth. This guide concentrates on what happens before and after production: receiving, storing, allocating, delivering and serving. In each case, the test is whether you can answer within minutes which supplier lot a case came from, which customers received it, how much life it has left and whether it is on hold.
2. Trace Lots One Step Back and One Step Forward
Know the legal baseline
In Great Britain, traceability rests on Article 18 of Regulation (EC) No 178/2002 as it applies in retained law. Food business operators must be able to identify anyone who supplied them with a food or ingredient, must have systems to identify the other businesses they have supplied, and must make that information available to the competent authorities on demand. Food placed on the market in Great Britain must be adequately labelled or identified to facilitate traceability.
The FSA and Food Standards Scotland guidance on traceability, withdrawals and recalls sets out what to record for each supplier and business customer: name and address, details of the product sufficient to identify it, the quantity supplied, and the date of the transaction and delivery.
What this means for distributors and caterers
The same guidance says records are not required where food is supplied directly to the final consumer. A caterer serving the public, or a shop selling over the counter, does not have to record each consumer. Once you supply another food business, such as a café, a care home kitchen or a school caterer, the normal one step back, one step forward rules apply.
Mixed businesses, such as a bakery with its own shop that also supplies cafés, need the system to know which sales go to businesses so those despatches carry full traceability data.
Retention and review
Unless specific legislation sets a period, the FSA guidance leaves record retention to the business, and recommends as best practice keeping traceability information on prepacked foods for the shelf life plus at least 12 months. It also recommends reviewing traceability systems at least annually, or sooner after a significant change such as a new supplier. In practice, goods in, transfers between sites, case splits, despatches, returns and write-offs should all carry the lot. For the mechanics, see our guide to batch and lot tracking.
3. Treat Use By and Best Before Dates Differently
Safety versus quality
GOV.UK guidance on best before and use-by dates states that use-by dates relate to the safety of food, while best before dates relate to quality. Article 24 of Regulation (EU) No 1169/2011, as it applies in GB, requires a use-by date on foods that are highly perishable from a microbiological point of view, and says that after the use-by date a food is deemed to be unsafe.
The FSA’s guidance on food safety for community cooking and food banks says food cannot be sold, redistributed or consumed after the use-by date, with the exception of food that has gone through a safe freezing or cooking process before the date passed. Food with a best before date can legally be sold and redistributed after that date if it is of sufficient quality.
Set system behaviour by date type
| Date type | Relates to | Suggested system behaviour |
|---|---|---|
| Use-by | Safety | Block picking, transfer and despatch once passed; alert in advance |
| Best before | Quality | Warn, apply customer minimum life rules, allow controlled clearance |
| Internal use within after opening | Your own process control | Start a new clock when a container is opened |
| Date of freezing, where applicable | Identification and control | Record against the lot when product is frozen |
If your kitchen or depot freezes chilled stock before its use-by date, record the freezing event against the lot rather than editing the original date.
Many trade customers also set a minimum remaining life on delivery. That is a contract term rather than a legal requirement, but it decides which lots can go to which customer, so hold it in the system rather than in a picker’s memory.
4. Allocate Stock by Expiry and Customer Rules
FEFO with constraints
First expired, first out (FEFO) means picking the lot with the earliest date first. In a wholesale or food service operation, plain FEFO is not enough: the earliest lot may be too short for a customer who needs seven days. The system should choose the earliest eligible lot for each order line.
Work through a hypothetical allocation
The following figures are hypothetical.
A chilled wholesaler holds one yoghurt product in two lots. Today is day 0.
| Lot | Use-by | Days of life left | Cases |
|---|---|---|---|
| Lot A | Day 6 | 6 | 60 |
| Lot B | Day 11 | 11 | 90 |
Three orders arrive for delivery tomorrow:
| Customer | Minimum life on delivery | Cases ordered |
|---|---|---|
| Contract caterer | 7 days | 40 |
| Independent retailer | 3 days | 50 |
| Café group | 4 days | 30 |
Delivered tomorrow, Lot A has 5 days left, so it is eligible for the retailer and the café group but not the caterer.
Allocated by eligible FEFO: the retailer takes 50 cases of Lot A; the café group takes the remaining 10 cases of Lot A (60 - 50 = 10) plus 20 cases of Lot B; the caterer takes 40 cases of Lot B. Lot A is fully used and 30 cases of Lot B remain (90 - 20 - 40 = 30), with 11 days of life.
Picked from the nearest pallet, which happens to be Lot B: the caterer takes 40 and the retailer 50, using all 90 cases of Lot B (40 + 50 = 90). The café group then takes 30 cases of Lot A, leaving 30 cases of Lot A (60 - 30 = 30) with only 6 days of life. At a hypothetical cost of £18 per case, those 30 cases are £540 of stock (30 × £18) at risk of write-off unless later orders absorb them before day 6.
Both approaches ship 120 cases (40 + 50 + 30). Only the rule-based allocation leaves the longest-life stock in the warehouse.
Practical allocation checklist
- Store each customer’s minimum life in days, by product group if needed.
- Calculate remaining life at the expected delivery date, not today.
- Propose the earliest eligible lot and block a scan of the wrong lot unless a reason is given.
- Report stock by days of life left so sales can act on short-dated lots early.
Pack size errors can undermine all of this, because lot quantities drift when a case is booked as a unit. Our guide to wholesale pack size management covers how to keep case and unit quantities consistent.
5. Keep Temperature Records With the Stock

Temperature checks are part of the food record, and are most useful when linked to the stock they describe. Illustrative photograph from a US school kitchen, not an OpsMavix project.
Image credit: Lance Cheung, USDA, CC BY 2.0. No edits.
The legal temperature points in England
In England, Schedule 4 of the Food Safety and Hygiene (England) Regulations 2013 makes it an offence to keep food that is likely to support the growth of pathogenic micro-organisms or the formation of toxins, and that is subject to a commercial operation, at a temperature above 8°C. It also requires cooked or reheated food kept for service or display, which needs to be kept hot, to be held at or above 63°C. Both rules have listed exemptions and defences, for example limited periods for service or display and for transfer to or from a vehicle. The schedule does not apply to operations covered by Regulation (EC) No 853/2004, and Wales, Scotland and Northern Ireland have their own regulations, so check which rules apply to each site.
Why records belong in the system
Article 5 of Regulation (EC) No 852/2004 requires food business operators to put in place a permanent procedure based on HACCP principles, including documents and records commensurate with the nature and size of the business. Temperature checks are a common part of those records.
A paper log on the cold room door shows that the room was checked, not which lots were inside when a reading was out of range. Linking checks to locations, and locations to lots, makes that question answerable.
| Check point | Record | Inventory link |
|---|---|---|
| Goods in | Product temperature on arrival, accept or reject | Lot status set at receipt |
| Cold room or freezer | Reading, time, person, corrective action | Lots in that location at that time |
| Loading and delivery | Vehicle or product temperature at despatch | Lots on that delivery |
| Kitchen service | Hot or cold holding checks | Batches prepared from which lots |
When a reading is out of range, the system should record who decided, which lots went on hold and what evidence released or rejected them. A hold status that blocks picking is more reliable than a note in a logbook.
6. Carry Allergen Information Through the Chain
What the law expects
The FSA’s allergen guidance for food businesses says businesses must tell customers if food they provide contains any of the 14 listed allergens as an ingredient. Businesses selling non-prepacked food, such as caterers, must supply allergen information for every item that contains any of the 14 allergens. The guidance also advises recording allergen information on product specifications, keeping it up to date, and storing ingredients and prepared foods separately in closed and labelled containers.
How inventory software supports it
For distributors and caterers, the risk often sits in substitution and specification change: a supplier swaps a brand or reformulates a sauce, and the allergen information your customers rely on is out of date. Practical controls include:
- An allergen profile on each product, linked to the current supplier specification and its review date.
- A flag at goods in when the received product or brand differs from the one on file.
- A rule that blocks a substitute product on a customer order until its allergen profile has been checked.
- Allergen data that follows ingredients when multi-site caterers transfer them between kitchens.
Software cannot replace segregation or kitchen procedures, but it can stop the stock record contradicting them.
7. Be Ready for a Withdrawal or Recall
Your duties when food is unsafe
Article 19 of Regulation (EC) No 178/2002 requires an operator that considers food it has handled not to comply with food safety requirements to immediately initiate withdrawal where the food has left its control, and to inform the competent authorities. Retail and distribution businesses whose activities do not affect packaging, labelling, safety or integrity must, within their activities, withdraw non-compliant products, pass on information needed to trace the food and cooperate with producers and authorities.
GOV.UK guidance on food incidents, product withdrawals and recalls says that if food you supplied is unsafe you must immediately withdraw or recall it and tell your local or port health authority, and it provides editable point of sale notice templates. You can also sign up to FSA food and allergy alerts so recall notices for products you stock reach you directly.
Work through a hypothetical distributor trace
The following trace is hypothetical.
A supplier tells a food service distributor that sliced ham lot CH-4471 may be contaminated. The distributor received 180 cases of that lot.
| Where the lot went | Cases |
|---|---|
| Care home group | 40 |
| School caterer | 25 |
| Café chain | 35 |
| Hotel kitchen | 30 |
| Despatched total | 130 |
| In stock per system | 50 |
| Total per system | 180 |
A physical count finds 46 cases in the cold room. The 4 case gap (50 - 46 = 4) is traced to a damaged pallet written off last week without a lot reference. Once that write-off is linked to CH-4471, the mass balance closes: 130 despatched + 46 in stock + 4 written off = 180.
The distributor quarantines 46 cases and contacts four business customers about 130 cases.
Now suppose despatches recorded the product but not the lot. Over the same period, the distributor shipped that ham to 11 customers, a total of 410 cases across three lots. Without lot data, all 11 customers and all 410 cases are in scope until proven otherwise. The lot record narrows the action to 4 customers and 130 cases, which is 280 fewer cases (410 - 130 = 280) to chase.
Mock recall checklist
- Pick a real lot received in the last month and trace it back to the supplier record.
- Trace it forward to every business customer, with quantities and dates.
- Count remaining stock and reconcile received, despatched, in stock and written off.
- Record the time taken and every gap found, then fix the process, not just the data.
The FSA guidance recommends reviewing recall plans annually with a mock exercise; customers and certification schemes may ask for more.
8. Choose a System Approach That Fits
Compare the options fairly
| Approach | Where it can fit | What to check |
|---|---|---|
| Configure current tools | Lot and expiry fields already exist but are unused | Whether picking can enforce lots and customer rules |
| Connect existing systems | Stock, ordering and accounts work but do not share lots | Record ownership, failed transfers, reconciliation |
| Packaged food or wholesale software | Standard distribution workflows fit your operation | Exact edition, lot handling on despatch, temperature and allergen features |
| Focused custom application | A clear gap such as goods in, holds or recall reporting | Data access, support and integration with accounts |
| Full ERP, packaged or custom | Wider finance, purchasing and multi-site needs | Implementation scope, migration, training and running costs |
Company size alone does not decide the answer. When comparing packaged products, ask each supplier to run the same tests with your data. Our guide to wholesale inventory management software sets out a practical order test you can adapt.
Acceptance checklist
- Goods in cannot complete without supplier lot, date type and date, and temperature where required.
- Every transfer, split, pick and despatch carries a lot.
- Allocation proposes the earliest eligible lot for each customer’s minimum life.
- Use-by stock is blocked once passed; held stock cannot be picked or despatched.
- Temperature checks link to locations, and out of range readings can place lots on hold.
- Allergen profiles link to current specifications, and substitutions are checked.
- A mock recall traces a lot both ways and the mass balance closes.
- Write-offs and adjustments carry lot and reason, and reach accounting correctly.
Frequently Asked Questions
What is inventory management software for the food industry?
It is stock software that records food by lot, with use-by or best before dates, status, location, temperature checks and allergen data, so producers, distributors, wholesalers and caterers can rotate stock correctly and trace any lot to its supplier and business customers.
Is lot traceability a legal requirement in the UK?
Article 18 of Regulation 178/2002, as retained in GB law, requires food businesses to identify their suppliers and the businesses they supply. Recording lots on goods in and despatch is the practical way to meet that requirement precisely and to keep withdrawals small.
Do caterers need to record which consumers they served?
No. The FSA guidance says traceability records are not required where food is supplied directly to the final consumer. Caterers still need to identify their suppliers, and full rules apply when they supply other businesses.
Can we sell food past its best before date?
The FSA says food with a best before date can legally be sold and redistributed after that date if it is still of sufficient quality. Food cannot be sold after its use-by date. Customer contracts may set stricter minimum life rules.
What temperature must chilled food be kept at in England?
Schedule 4 of the Food Safety and Hygiene (England) Regulations 2013 makes it an offence to keep relevant food above 8°C, with listed exemptions and defences. Other UK nations have their own rules, and products may carry lower storage instructions.
Can OpsMavix build food inventory software?
Yes. OpsMavix can build focused applications for lot control, allocation and traceability, or a full custom ERP, and can configure or integrate suitable existing tools where those approaches fit the requirements.
How OpsMavix Can Help
OpsMavix can map how lots, dates, temperatures and allergen data move through your goods in, storage, picking, delivery and kitchens today, then define the system scope needed to make traceability and allocation reliable.
That may mean configuring your existing tools, building an inventory automation system for lot, expiry and hold control, adding a wholesale order management system that applies customer minimum life rules at allocation, or using manufacturing production tracking where you also produce food.
Contact OpsMavix with one lot you would struggle to trace today, a recent short-dated write-off report and your customers’ minimum life requirements. We can use that evidence to define requirements and a practical pilot.
Getting value from OpsMavix? Add us as a preferred source on Google — you'll see more of our operations content in your AI Overviews, AI Mode and Search.