Amadeus ConsultingStart a project
Menu

Buyer guide

Make a restaurant menu usable on the web

A restaurant menu should be readable as web content and help the customer identify the item, price and relevant owner-approved details. Keep food, ingredient and allergen statements tied to current evidence. A visually attractive PDF alone may make the menu harder to inspect on a phone.

Present approved menu items as readable web content

Present menu names, prices and approved item details as readable web text with an update owner. Keep ingredient and dietary statements tied to current reviewed information. The synthetic layout demonstrates scanning and choice, while actual food claims need confirmation when recipes, suppliers or availability change at the restaurant.

Worked example — illustrative data.

Item specimen Web presentation Owner verification
Roasted vegetable bowl Item name, current price and concise description Recipe and price approved
Lunch soup State that selection varies only if true Daily update owner
Add-on bread Show separate amount and relationship to meal Actual option/price
Ingredient question Supported contact route Qualified staff response; no invented safety claim

Structure the menu with meaningful sections, readable item names and consistent price presentation. Use text so customers can enlarge and scan it without deciphering an image. Keep any PDF as an additional format where useful, with the web version’s update owner clearly assigned. Obtain explicit approval for ingredients, dietary labels and availability, then set review triggers when recipes or suppliers change. Test the route from homepage to a specific item on a phone.

Keep the web menu and its extra formats on one update task

When the approved menu changes, update the web item, price and any linked downloadable version together. Use a short publication checklist that names the food-information owner and the last review date. On a phone, find one dish, enlarge its text and identify its price without opening an image. Escalate uncertain ingredient wording to the responsible owner.

Decision: Publish only approved item details and keep uncertain food claims out of the page. The synthetic menu illustrates layout and does not provide real restaurant or dietary information.

Supplier substitutions can invalidate dietary wording: A supplier substitution can change a recipe while old dietary wording remains online. Do not infer allergen safety from the dish name or an earlier menu. The responsible food-information owner must confirm the statement.

Should a dietary icon be inferred from a dish name?

No. Use only current approved food information and a clear explanation of any symbol. Recipes and suppliers can change. The website layout cannot verify allergen safety, and an old menu is not evidence for a new statement.

Continue with Guides for stores, software teams and local businesses, Website design for local businesses and Website usability checklist for a buying journey.

For text enlargement and reflow, see the W3C WCAG quick reference.