It started with a single jar. A customer in a northern suburb wrote in to say a batch of chili sauce smelled funny when she opened it, and her family felt queasy after dinner. That one message triggered a nightmare for a 60-product sauce manufacturer whose production records lived in a binder of handwritten forms and a single spreadsheet that nobody could sort reliably.
It took the quality manager two full days to identify which batches were affected. Two days of guessing, while a whole aisle of jars sat waiting for an answer.
Luckily, the test results came back clean, and the company avoided a formal recall. But the scare itself was enough to convince the owner that “lucky” is not a strategy. That’s when ERPNext Consulting came into the picture, not to install a big package of unnecessary features, but to build a simple traceability loop that a small production team could actually follow.
The traceability trail that fits in a single afternoon
The design principle was brutal simplicity. Every production batch gets a number printed on the label. The system records three facts for each batch: which raw material lots went in, which line and shift produced it, and which customer orders it shipped to. That’s it. No barcode scanners with exotic equipment, no industrial engineering degrees required. Just a rule that no batch gets released until those three facts are entered.
- Raw material lots are tagged at the receiving dock with the supplier’s own lot number and the delivery date, so a problem can be traced all the way back to the farm or the processor.
- Every production run starts a new batch record, and the line supervisor confirms it the same day, while the details are still fresh.
- Customer returns go into a dedicated screen, so any pattern like “three returns from one region” is visible within days instead of months.
Six months later, a supplier’s tomato paste shipment was found to have a sulfur smell. The manufacturer pulled the batch numbers that used that paste, identified the four customer orders that contained it, and had the retail stores informed within 15 minutes. The cost of that rapid response was a few phone calls and one email, versus the potential 80 thousand dollars in recalls, disposal fees, and damaged distributor trust that a slow response would have meant.
What traceability is really worth
Managers often think of traceability as a compliance burden, something to build for auditors. But the real value is defensive speed. A food business cannot control every ingredient that arrives at the dock, but it can control how fast the organization reacts when something goes wrong. That speed is precisely what ERPNext Consulting focuses on when it reviews a food manufacturer’s production records: if the answer to “where did this batch go?” takes more than a coffee break, the process needs to change.
If you run any business that buys ingredients or components and ships them onward, run this test this week: pick the most recent batch you produced, and find the answer to two questions in writing — which materials went in, and which orders went out. If you need more than one hour to answer, you have a process gap that will eventually cost you money. Close that gap now, before a bad batch finds you first.