What Should a Food Business Do When a Recall Notice Is Updated?

Treat an updated food recall notice as a new scope-change event, not as a minor edit to a job that is already closed. Compare the updated notice with the version previously used, identify every newly affected product, batch, date code or location, re-screen all relevant stock and prepared food, replace outdated customer information and record who completed the second check.

TapTick can help multi-site operators issue a new task, collect site responses, record exceptions and corrective actions, and keep evidence visible in one place. It does not supply official recall data, decide whether a product is in scope or replace instructions from the supplier, the Food Standards Agency, Food Standards Scotland or the competent authority. See the TapTick features.

Why can a recall notice change?

A product withdrawal or recall can begin before every affected unit has been identified. Further investigation may add a batch, date code, pack size, country, store group or product. An update can also correct product details, change the action requested or provide a replacement customer notice.

A current example is the Food Standards Agency allergy alert for a Walkers Variety Snacks Sharing Box. The updated alert, last modified on 1 November 2026, added a further best-before date and stated that it replaced the original alert. That change is operationally significant: stock which did not match the first date may match the second.

The lesson is broader than that individual recall. A recall process needs a way to detect, compare and distribute changes after an initial stock check has begun or been completed.

What should happen first?

When an updated notice arrives, the incident owner should:

1. Authenticate the source. Use the current supplier communication or official FSA/FSS alert, not a screenshot forwarded without context.
2. Save the update. Record the alert reference, version, link, date and time received.
3. Compare it with the version used previously. Identify additions, removals, corrections and changed instructions.
4. Extend the control immediately. If the update may bring more stock into scope, stop sale and isolate potentially affected stock while the comparison is completed.
5. Reissue the task. Tell each relevant site that this is an update requiring another check, not a duplicate message.

Do not wait for the next routine stock count. The UK General Food Law duties in Article 19 require food businesses, within their respective activities, to initiate withdrawal procedures for food that does not comply with food-safety requirements, cooperate with producers and competent authorities, and pass on information needed to trace the food. The FSA/FSS joint guidance explains the practical steps for receiving and managing withdrawal and recall notifications.

How should the two notices be compared?

Use a short change log rather than relying on memory. Compare at least:

• official alert or supplier reference;
• product and brand name;
• pack size and product code;
• batch or lot code;
• use-by or best-before date;
• countries, regions or customers in scope;
• nature of the hazard;
• withdrawal, recall and consumer instructions;
• quarantine, return or disposal instructions; and
• point-of-sale notice or other communication material.

Label the differences clearly. For example: “Update 1 added best-before 16 January 2027; no change to product code, batch code, hazard or consumer action.” A concise statement gives sites a reliable basis for the second search and prevents teams from checking only the detail they happen to remember.

If the reason for an update is unclear, keep the wider precautionary control in place and ask the supplier or competent authority for clarification. Do not infer that an unmentioned batch has been cleared.

Must every site check again?

Every location that could hold the newly affected scope should provide a fresh response. This includes locations that:

• reported affected stock under the original notice;
• reported zero stock because the earlier batch or date did not match;
• did not stock the product at the time of the first check but may have received a later delivery;
• received transfers from another store, depot or central kitchen;
• hold stock in back rooms, off-site stores, vending areas or returns cages; or
• used the product as an ingredient or component of another item.

A previous “zero found” result proves only that the site checked the earlier scope at that time. It is not evidence that the site checked a newly added date code. Reissue the exact changed criteria and require a new confirmation.

For a multi-site operator, head office should track three states separately: sites that confirmed the updated check, sites that found affected stock and sites that have not responded. Silence is outstanding work, not a zero result.

What about food already opened or prepared?

The product search should extend beyond sealed retail packs. Check whether affected stock has been:

• opened or decanted;
• placed in a display, dispenser or self-service unit;
• used in sandwiches, salads, bakery products, meal deals or catering;
• repacked or labelled under the business’s own name;
• transferred to another site; or
• sold before the updated notice was received.

