---
id: KB-AL-007
url: https://app.codecontract.io/help/food-and-beverage/bakery-and-pastry-allergens
idioma: en
categoria: sector-alimentacion
subcategoria: panaderia
audiencia: usuario
nivel: intermedio
actualizado: 2026-08-13
tambienEn: [es]
relacionados: [KB-AL-006, KB-NO-007]
citadoPor: [KB-AL-011, KB-AL-013, KB-CS-038, KB-AL-020]
---

# Bakery and pastry: allergens

_Many product lines, recipes that change, and information that has to be exact._

**Responde a:** allergen control in bakery · recipe change and labelling · allergen information for customers · flour supplier documentation

A bakery has an unusual problem: hundreds of product lines, recipes adjusted by season or ingredient price, and consumer information that allows no approximation. Every recipe change is a label change and a spec change.

## Where it usually breaks

| Point | What happens | Consequence |
| --- | --- | --- |
| Changing an ingredient supplier | The new one has a different allergen declaration | The spec stops being true with nobody noticing |
| Recipe tweak in production | Changed on the floor and not on paper | Label and product no longer match |
| New seasonal product | Launched fast, with a half-finished spec | It is the one that fails an inspection |
| Information to catering customers | A PDF is sent and then ages | The customer misinforms using your data |

> [!IMPORTANT]
> The first row is the most treacherous. A supplier change is decided by purchasing on price or lead time, and nobody tells whoever maintains the specs. If supplier documentation enters through the same door as their onboarding, the change becomes visible.

## What must be linked

1. **A spec for each ingredient, with its supplier** — With allergen declaration and its date, not an email from three years ago.
2. **Each product line with its ingredients** — It is what lets you see, when one changes, which products are affected.
3. **Spec versions, retained** — So you can say what the product contained on the date it was sold.
4. **And what is delivered to customers, with proof** — Which version they received and when, especially for catering and institutional customers.

> [!WARNING]
> The fourth matters more than it looks. If a restaurant misinforms a customer using an outdated spec of yours, the conversation about who failed depends entirely on whether there is a record of which version you sent and when.

## Cross-contamination

The other front is process, not paperwork: what is produced after what, how you clean between batches, and what is declared as "may contain". What is paperwork is the record of that cleaning and of the production order, which is what audits ask for.

**En corto**

- Every ingredient change triggers a review of the affected specs.
- Every spec version is kept with its date.
- And what is delivered to the customer is recorded, not merely sent.

> [!NOTE]
> It is the same mechanic as safety data sheets in chemicals: a document that changes, that must reach whoever uses it, and whose current version at any date you must be able to prove.

**What about small bakeries?**

Same obligation, fewer lines. Usually solved with a well-linked ingredient list.

**How often should specs be reviewed?**

Whenever something changes, plus a full annual review.

**Must old specs be kept?**

Yes: they prove what was declared at each moment.

## Ejemplos

**A bakery switches flour supplier on price and nobody reviews the specs.**

- Links each ingredient to its product lines
- Reviews affected specs when the supplier changes

→ Finds twelve lines needed a different declaration before it reached the labels.

**A recipe changes and the label takes weeks to follow.**

- Reviews labels when approving the recipe change

→ Label and product say the same thing.

**A supplier changes an ingredient without notice.**

- Asks them to communicate any change of composition

→ The change arrives before the complaint.

**There are two hundred references and nobody knows which carry an allergen.**

- Checks which references use that raw material

→ The review narrows to the affected ones.

**Allergen information lives on a separate sheet.**

- Keeps it with the product's sheet

→ It is consulted where people look.

**A client asks about the composition of a specific run.**

- Checks the version current on that date

→ You answer per run rather than per catalogue.