ERP Software for Food Manufacturing: The Food-Specific Features Generic Systems Get Wrong

ERP software for food manufacturing lives or dies on batch traceability, shelf-life and recall speed, yet generic systems handle all three badly. If you're outgrowing spreadsheets and disconnected tools, here's how to get food-grade control without the bloat.

OpsMavix 16 min read
A food production line with batch labels and lot codes, illustrating traceability in food manufacturing ERP.

ERP software for food manufacturing has to do more than record stock, orders and invoices. It must link every ingredient lot to the batches it entered and the customers who received them, carry allergen data from supplier specification to finished label, enforce shelf life, and hold the quality evidence that proves each batch was made safely.

The practical problem is that many of those controls sit outside the system today. Lot numbers are written on batch sheets, allergen matrices live in a spreadsheet, yields are estimated once a year and temperature checks stay on a clipboard. Each gap is manageable on a normal day. On the day a supplier reports a problem ingredient, they decide how quickly and how narrowly you can respond.

Food safety inspector at work in a pork processing plant

Food ERP has to connect production records with the checks and evidence an inspector or customer may ask for. Illustrative photograph from a US processing plant, not an OpsMavix client.

Image credit: Lance Cheung, USDA, Public Domain Mark 1.0. No edits.

Key Takeaways

  • UK food law requires you to identify your suppliers and business customers; internal batch links are what make that information precise.
  • Allergen data should flow from supplier specifications through recipes to label versions, with changes controlled.
  • Shelf life needs a date on every lot and picking rules that use it, not a manual note.
  • Recipe yields drive real batch costs, so record actual output against the theoretical yield.
  • Catch weight, HACCP records and hold or release status need designing in, not adding after go-live.
  • Test any system with a full recall exercise and a mass balance before you commit to it.

In this guide:

1. Understand What Food ERP Has to Control

Start with the lot, not the product code

General manufacturing ERP is usually organised around items, bills of materials and production orders. Food manufacturing needs the same foundations, but the meaningful unit is the lot or batch: a specific quantity received, made or packed together, with its own dates, supplier, test results and status.

Two pallets of the same product code can be very different things. One may be on hold awaiting a micro result; the other may be released with nine days of life left. A system that only knows the product code and a quantity cannot make that distinction, so people make it outside the system.

Map the food requirements to system controls

Food requirement What the ERP must hold Control to demonstrate
Traceability Supplier, customer, lot, quantity and dates for every movement Trace a lot backwards and forwards from one screen or report
Allergen management Allergen data per raw material, recipe and label version A recipe change flags the affected labels and products
Shelf life Date type and expiry per lot, minimum life rules per customer Picking proposes the earliest expiring eligible lot
Recipe and yield Versioned formulas, theoretical yield, actual output Batch cost uses actual consumption and output
Catch weight Nominal count plus actual weight per unit or case Stock, invoice and cost agree on the weight basis
Quality and HACCP Checks, limits, results and corrective actions per batch A batch cannot be released while a required check is missing

These rows are the core of a food requirements specification. For the stock side of the same problem, our guide to inventory management software for the food industry covers batch picking and warehouse control in more depth.

2. Trace Lots One Step Back and One Step Forward

Know the legal baseline

In Great Britain, traceability rests on Article 18 of retained Regulation (EC) No 178/2002. Food business operators must be able to identify who supplied them with a food or ingredient and which businesses they 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 its traceability.

The FSA and Food Standards Scotland traceability, withdrawals and recalls guidance lists the information to record: the name and address of the supplier or customer, product details and quantity, and the date of the transaction and delivery. It describes internal traceability, linking raw material batches to production batches, as recommended good practice rather than a legal requirement, and states that defining batches is essential for good traceability.

Why internal links matter in an ERP

The legal minimum is one step back and one step forward. Without internal links, though, a problem with one ingredient lot can only be answered by listing every customer who bought any product that might contain it. Internal traceability is what turns “every customer this month” into “these three customers and these quantities”.

In system terms, that means:

  1. Goods in captures supplier, supplier lot, quantity, date and your own internal lot reference.
  2. Production consumes specific lots, not just quantities of an item.
  3. Rework, part pallets and returned stock keep their lot history.
  4. Despatch records the finished lots sent to each customer.
  5. Corrections are audited rather than overwritten.

