A 90-second restaurant food-withdrawal and recall workflow: stop sale, trace the affected batch, choose the correct notice route, update every guest-facing surface and leave a decision log.
What the film covers
- 1. Read the alert properly before you touch the stock
- 2. Stop sale before you finish the investigation
- 3. Work out precisely which dishes the product touched
- 4. Decide whether you owe a customer notice — the split most guides miss
- 5. Tell the authority — and tell the right one
- 6. Write the notice the FSA template already expects
- 7. Put the notice where guests will actually see it
- 8. Take the dish off every live guest channel at once
Read the full articleRestaurant food recall customer notice UK: pull the dish, publish the noticeYour enforcement authority may later check both that the affected food was removed from sale and that a consumer notification was issued where one was appropriate — that check is written into the Food Standards Agency and Food Standards Scotland guidance for enforcement officers. It can begin at 4.15pm, when an alert names one product code — a jar of sauce, a case of crumbed chicken, a bag of ground spice — and the pack is already open in your kitchen and already portioned into two dishes on tonight’s menu. The food has to leave service before the next ticket prints. The dish has to stop selling on every channel a guest can order from, including the ones you are not looking at. Someone has to work out whether guests who already took food away need to be told anything. This is not rare: the FSA alerts index listed 11 alerts dated July 2026 when its own date filter was read on 6 August 2026, roughly one every three days across England, Northern Ireland and Wales.