Food and Beverage Manufacturing Software: Running the Production Floor, Not Just the Ledger
Most tools sold as food and beverage manufacturing software are really accounting or stock ledgers with a food label. This guide is about the other job — running the production floor: recipes and BOMs, batch runs, yield and waste, shelf life and quality checks on the line. It's written for makers who are outgrowing spreadsheets and disconnected tools.
Food and beverage manufacturing software is the system that runs the production floor: it holds approved recipes, issues batches against them, records what was actually weighed, made and checked, and passes the result to stock, labelling and costing. The ledger tells you what a batch cost after the fact; the floor system records how it was made while it was being made.
The practical problem is that this layer is usually the last to leave paper. Recipes live in a spreadsheet, the day’s run order sits on a whiteboard, batch sheets and temperature checks are on clipboards by the mixer, and yields are worked out at month end. Each piece works on its own. The trouble starts when a label needs updating after a recipe change, a run overruns because of an unplanned allergen clean, or a margin slips and nobody can say which batches caused it.

Production floor software has to work for the people weighing, mixing, checking and packing, not only for the office. Illustrative photograph, not an OpsMavix project.
Image credit: Walter Otto, Unsplash License. No edits.
Key Takeaways
- The recipe is the master record: version it, approve changes and make every batch reference the version it used.
- A batch production record should capture actual weights, lots, times, checks and sign-offs, not just a completed tick.
- Allergen sequencing is a scheduling rule; modelling it can remove unnecessary full cleans from the day.
- Yield, waste and pack giveaway are separate losses and need recording separately to be fixed.
- HACCP monitoring results that should stop release belong with the batch, linked to whatever system controls release.
- Label data and batch costs should be calculated from the same recipe data the floor uses.
In this guide:
- 1. Understand the Production Floor Job
- 2. Control Recipes and Formulations
- 3. Build Reliable Batch Production Records
- 4. Schedule Runs and Allergen Changeovers
- 5. Measure Yield Waste and Giveaway
- 6. Capture QC Checks and HACCP Records
- 7. Keep Label Data Tied to the Recipe
- 8. Link Production to Costing
- Frequently Asked Questions
- How OpsMavix Can Help
1. Understand the Production Floor Job
Separate the floor from the ledger and the warehouse
Food businesses often buy software in three overlapping layers. A food ERP joins finance, purchasing, sales and stock; our guide to ERP software for food manufacturing covers recall testing, catch weight and the wider food controls. Inventory software controls lots, expiry and movements; see food manufacturing inventory management software for lot genealogy and shelf life. This guide covers the layer between them: what happens from the moment a batch is planned to the moment it is packed and released.
The floor layer can be an ERP module, a specialist application or a focused custom system. What matters is that people on the line actually use it.
Map the records the floor creates
| Floor activity | Record it creates | Who relies on it |
|---|---|---|
| Recipe and formulation control | Approved recipe version, specification and process steps | Production, technical, labelling, costing |
| Weighing and dispensing | Actual weights and ingredient lots per batch | Production, traceability, costing |
| Scheduling | Run order, line, allergen profile and changeover type | Planning, hygiene, production |
| Processing and QC | Temperatures, times, test results and corrective actions | Technical, quality, auditors |
| Packing | Output count and weight, label version, pack checks | Despatch, quality, costing |
| Batch close | Yield, waste by reason, sign-offs and release status | Planning, finance, management |
A row kept on paper becomes a problem when another team needs the record quickly and has to retype or chase it.
2. Control Recipes and Formulations
Treat the recipe as a controlled document
In food production the recipe is more than a bill of materials. It carries the formulation, the batch size, process steps and limits, the expected yield, the packaging, and the allergen and nutrition data that flow to the label. When the real recipe lives in a supervisor’s head or in a spreadsheet tab called “final v3”, every downstream record inherits the uncertainty.
A recipe module should hold versions with an effective date and approver, sub-recipes such as premixes or fillings, approved substitutions, scaling rules, and links to supplier specifications so a specification change identifies the affected recipes. For the general discipline of change control on product structures, our guide to bill of materials management explains approval and effectivity in more depth.
Work through a hypothetical scaling example
The following figures are hypothetical.
A maker of baked oat bars has an approved 50 kg base recipe and needs a 120 kg batch, a scale factor of 120 ÷ 50 = 2.4.
| Ingredient | Base recipe | Scaled batch (× 2.4) |
|---|---|---|
| Oats | 25.0 kg | 60.0 kg |
| Butter | 10.0 kg | 24.0 kg |
| Syrup | 8.0 kg | 19.2 kg |
| Dried apricots | 7.0 kg | 16.8 kg |
| Total | 50.0 kg | 120.0 kg |
The software should produce this weigh sheet automatically, check that enough released stock exists for each line, and reserve it so a second batch cannot claim the same apricots. The same oat bar is used in every worked example below, so the numbers connect.
3. Build Reliable Batch Production Records
Record what happened, not just what was planned
A batch production record is the evidence of one production run: the recipe version issued, the ingredient lots and actual weights used, the equipment and line, the process readings, the people who did and checked each step, and the output. A record that only says “batch completed” with a signature cannot answer the questions that matter afterwards.
The minimum useful content is:
| Section | What to capture | Control worth enforcing |
|---|---|---|
| Issue | Batch number, recipe version, planned quantity, line | Only the current approved version can be issued |
| Weigh and dispense | Ingredient, lot, target weight, actual weight, tolerance | Out of tolerance weights need a reason or approval |
| Process | Times, temperatures, speeds and test results at defined steps | Readings outside limits trigger a corrective action |
| Pack | Label version, pack date code, output count and weight | Label and date code checked at start and after changes |
| Close | Actual output, waste by reason, sign-offs | Batch cannot close with required fields missing |
Connect batch records to traceability
Article 18 of retained Regulation (EC) No 178/2002 requires food business operators to be able to identify who supplied them and the businesses they supplied, and to make that information available to the competent authorities on demand. The batch record is where ingredient lots meet finished batches, which lets you narrow a trace to specific batches. On the floor, the job is to make lot capture part of weighing, ideally by scanning the lot label and reading the weight from a connected scale, rather than a separate step.
4. Schedule Runs and Allergen Changeovers
Use the official sequencing advice
The Food Standards Agency’s allergen labelling guidance for food manufacturers lists the 14 allergens that must be declared and suggests that, where separate facilities are not possible, you try scheduling production in order of least allergenic to most allergenic. It also says to develop and follow suitable cleaning regimes, and to remove packaging at the end of a production run.
A scheduling tool can turn that advice into a rule. Give each product an allergen profile from its recipe, give each pair of products a changeover type, and let the schedule show the total changeover time before the day starts.
Work through a hypothetical changeover example
The following products, profiles and times are hypothetical; your own cleaning validation decides the real rules.
Four oat bar variants run on one line. The rule used here: if the next product contains every allergen present in the previous one, a 30 minute standard clean is used; otherwise a 120 minute full allergen clean is needed.
| Product | Allergen profile |
|---|---|
| P1 Apricot bar | Cereals containing gluten (oats) |
| P2 Yoghurt coated bar | Gluten, milk |
| P3 Sesame bar | Gluten, sesame |
| P4 Peanut and milk chocolate bar | Gluten, milk, peanuts |
Run in order-book sequence P4, P1, P3, P2, the changeovers are full (120) + standard (30) + full (120) = 270 minutes. Re-sequenced as P1, P2, P4, P3, they are standard (30) + standard (30) + full (120) = 180 minutes, saving 90 minutes of line time on the same day’s work.
One full clean remains because the sesame and peanut products do not nest inside each other. That is the useful insight: a schedule built on allergen profiles shows which clean is unavoidable and which ones were caused by order sequence alone.
Make the changeover a recorded step as well: the clean type, who cleaned and checked it, any verification your procedure requires, confirmation that the previous product’s labels and film were cleared, and a block on starting the next batch until all of that is complete. Our guide to production planning and control tools covers capacity and scheduling beyond food.
5. Measure Yield Waste and Giveaway
Separate the three losses
Yield, waste and giveaway are often blended into one “we made less than expected” figure, which makes them impossible to fix. Yield compares actual output with the recipe’s expected output. Waste is material lost with a recorded reason: trim, rejects, spills, start-up product. Giveaway is product sent out above the declared pack weight.
Giveaway is shaped by law as well as cost. The government’s packaged goods weights and measures guidance sets out the average quantity system, including the rule that package contents must not be less on average than the nominal quantity, and says records of any checks undertaken must be kept. Many packers therefore set a target fill above nominal; the commercial question is how far above.

