Traceability and recall: what happens after the product leaves the warehouse

Every earlier lesson in this course controlled something inside the building: the temperature, the thawing time, the surface, the person, the date on the label. But one class of problem only surfaces after the product has left the warehouse — a lab result that arrives late, a repeated consumer complaint, a fault in a packaging material, a labelling error that hides an allergen. At that moment no internal procedure helps, because the product is no longer yours. One capability remains: knowing exactly where it went, and getting it back fast. That capability is called traceability, the procedure is called recall, and in Saudi Arabia neither is optional housekeeping — both are legal obligations.

Traceability: being able to answer two questions#

Traceability is, at its core, very simple. For every consignment of chicken entering your operation you must be able to answer two questions within minutes: exactly where did this come from, and exactly where did it go. The first is called one step back, the second one step forward. The law does not ask you to know the whole chain from the farm to the last diner's plate — it asks you to know your own link precisely, because if every establishment in the chain knows its link, the full chain can be reconstructed in hours.

The executive regulation of the Saudi Food Law obliges a food establishment to put in place a written traceability guide, to operate one-step-forward and one-step-back tracing, and it spells out what that guide must contain. It also requires traceability records to be kept for not less than one hundred and eighty days after the end of the product's shelf life, and produced on request. Note that the clock starts at the end of shelf life, not at the sale: a chilled chicken with a few days of life still leaves a record that must exist for months after the product itself was eaten or discarded.

• Sources of food: which establishment supplied you, on what document, on what date.
• Every operation performed on the food while it was with you: receiving, storage, cutting, packing, dispatch.
• Raw materials and additives and their sources, including packaging and wrapping materials — the item most record systems forget.
• Who received the product from you: the customer, the quantity, the date, and precisely which lot they were given.

The lot code: the key that makes a recall possible#

Among all the elements of a record, one is load-bearing: the lot code. The Codex Alimentarius General Principles of Food Hygiene state that lot identification is essential in product recall and also helps effective stock rotation, and that each container of food should be permanently marked to identify the producer and the lot. The reason is purely practical: without a lot code there is no such thing as a partial recall. Suppose a problem arose on a single production day. If your records say "chilled chicken, August", you have to pull a month of production off the market. If they say "lot number X, produced on day Y, shipped to six named customers", you pull one day and let the rest of the month keep selling.

This is why the labelling lesson in this course is not a lesson in formalities: the lot code and production date printed on the pack are the visible end of a complete internal record. An establishment that prints an unreadable code, reuses the same code across different days, or relies on a label that dissolves in chiller condensation has effectively cancelled its own ability to run a partial recall long before it ever needs one.

A quick test of your coding quality: take a pack out of the chiller after two days of storage and photograph it on a phone under normal warehouse light. If you cannot read the lot code off that photo, neither can your customer nor an inspector.

A recall is a safety control, not a confession of failure#

The prevailing culture treats the words "product recall" as a scandal. That reading is upside down. Codex classes recall among the management procedures that must exist in advance: managers should ensure effective procedures are in place to deal with any food safety hazard and to enable the complete, rapid recall of any implicated lot of the finished food from the market. An establishment that recalls quickly is demonstrating that its system works. The one that cannot recall — because it does not know where the product went — is the only one that has actually failed.

Codex adds three rules that are widely missed. First: where a product has been withdrawn because of an immediate health hazard, other products produced under similar conditions which may present a similar hazard should be evaluated for safety and may need to be withdrawn too — a recall does not necessarily stop at the lot that was complained about. Second: the need for public warnings should be considered. Third, and this one settles the fate of the returned stock: recalled products should be held under supervision until they are destroyed, used for purposes other than human consumption, determined to be safe for human consumption, or reprocessed in a manner that ensures their safety. Returned goods do not drift back into normal inventory, and they are not binned casually either: their disposition is a documented decision.

The first hour: what the establishment does, in order#

When a serious signal arrives — a lab result, a repeated complaint, a supplier notification — the order of actions matters as much as the actions. The executive regulation of the Food Law requires an establishment to notify the Saudi Food and Drug Authority immediately about any food suspected of being capable of causing harm, to start withdrawal procedures immediately, and to supply the Authority with full information about the food to be withdrawn. "Immediately" is not a figure of speech: on a short-life chilled product, a delay of hours means part of the lot has already been eaten.