Set a retention rule

The FSA guidance says businesses decide how long to keep records unless specific legislation sets a period, and recommends as best practice that records for prepacked food are kept for the shelf life of the food plus at least 12 months. Configure archiving to match your own decision, and make sure archived records can still be searched quickly.

3. Control Allergens From Specification to Label

Know what the label must show

The FSA’s allergen labelling guidance for food manufacturers lists the 14 allergens that must be declared when used as an ingredient or processing aid in prepacked food: celery, cereals containing gluten, crustaceans, eggs, fish, lupin, milk, molluscs, mustard, tree nuts, peanuts, sesame seeds, soybeans, and sulphur dioxide and sulphites above 10 parts per million. Allergenic ingredients must be emphasised every time they appear in the ingredients list, for example in bold.

The same guidance says precautionary statements such as “may contain” should only be used after a thorough risk assessment, where the risk of cross-contamination is real and cannot be removed. It also recommends scheduling production from least to most allergenic where separate facilities are not possible.

Make the ERP carry the allergen chain

Stage Record to hold Failure the control prevents
Supplier approval Specification and allergen declaration per raw material Accepting a substitute ingredient with an undeclared allergen
Goods in Received item matched to the approved specification A different supplier’s version entering stock unnoticed
Recipe Allergens rolled up from every ingredient and sub-recipe Manual matrices drifting from the live formula
Label Label version tied to recipe version Old packaging used after a recipe change
Scheduling Allergen profile per run and changeover rule A high-allergen run scheduled before a free-from product
Despatch Label and lot checks before release Product leaving in the wrong packaging

The most important control is change management. When a supplier changes a specification, the system should list every recipe, label and finished product affected, and hold the change until someone responsible approves it.

4. Enforce Shelf Life and FEFO

Hold dates on the lot

First expired, first out (FEFO) means consuming or despatching the lot with the earliest expiry first. It only works when every lot has a reliable date and status. The ERP should record the date type you apply, how the date was calculated, and whether the lot is released, on hold or rejected.

Apply customer rules as well as stock rules

Many customers set a minimum remaining life on delivery. That is a commercial term in your agreements rather than a legal rule, but the system has to respect it. A lot can be the right one to use first and still be ineligible for a particular customer’s order.

Practical shelf life controls include:

  • Calculated expiry from production date and product life, with manual override audited.
  • Pick proposals that skip held lots and lots below the customer’s minimum life.
  • Alerts for lots approaching expiry while there is still time to use or sell them.
  • Raw material expiry checked before issue to production.
  • Reports that show stock by remaining life, not just by quantity.

5. Keep Quality and HACCP Records With the Batch

Know the requirement

Article 5 of retained Regulation (EC) No 852/2004 requires food business operators to put in place, implement and maintain a permanent procedure based on HACCP principles. Those principles cover identifying hazards and critical control points, setting critical limits, monitoring, corrective actions, verification, and keeping documents and records appropriate to the nature and size of the business. The FSA’s managing food safety guidance also says records should be kept up to date and reviewed so they match how you actually work.

Decide which records belong in the ERP

You do not have to run your whole food safety management system inside ERP. The useful test is whether a record changes what can happen to a batch. If a failed metal detector check or an out of limit cook temperature should stop release, that check needs to be linked to the batch and visible to the system that controls release.

Inspectors checking the temperature of chicken carcasses at a processing plant

Temperature checks at critical control points are only useful evidence when they are linked to the batch they cover. Illustrative photograph from a US processing plant, not an OpsMavix client.

Image credit: Lester Shepherd, USDA, Public Domain Mark 1.0. No edits.

Record Link it to System effect
CCP monitoring result Batch, line, time and operator Out of limit result places the batch on hold
Corrective action The failed check and the batch Release requires the action to be closed
Goods in inspection Supplier lot and internal lot Failed inspection blocks issue to production
Laboratory result Batch or sample reference Positive or pending result keeps stock on hold
Allergen changeover clean Line and following run Next run cannot start until the clean is signed off
Complaint Finished lot and customer Repeated complaints are visible by lot and supplier

Paper or a separate quality app can still work if it records the batch reference and the release decision reaches the ERP reliably. What fails is a release process that never checks whether the evidence exists.

