Almost everything written in English about allergen training assumes an American frame: nine allergens, a federal statute, a state health department. None of it applies in Antwerp or Rotterdam. The list is different, the legal basis is different, and the point at which the obligation bites is different in a way that matters operationally.
In the Benelux this is not really a labelling rule. It is about the twenty seconds in which somebody at a counter, often the newest person on the rota, gives an answer a customer will act on. The guide is written for a QSR network, but the legal position applies to foodservice generally: a hotel breakfast, a company canteen, a bakery counter, a hospital kitchen serving a tray.
Fourteen names, and where the law says they have to appear
Regulation (EU) 1169/2011 is the instrument. Annex II lists fourteen: cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, nuts, celery, mustard, sesame seeds, sulphur dioxide and sulphites above 10 mg/kg or 10 mg/l, lupin, molluscs.
Art. 9(1)(c) makes their presence a mandatory particular. Art. 21 governs the typography: where there is an ingredient list, the allergen has to be emphasised so it stands out from it. That is why allergens appear in bold on a packaged product, and it is worth staff understanding, because it explains why a supplier label is readable at a glance and a recipe card is not. Both articles concern prepacked food, and in a QSR most of what you sell is not prepacked.
Article 44 is the one that reaches the counter
Art. 44(1)(a) extends the allergen obligation to non-prepacked food, with the detail left to national implementation. This is the article your operation actually runs on, and it changes the problem: the information is not printed on the item, so it comes from somewhere else, and in most service formats that somewhere else is a person. Belgium and the Netherlands implemented it differently in wording and almost identically in effect.
Belgium, the KB of 17 July 2014. The information may be given orally or in writing. In writing means displayed visibly at the point of sale, or held in a register there with a clearly visible pointer telling the customer it exists. Orally is permitted on one condition: a member of staff must be present who can give correct and complete information.
The Netherlands, the Warenwetregeling allergeneninformatie niet-voorverpakte levensmiddelen. Art. 2 requires a clearly visible indication of where the information is available, the information itself being written or electronic, freely accessible, comprehensible and legible. Art. 3 permits oral information provided it is immediate and correct, provided the written or electronic version is available both to staff and to the inspection, and provided a visible notice directs the customer to ask.
Two things follow. The written file is not optional even where you answer orally: it is what the oral answer derives from and what an inspector asks to see. And the legal quality of the answer is a property of the person giving it. Correct and complete in Belgium, without delay and correctly in the Netherlands. That is a competence requirement written into a food information rule.
No article says train them, and three things still do
Be accurate here, because overstating it is the fastest way to lose a room of operators who know the regulations. Allergen training is not named anywhere as a standalone legal obligation. No article says staff shall receive allergen training every twelve months. It becomes mandatory through three routes.
The first is the accuracy duty above. If the law permits an oral answer only when the person can give it correctly and completely, that ability is the condition on which your service model is lawful. Training is how you produce it.
The second is Regulation (EC) 852/2004, Annex II, Chapter XII: food handlers are supervised and instructed and/or trained in food hygiene matters in line with their occupational activity. It prescribes no course, no certificate, no duration, no refresh interval. It is an obligation of result, and in line with their occupational activity is the licence to train the counter differently from the kitchen.
The third applies only to certified sites, and there it is decisive. BRCGS Food Safety Issue 9, clause 7.1.4 requires all employees to receive allergen awareness training and training in the site's allergen procedures, explicitly including engineers, agency staff and contractors. For a production site supplying a QSR chain, that is usually the sharpest instrument in the discussion.
The competence the rule is actually describing
Read art. 3 of the Dutch regulation and the Belgian KB side by side and you can reverse engineer what the person at the counter has to be able to do.
They have to know the fourteen as a defined list, not as a general idea of what people react to. They have to know where the written file is, physically, in that building, on that shift, and reach it fast enough that the answer is still immediate. They have to know the difference between what the recipe contains and what the process may have introduced, because a customer asking about peanuts in a shared fryer is asking something the ingredient list does not answer. And they have to know what to do when unsure.
That last one deserves its own scenario. The correct behaviour when uncertain is never to guess and never to reassure: check the file, or say plainly that the item cannot be guaranteed. A network where staff know they are allowed to say that is safer than one where they have memorised more.
Build the answers, not the list
Most allergen courses teach the fourteen and stop, producing staff who can recite a list and still get the question wrong. Build the course around the questions actually asked.
Take fifteen to twenty situations from your own menu and complaint log. A parent asks about milk in a specific item. Someone asks whether the fryer is shared. Someone asks about a bought-in sauce, where the answer depends on a supplier specification you did not write. Someone asks about an item changed last month, and the card at the till predates the change.
Each has a correct action, usually the same shape: check the file, answer from it, or decline to guarantee. Teaching that shape through scenarios travels between sites better than teaching the list, and it produces knowledge check results you can read afterwards, because a wrong answer tells you which situation that site cannot handle.
Cross-contact belongs to the kitchen, and it is a different lesson
Keep the two apart when you design the rollout. The counter question is an information duty. Cross-contact is a handling duty, taught where the work happens: separate utensils, order of preparation, the shared fryer, the cleaning step between two products, the glove change nobody times. Front of house needs to understand it well enough to answer honestly; kitchen staff need to prevent it. Different modules, different scenarios. Merging them produces one long course that satisfies neither role.
When the menu moves, the answer moves
The failure mode that produces incidents in multi-site foodservice is almost never ignorance of the fourteen. It is a site answering from a superseded version.
A supplier reformulates a sauce. A recipe is adjusted for cost. A seasonal item arrives with two new allergens. The specification is updated centrally, the card at site nineteen is not, and somebody gives an answer that was correct in March. The written file and the trained answer have to move on the same date, or the file becomes evidence against you rather than for you.
So allergens belong inside your change process rather than in an annual training slot. Every menu or supplier change is an allergen event until somebody has checked that it is not.
Keeping the allergen answer current in Aristotl
The specification you already maintain, whether a matrix, a recipe database or a set of supplier sheets, is the source. Aristotl converts it into short scenario based modules rather than a list to memorise, so what staff practise is the answer they will have to give.
Assignment runs by role and by site, which lets the counter version and the kitchen version differ without maintaining two programmes. Each person receives it in their own language, which matters in a sector where the shift rarely shares one.
When a specification changes, the module changes with it and goes out as a short refresh to the people it affects rather than a full re-run. Completion is tracked against the version, so the record shows which allergen answer a person was trained on and when, per site and per role, exportable when an inspector or a certification body asks.
Take one item off next month's menu
Bring one new or reformulated item and the supplier sheets behind it. In a demo we build the counter scenarios and the kitchen handling module from those documents, and show what reaches each site, in which language, and what the record looks like afterwards.