A sauce factory can make a good product and still lose control of the business.

The tomato paste came from one supplier lot. The chilli powder came from another. The recipe was adjusted because the last batch was too thin. Bottles from two packaging lots were used. The supervisor wrote the cooking temperature in a register, while the lab result lives in a spreadsheet.

Then a distributor reports swelling in a few bottles.

The first question is simple: which finished batches could be affected?

If answering that question takes hours of checking purchase bills, production notebooks, WhatsApp messages, and dispatch invoices, the factory does not have batch traceability. It has scattered records.

For sauce and condiment manufacturers, the operating system has to connect five things:

the approved recipe
the exact ingredient lots consumed
the process and quality record
the packaging and finished-goods batch
the customers who received it

Here is how to build that system without turning every production run into a data-entry project.

Why Sauce Production Is Harder to Track Than It Looks

A simple product may contain tomato paste, sugar, salt, vinegar, spices, stabilisers, preservatives, and water. But production is rarely as simple as multiplying one formula.

The team has to handle:

raw materials with different concentrations or quality characteristics
allergen and additive controls
recipe adjustments within an approved process
cooking loss and variable yield
bulk, bottle, pouch, sachet, and private-label pack sizes
quality holds before finished stock can be dispatched
shelf-life and label requirements

That means a purchase-and-sales package cannot provide the full record. It may show that 500 kg of tomato paste was purchased and 8,000 bottles were sold. It does not show which paste lot went into which bottles, which recipe version was used, or whether the batch passed its release checks.

1. Control Recipes as Versions, Not Spreadsheets

The recipe, or bill of materials, should be the approved starting point for every batch.

For each product, store:

ingredient and standard quantity
unit of measure
expected batch size
process stages and standard sequence
expected yield and an acceptable yield range
required quality checks
packaging materials for each SKU

The important part is version control.

Suppose the R&D team reduces sugar and adjusts the stabiliser after trials. Editing the old recipe in place destroys history. The next production batch should use Recipe Version 3, while batches already produced remain linked to Version 2.

Every version should have:

Field	Purpose
Version number	Distinguishes one approved formulation from another
Effective date	Controls when production may start using it
Approval status	Prevents trial recipes from reaching routine production
Change note	Explains what changed and why
Approved by	Creates accountability

Never let an operator choose ingredients from memory. The production order should load the approved recipe version automatically, while authorised deviations are recorded separately.

2. Give Every Ingredient Receipt a Lot Identity

Traceability starts at goods receipt, not during production.

When an ingredient arrives, record:

supplier
supplier batch or lot number
your internal lot number
receipt date and GRN
manufacture and expiry or best-before details where applicable
received and accepted quantity
certificate or test reference
quality status: quarantine, approved, or rejected
storage location

The stock ledger should separate lots even when the ingredient name is the same. If two chilli powder lots have different expiry dates or test results, combining them into one quantity removes the information needed later.

During issue to production, the store team selects the actual lot. FEFO, or first-expiry-first-out, can suggest the lot, but the system should preserve what was physically issued.

3. Create a Batch Manufacturing Record as Production Happens

A batch manufacturing record should tell the story of one production run.

It should include:

product and recipe version
planned and actual batch quantity
ingredients issued, by lot and actual weight
operators and equipment used
start and completion times
process readings and in-process checks
deviations, additions, or corrections
actual bulk yield
quality sample and test results
packaging run details
final released quantity

Do not wait until the end of the shift to reconstruct this record. Capture key events at the point where they happen. A shared phone or tablet with a short form is usually more reliable than asking the supervisor to re-enter a paper register later.

Receive

Create ingredient lots, attach supplier and quality details, and hold stock until accepted.

↓

Make

Open a production batch against an approved recipe and record actual ingredient consumption.

↓

Check

Capture process readings, samples, deviations, and release tests against the same batch.

↓

Pack and trace

Link packaging lots and finished batch codes, then preserve customer-wise dispatch history.

4. Separate Bulk Batch, Packing Run, and Finished SKU

One cooked batch may be packed into several formats:

1 kg food-service pouches
500 g retail bottles
20 g sachets
a private-label SKU for a customer

