Customer complaint trending: spot the pattern before your customer does

A retailer's technical team rarely calls about the first complaint. They call about the third. By that point they have already done the trending themselves, and the question they ask is why you had not.

Most small manufacturers handle individual complaints well. The customer gets a reply, the batch gets checked, a letter goes out and the record is closed. The weakness is that each complaint is treated as a separate event, so a pattern that runs across three closed records never gets looked at as a pattern.

What auditors and customers expect

BRCGS, SALSA and ISO-based systems all expect the same basic things from complaint handling: every complaint recorded, investigated in proportion to its seriousness, and the data analysed so that repeat issues lead to corrective action. ISO 9001 and ISO 22000 also list customer feedback as an input to management review.

The part that most often produces a finding is the analysis. An auditor will pick a category, such as foreign body, and ask to see every complaint of that type in the last year and what was done about the pattern. If the answer is a stack of individually closed forms, the trending requirement has not been met.

Trending only works if the data is consistent

You cannot trend free text. "Bit of plastic in the bag", "hard foreign object" and "plastic piece found" are the same complaint written three ways, and a search will only find one of them. Consistent fields are what make a register searchable.

Decide what counts as a trend before it happens

If spotting a trend depends on someone remembering that a similar complaint came in two months ago, it will depend on who is on shift. Written trigger rules take the judgement out of it. Two rules cover most of what matters:

• Category trend. The same category twice or more in three months, across any product. This catches site-wide issues such as a failing sieve, pest activity or a packaging supplier problem.
• Product trend. The same product with the same category twice or more in six months. This is the stronger signal, because it points at one line, one recipe or one ingredient.

A trigger should do more than change a colour on a report. It should tell a named person, and it should lead to an investigation that looks at all the related complaints together rather than each one on its own.

Normalise by volume

Raw counts mislead. A best-seller will always produce more complaints than a slow line. Complaints per million units (complaints divided by units sold, multiplied by a million) puts products and months on the same scale, and many retailers ask suppliers to report it. Track it monthly alongside the counts.

Targets, root cause and closure

A complaint register also needs clocks. A common policy is to acknowledge within three working days and complete the investigation within 28 calendar days. Your customers may set stricter terms. What matters is that the dates are recorded so you can show they were met, and that overdue complaints are visible without anyone having to count.

Closure should require a recorded root cause and corrective action. "Customer refunded" is a response to the customer, not an investigation. Where the root cause points at a process failure, it belongs in your non-conformance and CAPA records, and a complaint about a specific batch should prompt a trace to check which other customers received it.

What untrended complaints cost

• The repeat you could have prevented. Every complaint after the second one in a pattern is a cost that the trend rule would have avoided.
• Customer confidence. A retailer that spots your pattern first starts asking what else you are missing, and that conversation tends to end in extra audits or a delisting review.
• Audit findings. Complaint analysis is an easy area for an auditor to sample and a common source of non-conformities.
• Technical manager time. Rebuilding a year of complaint data from emails and spreadsheets before an audit takes days.
• Enforcement risk. A pattern of foreign body or allergen complaints that was never investigated as a pattern is hard to defend if it reaches Trading Standards.

A short checklist

• Record every complaint with a category, sub-issue, product, batch, source and severity chosen from fixed lists.
• Write down your trend rules, for category and for product, and who is told when one triggers.
• Track complaints per million units monthly, not only raw counts.
• Set acknowledgement and investigation targets and make overdue complaints visible.
• Require a root cause and corrective action before a complaint can be closed.
• Trace complained-about batches to see who else received them.
• Keep despatch errors in their own register and trend them by person and type.
• Take a complaints summary to every management review.

The bottom line

Handling each complaint well is necessary, but on its own it does not meet the standard. The trending is what an auditor or retailer will test, and it only works if complaints are recorded the same way every time and checked against written rules as they arrive. Set that up once and a repeat problem shows up in your own register first.

Frequently asked questions