Skip to content
1961 Digital TransformX

Industry

Your recall drill depends on a folder nobody has opened

Food companies fail on paperwork, not on production. The line runs. The batch ships. Then somebody asks which pallets carried lot 0412, and the answer sits in three notebooks, a weighbridge printout and one supervisor’s memory.

What the day actually looks like

  • Production starts at five. The first mix is weighed by eye because the scale printout jams, and the sheet is filled in at break.

  • Chiller temperatures are logged on a clipboard by the door, four times a shift, in handwriting that fades before the auditor arrives.

  • The central kitchen despatches to eleven branches before seven. Two vans return with unsold trays nobody credits back to anything.

  • Weighed items are priced at the counter by the scale, and the scale keeps its own product file that nobody reconciles.

  • Stock count night begins after closing, ends at two, and covers about two thirds of the shelves. The rest is copied forward.

Where it usually breaks

  1. Traceability that stops at the door

    You can name the supplier of the flour and the customer who bought the carton. You cannot connect them. The link breaks at the mixer, where three sacks from two deliveries went into one batch and nobody recorded which. A recall then becomes a guess with lawyers attached.

  2. Shelf life managed by eye

    Expiry lives on the carton, not in the system. So picking is first-in-first-out only when the storekeeper feels like walking to the back of the rack. Short-dated stock surfaces at the branch, on the shelf, in front of a customer, and gets written off as a surprise every month.

  3. HACCP kept in a binder

    The plan is real and the controls are real. The evidence is a lever-arch file. Nobody can show a month of critical control point readings without photocopying, and nobody notices a missed check until the auditor counts the gaps. The discipline exists; the proof does not.

  4. Yield loss nobody costs

    Trim, spillage, the tail of the batch left in the pipe, the tray that burned. Every plant knows these happen and no plant books them. So standard cost stays theoretical, and the gap between what you bought and what you sold is absorbed quietly into cost of sales.

  5. Branches and kitchen disagree

    The central kitchen despatches by tray count. The branch receives by weight, or by eye, or not at all until the shift ends. Transfers sit unconfirmed for days, so branch stock is fiction and kitchen stock is worse. Waste at the branch looks like theft at the kitchen.

How the work runs

  1. Walk the line first

    We start at goods-in and follow one real batch to the customer, standing where the work happens. That walk tells us which readings are taken honestly, which are filled in afterwards, and which three fields the mixer operator will never enter with wet gloves on.

  2. Build the lot genealogy

    Every receipt gets a lot with a supplier, a date and an expiry. Every production order consumes lots and produces one. Every despatch carries it. Then a recall query is a search, not an investigation, and the drill can be run on a Tuesday for practice.

  3. Capture at the point

    Temperatures, weights and checks are recorded where they are taken, on a tablet or a scale that talks to the system, by the person who took them. If a reading is late, the system says so at the time, not four weeks later during an audit.

  4. Cost the waste

    We give scrap, trim, rework and expiry their own reasons and their own accounts, so the production order shows what it actually consumed against what it should have. Yield stops being an argument between the plant manager and finance and becomes a number both of them read.

  5. Count in cycles

    The full night count is abandoned. Fast-moving lines and high-value items are counted on a rota during trading, a handful of locations a day, with variances investigated while the person who moved the stock is still on shift. The count finishes because it is small.

What changes once it holds

  • A recall query names the pallets in minutes, not days.
  • Short-dated stock is picked before it becomes a write-off.
  • HACCP evidence prints for any date range without a photocopier.
  • Yield variance is visible per batch, per line, per shift.
  • Branch transfers are confirmed on receipt, so both sides agree.
  • Stock counts finish, because they are small and continuous.

Traceability is a drill, not a document

Regulators do not ask whether you have a traceability procedure. They ask you to run it. Give us a finished-goods code and a date, and tell us within the hour which raw material lots went into it, which customers received it, and how much is still on your own shelves. Almost every food business we see can answer the first half and not the second. The fix is not a policy. It is making the lot a mandatory, cheap field at every point where material changes hands, then running the drill quarterly against a real code until it comes back clean.

Weighed items break the product master

A retail food business carries two kinds of item: the ones that scan and the ones that are weighed. The weighed ones are the problem. The scale holds its own PLU file, priced and described separately, and it is updated by whoever happens to be standing next to it. Within a season the scale file and the item file have drifted, so margin on fresh and prepared food is computed against prices that were never charged. We treat the scale as a slave device, not a second system: one product master, one price list, pushed outward, with a report that names every PLU the two disagree about.

The central kitchen is a factory, not a store

Companies running a production kitchen behind a chain of branches usually configure it as a warehouse. That is why nothing reconciles. A kitchen consumes ingredients against a recipe, produces output at a yield, and loses some of both, which is manufacturing. It needs a bill of materials, a production order and a scrap route. Configured as a store it can only issue and receive, so every loss looks like a transfer error and every recipe change is invisible. Model it as manufacturing and the questions become answerable: cost per portion, yield by product, waste by branch, and what the eleven o’clock bake actually costs to make.

Questions we get asked

Do we need full batch traceability if we make one product?
Yes, and it costs you less than it costs anyone else. A single line means a single recipe and few lots, so the discipline amounts to one field at goods-in and one at despatch. The obligation does not scale with your size: a recall is the same event whether you make one product or forty. Small operations usually have this working within a few weeks.
Our HACCP consultant already set up the records. Why change them?
We would not change the plan. The plan is normally sound. What we change is where the evidence lives. Paper records satisfy an inspector who visits and satisfy nobody at eleven at night when a chiller has drifted and no alarm exists. Capturing the same readings in the system keeps your consultant’s controls exactly as written, and adds the alert and the audit trail the binder cannot give you.
Can the system handle weighed items and barcode scales?
In most cases yes, and the integration is a normal part of the work rather than a custom project. The important decision is not technical. It is agreeing that the product master lives in one place and the scale receives from it, never the reverse. Once that is settled, price changes reach the counter the same day and fresh margin becomes a figure you can defend.
Will the production staff actually use it?
Only if you design for gloves, steam and a five o’clock start. That means very few fields, defaults that are right most of the time, scanning instead of typing, and a screen that works on a wall-mounted tablet. We test the entry screens with the actual operators before go-live and remove anything they hesitate over. A field nobody fills is worse than no field.
How soon can we run a real recall drill?
Traceability usually goes live before the accounting does, because it is the part carrying legal exposure. Once goods-in, production and despatch are recording lots, you can run a drill immediately: pick a code, start a clock, see what comes back. The first drill always finds gaps. That is what it is for. The second one is the one that counts.

Tell us what is not working

Send one line about what is going wrong. On the first call we will tell you whether it is a system problem, a process problem or a governance problem — and which one to fix first. That call is free and it is not a sales meeting.

Book a consultation