Treating all of these as one finished item causes confusion.

The better model is:

Bulk batch → packing run → finished SKU and batch

The bulk batch carries ingredient and process history. Each packing run adds the bottle, cap, pouch, label, or carton lots used. The finished SKU carries its batch code, quantity, and date information.

This gives the factory two-way traceability:

From a finished bottle, trace back to its packing materials, bulk batch, recipe, and ingredient lots.
From a rejected ingredient lot, find every bulk batch, finished SKU, and dispatch that may contain it.

Inventory screen for barcode and lot-level stock tracking — Lot-level inventory preserves the identity and status of ingredients instead of showing only one combined stock quantity.

5. Build Quality Gates Into the Flow

Quality checks should decide whether stock can move, not merely produce a report after it moves.

A practical sauce workflow may include:

incoming ingredient inspection
in-process readings defined by the product and process
sensory checks
fill-weight and seal checks during packing
finished-product testing
retained sample reference
quality release or rejection

The specific parameters and limits depend on the product, its category, the approved process, and applicable standards. FSSAI maintains the official food product standards and additives regulations, including category-specific requirements. Your technical and regulatory team should confirm the current standard for each SKU.

In the system, finished stock should begin in quality hold. Only an authorised approval should make it available for dispatch. A failed check should create a clear outcome: rework, downgrade, rejection, or investigation.

6. Treat Labels as Controlled Output

A label should not be a design file that someone edits before every print run.

Its variable information should come from controlled masters and the production record:

product name and variant
ingredient and allergen declarations
nutrition information
net quantity
FSSAI logo and licence number
vegetarian or non-vegetarian mark, as applicable
batch or lot code
date marking and storage instructions
manufacturer and customer-care details

The current FSSAI Labelling and Display Regulations require mandatory information for pre-packaged foods, including batch or lot identification and date marking. Because these rules are amended, use the official FSSAI labelling regulations and amendment page as the source of truth before approving artwork.

The useful software rule is simple: label data should inherit from the released batch and approved SKU master. This reduces manual typing and makes reprints auditable.

7. Be Able to Run a Mock Recall

Do not wait for a complaint to test traceability.

Choose one finished batch and ask the team to produce:

every ingredient and packaging lot used
the suppliers and receipt records for those lots
the batch manufacturing and quality record
the quantity produced, rejected, held, and dispatched
every customer and invoice that received the batch
the remaining stock by warehouse

Then run the exercise in reverse: choose one ingredient lot and identify every finished batch and customer it touched.

If the team cannot complete both directions quickly and confidently, close the data gaps before the next exercise.

A Practical Starting Setup

Small manufacturers do not need to digitise the whole factory at once.

Start with one high-volume product family:

Week 1: Clean the masters

Create ingredient, packaging, finished-product, supplier, and customer masters. Remove duplicate names and standardise units.

Week 2: Approve recipes and checks

Enter the current recipe versions, expected yields, process stages, and required quality gates.

Week 3: Track live batches

Record inward lots, actual issues, batch output, quality status, packing, and dispatch for the selected product family.

Week 4: Reconcile and test

Compare system stock with physical stock. Run a mock recall. Fix fields or steps that the team skipped.

Once that flow is reliable, add the remaining products.

Where FactoStack Fits

FactoStack connects recipe versions, ingredient lots, production batches, quality checks, packaging, finished inventory, and dispatch history in one manufacturing workflow.

Batch Traceability for Food Manufacturers

Trace ingredients from GRN to batch and finished goods from production to customer, with quality status and expiry-aware inventory at every step.

See how it works →Book a demo

Related Guides

Frequently Asked Questions

The Goal Is a Defensible Batch Story

Food manufacturing software is useful when it can answer a real operational question: what exactly happened in this batch?

The answer should connect the approved recipe, actual ingredient lots, process record, quality result, packaging run, and customer dispatch. That record makes daily production easier to control and gives the team a far stronger starting point when a complaint, audit, or recall test occurs.

Sauce and Condiment Manufacturing: How to Track Recipes, Batches, and FSSAI Compliance