Free 21-item 8D checklist (PDF): https://8d-gate.vercel.app/free-8d-checklist?utm_source=devto&utm_medium=article&utm_campaign=food-complaint_checklist (enter your email to download)
If your background is automotive supplier quality, a food or FMCG complaint can feel like a different sport. The customer may not ask for an 8D at all. The first hours are about hold, withdrawal and recall decisions, not a portal form. Traceability is measured in lots, shifts and ingredients rather than part numbers. And the investigation often sits inside a food safety system rather than a customer-dictated template.
This post is for people who know formal 8D and are learning how food complaint handling differs - and for food-quality people asked why theirs "doesn't look like an 8D." It is deliberately general. Food law, retailer codes and customer manuals change; I am not quoting clause numbers or inventing statistics. Check what applies to your plant and customer.
Earlier posts covered weak D4s, audit findings, symptom-only actions, rejected-8D resubmits, and aerospace/medical CAPA. Here the angle is sector: food complaint root cause versus a formal 8D wrapper.
How food / FMCG complaint handling tends to feel different
Speed of containment is the first product. Before anyone debates root cause: is product still in the plant, warehouse, transit, on a shelf, or already with consumers? Hold, withdraw and recall sit next to the investigation, not after it.
Traceability is the backbone of containment. Lot codes, production dates, lines, shifts, ingredient batches and packaging materials matter immediately. "We sorted stock" is incomplete without a clear map of which codes are affected and why neighbouring codes are not.
The food safety system is often the home of the work. Many plants run complaints through their food safety / HACCP-oriented system: hazard thinking, prerequisite programmes, critical control points, monitoring records, and corrective action when a control fails. An 8D can still be the investigation method, but the record the auditor or customer follows may be the food-safety CAPA or complaint file, not a D1-D8 template.
Retailers and brand owners may own the format. Private-label and brand customers often have their own portals, severity grades and timelines. Some accept an 8D; many want their form.
Consumer complaints bring incomplete evidence. Unlike a plant-to-plant defect with retained samples, a consumer complaint may arrive with a half-eaten pack, a photo, or only a description. Decide what can be verified and what remains a hypothesis.
Public and regulatory paths can sit beside the quality report. Depending on the issue (allergen, foreign body, pathogen concern, mislabel), notification or recall processes may run separately. Those are owned by the brand / legal / food-safety lead and the applicable rules - not by the 8D template.
Where 8D discipline still helps
Even when nobody asks for an 8D, the discipline travels well:
- Separate containment from cause. Holding product protects the consumer. It does not explain why the defect happened.
- Ask occurrence and escape. Why was the product made this way, and why did checks not stop it?
- Demand a verified cause. "Possible environmental contamination" is a hypothesis. A verified cause needs a link you can show: swab results, detector log gaps, seal-check data, supplier CoA mismatch, or a recipe/label change that lines up with the complaint window.
- Link every action to a cause. Retraining and extra inspection only count as corrective if they address a cause you proved.
- Plan effectiveness evidence. After the change, what will you look at, for how long? Lot trend, complaint rate, CCP monitoring - pick something measurable.
Keep the thinking; adapt the wrapper.
Common weak root causes in food complaint files
- "Operator error / did not follow hygiene rules." Stops at the person. What about training effectiveness, line design, time pressure, or a procedure hard to follow at speed?
- "Isolated incident / first time." Frequency is not a cause. Even a first event has a mechanism.
- "Supplier issue" with no flow-down evidence. Naming the ingredient supplier is a direction, not a closed cause. What was wrong, how was it verified, and what changed at the supplier and in your incoming checks?
- "Foreign body - source unknown, increased inspection." Extra inspection is detection. Without a credible source, the same object can return.
- "CCP was in control, so not a food-safety issue." CCP charts can be in limits while a complaint is still real. Do not use "CCP OK" as a substitute for investigating what arrived.
- "Consumer misuse." Sometimes true, often unproven. If you claim it, show why - and still check whether pack design or instructions contributed.
These are food-flavoured versions of unverified or symptom-level causes.
When to run full 8D thinking
| Situation | Typical food path | Where 8D-style depth still pays |
|---|---|---|
| Clear process excursion with retained samples | Complaint / CAPA in food-safety system | Full occurrence + escape + effectiveness |
| Consumer complaint, thin evidence | Triage, risk grade, limited lab work | Document what was and was not verifiable |
| Allergen / labelling / foreign-body risk | Hold/recall path + investigation | Traceability boundary + why escape failed |
| Retailer portal form required | Their template and SLA | Map fields to cause, actions, evidence |
| Recurring low-level quality complaints | Trend + CAPA | Treat the pattern as the problem |
Use the required form. Borrow 8D structure for the sections that usually go soft: cause verification, escape, and effectiveness.
A short self-check before you close
- Is the affected lot / code boundary written down, with a reason for what is in and out of hold?
- Is the cause a mechanism you can point to with data or a trial - or still a guess?
- Did you answer why it was made and why it was not caught?
- Does each corrective action name the cause it addresses?
- Is there an effectiveness check with a timeframe, or only "monitoring continues"?
- If a food-safety control was involved, is the system record updated, not only the narrative?
A checklist for the core logic
Whatever the sector, the same core questions decide whether a complaint investigation holds up: is the cause verified, does each action link to a cause, is containment complete, is effectiveness shown. The free 8D Gate checklist covers these in 21 items you can run through before you close a complaint or send a report. It does not cover food law, retailer codes, HACCP or any customer-specific requirement.
Get the 21-item PDF checklist: https://8d-gate.vercel.app/free-8d-checklist?utm_source=devto&utm_medium=article&utm_campaign=food-complaint_checklist (enter your email to download)
Free templates and tools (5 Whys, fishbone, Is/Is-not, CAPA form): https://8d-gate.vercel.app/free-8d-quality-tools?utm_source=devto&utm_medium=article&utm_campaign=food-complaint
If you'd rather have all of those templates in one download (Word, PDF and Excel), there is a paid 8D Template Pack for about €9: https://8d-gate.vercel.app/8d-template-pack?utm_source=devto&utm_campaign=food-complaint (each template is also free on its own page).
Advisory only. The checklist is a self-check before you send. It does not replace your customer's quality or food-safety review, your own sign-off, or any legal, retailer, HACCP or customer requirement.
Question for practitioners who work food and also supply other industries: when a complaint hits, do you start in the food-safety CAPA system and only wrap an 8D if the customer asks - or the other way around?
Top comments (0)