Batch traceability: where it came from and who you sold it to
What records a food recall needs under Mexico's NOM-251 and the FDA's FSMA 204, how to follow a batch from the raw material to the customer, and how Nori tracks it across purchasing, production and sales.
In this article
When a supplier calls to say a batch of their raw material came out contaminated, the next question is how many customers got product made with it. If the answer is split between the production notebooks and a shipping spreadsheet only the warehouse lead understands, pulling it together takes days, and by then the product has been sold and someone has eaten it.
What NOM-251 asks for
NOM-251-SSA1-2009 is Mexico's hygiene standard for anyone who processes food, beverages or supplements, and its chapter 6 covers food plants. That's where the batch rules are:
- 6.9.1. Every prepackaged product carries a code that identifies its batch.
- 6.7.1. The plant has a plan to pull from the market any identified batch that is a health risk. The plan names the person in charge, with a phone number, and the phone line for consumers.
- 6.7.3. Each recall is recorded with the date the problem was found, the cause, the product, the batch, where it was first distributed, how much was recovered, where that went and the measures taken.
- Table 2. On receiving raw materials you note supplier, quantity and batch. In manufacturing, product, batch, date and shift. In storage and distribution, receipts and shipments with product, batch, quantity and date.
- 6.6.1. Records are kept for at least one and a half times the product's shelf life, in Spanish, and if electronic, with backups and control over access and corrections.
"First distributed" means your direct customer. If you sell to a chain or a distributor, the standard doesn't ask you to know which store each unit ended up in, but it does ask who you shipped it to.
If you export to the United States, the FDA's food traceability rule (FSMA 204) asks for something similar for the foods on its list: a lot code that travels with the product through each receipt, transformation and shipment. The FDA moved its compliance date to July 20, 2028.
The three links
Answering "who got it?" in minutes takes three records that connect to each other.
On receipt. The supplier's batch goes on the goods receipt, with the expiry date. If someone writes "various" or leaves it blank because the truck showed up at six in the evening, everything downstream loses its origin.
In production. The production order says which input batches were consumed and which product batch came out. This is the link that breaks most, because on the floor people grab the nearest sack and the record gets filled in at the end of the shift with what "should" have been used.
On sale. The delivery or invoice says which batch went to which customer. Without it you know the batch existed, but not who to call.
How Nori tracks it
The batch is born on receipt
On the item you choose batch management. From then on, every goods receipt asks for the batch under the line: scan or type it, along with the supplier's batch and the expiry date. The scanner receipt does the same from a phone at the dock.
The production order ties them together
When you issue materials to a production order, Nori suggests the batch that expires first; if the floor used another, you change it right there, and an expired one shows up flagged. When you receive the finished product, Nori proposes the batch number and works out the expiry from the item's shelf life. If you receive in parts, each receipt creates its own batch.
Traceability walks the chain
In Production › Reports › Batch traceability you type the batch number and pick a direction:
- Where it went: the orders that consumed that batch and the product batches they made. If that product went into another order, it keeps going forward.
- Where it came from: the order that produced the batch and the input batches it consumed.
Traceability is by order, as in SAP Business One. If an order was received in three parts, all three batches point to everything the order consumed. When that's too broad for a recall, the fix is on the floor: smaller orders, one per shift or per run.
And who you sold it to
On the same screen, under the Where it went tree, is the Customers who received it list: every customer who got the batch or something made from it, with their phone, what was shipped, what came back, and the deliveries and invoices with their date and batch. That's the "where it was first distributed" the standard asks for, ready to start calling. Returns come back with the batch from the original document, so what you recover stays linked too, and for every movement in detail there's the inventory audit with Show batches and serials.
All of this lives in one database, with users, role permissions and backups, which is what the standard asks of electronic records.
A mock recall before you need one
Pick a raw-material batch you received two or three months ago. With the clock running, answer:
- Which product batches did it end up in?
- Which customers got those batches, and how many units each?
- How much is left in your warehouses and on your trucks?
If any answer takes more than an hour or depends on one particular person, that's the link to fix first. It's almost always the issue to production.
The recall plan itself, with who calls each customer and where recovered product is set aside, is your company's document, and no system writes it for you. What Nori gives you is the list of batches and customers to fill it in fast. If you make or distribute food, the dairy and deli page covers what else Nori does in the warehouse and on the road.
Frequently asked questions
What does NOM-251 require for product recalls?
Section 6.7 asks for a plan to pull from the market any identified batch that is a health risk, with the name and phone of the person in charge and a phone line for consumers. Each recall is recorded with the date, cause, product, batch, where it was first distributed, quantity recovered, where it went and the corrective actions.
How long do I have to keep the records?
NOM-251 (section 6.6.1) asks you to keep them for at least one and a half times the product's shelf life. A product that lasts 6 months means 9 months at minimum.
What's forward and backward traceability?
Backward starts from a product batch and reaches the raw-material batches and suppliers. Forward starts from a raw-material batch and reaches the products that used it and the customers who received them.
Does Nori handle batches with expiry dates?
Yes. Each batch keeps its number, the supplier's batch, the manufacturing date and the expiry date. When picking and when issuing to production, Nori suggests the one that expires first, and the inventory dashboard flags batches about to expire.
Does it work with SAP Business One?
Yes. With SAP connected, batch management comes from SAP and Nori sends up the batches on every document. Production traceability works the same as in SAP: by production order.