I didn't come to allergen software from a developer's desk. I came to it from the restaurant floor. I spent a decade working front of house across London, from fine dining rooms where the timing of a single plate was scrutinized to scrappier operations where you did a bit of everything, waiting tables first and then managing. That taught me something no spec document can: what it feels like to be asked mid-rush whether the special is safe for a severe nut allergy, and to realize the only source of truth is a laminated folder three suppliers out of date. Allergenie was designed around that moment, by someone who has carried the plates rather than theorized about a kitchen they've never stood in. I first built it for my own use, and found it so much better than the existing alternatives that I fleshed it out into a full product.
That grounding matters, because the real developments in allergen menu management aren't flashy. They're about closing the gap between what a kitchen knows and what a guest can see at the table.
From compliance checkbox to live data
The biggest shift is conceptual: allergen information is now live data, not static print. The UK and EU require fourteen major allergens to be declared, and "Natasha's Law" pushed full ingredient labelling further into the spotlight. But the regulatory floor is no longer the ceiling. Operators increasingly need to handle allergens beyond the official fourteen, such as the apple, kiwi, or citrus intolerances that make no statutory list but matter enormously to the person at table six, alongside dietary frameworks like halal, kosher, Jain, and keto. The trend is toward systems that let a venue extend its allergen vocabulary to match its actual clientele.
Nuance is the new requirement
A modern tool has to express nuance, because food does. "Contains nuts" and "may contain traces of nuts" are very different statements with very different consequences, and a credible system captures that at the dish level. The same goes for a dish that's vegetarian as served versus one that's vegetarian only if you remove an ingredient. Encoding removable modifiers and degrees of allergen presence is where this software earns its keep. It gives floor staff a defensible answer instead of a nervous guess.
The most encouraging thing I've seen is how varied the users are. Chain restaurants standardizing data across sites, food trucks running a tight menu off a phone, single-site independents, and hotels juggling multiple outlets all find the same tool useful. For larger operations it doubles as a training aid, giving new front of house staff a fast, consistent way to learn the menu and its allergens rather than relying on whoever happens to be on shift. An allergen system that only fits one shape of business isn't much use in an industry this diverse, so adaptability isn't a nice-to-have. It's the whole point.
-
The hardest problem that remains isn't technology. It's keeping data accurate as recipes, seasons, and suppliers change, because a system is only as trustworthy as its last update.
The QR code finally found its purpose
Most pandemic-era QR menus were just PDFs in disguise. The genuinely useful application is allergen filtering: a guest scans, declares what they need to avoid, and the menu reshapes itself, surfacing safe dishes and flagging dangerous ones without a stressful interrogation of a busy server. The guest gets dignity and speed; the staffs get a consistent source of truth.
The hardest problem that remains isn't technology. It's keeping data accurate as recipes, seasons, and suppliers change, because a system is only as trustworthy as its last update. Get that right, and allergen management stops being a back-office obligation and becomes part of how a restaurant earns trust.
