If you’re running a food manufacturing operation—whether you’re roasting peanuts, mixing sauces, or assembling meal kits—the moment you move beyond selling exactly what you buy, you need recipe management and batch tracking. Not because it’s nice to have. Because it’s the only way to know what you’ve made, what it cost, and where it went when a customer calls with a complaint or a food safety officer asks for records.

This guide walks through the practical setup: what recipes are, how batch tracking works, why traceability matters, and how to configure a system that handles it all without turning your operation into a paperwork factory.

Why Recipe and Batch Tracking Matters

Food manufacturing is transformation. You take raw materials—flour, sugar, meat, vegetables—and turn them into finished products. Every transformation needs a record:

Cost accuracy — You can’t price products correctly if you don’t know what goes into them.
Inventory integrity — Stock levels drift when transformations aren’t tracked in real time.
Compliance requirements — Australian food safety authorities require traceability from ingredient lot to finished batch.
Recall readiness — When a supplier issues a recall on a contaminated ingredient, you need to know exactly which finished batches used it and where those batches went.

Without recipe and batch tracking, you’re flying blind. With it, you’ve got a clear line from purchase order to customer invoice.

Recipe Management Basics

A recipe is a structured formula that defines what goes in and what comes out. In manufacturing software, recipes typically include:

Inputs (Raw Materials or Components)

Each input line specifies:

Item code — The SKU or product ID from your inventory
Quantity required — How much of the input is consumed per batch
Unit of measure — Kilograms, litres, units, etc.

Outputs (Finished Products)

Each output line specifies:

Item code — The finished product SKU
Yield quantity — How much of the finished product is produced
Unit of measure — Packs, kilograms, litres, etc.

Additional Metadata

Depending on your system, recipes may also include:

Labour time estimates — How long the transformation takes
Equipment or location requirements — Which line or facility produces the batch
Quality control checkpoints — Inspection or testing steps
Batch size — Minimum or maximum production quantities

Setting Up Your First Recipe

Let’s work through a real example: a peanut repacking operation that buys raw peanuts in 20 kg bulk sacks and produces 50 g retail packs.

Define the Inputs

You start by identifying what gets consumed:

Input Item	Quantity	Unit
Raw Peanuts (Bulk)	0.05	kg

Define the Outputs

Next, specify what gets created:

Output Item	Quantity	Unit
Roasted Peanuts 50g Pack	1	unit

Set the Recipe Ratio

The recipe says: for every 50 grams (0.05 kg) of raw peanuts consumed, you produce one 50 g retail pack. When you run a batch of 4,000 packs, the system calculates automatically:

Input consumption: 4,000 packs × 0.05 kg = 200 kg of raw peanuts
Output production: 4,000 packs

Account for Wastage or Yield Loss

Not every batch produces exactly what the recipe predicts. Shells, moisture loss, rejected units—these reduce yield. Some systems let you set a yield percentage (e.g., 95%) so the recipe accounts for expected loss.

If your recipe expects 4,000 packs but you only produce 3,800, recording the actual output quantity during batch completion keeps inventory accurate.

Batch Tracking Fundamentals

A batch is a single production run using a recipe. Each batch should be tracked as a discrete manufacturing event with:

Batch Number or ID

A unique identifier (e.g., BATCH-2026-0215-001) that links all records—material consumption, finished goods production, quality checks, and customer shipments—together.

Timestamp and Location

When and where the batch was produced. This matters for compliance and operational analysis.

Quantity Produced

The actual output, which may differ slightly from the recipe’s theoretical yield.

Status Lifecycle

Batches move through stages:

Status	Meaning
Pending	Batch is planned but production hasn’t started
In Progress	Active production is underway
Completed	Batch is finished and inventory updated
Voided	Batch was cancelled and had no inventory impact

Work Session Tracking

If you want to capture labour costs or throughput metrics, track start and stop times for each batch. Some systems include built-in timers so operators can clock in and out of production tasks.

Linking Batches to Raw Material Lots

This is where traceability gets real. When you receive a shipment of raw materials from your supplier, each delivery should be assigned a lot number or batch code—either from the supplier’s documentation or generated internally.

Lot Tracking on Receipt

