Food and beverage
Bakery and pastry: allergens
Many product lines, recipes that change, and information that has to be exact.
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.
Watch out
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.
Worth knowing
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.
A real case
The situation
A bakery switches flour supplier on price and nobody reviews the specs.
What you do
- Links each ingredient to its product lines
- Reviews affected specs when the supplier changes
What you get
Finds twelve lines needed a different declaration before it reached the labels.
The situation
A recipe changes and the label takes weeks to follow.
What you do
- Reviews labels when approving the recipe change
What you get
Label and product say the same thing.
The situation
A supplier changes an ingredient without notice.
What you do
- Asks them to communicate any change of composition
What you get
The change arrives before the complaint.
The situation
There are two hundred references and nobody knows which carry an allergen.
What you do
- Checks which references use that raw material
What you get
The review narrows to the affected ones.
The situation
Allergen information lives on a separate sheet.
What you do
- Keeps it with the product's sheet
What you get
It is consulted where people look.
The situation
A client asks about the composition of a specific run.
What you do
- Checks the version current on that date
What you get
You answer per run rather than per catalogue.
This article answers
- allergen control in bakery
- recipe change and labelling
- allergen information for customers
- flour supplier documentation