6. Manage Recipes, Yields and Batch Costs

Version the formula

A food recipe is more than a bill of materials. It has a batch size, scaling rules, sub-recipes, permitted substitutions, a theoretical yield and process losses from cooking, trimming or evaporation. Each change should create a new version with an effective date, so a batch can always be traced to the formula actually used.

Work through a hypothetical yield and cost example

The following figures are hypothetical and exclude labour, energy and overheads.

A manufacturer makes a tomato sauce in batches of 82 kg of ingredients:

Ingredient Quantity Cost per kg Cost
Tomatoes 60 kg £1.20 £72.00
Onions 15 kg £0.80 £12.00
Olive oil 5 kg £6.00 £30.00
Garlic 1 kg £5.00 £5.00
Salt and herbs 1 kg £4.00 £4.00
Total 82 kg £123.00

The recipe assumes an 85% yield after cooking, so the theoretical output is 82 kg × 85% = 69.7 kg. The batch is filled into 350 g jars, so the standard cost assumes 199 full jars (69.7 kg ÷ 0.35 kg = 199.1).

On a real batch, the operator records 66.0 kg of finished sauce, an actual yield of about 80.5%. That fills 188 jars (66.0 kg ÷ 0.35 kg = 188.6).

Measure Theoretical Actual
Output 69.7 kg 66.0 kg
Ingredient cost per kg of sauce £1.76 £1.86
Full jars 199 188
Ingredient cost per jar £0.62 £0.65
Cost per jar including £0.30 jar, lid and label £0.92 £0.95

The difference looks small per jar, but it is 11 jars per batch. Over a hypothetical 40 batches, that is 440 jars that were costed but never made. An ERP that only backflushes the standard recipe would hide that gap; one that records actual output shows it on every batch and lets you compare yield by line, shift or ingredient lot.

The same record also supports traceability. The batch shows which tomato and oil lots were consumed, so cost, yield and recall data come from one transaction rather than three. Our guide to food and beverage manufacturing software looks more closely at capturing yield and waste on the production floor.

7. Handle Catch Weight and Variable Packs

Understand the two units

Catch weight means an item is counted in one unit and valued or invoiced by its actual weight. A case of fillets, a whole cheese or a side of meat may be ordered as one case, but its weight varies. The ERP needs to hold both the count and the actual weight for each case or unit, and keep them together through stock, production, despatch and invoicing.

Work through a short hypothetical example

A customer orders three cases of a product with a nominal 5 kg weight, priced at a hypothetical £6.40 per kg. The cases weigh 5.12 kg, 4.96 kg and 5.07 kg, a total of 15.15 kg. Invoiced on actual weight, the order is 15.15 kg × £6.40 = £96.96, compared with £96.00 if the system assumed the nominal weight. Stock must also reduce by 15.15 kg, not 15 kg, or the stock valuation drifts away from reality.

Check packed quantity rules separately

Fixed weight packs are a different question. The Office for Product Safety and Standards guidance on packaged goods weights and measures regulations explains the average quantity system, including the requirement that contents must not be less on average than the nominal quantity and that packers keep records of checks. If your checkweighers or fill records feed the ERP, decide where those records are held and who reviews them.

Requirement Questions to ask a supplier
Dual units Can stock be held as count and weight at the same time?
Weighing integration Can scale or label printer data post weights without re-keying?
Pricing Can price lists, orders and invoices use price per kg with actual weights?
Costing Does production cost use actual weights consumed and produced?
Tolerances Can you set acceptable weight ranges and flag exceptions?

8. Run a Recall Exercise Before You Commit

Use the FSA guidance as the test design

The FSA guidance recommends reviewing traceability systems at least annually, or after significant changes such as a new supplier, and reviewing withdrawal and recall plans annually, including a mock exercise. The FSA’s food incidents, product withdrawals and recalls guidance says unsafe food must be withdrawn or recalled immediately and the competent authority informed. Your customers or certification scheme may set their own test frequency and timing, so confirm those requirements directly.

Work through a hypothetical mass balance

The following trace is hypothetical.

A supplier reports a problem with a 200 kg lot of sesame paste. The trace should account for every kilogram:

