> For the complete documentation index, see [llms.txt](https://docs.foodcore.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.foodcore.io/allergens/add-allergens.md).

# Add allergens to ingredients & recipes

{% hint style="warning" %}
FoodCore helps you organise and manage the information you need, but you should always check official guidance or speak to your local authority if unsure.
{% endhint %}

Setting allergens on your ingredients is the single most important thing you can do in FoodCore. Everything downstream — recipe allergen summaries, the allergen matrix, and the ingredient list on your labels — is calculated from what you enter here. If you get it right at the ingredient level, the rest of the system takes care of itself.

## The 14 UK/EU Declarable Allergens

Under UK and EU food law, the following 14 allergens must be declared whenever they're present in a food product:

1. **Cereals containing gluten** (wheat, rye, barley, oats, spelt, kamut)
2. **Crustaceans** (prawns, crab, lobster, crayfish)
3. **Eggs**
4. **Fish**
5. **Peanuts**
6. **Soybeans**
7. **Milk** (including lactose)
8. **Nuts** (almonds, hazelnuts, walnuts, cashews, pecans, Brazil nuts, pistachios, macadamia/Queensland nuts)
9. **Sesame**
10. **Sulphur dioxide and sulphites** (at concentrations of more than 10 mg/kg or 10 mg/litre)
11. **Celery** (including celeriac)
12. **Mustard** (including mustard leaves, seeds, and flour)
13. **Lupin** (including lupin flour and seeds)
14. **Molluscs** (clams, mussels, oysters, scallops, snails, squid)

Each of these must be declared individually and emphasised on your ingredient list — typically in bold — so that customers can identify them at a glance.

## How to Set Allergens on an Ingredient

**Open** the ingredient you want to update. You can find it via **Ingredients** in the main navigation, or by searching for it by name.

**Click** the **Allergens** tab inside the ingredient detail page.

You'll see a list of all 14 declarable allergens. For each one, **select** the appropriate status:

* **Contains** — this allergen is an ingredient in this product. For example, plain wheat flour contains gluten; whole eggs contain egg. Use this whenever the allergen is intentionally and directly present.
* **May Contain** — there is a risk of cross-contamination. For example, an oat product made in a facility that also processes tree nuts. This should reflect real manufacturing or preparation risk, not just a blanket disclaimer.
* **(unticked)** — the allergen is not present and there is no cross-contamination risk.

Once you've set the status for each allergen, **click Save**.

### Using "None Applicable"

Some ingredients are genuinely allergen-free and you've verified this — either from the supplier's specification sheet or a lab certificate. You can mark such an ingredient as **None applicable** to signal that you've actively checked, rather than simply not filled it in yet. This matters during an allergen audit, which distinguishes between "not set" and "confirmed none".

## Downstream Effect: Recipes and Labels Update Automatically

This is the key benefit of setting allergens at the ingredient level. The moment you save a change:

* Every **recipe** that uses this ingredient has its allergen summary updated immediately
* The **allergen matrix** reflects the change across your full menu
* Any **label** generated from those recipes will include the correct allergen information
* The **Allergen Statement** block on your labels will bold the relevant allergens in the ingredient list automatically

This means you never need to manually update a recipe or label when a supplier changes their product. You update the ingredient once, and everything else follows.

## What If a Supplier Changes Their Product?

This happens. A supplier switches to a shared facility, or reformulates a product. When that occurs:

1. **Update** the ingredient allergen status to reflect the change
2. **Check** the allergen matrix to see which recipes are now affected
3. **Review** any labels in your print queue or saved label designs to make sure they still reflect current data
4. **Consider** running the allergen audit to check for any remaining gaps

## A Note on Due Diligence

FoodCore records what you enter, but it can only be as accurate as the information you put in. Always cross-reference ingredient allergen data against the supplier's specification sheet or technical data sheet. If a supplier can't provide allergen documentation, that's worth noting as a food safety risk.

## What's Next

* [Understand contains vs may contain](https://docs.foodcore.io/allergens/contains-vs-may-contain.md)
* [Run the allergen audit](https://docs.foodcore.io/allergens/audit.md)
* [Generate a Natasha's Law compliant label](https://docs.foodcore.io/labels/natashas-law.md)
