Structured information
Standard allergen codes replace inconsistent free-typed labels across dishes.
Restaurant allergen menu software
Keep allergen information clear and under restaurant control.
Cravd connects restaurant-confirmed allergen information to each dish inside one branded digital menu—without relying on scattered notes, separate PDFs or AI making safety decisions.
Book a restaurant demo
The category
What is restaurant allergen menu software?
Restaurant allergen menu software helps a food business connect allergen information to individual dishes and present it consistently to guests. In Cravd, allergens are stored as structured codes, confirmed by the restaurant and shown separately from ordinary ingredients or preparation preferences.
Human confirmation
A restaurant staff member must confirm the safety information before a dish goes live.
Visible before ordering
Guests can reveal the restaurant-supplied information on the dish screen before choosing.
Built for careful restaurant teams.
Keep dish presentation beautiful while giving guests a clear route to the information supplied and maintained by the restaurant.
How it works
From restaurant records to the guest menu.
The software supports the workflow. The restaurant remains the source of truth.
Restaurant records the dish
Staff add the dish and select the relevant allergen codes.
A human checks the data
Safety information requires restaurant confirmation before publication.
The dish goes live
The confirmed data stays connected to the same dish across the menu.
The guest checks before choosing
Allergen information is available from the dish screen before ordering.
A deliberate boundary
Allergens are not ingredient exclusions.
Removing an optional ingredient is a preparation request. It is not evidence that a dish is safe for someone with an allergy. Cravd keeps these two kinds of information separate throughout the guest and kitchen workflow.
Safety information stays distinct
- Allergens use structured codes
- Ingredient exclusions remain guest preferences
- AI does not infer or certify allergens
- The restaurant approves information before publication
UK restaurant context
Support clearer information—not a compliance shortcut.
UK food businesses must provide accurate information when non-prepacked food contains any of the 14 regulated allergens. Current Food Standards Agency best practice is written information supported by a conversation with staff. Cravd helps present restaurant-supplied information clearly, but does not replace staff training, kitchen controls, official guidance or professional advice.
Keep it current
Restaurant teams can update dish information without replacing printed or PDF menus.
Keep it consistent
The same confirmed codes drive the guest-facing allergen legend across supported languages.
Keep the conversation open
Digital information supports—not replaces—a conversation with trained restaurant staff.
The regulated list
The 14 allergens, and how a guest sees them.
UK and EU law regulates fourteen allergens. Cravd stores each one as a fixed numeric code, so the same allergen means the same thing on every dish, in every language, and across every site you operate.
- Celery
- Cereals containing gluten
- Crustaceans
- Eggs
- Fish
- Lupin
- Milk
- Molluscs
- Mustard
- Tree nuts
- Peanuts
- Sesame
- Soybeans
- Sulphur dioxide and sulphites
A guest filters by the allergens that matter to them and the menu narrows to what is worth considering. Nobody is asked to decode fourteen superscript numbers against a footnote, and nothing depends on a member of staff remembering a recipe change from three weeks ago.
Across languages
Safety data that survives translation.
This is where most multilingual menus quietly fail. If allergen information is written as free text and then machine-translated, "nut-free" can come back as something a guest reads as "nuts" — and on a safety-critical field there is no acceptable error rate.
What Cravd does instead
- Allergens are numeric codes, never prose
- Each language renders from a checked legend
- Translation never touches the safety data
- A person confirms before the dish goes live
FAQ
Questions about digital allergen menus
Does Cravd decide which allergens a dish contains?
No. Allergen information comes from the restaurant and must be confirmed by a human before the dish can go live.
Can guests see allergens before ordering?
Yes. Restaurant-confirmed allergen information can be revealed on the dish screen before a guest adds the dish to an order.
Does Cravd guarantee legal compliance?
No. Cravd provides tools for presenting restaurant-supplied information, but the food business remains responsible for accurate allergen procedures and should follow current official guidance.
Are ingredient exclusions the same as allergens?
No. Optional ingredient exclusions are preparation preferences. Allergen information is separate structured safety data.
Can allergen information appear in several languages?
Yes. The allergen legend can be displayed in the guest’s selected language while the underlying restaurant-confirmed codes remain consistent.
Does Cravd process guest payments?
No. Cravd can send structured orders to the kitchen while the restaurant keeps its normal payment process.
Give guests clearer allergen information from one restaurant menu.
Bring your current allergen workflow to a short demo and see how Cravd keeps dish data structured, visible and under restaurant control.
Book a restaurant demo