What Should a Food Business Do When a Customer Reports Food Poisoning?

When a customer reports suspected food poisoning, treat it as a potential food-safety incident without assuming that your food caused the illness. Help the customer seek appropriate medical advice, record the facts accurately, protect any food that may still be under your control, preserve evidence and assess whether the information points to a wider risk that must be reported.

TapTick can help operators keep the original report, related checks, actions and management follow-up connected across sites. It does not determine the cause of illness, replace public-health investigation or decide whether a statutory notification is required. See the TapTick features.

What should the first response be?

Respond calmly and take the report seriously. A customer may be unwell, anxious or angry. The person receiving the complaint should know how to capture the essentials and contact the manager on duty without delay.

If the customer is seriously unwell, encourage them to seek urgent medical help. In Ireland, the Food Safety Authority of Ireland (FSAI) advises a person who suspects food poisoning to contact their GP. The business should not attempt to diagnose the illness or advise on treatment.

Thank the customer for reporting the concern and explain what will happen next. Give them a named contact or incident reference where possible. Do not say that the food definitely caused the illness, but do not dismiss the report simply because no one else has complained or because the food looked normal.

What information should you record?

Capture the customer’s account in their own words before memories, stock and shift information change. Record:

• the customer’s name, preferred contact details and consent for follow-up;
• who became ill and how many people may be affected;
• the symptoms described, when they started and whether medical advice was sought;
• what each affected person ate or drank, including accompaniments, sauces, ice and garnishes;
• the date, time and site of purchase, collection, delivery or service;
• order, receipt, delivery-platform or loyalty details that may identify the transaction;
• product name, portion, batch, use-by or best-before date where relevant;
• whether other people ate the same food and whether they became ill;
• whether any food or packaging remains with the customer; and
• the time the business received the report, the person who took it and every escalation made.

Record only information needed to manage and investigate the incident. Handle health and contact information according to the business’s privacy procedures and restrict access to people who need it.

What food and evidence should you protect?

Where the report identifies a particular food, batch, preparation period or ingredient, consider placing related stock on hold while the risk is assessed. Keep it clearly identified and separate from food available for sale. Do not quietly discard everything: destruction can remove evidence needed by the business or an investigating authority.

Preserve relevant records, including:

• supplier, delivery, batch and traceability information;
• cooking, cooling, reheating, hot-holding and refrigeration checks;
• opening, cleaning and equipment records;
• recipes, allergen information and ingredient substitutions;
• staff rotas and any employee-illness reports;
• other complaints, returns or unusual waste from the same period; and
• photos, packaging, labels and any retained sample or suspected food.

Keep the original record intact. Add corrections or new information as dated updates rather than overwriting what was first reported.

What should the initial investigation check?

The first review is a risk assessment, not a final diagnosis. Look for information that changes the urgency or scope:

• more than one person with similar symptoms;
• another complaint linked to the same food, site, shift or supplier;
• a vulnerable customer, hospitalisation or severe symptoms;
• a failed temperature, cooking, cooling, hygiene or allergen control;
• an ill food handler or unexplained absence;
• a supplier alert, positive test or similar concern at another site;
• food still on sale or distributed to other businesses or locations; and
• a product that cannot be traced or a missing control record.

Check the actual records and speak to the people involved. Avoid creating or backfilling records after the complaint. If a required check was missed, record it honestly and manage the resulting uncertainty.

Some foodborne illnesses appear hours or days after eating, and the last meal eaten is not automatically the source. That uncertainty is a reason for careful evidence gathering, not for delaying action when the available facts suggest a wider hazard.

When must the incident be reported?

A single allegation does not automatically prove that food is unsafe. The legal threshold is reached when the operator considers or has reason to believe that food it has handled or placed on the market is not compliant with food-safety requirements or may be injurious to health.

Article 19 of Regulation (EC) No 178/2002 requires an operator in that position to act immediately. Depending on the circumstances, this includes withdrawing affected food, informing the competent authority, accurately informing consumers and recalling food when other measures are not sufficient. Retailers and distributors must cooperate, provide traceability information and support action within the limits of their activities.

Ireland

Food businesses can use the FSAI’s Report a Food Incident form. It requests the hazard, associated illness, product and batch details, distribution, testing, traceability and actions already taken. The FSAI publishes an out-of-hours incident number on that page. If the facts suggest unsafe food or a risk beyond the individual complaint, contact the FSAI and the relevant competent authority promptly rather than waiting for laboratory certainty.

England, Wales and Northern Ireland

The Food Standards Agency’s incident-reporting guidance says businesses must inform the local authority or port health authority and the FSA where there is reason to believe food is unsafe and should be withdrawn or recalled. The current guidance provides separate incident email addresses for England, Wales and Northern Ireland and lists the information to include.

Scotland

Food Standards Scotland says a food business that has reason to believe an incident has occurred must inform its local authority, inform Food Standards Scotland where relevant, withdraw or recall affected food and notify the authority of that action. Use its food and feed incidents guidance for the current reporting route.

Reporting is not an admission that the business caused the illness. It allows the competent authority to connect complaints, testing and epidemiological evidence that one business cannot see. Follow any instructions about samples, stock, customer communication and reopening a process.

What changes for a multi-site business?

One customer report may identify a wider supply or process issue. Head office should be able to search quickly for the same product, batch, supplier, recipe, equipment, employee symptom or control failure at other locations.

A multi-site procedure should define:

• who owns the incident at site and group level;
• which facts trigger an immediate cross-site check or stock hold;
• how sites identify affected stock and report quantities;
• who contacts suppliers, insurers and competent authorities;
• how customer communications are approved and kept consistent;
• how unresolved locations and missing evidence are escalated; and
• how the incident is closed, reviewed and translated into preventive action.

Do not wait for several sites to receive complaints independently. A central view can reveal a pattern early enough to protect customers and narrow the affected stock.

What should staff avoid doing?

• Do not diagnose the illness or tell the customer which organism caused it.
• Do not promise compensation, deny responsibility or speculate about blame.
• Do not ask the customer to return or transport suspect food without checking the safe and appropriate route.
• Do not discard implicated stock, packaging or records before the investigation decision.
• Do not alter checks, rotas or other records after the event.
• Do not contact other customers publicly or issue a recall without coordinating the risk decision and competent authority where required.
• Do not keep selling suspect food merely because the complaint is unconfirmed.

Practical response checklist

• Help the customer seek appropriate medical advice if needed.
• Record symptoms, timing, food, transaction, contact and other affected people.
• Give the report an incident reference and escalate it immediately.
• Identify and hold potentially affected food where proportionate.
• Preserve product, packaging, traceability and control records.
• Check for related complaints, staff illness and control failures.
• Assess whether other sites, customers or businesses may be affected.
• Contact the competent authority promptly when the legal or risk threshold is met.
• Record every decision, action, communication and authority instruction.
• Complete root-cause review and verify preventive action before closure.

Official sources

• FSAI: Making Complaints
• FSAI: Report a Food Incident
• EUR-Lex: Regulation (EC) No 178/2002, Article 19
• UK legislation: Regulation (EC) No 178/2002, Article 19
• FSA: Report a food safety incident for local authorities and businesses
• FSA: Food or feed incidents—what to do
• Food Standards Scotland: Food and feed incidents