Building an allergen matrix that survives an audit

Allergen mislabelling is one of the most common reasons food gets recalled — and at the centre of nearly every allergen incident is a matrix that was wrong, or out of date. Get this one document right and you've closed off a whole category of risk. Here's how.

First, the 14

UK and EU law requires you to declare 14 named allergens whenever they're present. Your matrix exists to answer one question for every product you make: which of these does it contain?

Celery Cereals containing gluten Crustaceans Eggs Fish Lupin Milk Molluscs Mustard Tree nuts Peanuts Sesame Soybeans Sulphur dioxide & sulphites

What the matrix is — and why auditors care

An allergen matrix is a grid: products down one side, the 14 allergens across the top, a mark in every cell where a product contains (or may contain) that allergen. It's the master reference your labels, your spec sheets and your "free from" claims all trace back to.

Auditors care because it's a single point of failure. If the matrix is wrong, the label is wrong, and a wrong allergen label is a genuine safety risk — not a paperwork slip. So they test it: pick a product, ask you to justify every allergen mark from the recipe up. If you can't, that's a finding.

Where matrices go wrong

Almost always for the same handful of reasons:

It's a manual spreadsheet. Someone built it once, by hand, and every cell is a chance to mistype.
It drifts out of date. A recipe changes or a supplier reformulates an ingredient, and the matrix doesn't get the memo.
Sub-ingredients get missed. The seasoning blend that itself contains mustard or celery is easy to overlook when you only look at top-line ingredients.
Cross-contamination is ignored. The matrix records what's in the recipe but not what's on the line — the shared mixer, the airborne flour — so "may contain" warnings are missed.

Recipe-level, not product-level

The only reliable way to build a matrix is from the bottom up: tag each ingredient with its allergens, then let the product inherit them. Build it product-by-product from memory and you will eventually miss a sub-ingredient. Build it ingredient-by-ingredient and the maths does itself.

Building one that holds up

Start at the ingredient. Record the allergens for every raw material once, from its specification. Every product that uses it inherits them automatically.
Account for the line, not just the recipe. Map shared equipment and adjacent production to decide where a "may contain" is honest and necessary.
Link it to your recipes. When a formulation changes, the matrix should change with it — not wait for someone to remember.
Date and version it. An auditor's first question is "is this current?" A clear date and version answers it before they ask.
Make it exportable. You'll be asked for a clean copy for the audit pack and for customers. A one-click PDF beats screenshotting a spreadsheet.

How Prodara builds your matrix

Prodara OS includes an Allergen Manager that scans every ingredient in your system against all 14 UK and EU allergens and shows you the results in a review table — so you confirm or correct each detection rather than typing a grid from scratch.

From there it builds the product matrix automatically by rolling each ingredient's allergens up to every product that uses it — sub-ingredients included. Change a recipe and the matrix updates. When you need it for an audit, export an audit-ready PDF in one click, and the same allergen data feeds straight into your labels, so the grid and the pack can never disagree.

The bottom line

A good allergen matrix isn't a document you write — it's a calculation you keep current. Tag your ingredients properly, account for your lines, keep it linked to your recipes, and the matrix stops being the thing you dread before an audit and becomes the thing that quietly protects you all year.

Never hand-build a matrix again.

See the Allergen Manager build your matrix from your own ingredients.

Request details