Fourteen allergens Always in writing Kept in step with the menu

Custom app for allergen information on your menu

For non-prepacked food, you may give allergen information verbally, provided there is a notice somewhere telling guests they can ask for it. But the information itself must always be available in writing or electronically, for your staff and for the NVWA (the Dutch Food and Consumer Product Safety Authority). So that verbal answer has to be backed by something.

Appfront
Live

What the rules actually require

There are fourteen allergens: cereals containing gluten, egg, fish, peanut, nuts, soya, milk including lactose, crustaceans, molluscs, celery, mustard, sesame seeds, sulphites and lupin. This list has applied since the end of 2014 under the Dutch Commodities Act decree on allergen information for non-prepacked food.

For prepacked products, the information is on the label. Non-prepacked food works differently: in hospitality, ice cream parlours, care institutions, catering, bakeries, butchers, greengrocers and fish counters. There, it can be provided on shelf labels and menus, or verbally.

If you provide it verbally, there must be a notice somewhere saying guests can ask for this information. That is the visible side. The invisible side weighs more: the information must always be available in writing or electronically for staff and for the NVWA.

That is exactly where things go wrong in practice. Not with the guest at the table, but with the question of what the answer was based on. A chef who knows it by heart is not written availability, and neither is a folder in the kitchen that still contains last season's menu.

How we build this

The core is the dish and its ingredients. Allergens are not a property you attach to a dish; they follow from what is in it, and that changes when a supplier changes.

1
Recording ingredients

For each dish, what goes into it, with the allergens attached to each ingredient.

2
Derived rather than filled in

A dish's allergens follow from its ingredients, so any change carries through automatically.

3
Making it available to staff

On a screen in the kitchen and at the bar, showing today's menu and not last month's.

4
Ready for an inspection

An overview an inspector can read without anyone having to operate the system.

What the app actually does

The link between ingredient and dish carries the whole thing. What else you need depends on how often your menu changes and whether you have multiple locations.

Allergens from the ingredients

When an ingredient changes, the dishes that contain it change too. No second list falling behind.

Quick look-up at the table

Staff search by dish or by allergen and have the answer within a few taps.

Daily specials and rotating dishes

Today's special should carry the same information as a permanent dish, even if it is only on the menu for one day.

Traces and cross-contamination

What happens in the same fryer or on the same board is information your staff need to be able to give.

Guests can look for themselves

A page or code with the menu, without replacing the conversation in person.

Always available in writing

An export or screen that staff and the NVWA can consult, even if the network falters.

Who we build for

Who uses this differs from business to business. Four situations.

Restaurants with a changing menu

If you change something every week, you are most likely to have an allergen list that falls behind.

Caterers and care institutions

They serve people who often cannot ask for themselves, and then what has been recorded is what counts.

Bakeries and butchers

At a counter with unpackaged products, the same duty applies as in a restaurant.

Chains and multiple branches

One recipe, several kitchens, and the question of whether everyone gives the same information.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

Technology and integrations

Recipes change, suppliers change and the menu moves with the seasons. Ingredients, dishes and allergens should be configurable and not hard-coded into the app.

For chains and caterers with one central recipe for all branches, there is our software for allergen information on the menu.

React Native or native iOS and Android Ingredients with allergens as the source Deriving allergens per dish Available offline in the kitchen Search by dish and by allergen Multiple locations, each with its own menu Roles for kitchen, front of house and management Integration with your till or recipe system Export for an inspection History per menu version

Why Appfront

Verbal is allowed, but it needs something to rest on

The information must always be available in writing or electronically for staff and the NVWA. We build that foundation.

Allergens follow from ingredients

A separate list falls behind as soon as a supplier changes. Deriving allergens prevents that.

The daily special is the weak point

What is only on the menu for one day rarely gets the same care. That is exactly where things get missed.

We don't define your recipes

Your kitchen knows what is in a dish. We make sure that knowledge is recorded and easy to look up.

Security and privacy

Your recipes are commercially sensitive: exactly what goes into a dish and who you buy from should not be available to everyone. We set access per role, show front-of-house staff the allergens without the full recipe, and log who views what. Data stored locally on the device is encrypted and can be wiped remotely if a device goes missing.

For this topic, what matters is reliability at the moment in question. After an incident, the question is which information was available that day, not what it says now. We keep menu versions with a timestamp and the person responsible, so you can show what applied on a given day, and we make a correction a visible correction alongside the original entry. How we handle security ourselves is described in our information security policy.

Frequently asked questions about allergen information

Fourteen: cereals containing gluten, egg, fish, peanuts, nuts, soya, milk including lactose, crustaceans, molluscs, celery, mustard, sesame seeds, sulphites and lupin.

Yes, that is allowed for non-prepacked food. However, there must be a notice somewhere stating that guests can ask for this information. And the information itself must always be available in writing or electronically for your staff and the NVWA.

Everyone who provides non-prepacked food: hospitality, ice cream parlours, care institutions, catering, bakers, butchers, greengrocers and fish counters. The rules have applied since the end of 2014.

A list that lives alongside the recipe. As soon as a supplier or an ingredient changes, the allergen list is no longer correct, and nobody notices. By deriving the allergens from the ingredients, any change carries through automatically.

That is information your staff must be able to give, for example about what goes in the same fryer or is prepared on the same chopping board. Record it against the dish rather than leaving it to whichever cook is on duty.

No. This is specifically about allergen information and recording it. We cover menus, ordering and the kitchen on our page about the restaurant app. See also our approach to building an app.

Where is the allergen information for today's dish?

Ask in your own kitchen about the allergens in a daily special. If the answer comes from someone's head, you do not meet the requirement that it is available in writing or electronically. We build this as a standalone app and as part of a broader app development project.

Edit content