· Codemax · 7 min read
Batch traceability, explained for F&B operators
What a batch code is, what to record from supplier receipt to the bin, and how to test the whole chain with a mock recall before you ever need a real one.
TL;DR
Batch traceability links every batch of food to the batches it was made from and every place it was sent, so it can be traced one step back to suppliers and one step forward to outlets and sale windows. For F&B operators, it depends on recording batch codes at receipt, production, dispatch, outlet receipt, use and wastage, and testing the chain with regular mock recalls.
- Record which batch came in and which went out at every step, including inside the kitchen.
- The production batch ticket links raw materials to finished goods; without it the chain stops.
- Smaller, unmixed batches mean smaller, more precise recalls.
- Run a quarterly mock recall and balance the quantities, not just the names.
- Decanting, topped-up containers and handwritten labels are where chains usually break.
Batch traceability is the ability to take any batch of food and say quickly what went into it and where every portion of it went. For an F&B operator with a central kitchen, it rests on one habit: at every step, record which batch came in and which batch went out, so the chain can be followed one step back and one step forward.
It builds on yesterday’s post on what the Lenggong food poisoning case means for central kitchens. The cause of that case has not been established; this piece is about a capability every central kitchen benefits from having in place before anything goes wrong.
What is batch traceability?
Batch traceability is the record-keeping that links each batch of food to the batches it was made from and to every place it was sent, so any batch can be traced backward to its source and forward to its customers. A few terms make the rest easier.
Batch (or lot). A quantity of product received or made under the same conditions: one supplier delivery, one production run, one date. Everything in a batch is treated as a single unit for tracing. Lot tracking is the same idea under a different name.
Batch code. The identifier on the label that links the physical product to its record. At receipt it is the supplier’s code; from production onwards it is your own.
Backward trace. Starting from a finished product, a complaint or an outlet, and working back to the raw-material batches and the suppliers behind them.
Forward trace. Starting from a raw-material batch, and working forward to every product made from it, every outlet that received those products and when they were sold.
One step back, one step forward. The working principle: at every handover, record who you got the batch from and who you gave it to. Join those records end to end and you have a chain. Central kitchen traceability adds the step in the middle: which input batches went into which output batch.
What should you record at each step?
The table lists the minimum record at each step of a central-kitchen-to-outlet operation, and why it matters if a food recall ever comes.
| Step | What to record | Why it matters in a recall |
|---|---|---|
| Supplier receipt | Supplier, item, supplier batch code, expiry, quantity, date, who received it | Links a supplier’s recall notice to the exact stock you hold |
| Storage | Location and any move between stores; batch code kept on the container | Tells you where to look and what to quarantine |
| Production (batch ticket) | Recipe and version, input batches and quantities, output quantity, your new batch code, date, who made it | The link between raw-material batches and finished batches |
| Semi-finished goods | Batch code and production date on every tray, tub or bag; which later batches used it | One sauce or base can feed many dishes |
| Dispatch | Batch codes, quantities, destination outlet, vehicle, date and time | Turns a batch into a list of outlets |
| Outlet receipt | Batch codes and quantities received, checked against the dispatch note | Confirms what actually arrived, not just what was sent |
| Sale or use | Which batch was in use, from when to when | Defines the sale window and which customers might be affected |
| Wastage and disposal | Batch code, quantity, reason, date | Rules out stock that never reached a customer |
The production row does the most work. Receiving logs and dispatch notes are common; the batch ticket that ties them together is often missing.
Why your batch size sets the size of a food recall
How big a recall becomes depends on how precisely you can draw a line around the problem. Take a hypothetical case: a supplier flags one delivery of chicken, and your records show it went into two marinade batches dispatched to six outlets on Tuesday. The recall is two batches, six outlets and a known sale window. If the records only show “chicken used this week”, everything made that week is in scope.
Three choices set the width of that line:
- How big a batch is. “One day’s production” is easier to record but makes every trace a full day wide. One production run per batch keeps it narrow.
- Whether batches mix. Topping up a tub of sauce from a new batch merges two batches, and anything served from it belongs to both.
- Whether outlets record which batch is in use. Without that, the sale window is everything between receipt and the last portion.
Food traceability in Malaysia sits within the Food Act 1983 and its regulations, and many operators face further record requirements from halal certification, food safety schemes or their own customers. Requirements differ by business type, so confirm what applies to you with the Ministry of Health (KKM) or your adviser. The records in the table are good practice whatever applies.
How do you run a mock recall?
A mock recall tests the chain before a real recall does. Run one each quarter, alternating backward and forward traces.
- Pick a real batch without warning the team. A raw material received two or three weeks ago, or a finished product on sale at one outlet today.
- Start the clock. Set your own target time and tighten it each round.
- Trace one step back. From the finished product, find its batch code and batch ticket, then the input batches it used.
- Trace back to the supplier. For each input batch, find the receiving record: supplier, supplier batch code, delivery date.
- Trace forward. From the raw-material batch, list every production batch that used it, including semi-finished goods and the products they fed.
- List every dispatch. Which outlets received those batches, how much, and when.
- Establish sale windows. At each outlet, find when the batch went into use and when it ran out or was discarded.
- Balance the quantities. Quantity received should equal quantity used, plus stock on hand, plus recorded wastage. Any gap is product you cannot account for.
- Stop the clock and write it up. Record the time taken, every point where someone had to guess, and who will fix each gap before the next drill.
Step 8 is the one most drills skip, and the one that shows whether the records match reality.
Where the chain usually breaks
Decanting. Product moves from a labelled carton into an unlabelled container, and the batch code goes in the bin with the carton. The code has to move with the food.
Mixed batches. Two batches combined in one container, or yesterday’s remainder added to today’s, make the output part of both. If mixing is unavoidable, record it as a new batch with both inputs.
Handwritten labels. “Chilli paste, Tues” cannot be matched to a record with confidence. Printed labels with a batch code, or a QR code linked to the record, remove the guesswork.
Unrecorded substitutions. When a cook uses another brand because the usual one ran out, the batch ticket should say so, or the trace points at the wrong supplier.
Outlet-to-outlet transfers. A tray passed between outlets on a busy night rarely gets recorded, but it is still a link in the chain.
The same discipline produces food safety records that hold up, and our earlier piece on traceability from kitchen to counter covers why it pays commercially.
Where RMS fits
Codemax RMS (Resource Management System) builds batch traceability into work the kitchen already does, rather than adding a separate log. Batches are captured at supplier receipt. Production generates batch tickets and pick lists automatically, linking input batches to the output batch. Dispatch, outlet receiving and sale are recorded against the same batch, with a QR-based trace from raw material through production to delivery.
FIFO and expiry checks are enforced when stock is issued, so older batches go first and expired stock is caught before use. Inter-branch transfers are recorded too, so stock moved between outlets stays on the chain.
In a recall, RMS identifies the affected batches, outlets and sale windows in minutes, which turns the mock recall above into a query rather than a morning of phone calls.
A ten-minute check
Pick one semi-finished item sold at one outlet yesterday, such as a sauce or a marinade, and ask:
- Which batch was in use, and how do you know?
- Which raw-material batches went into it, and from which suppliers?
- Which other outlets received the same batch?
- How much is still on hand, and how much was thrown away?
If any answer starts with “probably”, start there. The fix is usually a label, a field on a batch ticket or a quick scan, not a new department.
Frequently asked questions
What is the difference between batch tracking and lot tracking?
Batch tracking and lot tracking describe the same practice: grouping product received or made under the same conditions under one code, so it can be traced as a unit. Some industries say batch for production runs and lot for received goods, but in F&B the terms are used interchangeably. What matters is that every batch or lot code links to a record.
What does one step back, one step forward traceability mean?
One step back, one step forward traceability means each business records where every batch came from and where it went next. When every business, and every step inside a central kitchen, keeps those two records, they join into a chain that can be followed from supplier to customer and back again if a problem is found.
How do you run a mock recall in a central kitchen?
A mock recall in a central kitchen starts with a real batch chosen without warning. The team traces it back to the supplier and forward to every product, outlet and sale window, then balances quantities received against quantities used, on hand and wasted. Record the time taken and every gap, fix the gaps, and repeat the drill each quarter.
Is food traceability required in Malaysia?
Food traceability in Malaysia sits within the Food Act 1983 and its regulations, and many operators also face record-keeping requirements from halal certification, food safety schemes or customer contracts. Exact requirements depend on the type of business, so check with the Ministry of Health (KKM) or a qualified adviser. Batch-level records are good practice either way.
What should a batch label in a kitchen show?
A batch label in a kitchen should show the product name, a batch code, the production or received date, the use-by or expiry date and, where relevant, storage conditions and allergens. The batch code must match a record of what went into the batch and where it was sent. Printed or QR labels are easier to match than handwritten ones.
Trace any batch both ways in minutes.
See how Codemax RMS records every batch from supplier receipt through production, dispatch and outlet sale.
Related reading
- What the Lenggong food poisoning case means for central kitchens The cause hasn't been established, so this isn't about blame. It's about why bulk catering is different, the control at each stage, and the records to have ready if the health office calls.
- Food Act amendment: stronger closure powers and what kitchens should do now The Food (Amendment) Bill 2026 has passed the Dewan Rakyat but isn't law yet. What it adds to the Food Act 1983, and five practical steps kitchens can take in the meantime.
- Traceability and Transparency: From Kitchen to Counter in Seconds When an auditor — or a recall — asks where a batch went, the answer should take seconds, not a war room. Here's how end-to-end traceability protects both customers and the business.