Compliance · · 9 min read
FIC Software for Contract Catering: Automate Allergen Labelling Instead of Retyping It
By Shideh Heravi, Founder
In Austria, around 2.5 million people eat in contract and institutional catering every day; in Germany, the figure is more than 16 million diners.12 For every one of these meals, the business must be able to say which of the 14 EU allergens it contains. Anyone still handling this with Excel lists and supplier data sheets in binders is working against the clock. This article shows what the EU Food Information to Consumers Regulation (Regulation (EU) No 1169/2011, known in German as LMIV) requires, where large kitchens typically fall short, and how FIC software automates allergen labelling.
- 2.5 million meals a day in Austrian contract and institutional catering1
- 16 million+ diners a day in German contract and institutional catering2
- 14 allergens under Annex II of the LMIV that must always be declared3
What the LMIV actually requires
Regulation (EU) No 1169/2011, the LMIV for short, has applied in all EU member states since 13 December 2014.3 For non-prepacked food, meaning everything served in staff canteens, university cafeterias, hospitals, care homes and restaurants, Article 44 makes only one particular mandatory: information on substances that can cause allergies or intolerances.3 Nutrition labelling is voluntary for loose food.
Annex II of the Regulation defines which substances these are. There are 14 allergens or allergen groups:
- Cereals containing gluten (wheat, rye, barley, oats, spelt, kamut)
- Crustaceans
- Eggs
- Fish
- Peanuts
- Soybeans
- Milk (including lactose)
- Tree nuts (almonds, hazelnuts, walnuts, cashews, pecans, Brazil nuts, pistachios, macadamia nuts)
- Celery
- Mustard
- Sesame seeds
- Sulphur dioxide and sulphites (at 10 mg/kg or 10 mg/l and above)
- Lupin
- Molluscs
Article 44(2) leaves it to the member states to decide how this information must reach the guest.3 That is why the rules in Austria and Germany differ in the detail. The ground rules for every business, from the letter code to verbal information, are set out in Allergen labelling in restaurants.
Austria and Germany compared
| Austria | Germany | |
|---|---|---|
| Legal basis | Austrian Allergen Information Regulation (Allergeninformationsverordnung), BGBl. II No. 175/20144 | German Food Information Implementing Regulation (LMIDV), § 45 |
| Written information | Menu, notice, menu plan; the letter code A to R is common practice6 | Menu, sign on the food, notice or electronic5 |
| Verbal information | Permitted if a trained person provides the information, written documentation is available and a clearly visible notice points to it6 | Permitted if written or electronic documentation is easily accessible on request and a notice is displayed on the premises5 |
| Training | Training of the staff who give information must be documented6 | Information given by the business operator or a sufficiently informed person5 |
| Penalties | Administrative penalties under § 90 LMSVG, depending on the offence up to 50,000 euros, for repeat offences up to 100,000 euros7 | Administrative fines under the LFGB and LMIDV |
National implementation of allergen information for non-prepacked food
The decisive point in both countries
Even if you inform guests verbally, you need written documentation for every dish that is available immediately on request and can be shown during an inspection. Verbal information is a way of delivering the information, not a substitute for maintaining the data.
Why large kitchens are hit hardest
A restaurant with 40 dishes can, at a push, maintain its allergens by hand. A large kitchen cannot, for four reasons:
- Recipe volume. A catering business or a hospital kitchen works with hundreds to thousands of recipes, often across several levels: the sauce is a recipe that goes into the main course, which in turn is part of a menu line. If the sauce changes, every dish above it changes too.
- Changing suppliers and batches. When an item is swapped, say one vegetable stock for another brand, it may suddenly contain celery or gluten. The allergen information comes from the supplier data and must be checked again with every change.8
- Several sites, one menu plan. Centrally planned menus are cooked locally. Every local deviation, such as a different substitute item, makes the central labelling wrong.
- Vulnerable groups. Children, patients and care home residents cannot always ask for themselves. In Europe, according to parents, around 4 per cent of children have a food allergy diagnosed by a doctor; among young adults, an average of 12 per cent report reactions to food.9 More figures for Austria and Germany are in Food allergies and intolerances in numbers.
The result: the labelling is correct on the day it is created, and after that only until someone forgets to carry a change through. Carrying those changes through is exactly the job software should take over.
How FIC software closes the loop
At its core, FIC software is recipe management in which allergens are not entered but inherited. The chain looks like this:
- Take over item data from the supplier Allergens and ingredient lists come from the supplier's product data, via a data interface, a data sheet or AI-assisted capture. Every ingredient in the system carries its allergens.
- Build recipes from ingredients A recipe inherits the allergens of all its ingredients. A sub-recipe passes them further up. Nobody types letters into a spreadsheet any more.
- Fill the menu plan and service automatically Menu plan, notice, digital menu and QR code all draw their allergen information from the same source. One data record, every channel.
- Changes everywhere, instantly If an item is swapped or a supplier updates its data, every affected recipe and menu plan changes with it. The history remains traceable for the food safety authority.
| Manual (Excel, binders) | FIC software | |
|---|---|---|
| Change of supplier | Check every affected recipe one by one | Update the ingredient, recipes follow automatically |
| Sub-recipes | Allergens are copied across and go out of date | Inheritance across all levels |
| Several sites | Copies at different stages | One source, local deviations visible |
| Inspection by the authority | Searching through binders and emails | Documentation per dish with change history |
| Output | Maintain menu plan, notice and menu separately | All channels from the same data record |
Manual maintenance compared with recipe management with allergen inheritance
Checklist: what FIC software must be able to do
- Cover all 14 allergens under Annex II of the LMIV, including the subgroups for cereals and tree nuts
- Inherit allergens through multi-level recipes instead of entering them dish by dish
- Import supplier and item data and detect changes
- Keep traces ("may contain") separate from ingredients
- Output in every channel: menu plan, notice, digital menu, QR code at the table or the serving counter
- Allergens in the form each country expects, letter code or plain text, from the same data record
- Change history and export for the food safety authority
- Approval by a responsible person, because legal responsibility stays with the business
How HealthBlokk handles allergen labelling on the menu
HealthBlokk starts where most businesses are today: with the existing menu, on paper or as a PDF. From there, it takes you to a checked digital menu with allergen labelling in a few minutes.
- Photograph the menu, detect the allergens. Upload a photo or PDF of the menu; the AI reads dishes, prices and ingredients and suggests the allergens under Annex II of the LMIV for every dish, all 14, per ingredient.
- Review and approval by the business. Every entry is marked as estimated or as confirmed by the kitchen and can be corrected. Responsibility stays with the food business operator, which is why HealthBlokk publishes nothing unchecked.
- Digital menu with allergens via QR code. Guests open the menu on their phone, see the allergens per dish and filter by what they avoid. The selection stays on the guest's device and is not stored anywhere.
- Nutritional values per dish. Voluntary for loose food, a bonus for hospitals, care homes and health-conscious guests: energy, protein, carbohydrates, fat and salt, estimated from the recipe.
- Weekly menu without retyping. Read the lunch menu from a photo or have it suggested from your own dishes; it appears in the digital menu with its allergens for the current week only.
- When a recipe changes, the menu changes. Change an ingredient, and the allergens and nutritional values on the menu follow.
- Written documentation per dish. The allergen list is available at all times, even when guests are informed verbally on the premises.
Anyone running a large kitchen with supplier interfaces, multi-level recipes and many sites needs more than this, and HealthBlokk is not built for that today. For restaurants, cafés, canteens with a single menu and any business just getting started with allergen labelling, it is the shortest route from the paper menu to a digital menu with checked allergens.
Our recommendation for getting started
Start with your 20 most frequently cooked dishes and the components that go into everything: stocks, sauces, breadings, dressings. Once these sub-recipes are clean, most of your menu plans are covered.
Upload your menu, see the allergens per ingredient. No account, no credit card, in about a minute. Try your menu now
Frequently asked questions
Do large kitchens also have to declare nutritional values?
No. For non-prepacked food, Article 44 of the LMIV requires only the allergen information. Nutritional values are voluntary, but they can make sense for hospitals and care homes for dietary reasons.3
Is a notice saying "Please ask our staff" enough?
Only in combination with written documentation for every dish and trained staff. In Austria, the training must be documented; in Germany, the documentation must be easily accessible on request.65
Who is liable if the software makes a mistake?
The food business operator remains responsible. That is why any software should require approval by a responsible person and publish nothing without a check.
Does allergen labelling also apply to a small restaurant?
Yes. Article 44 of the LMIV applies to all food supplied non-prepacked, regardless of the size of the business. A restaurant with a single menu can show the allergens on the printed menu or in a digital menu via QR code; written documentation for every dish is needed in any case.36
Sources
-
GASTRO.at: Where 2.5 million people eat every day (Wo 2,5 Millionen Menschen täglich essen) ↩ ↩2
-
DGE: How many people in Germany eat in contract and institutional catering every day? ↩ ↩2
-
Regulation (EU) No 1169/2011 (LMIV), Art. 9, Art. 44 and Annex II, EUR-Lex ↩ ↩2 ↩3 ↩4 ↩5 ↩6
-
Allergeninformationsverordnung, BGBl. II No. 175/2014, RIS ↩
-
Bavarian LGL: FAQ on the Food Information Regulation (LMIV) and LMIDV ↩ ↩2 ↩3 ↩4 ↩5
-
WKO: Allergen labelling for loose food in the hospitality sector ↩ ↩2 ↩3 ↩4 ↩5
-
Allergieinformationsdienst (Helmholtz Munich): How common are food allergies? ↩