1. Stop dispatch immediately and lock down whatever remains of the lot on site, clearly marked "on hold — do not release".
2. Define the scope from the records: affected lot numbers, production dates, quantities produced.
3. Notify the Saudi Food and Drug Authority immediately with the full information; do not wait until the cause is fully understood.
4. Notify one step forward: every customer who received the lot, by name and quantity, through a provable channel — not a verbal phone call.
5. Retrieve and segregate: returned goods are stored separately, labelled, under supervision, and never mixed with sound stock.
6. Decide and document the disposition: destruction, diversion away from human consumption, or release after safety is demonstrated.
7. Check effectiveness: how much of the shipped quantity actually came back, how much did not, and why. Then fix the root cause, not the symptom.

The drill almost nobody runs: the mock recall#

All of the above looks sound on paper and then collapses in practice for one reason: nobody has ever tried it. A mock recall is cheap and takes less than a day. Pick a random lot from last month, start a clock, and answer three questions: how much of this lot was produced, exactly who received it, and how much of it is still out in the market. The two metrics that matter are the time taken to produce the complete list, and the share of the produced quantity you can actually account for. If the clock passes four hours, or the share falls short of the whole lot, the problem is in your records rather than your luck — and you found it on a quiet day instead of a crisis day.

Run the mock recall twice a year and log the result as a time and a percentage. That log is one of the strongest things you can show an institutional buyer or a quality auditor: it proves the traceability system has been tested, not merely written down.

And as a shopper: what to do when a recall is announced#

The last party in the chain is the buyer, and the Saudi Food and Drug Authority publishes warnings and recall notices on its official website and channels. The common reaction goes wrong in one of two directions: ignoring the news because the product "looks fine", or throwing out everything of that type in the fridge without reading the notice. The right response sits between the two, and it starts with the lot code.

• Read the whole notice and match three things against your pack: the brand, the lot code, and the production or expiry date. Anything outside that range is not affected.
• Do not test it with your senses. Most recall causes have no smell and no colour: a foreign body, an undeclared allergen, a chemical fault.
• Do not rely on cooking. Heat kills bacteria, but it does not remove preformed toxins, foreign objects or allergens.
• Follow what the notice actually says: return to the point of sale, or dispose of it. If a reporting number is given, use it — your report is part of how the recall's effectiveness is measured.
• Clean the shelf or drawer the product sat in, especially if it was raw chicken and juices reached other surfaces.

Why this gets harder with chicken specifically#

Chilled chicken combines three properties that turn a recall into a race. Its shelf life is short, so a lot is consumed in days rather than months. Its distribution is fast and wide — a single lot can pass through a depot, two restaurants and three groceries within twenty-four hours. And it is often re-cut and re-packed at the buyer's premises, losing its original pack and with it its lot code unless that code was captured on receipt. The weakest link in chicken traceability is therefore usually not the producer, but whoever opens the master case and never writes its code into the receiving log. The fix is cheap: one field labelled "lot code" on the receiving form, filled in before the carton goes to the bin.

The regulatory side: traceability is now an explicit inspection item#

On 31 August 2025 the Ministry of Municipal and Rural Affairs and Housing, together with the Saudi Food and Drug Authority, announced an updated schedule of Food Law violations that widened supervision to new elements of the supply chain — among them delivery representatives, food traceability, the handling of food-poisoning incidents, and record keeping. The schedule adopts a warning-first principle for non-serious violations, with a correction period, while serious violations touching consumer safety draw immediate penalties. For a restaurant or depot operator the practical message is plain: the traceability file is no longer an optional internal document, it is an item you can be asked for during an inspection visit.

Internationally the frame is completed by the Codex principles for traceability and product tracing: the revised General Principles of Food Hygiene added a requirement for a product-tracing system designed and implemented so as to enable the recall of products where necessary. Traceability, in other words, is not an end in itself — its entire value is realised in the moment you need a fast, precise recall. Establishments that build their records on that premise find they have gained something they did not plan for: cleaner stock rotation, complaints resolved faster, and more confidence from institutional buyers, who always ask the same question — if something goes wrong, how long do you need to know where the product went?