Yield and giveaway are decided on the line, one unit at a time, so they need recording there. Illustrative photograph, not an OpsMavix project.
Image credit: Juno Jo, Unsplash License. No edits.
Work through a hypothetical yield and giveaway example
The following figures are hypothetical.
The 120 kg oat bar batch has an expected yield of 90% after baking, so 120 kg × 90% = 108 kg of packed bars. Bars have a 40 g nominal weight and a 41 g target fill, so the plan is 108 kg ÷ 0.041 kg = 2,634 bars.
The batch record shows 103.2 kg packed at an average of 42 g per bar, which is 103.2 ÷ 0.042 = 2,457 bars. Actual yield is 103.2 ÷ 120 = 86%.
| Loss against plan | Quantity |
|---|---|
| Expected packed output | 108.0 kg |
| Actual packed output | 103.2 kg |
| Shortfall | 4.8 kg |
| Recorded edge trim | 2.4 kg |
| Recorded broken bar rejects | 1.5 kg |
| Unexplained | 0.9 kg |
Separately, the bars averaged 1 g above the 41 g target. Across 2,457 bars that is 2,457 × 1 g = about 2.5 kg of extra giveaway, roughly 60 bars at the target weight.
Each line points to a different fix: trim settings, handling, the weigh-in and depositor settings. A month-end yield percentage would show none of them.
To make this routine, require actual output and a fixed list of waste reasons before a batch can close, pull pack weights from checkweighers or sample checks, and report yield and giveaway by product, line, shift and recipe version.
6. Capture QC Checks and HACCP Records
Know the legal requirement
Article 5 of retained Regulation (EC) No 852/2004 requires food business operators to put in place, implement and maintain a permanent procedure or procedures based on HACCP principles. Those principles include critical control points, critical limits, monitoring, corrective actions, verification, and documents and records commensurate with the nature and size of the business. The FSA’s managing food safety guidance adds that procedures should be reviewed regularly so they reflect what you produce and how you work.
Many manufacturers also hold certification to a customer-required standard. BRCGS states that its Global Standard Food Safety specifies the safety, quality and operational criteria required in a food manufacturing organisation; Issue 9 has been used for audits since 1 February 2023, and BRCGS reports that Issue 10 is still in development. Check the exact clauses that apply to you in the standard itself and with your certification body; software supports compliance but does not provide it.
Put the checks where the work happens
| Check type | Example on an oat bar line | System behaviour |
|---|---|---|
| CCP monitoring | Metal detector test pieces at start, set intervals and end | Missed or failed test holds output since the last good check |
| Process control | Oven temperature and belt speed | Out of range reading prompts a corrective action |
| Quality attribute | Bar weight, colour, moisture | Results trend by batch and shift |
| Label and date code | Correct label version and date on first pack and after reel changes | Batch cannot continue until confirmed |
| Allergen clean | Changeover clean sign-off | Next batch cannot start until signed |
The FSA allergen guidance says to ensure the correct labels are applied to products and outer packaging. A start-up check that scans the label against the batch’s recipe version is a simple guard. When any check fails, the corrective action and the decision about affected product should sit with the same batch.
7. Keep Label Data Tied to the Recipe
Know which label data comes from production
Article 9 of retained Regulation (EU) No 1169/2011 lists the mandatory particulars, including the name of the food, the list of ingredients, allergens, the quantity of certain ingredients, the net quantity, the date of minimum durability or use by date, storage conditions, the food business operator’s name and address, and a nutrition declaration. Article 21 requires allergens in the ingredients list to be emphasised through a typeset that clearly distinguishes them, for example by font, style or background colour.
Several of those particulars are calculated from the recipe: the ingredients list order, allergen declaration, quantitative ingredient declarations and nutrition. When the recipe and the label data are maintained separately, a recipe change can leave the label behind.
Work through a hypothetical QUID example
The following figures are hypothetical and illustrate the calculation only; check the rules that apply to your product with the legislation and your technical adviser.
Annex VIII of the same regulation says the quantity of an ingredient is expressed as a percentage corresponding to its quantity at the time of use, and that for foods which have lost moisture through heat treatment or other treatment, it is related to the finished product.
In the 120 kg oat bar batch, dried apricots are 16.8 kg. At the time of use that is 16.8 ÷ 120 = 14.0% of the mix. Baking brings the standard output to 108 kg, so related to the finished product the apricots represent 16.8 ÷ 108 = 15.6%.
Storing input weights and the standard finished weight on the recipe makes the calculation repeatable. If batch records show actual yields drifting from the standard, the technical team should review the figure.
Link each label version to the recipe version it describes, block a new recipe version until its label data has been reviewed, and record the label version on every batch.
8. Link Production to Costing
Cost the batch you actually made
Standard costs are useful for quoting and planning. They become misleading when nobody compares them with batch actuals. Once batch records hold actual weights, times and output, the cost of each batch can be calculated rather than assumed. Our guide to job costing software for manufacturing covers the same principle outside food.
Work through a hypothetical batch cost
The following prices and rates are hypothetical and exclude energy and overheads.
Ingredient cost for the 120 kg batch is 60 kg oats at £1.10 (£66.00) + 24 kg butter at £6.50 (£156.00) + 19.2 kg syrup at £1.40 (£26.88) + 16.8 kg apricots at £5.20 (£87.36) = £336.24. The standard allows 3.0 hours for two operators at £14.00 an hour, which is £84.00. The changeover overran, and the batch record shows 3.5 hours, which is £98.00. Packaging is £0.05 per bar.
| Measure | Standard | Actual |
|---|---|---|
| Ingredients | £336.24 | £336.24 |
| Labour | £84.00 | £98.00 |
| Bars packed | 2,634 | 2,457 |
| Ingredients and labour per bar | £0.160 | £0.177 |
| Cost per bar including packaging | £0.210 | £0.227 |
The actual cost is about £0.017 a bar higher, or about £42 across the 2,457 bars made. The breakdown matters more than the total: 177 fewer bars from yield loss and giveaway, and 30 extra minutes of labour from the overrun.
Choose a fitting system approach
| Approach | Where it can fit | What to check |
|---|---|---|
| Configure current tools | Recipe, batch or QC features exist but are unused or optional | Mandatory fields, permissions and whether users can bypass them |
| Connect existing systems | Scales, checkweighers, label printers or a QC app already work | Shared batch references, failed transfer handling and reconciliation |
| Packaged food production software | Its batch, recipe and QC workflows match your process | Exact modules, line-side usability, licence scope and data export |
| Focused custom application | One gap, such as batch records or changeover scheduling, is clear | Integration with stock and finance, support and data ownership |
| Full ERP, packaged or custom | Several processes need replacing together | Migration, training, testing capacity and long term support |
Ask each option to run the same scenario with your data: scale a recipe, weigh a batch with one out of tolerance ingredient, sequence four products with allergen changeovers, record a failed CCP check, close the batch with waste reasons and show the batch cost.
Pilot acceptance checklist
- Only the current approved recipe version can be issued to a batch.
- Actual weights and ingredient lots are captured at the weigh station.
- The schedule shows changeover types and total changeover time.
- A changeover cannot be skipped without sign-off.
- A failed CCP or label check holds the affected output.
- Batches cannot close without actual output and waste reasons.
- Label data is calculated from the recipe and versioned with it.
- Batch cost uses actual consumption, time and output.
- Reports compare yield, giveaway and cost by product and line.
- Records can be exported for auditors, customers and finance.
Frequently Asked Questions
What is food and beverage manufacturing software?
It is software that runs the production side of a food or drink business: recipe and formulation control, batch production records, scheduling, yield and waste, quality and HACCP records, and the data that feeds labels and batch costs. It may be a module of a food ERP or a separate system connected to one; some ERPs cover the floor well, others leave it on paper.
Do HACCP records have to be digital?
The law requires HACCP-based procedures and records commensurate with the nature and size of the business; it does not require a particular format. Digital records help most where a check should stop a batch or where records must be found quickly.
How should allergen changeovers be scheduled?
FSA guidance suggests scheduling from least to most allergenic where separate facilities are not possible. Software helps by holding each product’s allergen profile and changeover rules so the run order and total cleaning time are visible before the day starts.
What is the difference between yield and giveaway?
Yield compares actual output with expected output. Giveaway is product supplied above the declared pack weight. Both reduce the number of saleable packs, but they have different causes and fixes, so record them separately.
Can the software produce our labels?
It can calculate and hold the label data, such as the ingredients list, allergens, quantitative declarations and nutrition, and pass it to a label system. Your technical team should still review and approve label content.
Can OpsMavix build food and beverage manufacturing software?
Yes. OpsMavix can build focused production applications 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 recipes, batch records, run schedules, quality checks and label data move through your production floor today, and define the system scope needed to make them reliable.
That may mean configuring your existing tools, connecting scales and label printers, building manufacturing production tracking with batch records, yield and changeovers, adding an inventory automation system for ingredient lots, or developing a full custom ERP.
Contact OpsMavix with one completed batch sheet, the recipe it was made from and a recent day’s run order. 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.