Can Your Food Factory Trace a Contaminated Batch in Minutes? What Indian Manufacturers Should Ask an SAP Business One Agency
It's a Monday morning, a little after ten. The phone on the plant head's desk rings, and it's the regional FSSAI office. A sample picked up from a retail shelf has failed a lab test, and the batch code on the pack is yours. The person on the line asks a simple question. What went into that batch, and where did the rest of it go?
Most of us in food manufacturing have played that scene out in our heads at least once. This year it has been playing out for real. Since July, FSSAI has ordered recalls of packaged raisins, a coriander powder and a carrageenan product and a pre-packed cumin powder. In the first week of October it also suspended the licences of food units over serious hygiene and safety violations.
Those suspensions were about hygiene, and no software fixes a dirty plant. Recalls are a different test. They ask whether you can find the affected stock before a consumer does. That is what this article is about. It is written for plant owners, QA and operations heads, and the finance heads who sign off ERP budgets. It covers what FSSAI expects you to be able to show, how SAP Business One links a raw material batch to production and to customers, what an SAP Business One agency should demonstrate with your data, and what to check before you pick a partner.
One more thing about the one-year retention rule. A register kept by one stores supervisor goes wherever that supervisor goes. Records held in the system stay with the business. This is a plain-language summary and not legal advice, so please check the notified text and your own recall plan with your regulatory consultant.
The last row is the one that separates good partners from the rest. Ask for a mock recall as an acceptance test before go-live, with a target time agreed in writing. We would say the same about any batch tracking software for food manufacturing, whoever supplies it. A drill on your own data tells you more than a slide deck of features.
Capture matters as much as reporting. Batches are only as reliable as the people keying them, so ask how the godown will scan and label stock. Handheld scanners and printed batch labels, as in our warehouse management extension, take typing out of the process at the exact point where errors start.
What Happens When an Indian Food Manufacturer Discovers a Contaminated Batch?
The clock starts the moment you know a recall is needed. Under the Food Safety and Standards (Food Recall Procedure) Regulations, 2017, a manufacturer has to send the prescribed information to the concerned authority immediately, and no later than 24 hours after that point. You stop distributing the food, and stop production too if necessary, without waiting to be told. You also have to get in touch with everyone from the raw material vendor to the final consumer. The regulation text then asks for a recall notice that names the product and the reason, carries a clear "do not consume" message, says where the food was sold and gives a contact number. Recovered stock is kept apart and labelled "Recalled product not fit for human consumption". Status reports go in weekly, and a follow-up report is due within 30 days of the recall being completed. Look at what all of that quietly assumes. It assumes you can name the ingredient lots involved, every production run that used them, every finished batch those runs produced and every customer who received them. In practice the first hour comes down to four questions. Which supplier lot is it? Which of our production runs used it? Which finished batches came out of those runs? And who bought them, how many packs, and what is still sitting in our godown? A manufacturer who can answer in an hour runs a targeted recall. One who can't tends to recall everything made that week, just to be safe. That costs more in stock and goodwill, and it tells customers something about how well you know your own plant.Why Can Batch Tracing Take Hours When Records Are Spread Across Excel and Different Departments?
Walk through a typical plant and you'll find the data is all there. It's just in five places. Stores keep a goods receipt register, often in Excel, with the supplier's lot number written the way the gate clerk read it off the invoice. Production keeps batch cards or a shift sheet, on paper or in a spreadsheet, showing what was issued to the line. QC keeps test reports in a folder. Dispatch raises invoices in the accounting package. Sales holds customer contacts somewhere else again. Nobody has made a mistake. Each team keeps what it needs, in the format that suits it. Tracing is where those formats collide. The lot number is spelt one way in stores and another way on the batch card. A run drew from two lots because the first bag ran out. Yesterday's leftover went into today's batch. A finished batch left the gate on three different invoices. So somebody sits down with five files, a calculator and a phone, and starts ringing the stores supervisor, who happens to be on leave. That is the gap food recall management ERP India buyers are really trying to close. They don't need another module so much as one connected chain of records, so that the answer to a recall question is a lookup and not an investigation.What Does FSSAI Expect Food Businesses to Know About Product Traceability?
The recall regulations are specific about records. Every food business has to keep distribution records that show the names and addresses of suppliers and customers, the nature of the food, the date of purchase and the date of delivery, the lot number or batch code, the pack size, the brand name, and the dates of manufacture, expiry and best before. The records have to be kept for one year from the best before or expiry date, as applicable. Manufacturers, importers and wholesale suppliers must also hold an up-to-date recall plan as part of their food safety management system, and send implementation details to FSSAI and the state commissioner when a recall happens. Read that list of fields again. Every item is something an ERP already holds somewhere. The regulation asks for records, not for a particular tool, so be wary of anyone selling "FSSAI approved" software without being able to show these records working on your own data. But a regulation that expects a first response within 24 hours and a full trail from vendor to consumer is hard to meet from five spreadsheets. That is why people go looking for FSSAI traceability software, and why the useful question isn't whether a product carries a badge. It's whether it holds these fields, linked together, for every batch. Table 1 shows where each one typically sits in SAP Business One. Table 1: FSSAI distribution record fields and where they typically sit in SAP Business One (typical set-up, to be confirmed during design)| What FSSAI expects on record | Where it usually sits in SAP Business One | What to settle in design |
| Names and addresses of suppliers and customers | Business partner master data, linked to purchase and sales documents | Complete, current address and contact details for every distributor and retailer |
| Nature of food | Item master data (description and item group) | Consistent naming across pack formats and plants |
| Date of purchase | Goods receipt and purchase invoice documents | Which date your auditors treat as the purchase date |
| Date of delivery | Delivery note, with the linked sales invoice | Do you record the dispatch date, the date at the customer, or both? |
| Lot number and batch code | Batch number on the batch-managed item, recorded on every stock movement | One numbering convention for supplier lots and your own batches |
| Pack size | Item master (packaging and unit of measure) | A separate item code or unit for each pack size |
| Brand name | Item master, usually through a user-defined field or item property | Where the brand is stored and who keeps it correct |
| Date of manufacture | Batch attributes | Make it mandatory when finished goods are received from production |
| Expiry and best before dates | Batch attributes, with a user-defined field if you store both dates | Make sure the stored date matches the date printed on the pack |
How Can SAP Business One Connect Raw Material Batches with Production and Finished Goods?
Think of it as a chain with four links. Each link is an ordinary business document in SAP Business One: a goods receipt, a production order, a receipt of finished goods and a delivery. Nobody has to remember to "do traceability" as a separate job. With SAP Business One batch traceability set up properly, it becomes a by-product of receiving, producing and dispatching, as long as the batch is captured at every step. Figure 1 follows one contaminated ingredient lot through that chain.Recording supplier batch information
It starts at the gate. In SAP Business One you mark ingredients and finished goods as managed by batches in the item master, and from then on the system asks for a batch on every movement of those items. At goods receipt, the stores team records the supplier's lot number, your own internal batch ID and the dates that matter, such as manufacture and expiry. Our own guidance on batch management recommends a standard numbering convention and automatic code generation, because hand-typed codes are where traceability quietly breaks. Two decisions are worth taking early. First, whether incoming lots wait in a quarantine warehouse until QC releases them, which many food plants do. Second, how supplier certificates and your own test results get attached to the batch, usually through user-defined fields. And settle the item set-up before opening stock is loaded. Once an item holds stock under one batch method, changing it later is not straightforward.Connecting production orders and ingredient consumption
A production order carries the bill of materials, which in a food plant is the recipe. When ingredients are issued to the order, the batch each one came from is recorded. When finished goods come back from the line, the finished batch is received against the same order. That order is the bridge between the ingredient batches that went in and the finished batch that came out. The decision that matters here is how ingredients get issued. They can be issued by the stores team against the order, or backflushed when production reports its output. Manual issue gives sharper batch detail and means more keying. Backflushing saves keying and demands discipline over batch selection. Neither is wrong, but the choice decides how reliable your link is and how much your operators will put up with. Bulk ingredients need a rule as well. If a silo or day tank is topped up from different lots, decide what counts as a batch for that tank, or the chain blurs.Identifying affected finished-goods batches
Now the moment that counts. Starting from the failed supplier lot, you open its batch history. SAP Business One's batch number transactions report lists every movement of that batch in and out: the receipt, any warehouse transfers and the issues to production. Each issue points to a production order, and each production order points to the finished batch it made. In Figure 1 the lot goes into three orders, which produce three finished batches. Run it the other way, from a failed finished batch back to its ingredient lots and suppliers, and you are using the same records. One thing to ask about directly. The batch history is a standard report. The step from an ingredient batch to the finished batches across several production orders is, in many set-ups, handled by a saved query or a purpose-built report. That's perfectly fine, as long as it exists, has been tested with your data and has an owner. It shouldn't be something an analyst writes at midnight in the middle of a recall.Tracing dispatches and customer records
The last link is the delivery. When goods leave, the delivery note records the batch picked for each line, against a customer who already sits in your business partner master with an address and contact details. So the forward trace ends in a list: customer, delivery, invoice, batch, quantity and date. That is the list your recall notice needs, and the one the regulator's distribution records expect. Two other things happen alongside it. The remaining stock of the affected batch is moved to a blocked or quarantine location, so nobody picks it for tomorrow's truck. That is the "stop distribution" duty in practice. And anything that comes back is booked against the same batch, so the recovery figures you report each week match what is physically in the returns area. In the Figure 1 example, a 500 kg lot of dry red chilli fails a lab test. 360 kg of it went into three production orders, 140 kg is still in the godown, and the three finished batches total 3,600 packs. 2,700 of those packs went to five customers and 900 are still in stock. That is the whole recall list, built from linked records and not from memory.Which Batch Traceability Functions Should an SAP Business One Agency Demonstrate?
A demo run on tidy sample data proves very little. Ask any SAP Business One agency to run the steps in Table 2 with an ingredient and a product of your own, and keep an eye on the clock.Table 2: A demo script for batch traceability in SAP Business One
| Function to see | What a good answer looks like |
| Goods receipt with supplier lot, internal batch and expiry | The batch is created at receipt, mandatory fields can't be skipped and the supplier certificate is attached. |
| A batch required on every movement, including warehouse transfers | The system refuses a transfer or issue with no batch, so gaps can't creep in. |
| Production order with batch-selected ingredient issue and finished batch receipt | Ingredient batches are visible on the order and the finished batch is tied to it. |
| Backward trace: finished batch to ingredient lots and suppliers | One report or screen, not three separate exports. |
| Forward trace: ingredient lot to finished batches and customers, with quantities | Customer, document, batch, quantity and date appear in one list that can be exported. |
| Blocking the remaining stock | The leftover quantity moves to a blocked location in a few steps and can't be picked for a delivery. |
| Expiry control and earliest-expiry-first picking | Picking suggests the earliest expiry first, and near-expiry batches raise an alert. |
| A timed mock recall on your data | They run the whole sequence live and you note how long it takes. |
Applicable for Package
Optional