The 14 EU allergens: a complete labeling guide under Reg. 1169/2011

Allergen labeling is one of the few areas of compliance where a single mistake can put a consumer in hospital and a manufacturer in court. It is also one of the most checkable — the EU defines exactly which allergens must be declared, and the rule applies consistently across food and supplements. Here is what every manufacturer needs to have locked down.

The legal basis

Allergen declaration in the EU is governed by Regulation (EU) No 1169/2011 on the provision of food information to consumers. It defines a list of substances that must always be declared when present, and sets rules for how that declaration appears.

The principle is simple: if a listed allergen is in the product, the consumer must be able to see it clearly. The execution is where care is needed.

The 14 allergens

The regulation lists 14 allergens or groups that must be declared:

1. Cereals containing gluten (such as wheat, rye, barley, oats)

2. Crustaceans

3. Eggs

4. Fish

5. Peanuts

6. Soybeans

7. Milk (including lactose)

8. Nuts (tree nuts such as almonds, hazelnuts, walnuts, and others)

9. Celery

10. Mustard

11. Sesame seeds

12. Sulphur dioxide and sulphites above defined levels

13. Lupin

14. Molluscs

This list is the baseline every EU-facing product is measured against.

How declaration works

Under the regulation, allergens present in the product must be emphasised in the ingredient list — typically through formatting such as bold type — so they stand out from the surrounding text. The allergen has to be named in a way the consumer understands.

The emphasis requirement is easy to overlook. Listing an allergen in the ingredients is not enough on its own if it is not distinguished in the way the rule requires.

Why allergens hide in supplements

In supplements, allergens often arrive through ingredients that are not obviously allergenic. They can come in through excipients, carriers, flavours, capsule materials, or processing aids — not just the headline actives.

A softgel shell, a flowing agent, a natural flavour, a protein source — any of these can introduce a listed allergen. This is why allergen checking cannot stop at the active ingredients; it has to cover everything in the formula, down to the smallest excipient.

Cross-contamination and precautionary labeling

Beyond what is deliberately in the formula, there is the question of cross-contamination from shared equipment or facilities. Precautionary allergen labeling — the "may contain" style statement — addresses this, and is its own area of judgement and good manufacturing practice.

The deliberate-presence declaration and the precautionary statement are different things, and both deserve attention.

Why manual checking is risky

The failure mode is almost always the same: an allergen enters through a minor ingredient, nobody flags it, and it does not make it onto the label correctly. With formulas containing dozens of ingredients, each with its own allergen profile, manual cross-checking is exactly the kind of repetitive task where human attention slips.

The stakes make this worse than most compliance errors. An allergen mistake is not a paperwork problem — it is a safety and recall problem.

Automating the check

The robust approach is to attach an allergen profile to every ingredient and let the system roll those profiles up across the whole formula automatically. When an allergen-bearing ingredient goes in, the allergen appears in the product's declaration without anyone having to remember it.

The formula composition drives the allergen declaration directly, so the two can never drift apart.

The takeaway

The 14 EU allergens are a fixed, knowable list, and the rule applies across food and supplements. The danger is not knowing the list — it is missing an allergen that entered through a minor ingredient, or failing to emphasise it correctly. Automatic roll-up from ingredient to declaration removes the part of the process most prone to human error.

Lemoniq attaches allergen data to every ingredient and rolls it up across the formula automatically, so the declaration always matches what is actually in the product. See how it works