About Crumb.

Crumb exists because allergen information is too important to live in a spreadsheet, a PDF, a staff group chat, and someone's memory at the same time.

Why we built Crumb

Restaurants do not need another generic QR menu. They need one reliable menu source that can serve guests, guide staff, support the kitchen, and produce the print materials service actually uses. EU 1169/2011 makes allergen control a legal duty — not an afterthought — so we designed Crumb around it from the first line of code, not bolted it on.

One source, every output

So we made Crumb — a menu and allergen service for restaurants. Dishes are built from ingredients. Allergens flow from those ingredients into guest menus, kitchen matrices, staff sheets, QR table cards, and print-ready PDFs. When something changes, the whole service flow stays aligned — front-of-house, back-of-house, and the guest reading the menu on their phone.

Independent restaurants, hotel groups, and multi-venue operators all use the same engine. Pricing scales with the group on our plans page.

Four menu styles

Presentation matters too. A fine dining tasting menu should not look like a hotel allergen grid, and a large hotel menu should not pretend to be a tiny bistro. That is why Crumb supports Editorial, Typographic, Hybrid, and Matrix styles — each tuned for a different service context, all sharing the same allergen-aware data underneath.

Made in Dublin, for restaurants anywhere

Crumb is built and supported from Dublin. Every detail matters — especially when a guest is deciding what they can safely order. Take a look around with a live demo or get in touch if you'd like a guided walkthrough.