When 25 × 20 kg sacks of raw peanuts arrive from GreenFields Farms, you record:

Supplier: GreenFields Farms
Product: Raw Peanuts (Bulk)
Lot number: GF-2026-W07 (supplier’s batch code)
Quantity: 500 kg
Received date: 15 February 2026

Lot Consumption During Production

When you start a manufacturing batch, the system should record which input lots were consumed. If your 4,000-pack batch uses 200 kg from lot GF-2026-W07, that linkage is recorded.

Finished Goods Lot Assignment

The finished batch of 4,000 packs gets its own lot number: RP50G-2026-0215-001. Now you have a chain:

Supplier Lot (GF-2026-W07)
  → Manufacturing Batch (BATCH-2026-0215-001)
    → Finished Lot (RP50G-2026-0215-001)
      → Customer Shipments

Traceability for Recalls

Here’s why all this matters. Imagine GreenFields Farms issues a recall notice for lot GF-2026-W07 due to potential contamination.

With proper batch and lot tracking, you can immediately:

Identify affected batches — Query which manufacturing batches consumed lot GF-2026-W07.
Find finished lots — Determine which finished goods lots were produced from those batches.
Trace customer shipments — See which customers received products from the affected lots.
Execute a targeted recall — Contact only the customers who received affected stock, rather than issuing a blanket recall.

Without batch tracking, you’d have to recall everything produced in that timeframe—or worse, have no idea where the contaminated product went.

Meeting Compliance Requirements

Australian food manufacturers must comply with the Food Standards Australia New Zealand (FSANZ) code, which includes traceability requirements under Standard 3.2.2A.

Traceability Records Required

You must be able to trace:

One step back — Which suppliers and lots you received ingredients from
One step forward — Which customers and batches you supplied finished products to

Record Retention

Traceability records must be kept for the shelf life of the product plus one year, or two years minimum—whichever is longer.

Audits and Inspections

State and territory health departments conduct inspections. Auditors will ask to see:

Supplier invoices and delivery dockets with lot numbers
Manufacturing batch records showing inputs and outputs
Finished goods inventory with lot codes
Dispatch records linking lots to customers

If you can’t produce these records within minutes, you’re at risk of non-compliance penalties.

Software Setup Walkthrough

Here’s a step-by-step process for configuring recipe management and batch tracking in a manufacturing-capable system like EQUOS9.

Step 1: Set Up Your Inventory Items

Before you create recipes, make sure all raw materials and finished products exist in your inventory module:

Raw Peanuts (Bulk) — SKU: RP-BULK, Unit: kg
Roasted Peanuts 50g Pack — SKU: RP-50G, Unit: unit

Step 2: Create the Recipe

Navigate to the Manufacture module and create a new recipe:

Recipe name: Roasted Peanuts 50g Production
Task type: Create (or Batch, depending on your workflow)
Inputs: Add RP-BULK with quantity 0.05 kg
Outputs: Add RP-50G with quantity 1 unit

Step 3: Plan a Batch

When you’re ready to produce, create a manufacturing task:

Description: Batch production - 4,000 packs
Location: Main production facility
Due date: 16 February 2026
Input quantity: Scale the recipe to 200 kg raw peanuts
Expected output: 4,000 packs

Step 4: Start Work and Track Time

Operators can start a work session timer when production begins. This captures labour time and provides an audit trail of who worked on the batch.

Step 5: Complete the Batch

When production finishes, mark the batch as completed:

Actual output: Enter the real quantity produced (e.g., 3,950 packs if some failed QC)
Lot assignment: System assigns or prompts for a finished goods lot number
Inventory update: Raw material stock decreases by 200 kg, finished goods stock increases by 3,950 units

Step 6: Link to Customer Orders

When a customer places an order for 500 packs, the system reserves stock from finished lot RP50G-2026-0215-001. On dispatch, the shipment record includes the lot number for traceability.

Practical Tips for Small Manufacturers

Start Simple

Don’t build complex multi-stage recipes on day one. Start with your highest-volume product and a single-step transformation. Once that works, expand to more complex workflows.

Automate Where Possible