Use traceability, delivery, recipe, production and transfer records to establish where the newly affected stock went. The correct action for prepared products depends on the notice, the hazard and instructions from the responsible supplier or authority. Quarantine them while the position is confirmed; do not assume that removing the original packaging removes the recall risk.

Should the point-of-sale notice be replaced?

Yes, where the updated recall includes revised customer information. Remove superseded notices and display the current version in the required locations. Check websites, social posts, customer-service scripts and direct customer communications as well as physical point-of-sale notices.

The FSA says consumer recall communication should accurately identify the product, relevant batch or date information, the reason for the recall and what the customer should do. An outdated poster that omits a newly affected date may give a customer false reassurance.

Keep a copy or photo of both versions and record when the replacement was displayed. If the business sold the product online or through delivery channels, make sure the update reaches those customers through the channels available to the business.

Can previously quarantined stock be released?

Do not release quarantined stock because an update appears to narrow or change the scope unless the current written instruction clearly supports release and the responsible manager has verified the exact product details. If the stock was isolated under supplier or authority direction, obtain confirmation where needed before returning it to sale.

Keep release separate from the physical stock check. A useful record identifies the product, quantity, original reason for quarantine, authority for release, decision-maker, date and the evidence reviewed. If safe re-labelling or rework is proposed, follow the competent authority’s direction; the FSA guidance advises obtaining permission before using such a route.

What records should be kept?

Keep an incident history that shows what was known and done at each stage:

• the original and updated notices;
• when each version was received and by whom;
• a clear comparison showing what changed;
• the sites, channels and people notified for each version;
• fresh site responses against the updated scope;
• affected and zero quantities found;
• prepared products, transfers and customer sales considered;
• photos or copies of updated point-of-sale notices;
• quarantine, return, disposal or authorised release evidence;
• communications with the supplier and competent authority; and
• the manager’s verification and closure decision.

Do not overwrite the first record to make it look as though the wider scope was known from the start. The earlier version may explain why a site’s first response was reasonable at the time. Version history creates a defensible timeline and makes it possible to assess whether the update was handled quickly.

When can the updated recall be closed?

Close the updated action only when the current scope has been checked across every relevant location and channel, affected stock is controlled, required customer information is current, outstanding responses are resolved and the final disposition is recorded.

The FSA/FSS guidance recommends maintaining records, monitoring progress and reviewing the effectiveness of a withdrawal or recall. For a multi-site business, that means a manager should verify the response set rather than closing the incident when most sites have replied.

After closure, review how the update was detected and distributed. If the original action could not be reopened, site teams could not distinguish versions or a newly affected batch was missed, update the recall plan and next mock-recall test.

Practical update checklist

• Confirm the update through the supplier or official FSA/FSS source.
• Save the alert reference, version, link and receipt time.
• Write one clear statement of what changed.
• Extend stop-sale and quarantine controls where the scope may have widened.
• Reissue the recall task to every potentially affected site.
• Require a fresh response against the updated product, batch and date details.
• Check opened, decanted, prepared, transferred and online-sold stock.
• Replace superseded point-of-sale and customer information.
• Keep both notice versions and both rounds of site evidence.
• Do not release quarantined stock without clear written authority and verification.
• Escalate non-responsive sites until their status is confirmed.
• Close only after a manager verifies the complete updated scope.

Official sources

• FSA: Update 1 — PepsiCo updates its recall of Walkers Variety Snacks Sharing Box (last modified 1 November 2026)
• FSA: Food incidents, product withdrawals and recalls
• FSA and FSS: Guidance on Food Traceability, Withdrawals and Recalls within the UK Food Industry
• FSA and FSS: Food traceability, withdrawals and recalls quick reference guide
• Food Standards Scotland: Food and feed incidents
• UK legislation: Regulation (EC) No 178/2002, Article 19

Important: This article is general information based on UK official sources available on 3 November 2026. Follow the current notice and instructions issued for the specific product and contact the supplier, local authority or other competent authority where the scope or required action is unclear.