A menu is both editorial content and an operational promise. It influences ordering, allergies, budgeting and expectations, so it cannot be filled with plausible copy and corrected later. This guide connects the public page to kitchen records, pricing decisions and service training.
Key point: One approved source of truth should feed web, print, booking and staff information. When the recipe or price changes, every customer-facing version needs coordinated review.
Compare this workflow with the Maui menu framework. For safety-critical dietary choices, consult the Food Standards Agency’s allergen guidance for food businesses rather than relying on a decorative icon.
1. Create an item record
Give each item a stable internal identifier, public name, category and status. Record serving period, main ingredients, preparation, portion or unit, price, tax treatment and the person responsible for approval. This structure makes a change traceable and prevents similar names from drifting across channels.
The public description should help a guest choose, not hide the essentials under mood language. It may highlight technique, flavour or texture when those details are accurate. Avoid health, origin, sustainability or “fresh” claims unless the operator can define and support them.
2. Connect recipes and allergens
Maintain a current recipe or specification that identifies ingredients and the allergens they contain. Include garnishes, sauces, shared oils and common substitutions. When a supplier changes a product, the record and staff guidance need review before service continues under the same label.
The website should explain how guests request current allergen information and that cross-contact may matter. A dietary icon needs written criteria. Do not rely on an automated label generated from an incomplete ingredient list.
3. Price transparently
Show the total price and currency, and explain taxes, service charges, deposits, minimum spend or supplements before the order. Weight, unit and market-price items require a clear method and timely confirmation. Packages need a list of included items and conditions.
Promotions should have dates, eligibility and a defensible reference price. A discount carried over from an old menu can mislead even if the original page was accurate when captured.
4. Manage availability and substitutions
Decide who can mark an item unavailable and how quickly every channel updates. Seasonal categories should communicate variation as part of the offer, not leave guests to discover it after ordering. Where a substitute changes price, ingredients or allergens, obtain agreement before service.
Signature items that are no longer served can remain in editorial stories if clearly labelled, but they should not sit in the active ordering path. Keep current choices separate from past favourites.
5. Use accurate photography
Photograph the actual served item in a representative portion and presentation. Record the date and rights. Styling may improve clarity but should not add ingredients, scale or surroundings that a guest will not receive. Captions can identify seasonal garnish or serving suggestions.
Optimise image size and crop for different screens. Alternative text should describe the useful visual content, not repeat promotional phrases. If no verified image exists, clear typography is preferable to a stock photograph presented as the dish.
The written enquiry form provides a practical route for current menu, dietary and group questions.
6. Approve and train
Kitchen confirms recipe and feasibility; service confirms explanation and timing; management confirms price, availability and legal information; the content owner checks language and accessibility. Record the version and publication date. Staff should know where to find the same source.
Test common questions and a substitution scenario before launch. If teams answer differently, the menu is not ready even when the page looks complete.
7. Review as a live system
Set regular review points and a rapid path for supplier, safety or price changes. Monitor questions, returns and items frequently unavailable; they reveal where wording or operations need adjustment. Retire obsolete versions from caches, downloads and QR destinations.
A trustworthy menu is maintained, not merely written. Regular checks keep the website, printed menu and staff information aligned.
8. Design the page around real decisions
Structure the public menu for the way guests actually compare choices. Keep category names visible, place price close to the item, show serving context where it changes value and make dietary information easy to request. On mobile, a guest should not need to drag a wide table sideways or decode a decorative card before understanding what can be ordered.
Use internal links to connect the menu with group planning, accessibility, booking conditions and the journal, but keep the ordering path focused. External links belong where they improve a safety-critical explanation, such as official allergen guidance; they should not interrupt every item description or replace the venue’s own current records.
Before publishing, test the page with a first-time guest, a returning guest and a staff member. Ask each person to find a price, compare two options, identify the allergen route and explain what happens when an item is unavailable. Their friction points reveal where the content system still needs work.