Recall Readiness: When the Cold Store Becomes the Evidence Room

The first hour is usually untidy. Someone has a lab result, a retailer has stopped stock, a supplier is checking a batch code, and the cold store team is being asked to find pallets that may already have left. Recall readiness is the ability of a food business to trace affected lots, block stock, contact customers, manage distribution records and act quickly when unsafe or potentially non-compliant food may have reached the market. In frozen food, where cases can sit in storage, move through several depots and remain in domestic freezers for a long time, the recall is rarely won on the day it begins. It was either prepared earlier, or it was not.

The first question is always: where did it go?

A recall does not start with a press statement. It starts with a search.

Which lot is involved? Which line ran it? Which ingredients were used? Was any rework added? Which cases are still on site? Which pallets left? Which customer received them? Did the stock go to retail, foodservice, export, a distributor, or an external cold store that now needs to answer its phone quickly?

Frozen food makes that search slower when the records are weak. A chilled item may move through the market quickly. A frozen item can remain in the system for months. It may sit in a regional depot, a restaurant freezer, a wholesaler’s cold room, or a home freezer long after the factory has closed the production order.

That is why recall readiness is built inside ordinary factory habits. Lot coding. Pallet labels. Case scans. Supplier batch links. Warehouse movement records. Transport documents. Customer dispatch files. All of it feels routine until somebody needs the answer in minutes, not after lunch.

The painful difference is usually granularity. A company may know that a full day’s production is suspect. That is not always good enough. The real affected window might be one supplier batch, one kettle, one filler, one label reel, one metal detector failure period, one shift, one section of a freezer belt, one rework bin. If the data cannot narrow the window, the recall widens. More stock blocked. More customers disturbed. More cost. More doubt.

A broad recall can be necessary. A broad recall caused by poor records is a different matter.

Lot control looks boring until it starts saving pallets

Lot control is not just a code printed on the pack. It is the link between what happened in the plant and what moved into the market.

A frozen vegetable line may run raw material from several growers or deliveries. A seafood operation may handle supplier batches, glaze, allergens and different pack formats. Ready meals bring sauces, proteins, starches, vegetables, sleeves and trays together in one finished unit. Ice cream can carry mix batches, inclusions, sauces, wafers, tubs and lids. A label error may have nothing to do with the food itself and still require urgent market action.

The recall team needs those links to be clean.

Supplier data is often where confidence starts to fray. A certificate is filed somewhere else. A batch number has been typed in three different formats. A delivery was split between two rooms. A substitute ingredient was approved during a supply shortage and recorded in an email, not in the normal route. These small exceptions are manageable in production. During a recall, they become holes in the story.

Rework deserves special suspicion. It can be perfectly legitimate and still dangerous for traceability if handled loosely. A frozen block of sauce, pastry trim, vegetable fines, coated pieces or off-spec but usable material can connect production runs that otherwise look separate. If rework is not clearly identified by origin, allergen profile, date, permitted use and destination, the affected scope may spread far beyond the original incident.

Cold-store movement adds another layer. Finished goods may be transferred to outside storage, moved between chambers, repalletized, relabelled, picked into mixed loads, or held for a customer promotion. Every handover is a chance to keep the trail intact or blur it.

On recall day, nobody is impressed by a beautiful warehouse if the pallets cannot be traced.

A mock recall should not feel comfortable

Many companies run mock recalls because the audit schedule requires them. A lot is selected, records are pulled, the time is noted, the exercise passes. Everyone returns to work. The file looks fine.

Too fine, sometimes.

A useful mock recall should test the awkward corners. An ingredient used across two lines. A night-shift run. A stock transfer to an outside cold store. A mixed pallet. Rework used three days later. A private-label product with two similar artworks. A supplier alert received after goods have already shipped. A key manager on holiday. A customer contact list that has not been checked since the last personnel change.

Real incidents do not respect tidy exercises.

Speed matters, but only if the answer is right. A fast trace that later changes several times damages trust inside the business and outside it. Customers want to know whether they have affected goods, how much, under which codes, and what action to take. Regulators may need clear information. Distributors need usable instructions. Retailers need store and depot action that does not drift into guesswork.

Communication also needs rehearsal. Who can stop shipment? Who can release a customer notice? Who contacts the retailer? Who speaks to the authority? Who signs the technical risk assessment? Who handles out-of-hours calls? Who checks whether a website notice, consumer line or social media response is needed?

Those roles should not be negotiated while the stock is moving.

The best mock recalls are slightly irritating. They find missing numbers, slow responses, unclear authority, weak supplier links, poor warehouse visibility or contact lists that no longer match reality. That irritation is useful. It is cheaper than discovering the same weakness with a regulator, a retailer and a journalist waiting.

Industry misconception: digital traceability means recall readiness

A common mistake is to trust the screen too much.

Digital traceability, barcode scanning, enterprise resource planning (ERP) records and warehouse management system (WMS) data can make recalls faster. They can also make bad habits look organised. If operators skip scans during pressure periods, the platform is incomplete. If rework is entered later from memory, the record is weaker than it looks. If supplier batch codes are inconsistent, searching becomes slow. If pallet labels are replaced without a proper link, the trail has a crack in it.

Good software cannot repair careless exceptions. It only stores them more neatly.

Recall readiness still depends on people making firm decisions. Holding stock before the full picture is comfortable. Blocking dispatch when the order is urgent. Calling a customer before all the internal politics are settled. Admitting that the affected window may be wider because records are not strong enough to narrow it. These are not software functions. They are management choices.

There is also the consumer end of the route. Frozen food can remain in home freezers after store shelves are cleared. A quiet withdrawal from the warehouse may not be enough if packs have already reached shoppers. The difference between withdrawal and recall is not just vocabulary. It changes urgency, communication and exposure.

Some brands think recall readiness protects them from embarrassment. It does something more practical. It helps them act before embarrassment becomes confusion.

Questions buyers should ask suppliers

A supplier with a recall procedure may still be badly prepared. The useful questions are about what happens when the neat procedure meets real stock.

• How quickly can one finished lot be traced back to ingredients, packaging, rework and production records?
• How narrowly can the supplier define an affected window by line, shift, time, supplier batch or equipment fault?
• How are goods traced through outside cold stores, distributors, export partners, retailer depots and foodservice wholesalers?
• What was tested in the last mock recall, and what weakness was found?
• Who has authority to stop shipment, block stock, notify customers and escalate to regulators?
• How are out-of-hours customer contacts and distribution records kept current?
• How are returned, blocked or recalled goods physically controlled in cold storage?
• How are supplier alerts, complaints, label errors and audit findings used to update the recall plan?

These are not theoretical questions. They decide whether a problem remains contained or starts wandering through the market.

Recall readiness sits between technical records, warehouse practice, supplier control, customer service, legal exposure and executive nerve. It is a food safety issue, but not only that. It is a test of how accurately the business knows itself.

When the call comes, the brand does not suddenly become prepared. It discovers whether the ordinary records, ordinary scans, ordinary labels and ordinary handovers were good enough all along.