Pricing for safer restaurant menus.

Most restaurants go live in under 20 minutes. Pick your style, add your dishes, publish. Ingredients auto-build their allergen profile as you type — so by the time your menu is complete, your allergen compliance is done.

No. Typographic, Hybrid, and Matrix styles are designed to work beautifully without a single photo. Typographic is the style used by Noma, Lyle's, and Chez Panisse — restraint as luxury. Choose the style that matches your restaurant, not the other way around.

Crumb is built around EU Regulation 1169/2011. All 14 regulated allergens, contains vs may-contain distinction, ingredient-level tracking, optional acknowledgment disclaimer with session logging. Compliance is the foundation, not an afterthought.

Yes. Custom colours from a curated palette, embedded venue logo, custom header text and tagline. Download PNG, SVG, or print-ready PDF at A6 size. Designed to sit beautifully on a table card, not shout.

Crumb can generate guest-ready menu PDFs, branded QR table cards, kitchen allergen matrices, and staff sheets from the same menu source. That means the printed pack, service notes, and QR menu all reflect the same dish and ingredient records.

Yes. Crumb uses one menu source for the guest QR menu, table cards, PDF menus, kitchen matrices, and staff sheets. Change the dish once, then regenerate the materials that service needs.

Venues choose the languages they want to publish, then manage dish, section, menu, and ingredient translations alongside the original content. Guests can switch language on the QR menu, while printed exports and staff materials continue to use the approved menu source.

Crumb separates contains, may-contain, and can-be-made-without notes so guests and staff do not treat every warning the same. Severe allergy language can be surfaced through the disclaimer and strict filtering flow.

Yes. Guests can filter allergens and dietary needs from the QR menu, see which dishes remain, and spot possible modifications before the conversation reaches the table.

Four roles: Owner, Manager, Editor, Viewer. Editors and Viewers can be scoped to specific venues — a Dublin editor can't accidentally change your Cork menu. Every role has permissions enforced at the database level, not just hidden in the UI. (Duo limits you to Owner, Manager, and Editor — Viewer role is a Studio feature.)

Studio+ teams get a compliance evidence pack with allergen accuracy, nutrition data, and kitchen review documents, plus activity records for document downloads and review acknowledgements. It helps show when the team reviewed the menu before publishing, without replacing supplier checks or kitchen judgement.

Many of our customers run daily-changing menus. Crumb handles it well — reuse ingredients from your library, duplicate yesterday's menu as a starting template, publish in two clicks. For tasting menus and seasonal restaurants, Typographic style was specifically designed around this.

Your published menus stay live for 30 days so your guests don't hit broken links. Export everything to PDF at any time. Your data is yours — we'll hand it over in JSON on request, free of charge.

A single allergen incident can cost thousands in fines, insurance, and reputation. A custom QR menu and allergen matrix built by a designer and developer would cost €2,000–€5,000. Crumb replaces all of that for less than the price of one service shift. Most teams save two hours of menu admin per week — that alone covers the subscription.