Where the lot went Quantity Forward result
Production batch A 80 kg 400 units: 250 to customer X, 100 to customer Y, 50 in stock
Production batch B 70 kg 350 units: 300 to customer Z, 50 in stock
Remaining raw material 45 kg Quarantine in stock
Recorded waste 5 kg Disposal record
Total accounted 200 kg 650 units shipped to 3 customers, 100 units held

If the records only accounted for 190 kg, the missing 10 kg would need investigating before you could be confident the withdrawal was complete. That gap is often more revealing than the time the trace took.

Compare the system approaches on the same test

Approach Where it can fit What to check
Configure current tools Lot and expiry features exist but are not enforced Mandatory fields, permissions and whether users can bypass them
Connect existing systems Separate quality, scale or label systems already work Shared lot references, failed transfer handling and reconciliation
Packaged food ERP Established food workflows match your process Exact modules, catch weight support, configuration and licence scope
Focused custom application One gap, such as batch records or traceability, is clear Integration with finance and stock, support and data ownership
Full ERP, packaged or custom Several processes need replacing together Migration, training, testing capacity and long term support

Ask each supplier to run the same hypothetical recall, the same recipe change and the same catch weight order with your data. For wider manufacturing scope beyond food, see our guide to ERP software for the manufacturing industry.

Acceptance checklist

  1. Goods in cannot be completed without a supplier lot and expiry where required.
  2. Production records consume specific lots and record actual output.
  3. A backward and forward trace runs from any lot, including rework.
  4. The mass balance accounts for the full lot quantity.
  5. A supplier specification change identifies affected recipes and labels.
  6. Picking follows FEFO and respects customer minimum life rules.
  7. A failed quality check places the batch on hold.
  8. Catch weight orders invoice and relieve stock on actual weight.
  9. Held, released and rejected statuses are visible to planning, warehouse and sales.
  10. Records can be exported for inspectors, customers and auditors.

Frequently Asked Questions

What is ERP software for food manufacturing?

It is an integrated system for running a food manufacturing business that adds food controls to standard ERP functions: lot traceability, allergen data, shelf life, recipe and yield management, catch weight and links to quality records.

Is batch traceability a legal requirement in the UK?

Identifying your suppliers and business customers is a legal requirement under retained Regulation 178/2002, Article 18. The FSA describes internal traceability between raw material and finished batches as recommended good practice, and it is what makes a withdrawal precise.

How long should we keep traceability records?

The FSA guidance leaves the period to the business unless specific legislation applies, and recommends keeping records for prepacked food for the shelf life plus at least 12 months as best practice.

Does the ERP have to print allergen labels?

Not necessarily. It should hold the allergen data and the recipe and label versions, and pass accurate data to whichever labelling system you use. The key control is that a recipe or specification change cannot go live without the affected labels being reviewed.

Do we need HACCP records inside the ERP?

Not all of them. Link the records that should affect batch release, such as critical control point results, corrective actions and laboratory holds. Other food safety documents can stay in a dedicated system if the batch reference connects them.

Can a generic ERP handle food manufacturing?

Some can with configuration and add ons, particularly for lot tracking and expiry. Test catch weight, allergen roll up, yield recording and the recall exercise with your own data before assuming the features fit.

How OpsMavix Can Help

OpsMavix can map how lots, recipes, quality checks and despatch records move through your operation today, and define the system scope needed to make traceability, yield and release decisions reliable.

That may mean configuring your existing tools, connecting quality, scale or label systems, building manufacturing production tracking with batch records and yield, adding an inventory automation system for lot and expiry control, or developing a full custom ERP.

Contact OpsMavix with your last mock recall, one recipe with its recorded yields and the step where lot information is most often re-keyed. 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.

Free · built for your business

Don't see your business in our demos?We'll build one for yours. Free.

Book a call with us and we'll build a demo for your business, for free. Not a generic tour: your products, your steps and your numbers, running on screen before you decide anything.

Free 30-min call first. If we're a fit, we build it and show it to you. No card, no pitch.

  1. 1
    Book a free call30 minutes. We learn how your business runs.
  2. 2
    We build your demoAround your products, your steps, your numbers.
  3. 3
    You see it runningYour own operation on screen. Then you decide.
WhatsApp us