Manual batch logging is error-prone. Use barcode scanners or tablet-based data entry at the production line to capture lot numbers and quantities in real time.

Don’t Skip Lot Numbers on Inputs

Even if your supplier doesn’t provide lot codes, assign them yourself on receipt. A simple format like SUPPLIER-YYYYMMDD gives you traceability without relying on external documentation.

Review Yield Variances Weekly

Compare expected recipe yields to actual output. Persistent variances indicate waste, theft, or recipe inaccuracies that need correction.

Test Your Recall Process

Run a mock recall exercise every six months. Pick a random finished lot, trace it back to input lots, and forward to customer shipments. Time how long it takes. If it’s more than an hour, your process needs tightening.

Real-World Example: Peanut Biz

Peanut Biz runs a bulk-to-retail peanut repacking operation. They buy 20 kg sacks from agricultural suppliers, roast and repack into 50 g retail packs for supermarkets and 1 kg wholesale packs for cafés.

Before implementing recipe and batch tracking:

Stock counts were guesswork
Manufacturing yields weren’t measured
Traceability was impossible
Invoices were weeks late because inventory was always wrong

After setup:

A shipment of 10 × 20 kg sacks arrives, system records lot GF-2026-W07
Manufacturing run starts, consumes 200 kg, produces 4,000 packs
Inventory updates automatically—no spreadsheet reconciliation
Customer orders ship same-day with lot traceability
Invoices generate automatically on dispatch

When a food safety audit happened, Peanut Biz pulled full traceability records in under 10 minutes. No drama, no penalties, no sleepless nights.

Common Pitfalls to Avoid

Ignoring Actual Yield

If your recipe says 4,000 packs but you only made 3,800, recording the theoretical yield instead of the actual quantity will corrupt your inventory. Always enter real output.

Batch Completion Without Lot Assignment

Completing a batch without linking it to a lot number breaks the traceability chain. Make lot assignment mandatory in your workflow.

Skipping Work Session Tracking

If you don’t track labour time, you can’t accurately calculate cost of goods sold (COGS) or identify process bottlenecks.

Not Training Operators

Batch tracking only works if production staff understand why it matters and follow the process consistently. Invest in training and spot-check compliance.

Scaling Beyond Simple Recipes

Once you’ve mastered basic recipe and batch tracking, you can expand to:

Multi-Stage Production

Complex products may require multiple steps—mixing, cooking, cooling, packaging. Each stage can be tracked as a separate task with intermediate outputs feeding into downstream batches.

Composite Items and Bills of Materials (BOM)

If you assemble products from multiple components (e.g., meal kits), set up assemblies with multi-item BOMs that consume several inputs in a single batch.

Quality Control Checkpoints

Add QC tasks between production stages to inspect batches before they proceed. Failed batches can be voided or reworked without corrupting finished goods inventory.

Automated Replenishment

When raw material stock drops below a threshold, trigger purchase orders automatically to keep production running smoothly.

Software Features to Look For

When evaluating manufacturing software, prioritise:

Recipe builder — Easy setup of multi-input, multi-output formulas
Lot tracking — Full support for input and output lot assignment
Batch lifecycle management — Pending, in progress, completed, voided statuses
Work session timers — Built-in time tracking for labour cost capture
Inventory integration — Real-time stock updates on batch completion
Traceability reporting — Forward and backward lot trace queries
Compliance-ready exports — Audit trail reports formatted for regulatory review

Conclusion

Recipe and batch tracking isn’t just paperwork—it’s the operational backbone of food manufacturing. It keeps inventory accurate, costs transparent, compliance obligations met, and recall processes fast. When you can trace a finished pack back to the supplier’s lot in seconds, you’re running a professional operation.

Start with one high-volume product. Set up the recipe. Run a batch. Track the lot. Link it to customer shipments. Once that workflow is solid, expand to the rest of your product range.

If you’re still reconciling spreadsheets or guessing at stock levels, it’s time to fix it. The software exists. The process is proven. And the cost of not doing it—lost inventory, failed audits, botched recalls—is far higher than the effort to set it up properly.

Want to see batch tracking in action? Check out the Manufacture module documentation or explore how Peanut Biz runs purchasing to invoicing in one system.