Batch Traceability: Knowing Where Every Lot Went When Something Goes Wrong

Batch Traceability: Knowing Where Every Lot Went When Something Goes Wrong

Everything in this series so far has been about quantity: how much is on the shelf, how much was issued to a production order, when to reorder and how much. Today the question changes entirely. It is no longer how many, but which ones exactly.

The difference does not show on an ordinary day. It shows on the day a customer calls to report a problem with a shipment they received, or a supplier notifies you that a raw material lot they delivered was defective. At that moment your only question is: where did that lot go? A plant with no fast answer is left with one brutal option — pull everything, because it cannot identify what actually needs pulling.

The batch number: identity before quantity

A batch or lot number is an identifier that ties together units produced or received under the same conditions: the same raw material, the same line, the same time window, the same process settings. Units inside one batch share a fate — if there is a defect in a source or a setting, it almost always affects all of them, and not the batch before or after.

That is where the economic value of the whole idea sits. The batch is your unit of isolation. The more precisely your batches are defined, the smaller the quantity you are forced to recall or quarantine. Plants that record a batch number on paper only, or capture it in a free-text field disconnected from stock movement, have the number without having traceability.

The same logic applies well outside food and pharma. A chemicals, paint, building materials or industrial parts plant needs batches for the identical reason: isolating the effect of one raw material or one process setup onto a defined set of outputs.

Backward and forward traceability

Complete traceability runs in two directions, not one, and each has a different use.

• Backward traceability: you start from a finished product in your hand and work back to the production order that made it, then to the raw material lots consumed in it, then to the purchase orders, suppliers and receipt dates. You use it when a complaint appears in the market and you want the cause: was it a raw material from a particular supplier, or a line setup on a particular day?
• Forward traceability: you start from a raw material lot or a production batch and work forward to every production order that consumed it, then to every sales order and issue note it left on, then to the customers and locations that received it. You use it when a supplier notifies you of a problem, or you find an internal defect, and you need to know exactly who is holding it right now.

Both directions depend on one thing we built in parts two and three: that every receipt, issue and transfer is captured as it happens, and that the production order records what was actually consumed rather than what was planned. Without those two, a batch number is just an extra field on a screen.

Expiry dates and the rules that govern issuing

For items with a limited life, a batch carries a date and not only a number, and that changes how stock is issued. Issuing by instinct, or by whatever sits closest to the door, produces a familiar outcome: old stock stays buried at the back until its life runs out while newer stock goes out first.

• First expired, first out: the batch closest to its expiry date is issued first — the right rule for most dated items.
• First in, first out: the oldest receipt is issued first, which suits items with no expiry date that still degrade or become obsolete in long storage.
• Quarantine and release: a received batch is not automatically available for issue but sits on hold until it is released after inspection, which stops non-conforming material from entering production at all.
• Hold on suspicion: the ability to freeze one specific batch instantly across every location so it can neither be issued nor sold until the investigation closes.

These rules are useless as instructions taped to a wall. They work when the system enforces them at the point of scanning: when a storekeeper tries to issue a newer batch while an older one is available, it blocks or warns right then.

What makes a recall take hours instead of days

When the event actually happens, time is everything, and the gap between a plant that takes hours and one that takes days is not headcount. It is four things prepared before the event:

• The batch lives in the movement, not on a sheet: the number is captured at receipt, issue, transfer and sale, so producing the affected list becomes a query rather than a manual search.
• The link to the customer exists: issue notes and sales orders carry the batch number, so you know who received what, how much, when and against which document.
• Ownership is clear: a named person holds the decision, and the escalation path is agreed in advance rather than invented during the crisis.
• The scenario has been rehearsed: you have run a mock recall before, so you know where it breaks in practice.

For food and pharmaceutical products specifically, the Saudi Food and Drug Authority regulates traceability and market withdrawal requirements, and its official platforms and guidance are where you check what applies to your particular product and activity, because requirements differ by category and cannot be settled with a general rule.

A mock recall to run this week

This exercise costs you nothing and exposes your real level of readiness:

• Pick one production batch that left your plant in the last two months — at random, not the easiest one.
• Start a timer and ask your team to identify every customer and location that received units from that batch, with quantities and dispatch dates.
• Then reverse direction: from the same batch, identify every raw material lot that went into it, its supplier and its receipt date.
• Record how long each direction took, and where the team got stuck and why: a missing document, a movement posted retrospectively, an item issued with no batch number.

What you end up with is your true response time. And if the answer in either direction is not a number but a sentence like we would need to go through the records, you now know what to fix before a real event forces the issue.

The Origami view

Across the industry and warehouses sector we find that most plants do record a batch number — but they record it somewhere disconnected from stock movement: a separate production file, or a free-text field on the receiving screen that issuing never references. The number exists and helps nobody when it matters, because producing the list of affected customers is still manual work measured in days.

The order we recommend: make the batch number mandatory at receipt and issue for the items that warrant it rather than for every item, link it through the production order and on to the sales order so both directions close, then test it with a mock recall before you actually need it. Traceability that has never been exercised once is a claim, not a capability.

In the next part

We move from inside the plant to its point of contact with the outside world: the invoice. Why do plants that treat the e-invoice as a document printed at the end, rather than the result of a stock movement, keep running into trouble? Part six covers linking the sales order to the warehouse issue to the invoice, credit notes and returns, and what the integration phase requires.

Sources

• Saudi Food and Drug Authority — traceability and market withdrawal requirements for food and pharmaceutical products.
• Saudi Standards, Metrology and Quality Organization — standards and product labelling requirements.
• Ministry of Industry and Mineral Resources — programmes for raising the efficiency and output quality of industrial facilities.