Use case
Allergens handled, compliance covered.
Gluten, dairy, tree nuts, shellfish, soy, eggs — discreet tags next to every dish. Meets EU FIC 1169/2011 and the US FDA Big-9. Editable in seconds from the CMS.
Allergen disclosure is the law in most markets — the EU's FIC 1169/2011, the FDA's FALCPA in the US, and equivalents elsewhere. A paper menu with a footnote no longer cuts it. Crubby handles allergens as structured data: every dish carries its own tags, shown as discreet chips (🌾 gluten, 🥛 dairy, 🥜 tree nuts). A guest with an allergy sees at a glance what they can order. You update a tag the moment you change a prep — say, when you drop the dairy from a sauce.
The 14 EU allergens, handled
Cereals with gluten, crustaceans, eggs, fish, peanuts, soy, milk, tree nuts, celery, mustard, sesame, sulphites, lupin, molluscs — all 14 from FIC 1169/2011, and they map cleanly to the US FDA Big-9.
Visible but discreet tags
A small icon next to the dish name, with details on tap. No unreadable footnotes.
Guest filtering
A guest can filter the menu to 'gluten-free only' or 'no dairy.' UX-first, and compliance-first.
Kitchen confirmation
When a guest orders via QR, the kitchen ticket carries the allergen flags — fewer mistakes in prep.
Frequently asked questions
Is Crubby compliant with EU FIC 1169/2011?+
Yes. It handles all 14 regulated allergens with clear, guest-facing tags — compliance out of the box — and it maps cleanly to the US FDA Big-9.
Can I change an allergen when I change a recipe?+
Yes. Toggle an allergen per dish in the CMS in about five seconds — it updates on every screen instantly.
What if a guest has an uncommon allergy?+
Crubby supports a 'flagged intolerances' note a guest can add when they order, and the kitchen ticket receives it.