Restaurant menu management means keeping one accurate menu across every place a customer can order: the till, your website, the phone and each delivery app. The menu is more than names and prices. It holds modifiers, meal deals, allergen information, photos, descriptions, opening windows, sold-out items and the VAT treatment of each line. When any of those is wrong on one channel, you pay for it in refunds, remakes, complaints or a food safety incident.
If you sell on a till, a website and two delivery apps, you have four copies of your menu. Every copy has to change when a supplier puts up the price of chicken, when a dish sells out or when a recipe changes. The job is to make each change once, check it once and know it reached every channel.
The rules with legal weight come first. In Ireland and the UK, allergen information must be accurate on every channel, including delivery apps, and must reach the customer before the order and again at delivery. Prices shown must be the prices charged. After that, pricing per channel, modifiers and menu engineering decide how much cash each order leaves you.
Restaurant menu management basics
What a menu record holds
| Field | What it is | What goes wrong when it is missing |
|---|---|---|
| Item name | The customer-facing name, plus a short kitchen name | Kitchen tickets too long to read; names differ between channels |
| Category | Starters, mains, sides, deals, drinks | Customers scroll past what they came for |
| Description | Main ingredients, portion, spice level | Wrong expectations, refunds, poor reviews |
| Price per channel | Eat-in, collection, delivery, each app | Undercharging on one channel for weeks |
| Modifiers and add-ons | Sizes, bases, extras, removals, swaps | Free-text notes, missed charges, missed allergens |
| Meal deals | Bundles of items at one price | Wrong VAT split, wrong kitchen routing |
| Allergens | Which of the 14 allergens each item and modifier contains | Legal breach and a real risk to customers |
| Photo | One consistent photo per item | Low conversion online, mismatched expectations |
| Availability | Days, times and channels the item is sold | Breakfast items ordered at 9pm |
| Sold-out status | Temporarily unavailable today | Orders taken for food you cannot make |
| VAT treatment | Rate for eat-in and takeaway | Wrong VAT on returns |
| Kitchen station | Where the item is cooked | Tickets at the wrong station |
| Calories | Energy in kcal, where the law requires it | Non-compliance for large businesses in England |
Menu drift
Menu drift is what happens when copies of the menu stop matching. It is rarely one big error. It is small gaps that last for weeks.
Example: a chicken shop raises its 6-wing box from €7.00 to €7.50 on the till on Monday. The website is updated on Wednesday. One delivery app is forgotten for three weeks. If that app sells 20 wing boxes a week, the shop loses 3 × 20 × €0.50 = €30 before commission. The bigger cost is the customer who pays €7.00 on the app, sees €7.50 on the website and asks why.
Drift also hits allergens. A supplier swaps a sauce base, the recipe now contains mustard, and the website is updated but one app is not. That is a legal and safety problem, not a pricing one.
One menu across POS, website and delivery apps
There are three ways to keep menus in step. None is free of work.
| Approach | How it works | Suits | Risk |
|---|---|---|---|
| Manual in each system | Type every change into the POS, the website and each app’s partner portal | One site, a short menu, few changes | Drift, typos, forgotten channels |
| Central menu with an integration service | One master menu pushed to the POS, website and apps through a paid integration | Many channels and frequent changes | Integration fees, mapping errors, one mistake published everywhere |
| One system for POS and website, apps updated in their own portals | The POS and ordering website share a menu; each delivery app is updated in its partner tools | Owners who take most orders on the till and their own website | App menus still need a fixed routine |
Ask any provider exactly which channels a single change reaches, and what you still update by hand. The online ordering system for restaurants and restaurant POS system pages cover how those two systems should connect.
Master menu rules
- One owner. One named person approves every menu change. Everyone else asks them.
- One master. Keep a master menu, in your POS or a spreadsheet, that every channel copies from.
- Same names everywhere. The kitchen should see the same item name whatever the channel.
- Documented differences. If an item is collection-only or priced differently on an app, write it in the master.
- Change log. Record the date, the change, the channels updated and who checked each one.
Change routine
- Make the change in the master menu.
- Update the POS.
- Update the ordering website.
- Update each delivery app in its partner portal.
- Update any printed menu, leaflet or price notice at the entrance.
- Place a test order on each online channel and check the price, modifiers and allergen information.
- Tell the kitchen and front of house what changed.
- Log the change.
Menu structure, descriptions and photos
Categories
Online, customers scan the first screen and the category bar. Put the categories most people order from near the top: deals, best sellers or mains, then sides, drinks and desserts. Keep categories short and specific. “Burgers”, “Chicken”, “Sides” works better than “Mains” with 30 items in it.
Use the same category order on the website and each app where the app allows it. Customers who order on one channel and then another should find the same menu.
Item names
Each item needs two names: the customer name and a short kitchen name. “Smoky BBQ Double Smash with Crispy Onions” becomes “BBQ DBL SMASH” on the ticket. Write the kitchen name into the POS so tickets stay readable on printers and kitchen screens.
Descriptions
A good description answers what the customer needs before ordering:
- Main ingredients and cooking method.
- Portion size, such as 6 wings, 12-inch or 350ml.
- Spice level, with the same scale on every dish.
- What comes with it, such as chips, dip or salad.
Do not rely on descriptions for allergen information. The Food Safety Authority of Ireland says the specific cereal or nut must be named, such as “wheat” rather than “gluten” (FSAI, the 14 allergens, checked September 2026). A description that mentions “pesto” does not tell a customer the dish contains pine nuts, cheese or both. Use your structured allergen fields.
Photos
- Photograph your own food, as you serve it, in the same light and angle for every item.
- Use one photo per item across the website and every app, so customers recognise the dish.
- Retake the photo when the dish changes. A photo showing a side that no longer comes with the dish creates complaints.
- Start with best sellers and deals. Photos matter most where customers decide fastest.
Marketplaces often offer photography during sign-up. Uber Eats, for example, lists menu creation and photography in its activation fee (Uber Eats Ireland pricing, checked September 2026). Ask whether you may reuse those photos on your own website before you rely on them. The restaurant website builder page covers menu pages and photos on your own site.
Channel-specific menus
Not every item belongs on every channel.
- Delivery menu. Remove dishes that travel badly, such as some fried items that go soft in 25 minutes.
- Lunch menu. Time-limited items with their own availability window.
- Eat-in only. Dishes that need to be served immediately or plated at the table.
- Collection deals. Offers that only make sense without a delivery cost.
Set these with availability rules on the item, not by creating duplicate items. Duplicates break reports and kitchen routing.
Menu modifiers and add-ons
Modifiers are the choices attached to an item. They carry money, kitchen instructions and allergen information, so build them with care.
| Modifier type | Example | Price rule | Allergen check |
|---|---|---|---|
| Required choice | Pizza size, curry spice level, burger bun | Price differs by option | A brioche bun may add egg and milk |
| Optional add-on | Extra cheese, add bacon | Priced per add-on | Cheese adds milk |
| Removal | No onions, no sauce | Free | Removal does not guarantee no trace of an allergen |
| Substitution | Swap chips for salad | Price difference, if any | Dressing may add mustard |
| Meal upgrade | Make it a meal with fries and a drink | Fixed upgrade price | Fries fried in shared oil |
| Half and half | Two pizza toppings on one base | Higher topping price, or average | Both halves’ allergens apply |
| Instruction | Well done, cut in 8 | Free | None |
Modifier rules
- Minimum and maximum. A required choice needs a minimum of 1. A “choose up to 3 toppings” group needs a maximum.
- Default option. Pre-select the most common choice to save a tap, but never pre-select a paid extra.
- Allergen tags on modifiers. Each modifier needs its own allergen information, because it changes the dish.
- Kitchen order. List modifiers on tickets in the order the cook needs them.
- Station routing. “Add a side of wings” must reach the fryer, not only the pizza station. The kitchen display system page covers routing.
- No free-text allergy requests. Offer structured options and a clear message on what you cannot cater for.
Priced add-ons and meal upgrades raise order value. Tactics, testing and the maths of upselling are covered in how to increase average order value.
Modifier mistakes
- Nested choices online that nobody finishes. Five screens of options to order a burger loses the order.
- Free extras by accident. An add-on created at €0.00 during set-up and never priced.
- Modifiers copied between items without checking. A “no nuts” option on a dish that never had nuts confuses staff.
- Different modifier names per channel. “Xtra cheese” on the app and “Extra mozzarella” on the till create two lines in reports.
Menu pricing
Food cost pricing
Start from what the plate costs you. Price ex VAT = plate cost ÷ target food cost percentage. Then add VAT and round.
Example, labelled as an example, with a target food cost of 30% chosen for illustration:
- Ireland. Plate cost €3.40. €3.40 ÷ 0.30 = €11.33 ex VAT. Add 9% VAT: €11.33 × 1.09 = €12.35. Menu price €12.50.
- UK. Plate cost £2.90. £2.90 ÷ 0.30 = £9.67 ex VAT. Add 20% VAT: £9.67 × 1.20 = £11.60. Menu price £11.50 or £11.95.
Plate cost includes every component: protein, carbs, sauce, garnish, oil, dip and, for takeaway, packaging. Update it when supplier invoices change. A 10% rise in chicken price on a dish where chicken is half the plate cost moves the plate cost by 5%.
VAT on menu items in Ireland
Irish VAT on food depends on what is sold and how. From 1 July 2026, the second reduced rate applies to restaurant and catering services and to hot takeaway food (Revenue, VAT treatment of restaurant and catering services, last reviewed June 2026). Revenue lists the second reduced rate as 9% and the standard rate as 23% (Revenue, current VAT rates).
The same Revenue manual sets out:
- Alcohol, bottled waters, soft drinks, sports drinks and vegetable juices are standard-rated, including in a restaurant.
- Hot takeaway food, including food kept hot or supplied while still warm, is at the second reduced rate.
- Cold takeaway food is zero-rated.
- Cold food supplied with hot food for one price, such as coleslaw with hot chicken, is at the second reduced rate.
- In a meal deal with hot food and a soft drink, the discount is apportioned between the items at their own VAT rates.
- Delivery services are standard-rated and are not generally treated as ancillary to the food.
- Between 1 September 2023 and 30 June 2026, the reduced rate applied instead of the second reduced rate.
VAT on menu items in the UK
HMRC’s VAT Notice 709/1 (updated 8 June 2026) says hot takeaway food is standard-rated at 20% and cold takeaway food is zero-rated, unless the item is one that is always standard-rated, such as crisps or sweets. Food eaten on your premises, including seating areas you provide outside, is standard-rated whether hot or cold. Food counts as hot takeaway if it is hot when handed over and meets one of the notice’s tests, such as being heated to order, kept hot or supplied in packaging that retains heat. When you sell standard-rated and zero-rated items together for one price, you apportion the value between them on cost or market value.
What VAT means for your menu set-up
- Give every item a VAT rule for eat-in and one for takeaway.
- Split meal deals into their parts so the VAT on the drink is right.
- Check delivery charges separately from food.
- Ask your accountant to review the VAT settings in your POS once a year and after any rate change.
Price display rules
Ireland. The Retail Price (Food in Catering Establishments) Display Order, 1984 applies to restaurants and cafés and is enforced by the Competition and Consumer Protection Commission. A price notice goes immediately outside or inside the entrance. Menus must show prices, and prices must be the final price including taxes and charges, with any minimum charge, cover charge, service charge status and time-based price differences shown. Charging a different price from the one displayed can be a misleading price indication under the Consumer Protection Act 2007 (CCPC, restaurants and cafés).
UK. The Price Marking (Food and Drink Services) Order 2003 requires prices at or near the entrance to an eating area so customers see them before entering, and at the point of choice for takeaway. If you sell more than 30 food items, you show at least 30 prices, and the Order sets minimums for soft drinks and wine. Service charges and minimum charges must be shown as prominently as food prices, and prices must include VAT.
When you change prices, the notice at the door and any printed menu change too.
Menu prices on delivery apps
Commission changes the maths of every item. Uber Eats publishes a 30% fee when its couriers deliver, 13% when you deliver yourself and 13% for pickup, in both Ireland and the UK (Uber Eats Ireland pricing, Uber Eats UK pricing, checked September 2026). Rates for Just Eat and Deliveroo vary by agreement; the Deliveroo, Just Eat and Uber Eats commission guide sets out each app’s fees.
The pricing formula
To keep the same cash per item on an app as on a direct order:
App price = direct price × (1 − direct cost %) ÷ (1 − app cost %)
Example: a €14.00 dish on your own website with no commission, moved to an app charging 30%: €14.00 × 1.00 ÷ 0.70 = €20.00. At the same €14.00 on the app, you keep €9.80 before VAT and food. At €16.10, a 15% uplift, you keep €11.27 (€16.10 × 0.70).
Pricing the full difference makes app prices look high next to your own website, and customers compare. Decide item by item. Items with high food cost need more uplift. Items with low food cost, such as drinks and sides, can carry more of the uplift quietly.
Rules to check before you set app prices
- Your contract. Read the pricing clauses in each partner agreement, and ask your account manager in writing if anything is unclear.
- Displayed price equals charged price. Show the price the customer pays on that channel, and charge exactly that.
- Consistency beyond price. Keep names, descriptions, allergens and photos identical across apps, even if prices differ.
- Fee basis. Check whether the app calculates its fee on the price including VAT, and whether VAT is added to the fee. Your monthly statement shows it.
Marketplaces are for discovery. Keep your best sellers visible there, and give customers a reason to order direct next time. The playbook for that is in how to get more direct orders.
Worked example: one dish priced for three channels
Example only. A pizzeria sells a 12-inch margherita. Plate cost and box cost are illustrative assumptions. The app fee assumes the percentage is charged on the menu price including VAT; check your own statement. Card fees apply on every channel and are left out.
Ireland, in euro
Assumptions: menu price €13.50 including 9% VAT; plate cost €3.20; box €0.45.
| Channel | Price | Net of VAT | App fee | Food and box | Cash left |
|---|---|---|---|---|---|
| Direct collection on your website | €13.50 | €12.39 | €0.00 | €3.65 | €8.74 |
| Uber Eats pickup, 13% | €13.50 | €12.39 | €1.76 | €3.65 | €6.98 |
| Uber Eats with Uber delivery, 30% | €13.50 | €12.39 | €4.05 | €3.65 | €4.69 |
| Uber Eats with Uber delivery, priced at €16.50 | €16.50 | €15.14 | €4.95 | €3.65 | €6.54 |
Workings: €13.50 ÷ 1.09 = €12.39. 13% of €13.50 = €1.76. 30% of €13.50 = €4.05. €16.50 ÷ 1.09 = €15.14, and 30% of €16.50 = €4.95.
To leave the same €8.74 on the delivery app as on a direct collection, the app price X must satisfy X ÷ 1.09 − 0.30X − €3.65 = €8.74. That gives X × 0.6174 = €12.39, so X = €20.07.
UK, in sterling
Assumptions: menu price £11.50 including 20% VAT; plate cost £2.80; box £0.40.
| Channel | Price | Net of VAT | App fee | Food and box | Cash left |
|---|---|---|---|---|---|
| Direct collection on your website | £11.50 | £9.58 | £0.00 | £3.20 | £6.38 |
| Uber Eats pickup, 13% | £11.50 | £9.58 | £1.50 | £3.20 | £4.88 |
| Uber Eats with Uber delivery, 30% | £11.50 | £9.58 | £3.45 | £3.20 | £2.93 |
| Uber Eats with Uber delivery, priced at £14.00 | £14.00 | £11.67 | £4.20 | £3.20 | £4.27 |
To leave the same £6.38 on the delivery app, X ÷ 1.20 − 0.30X − £3.20 = £6.38, so X × 0.5333 = £9.58 and X = £17.96.
What the example shows
- The higher VAT rate on hot food in the UK leaves less room than in Ireland at similar prices.
- A 30% fee takes more from the pizza than the dough, sauce, cheese and box together, in both countries.
- Your own delivery has its own cost per drop, which the restaurant delivery management software page works through.
Restaurant menu engineering
Menu engineering sorts dishes by popularity and by cash margin, then gives each group an action. It uses data you already have in your POS.
Method
- Export 8 to 12 weeks of item sales from your POS, by channel if you can.
- For each item, record units sold, price ex VAT and plate cost.
- Cash margin = price ex VAT − plate cost.
- Popularity cut-off: a common rule is 70% of an equal share. With 8 items, an equal share is 12.5%, so the cut-off is 8.75% of units.
- Margin cut-off: the average cash margin across all units sold.
- Put each item in one of four groups and act.
In practice, run it within a category, such as mains or sides. The example below mixes a few categories to keep it short.
Example: a burger shop over 8 weeks
Example figures only. Prices shown ex VAT.
| Item | Units | Price | Plate cost | Margin | Total margin |
|---|---|---|---|---|---|
| Classic burger | 620 | €10.00 | €3.10 | €6.90 | €4,278 |
| Double smash | 410 | €12.50 | €4.60 | €7.90 | €3,239 |
| Chicken burger | 380 | €10.50 | €3.00 | €7.50 | €2,850 |
| Loaded fries | 520 | €6.00 | €1.40 | €4.60 | €2,392 |
| Wings, 6 | 300 | €7.50 | €2.90 | €4.60 | €1,380 |
| Onion rings | 140 | €4.50 | €1.00 | €3.50 | €490 |
| Veggie burger | 90 | €10.50 | €2.60 | €7.90 | €711 |
| Fish burger | 60 | €11.00 | €4.40 | €6.60 | €396 |
Total units: 2,520. Popularity cut-off: 8.75% × 2,520 = 221 units. Total margin: €15,736. Average margin: €15,736 ÷ 2,520 = €6.24.
| Group | Rule | Items in the example | Action |
|---|---|---|---|
| Stars | Popular, margin above €6.24 | Classic, double smash, chicken burger | Keep prominent; protect the recipe; top of the category |
| Workhorses | Popular, margin below €6.24 | Loaded fries, wings | Review portion cost or price; test a €0.50 rise |
| Puzzles | Not popular, margin above €6.24 | Veggie burger, fish burger | Better name, photo or position; remove if nothing changes |
| Dogs | Not popular, margin below €6.24 | Onion rings | Remove, or only offer inside a deal |
If the wings rise by €0.50 and volume holds, margin rises from €4.60 to €5.10, adding €150 over the 8 weeks (300 × €0.50). To keep the same €1,380 total margin at €5.10, you need €1,380 ÷ €5.10 = 271 boxes. If sales fall below 271, a drop of 30 boxes or more, the rise loses money.
Run the analysis again 8 weeks after changes. Your restaurant analytics software should give you item sales by channel without manual counting.
Allergen rules in Ireland and the UK
The 14 allergens
Both countries use the same list: cereals containing gluten (wheat, rye, barley, oats), crustaceans, eggs, fish, peanuts, soybeans, milk, tree nuts (almonds, hazelnuts, walnuts, cashews, pecans, Brazil nuts, pistachios, macadamia), celery, mustard, sesame, sulphur dioxide and sulphites, lupin and molluscs (FSAI, the 14 allergens; GOV.UK, starting a food business).
Ireland
The FSAI says allergen information for non-prepacked food, including restaurant and takeaway food, must be:
- In writing, in English or in Irish and English.
- Easy to find and available before the sale.
- Linked to the specific food, for example “spaghetti bolognaise: contains milk, celery, wheat”.
- Beside the menu item or in a central place with clear signposting.
Verbal information from staff is only a supplement to the written information (FSAI, allergen information for non-prepacked food). The legal basis is EU Regulation 1169/2011 and S.I. No. 489 of 2014, updated by S.I. No. 656 of 2024.
For food sold by phone or online, allergen information for non-prepacked food must be available before the purchase is concluded and again at delivery, and it must be given in writing at least once (FSAI, labelling for distance selling). The FSAI publishes a menu items allergen checklist to record allergens dish by dish.
UK
Allergen information for food sold online or by phone is needed at two stages: before the purchase is completed, in writing or orally, and when the food is delivered, in writing such as allergen stickers or an enclosed menu, or orally by the driver (GOV.UK, starting a food business, updated 19 August 2026).
The Food Standards Agency’s best-practice guidance (updated 24 February 2025) adds:
- On your own website, allergen information should be no more than one click away if it is not on the main menu.
- On third-party platforms, customers should be told clearly where to find allergen information before they order.
- Written allergen information should go with the order at delivery, such as stickers on containers or a menu with clear cross-references.
- Phone orders: ask about allergies before taking the order.
- Allergen requests should reach kitchen staff in writing.
Natasha’s Law and prepacked for direct sale food
Since 1 October 2021, prepacked for direct sale (PPDS) food across the UK needs a label with the name of the food and a full ingredients list with allergens emphasised. PPDS food is packaged at the same place it is sold, before the customer orders it. The FSA’s examples for fast food and takeaways include boxed burgers, chips or nuggets packed in cartons and kept under heat lamps, and sandwiches or salad boxes packed ready for sale. Food packed only after the customer asks for it is not PPDS. Food sold by distance selling is not covered by the PPDS rules, but allergen information is still required before purchase and at delivery (GOV.UK, PPDS allergen labelling for fast food and takeaway restaurants).
If you pre-box food before a rush, those boxes may be PPDS. Pack after the order, or label them.
Calorie labelling in England
Businesses with 250 or more employees selling food out of home in England must show calories in kcal at the point of choice, including online menus and third-party delivery platforms, with the statement “adults need around 2000 kcal a day”. The rules came into force on 6 April 2022. Exemptions include items on the menu for fewer than 30 consecutive days and alcoholic drinks above 1.2% ABV (GOV.UK, calorie labelling in the out of home sector). A single restaurant or takeaway with a small team is far below 250 employees. If you are part of a larger business or franchise, check how the rules count staff.
Ireland and UK compared
| Rule | Ireland | UK |
|---|---|---|
| Regulator guidance | FSAI | Food Standards Agency, published on GOV.UK |
| Allergen list | 14 allergens | 14 allergens |
| Non-prepacked food in the restaurant | Written information required; verbal only as a supplement | Information required; FSA best practice sets out written and verbal methods |
| Online and phone orders | Before purchase and at delivery, in writing at least once | Before purchase and at delivery, in writing or orally at each stage |
| Food packed before ordering | Check FSAI labelling guidance | PPDS labels with full ingredients since 1 October 2021 |
| Calories on menus | Not covered on this page | Required in England for businesses with 250 or more employees |
Allergen matrix steps
- List every dish, sauce, dip, dressing, bread, oil and garnish.
- Get the ingredient specification for every bought-in product from the supplier.
- Mark each of the 14 allergens against each component.
- Build each dish’s allergens from its components, including modifiers.
- Enter the allergens into your POS, website and each app.
- Print the matrix for the kitchen and front of house.
- Re-check whenever a recipe, product or supplier changes, and date every version.
- Train staff to check the matrix, never memory, when a customer asks.
Menu updates: sold-out items, price changes and seasonal dishes
Sold-out items
- Mark the item unavailable on every channel within minutes of running out.
- Name one person per shift who does it, usually whoever runs the pass or counter.
- Use “unavailable today” rather than deleting, so the item returns tomorrow with its photo, modifiers and allergens intact.
- Delivery app portals each have their own sold-out switch. Put them on the shift checklist.
- At close, reset everything that is back in stock for tomorrow.
Price changes
- Check supplier invoices against plate costs every month.
- Work out the new price per channel with the formulas above.
- Decide the start date and tell staff.
- Update the master menu, POS, website and each app on the same day.
- Update printed menus and the price notice at the entrance.
- Place test orders and check totals, including meal deals that contain the item.
- Log the change.
Change several prices at once, a few times a year, rather than one item every week. Customers notice constant small changes more than one planned review.
Recipe and supplier changes
A new supplier for mayonnaise or a new batch of spice mix can change the allergens in a dish. The FSA’s best-practice guidance notes that ingredients may have changed between an advance booking and the day of service. Treat every supplier or product change as an allergen change until you have checked the specification.
Seasonal and limited dishes
Before a seasonal dish goes live anywhere, have ready:
- Name, short kitchen name and description.
- Photo.
- Price per channel and VAT treatment.
- Modifiers and their prices.
- Allergens for the dish and each modifier.
- Kitchen station routing.
- Start and end dates.
In England, businesses in scope of calorie labelling do not need calories for items on the menu for fewer than 30 consecutive days.
Change log example
| Date | Change | Channels | Checked by |
|---|---|---|---|
| 3 March | Wings 6 from €7.00 to €7.50 | POS, website, 2 apps, door notice | Owner |
| 10 March | New garlic dip supplier, adds egg | Matrix, POS, website, 2 apps | Head chef |
| 1 April | Spring special added until 31 May | POS, website, 2 apps | Owner |
Restaurant menu management set-up steps
- Collect every current menu. Till, website, each app, printed menu, leaflets.
- List differences. Mark every price, name, modifier and photo that does not match.
- Build the master menu. One line per item with every field from the table at the top of this page.
- Fix structure. Categories, kitchen names, availability windows and channel rules.
- Build modifiers. Required choices, add-ons, removals and swaps, each with price and allergens.
- Build the allergen matrix. Supplier specifications for everything bought in.
- Set VAT rules. Eat-in and takeaway for every item, and meal deal splits.
- Set prices per channel. Use the pricing formula and your commission rates.
- Add photos and descriptions. Best sellers and deals first.
- Publish to every channel. POS, website and each app.
- Test. One order per channel with a modifier, a meal deal and an allergy request.
- Train staff. Where the matrix lives, who changes the menu, how to mark items sold out.
- Set the review calendar. Monthly price check, six-monthly menu engineering.
Menu audit checklist
- Item names match on every channel.
- Prices per channel are deliberate and documented.
- Every modifier has a price, including €0.00 where intended.
- Every item and modifier has allergen information.
- Allergen information is one click or less from the online menu.
- Delivery orders leave with written allergen information.
- Pre-boxed food is either labelled or packed after ordering.
- VAT rules are set for eat-in, takeaway and meal deals.
- Price notice at the entrance matches the menu.
- Photos match the dish as it is served today.
- Sold-out switch is on the shift checklist for each app.
- Change log is up to date.
Questions to ask and common mistakes
Questions to ask a menu management provider
- Which channels does one change reach: POS, website, each delivery app, printed menus?
- Can I set different prices per channel for the same item without duplicating it?
- Can modifiers carry their own prices and allergen information?
- Can I set availability by day, time and channel?
- How do I mark an item sold out, and does that reach every channel?
- How are meal deals split for VAT?
- Can I import my menu from a photo or file, and who checks it?
- Is there a change history showing who changed what and when?
- What happens to reports when an item is renamed?
- What does each connected channel cost per month?
Common menu mistakes
- Duplicate items for each channel. Reports split, routing breaks and one copy gets forgotten.
- Allergens only in descriptions. Customers cannot filter and staff cannot check.
- Free-text allergy notes. Spelling varies and nobody is accountable.
- Round-number app uplifts. €2 on a €6 side and €2 on a €20 family meal are very different decisions.
- Photos from a stock library. The food that arrives does not match.
- Pre-boxing without labels. In the UK that can turn takeaway food into PPDS food.
- Menus too long for the kitchen. Every extra item adds stock, prep and allergen work.
- Forgetting the door notice. Prices change on screens but not on the entrance display.
Menu management in Eclyde
Eclyde is the restaurant growth platform for independent restaurants in Ireland and the UK. Menu work starts at launch.
- Menu build. The €499 launch covers menu build, website and ordering set-up, POS and printer configuration, customer import, staff onboarding, testing and go-live support.
- Menu import from a photo. Import a menu from a photo.
- Menu photo enhancement. Enhance existing menu photos.
- POS menu tools. Menu modifiers and add-ons, deals and discounts, and gift vouchers.
- Ordering website. A branded ordering website on your own domain, with pickup and delivery, Apple Pay and Google Pay at checkout, and payments through your own Stripe account.
- Kitchen display. Real-time order display with order timers and status updates.
- Analytics. A sales dashboard and AI insights.
After launch, Eclyde costs €99 a month for the whole platform. There is no Eclyde commission on direct orders and no limit on orders or customers. The launch fee is refunded in full within 30 days if Eclyde is not right for your restaurant. See Eclyde pricing.
For plate costing and stock counts, use a supplier invoice spreadsheet or a dedicated tool, and keep the master menu as the single place prices are decided.
Your menu’s numbers
Menu prices decide how much each order leaves you. Channel mix decides how many of those orders lose 13% or 30% before you see the money. The free Eclyde restaurant audit takes about 2 minutes. It checks your Google profile, your website and how much you depend on the marketplaces, then shows what you pay in marketplace commission a year and what direct ordering is worth to your restaurant.
Questions
What is restaurant menu management?
Restaurant menu management is the work of keeping one accurate menu across every place customers order: the till, your ordering website, phone orders and delivery apps. It covers items, categories, prices, modifiers, photos, descriptions, allergen information, availability times and sold-out items. Done well, a price change or a new dish is made once, checked once and shows correctly everywhere, instead of being typed into four systems by hand.
Can I charge higher prices on Just Eat, Deliveroo and Uber Eats?
Your contract with each app decides what is allowed, so read the pricing clauses in your partner agreement or ask your account manager in writing. Whatever you charge, show the price the customer will pay on that channel and charge exactly that. Work out any app price from your commission rate and VAT, not by adding a round number, and keep item names, allergens and photos the same everywhere.
What are the 14 allergens?
The 14 allergens that must be declared in Ireland and the UK are cereals containing gluten, crustaceans, eggs, fish, peanuts, soybeans, milk, tree nuts, celery, mustard, sesame, sulphur dioxide and sulphites, lupin and molluscs. Name the specific cereal or nut, for example wheat or almonds, rather than only writing gluten or nuts. The rules apply to loose food in restaurants and takeaways as well as packaged food.
Do takeaways need allergen information on their online menu?
Yes. In Ireland, allergen information for food sold by distance selling must be available before the purchase is concluded and again at delivery, and it must be given in writing at least once. In the UK, allergen information is needed before the purchase is completed and again when the food is delivered. UK best practice is to keep it no more than one click away from your online menu.
Does Natasha's Law apply to takeaways?
Natasha's Law covers prepacked for direct sale food in the UK: food packed on the same premises before a customer orders it, such as boxed burgers or pre-wrapped sandwiches kept ready to sell. That food needs a label with its name and a full ingredients list with allergens emphasised. Food packed after the customer orders, and food sold by distance selling, is not covered, but allergen information is still required.
How often should I update my restaurant menu?
Update availability the moment an item sells out, and update allergen records whenever a recipe, ingredient or supplier changes. Check prices against supplier invoices every month and after any VAT or commission change. Review the whole menu, including what sells and what earns, every six months. Prepare photos, descriptions, modifiers and allergen details for seasonal dishes before they go live on any channel.
What is menu engineering?
Menu engineering sorts dishes by two numbers: how many you sell and how much cash each one leaves after food cost. Dishes that sell well and earn well stay prominent. Popular dishes with thin margins get a price or portion review. Profitable dishes that do not sell get a better position, name or photo. Dishes that neither sell nor earn usually come off the menu to make room.
Does Eclyde manage my menu for me?
Eclyde builds your menu as part of the €499 launch, which also covers website and ordering set-up, POS and printer configuration, customer import, staff onboarding, testing and go-live support. Menus can be imported from a photo, menu photos can be enhanced, and the POS handles modifiers, add-ons, deals and discounts. After launch Eclyde costs €99 a month for the whole platform.