Updating the menu in one place, not five

Updating the menu should be simple. A supplier raises a price, a dish is replaced for the season, a garnish changes, or a dish runs out on a busy Saturday. In theory, someone makes the change and the menu is right again. In practice, the same dish and price live in several places at once, and updating the menu means updating all of them, by hand, usually by different people, often at different times.

The result is a menu that disagrees with itself. The printed menu says one price, the till another. The QR menu still shows a dish the kitchen stopped making a week ago. The website has last season's PDF. A guest orders from one version and is charged from another, and the server is left to explain why the menu they handed over was wrong.

This guide sets out the five places a price usually lives, what happens when they disagree, and the habits and tools that keep them aligned. It covers changing the menu for the season, marking dishes sold out, printing menus without waste, updating a QR menu, and the menu management routine that stops the disagreements before they reach a guest.

In most venues, each dish and its price live in at least five places:

Venues that sell through delivery apps add another place for every app. Each of these is a copy of the same information, and each copy can drift. The more copies, the more often they disagree, and the more work every change creates.

When the copies disagree, guests notice first. A guest who orders a dish at the printed price and sees a higher price on the bill feels misled, even if the difference is small and the mistake is innocent. A guest who orders a dish from the QR menu and is told it is not available feels the same. Both are moments that can turn a good visit into a complaint.

The team notices next. Servers have to explain the discrepancy, managers have to decide whether to honour the lower price, and the end-of-night reconciliation has to account for the difference. Each correction takes time, and the same mistake tends to repeat until the copies are fixed.

The business notices last, usually in the numbers. A price increase that reached the menu but not the till means weeks of selling at the old price. A dish removed from the till but not the menu means orders that cannot be fulfilled. These are small losses, but they are invisible until someone looks, and they add up.

Prices are not the only thing that can disagree. Allergen and ingredient information that differs between the printed menu and the record the kitchen uses is a food safety problem, not just an inconvenience. When a recipe changes, every copy of its allergen information has to change with it. In the UK, for example, the Food Standards Agency's allergen guidance for food businesses sets out what allergen information must be provided and kept accurate, and other countries have rules of their own.

Most of the time, updating the menu goes wrong for organisational reasons rather than technical ones. Different people own different copies: the chef owns the printed menu, the manager owns the till, someone else owns the website and nobody quite owns the QR menu. A change made by one person does not reach the others.

Timing is the next problem. A printed menu cannot change until it is reprinted, so price changes wait for the next print run, while the till changes the same day. For a few days or weeks, the two disagree by design.

And some copies are simply forgotten. The PDF on the website, the price on the delivery app, the board behind the bar: each is updated less often than the main menu, and each falls further behind with every change.

The answer is to keep one source of truth for every dish: one place where its name, description, price, allergens and availability are set, and from which every other copy is produced. Change the dish there, and every copy changes with it.

That is easier said than done with separate systems. A printed menu designed in a desktop publishing tool, a till with its own product list and a QR menu hosted somewhere else will always be three separate copies, however careful the team. One source of truth needs the menu, the till and the digital menu to read the same dishes.

Where that is not possible, the next best thing is a single master list, such as a spreadsheet, that every change goes through first, with a clear owner and a checklist of every copy that must be updated afterwards. It is slower and more error-prone, but far better than changes made directly in each copy.

Menu management is the routine that keeps the menu right. It does not need to be complicated, but it does need an owner and a rhythm.

Name one person who owns the menu: every change goes through them, and they make sure every copy is updated. In a small venue, this might be the chef or the general manager; in a group, it may be a central role. What matters is that nobody else changes a copy directly.

Set a rhythm for routine changes. Many venues review prices monthly or quarterly, change dishes seasonally and handle urgent changes, such as a dish running out, as they happen. Keep a short log of every change: what changed, when, why and who approved it. The log is what lets you answer a guest's question about a price, and what shows whether a change reached every copy.

Seasonal changes are the largest and most error-prone updates. Several dishes change at once, prices are reviewed, descriptions are rewritten and allergen information has to be updated for every new recipe.

Plan them like a small project. Agree the new dishes and prices first, then update the source of truth, then check every copy against it before the change goes live. Brief the floor team on the new dishes before the first service, including their allergens, so servers can answer questions with confidence.

Pick a quiet day to go live, and keep the old menu available until every copy has changed. Changing the menu on a Friday night means discovering the problems during the busiest service of the week.

Price changes need the most care, because they are what guests notice. Change the price in the source of truth first, then in every copy at the same time, so there is no window in which the menu and the bill disagree.

When the printed menu cannot be reprinted immediately, choose a date for the change and make it everywhere on that date. Some venues print new menus in advance and swap them on the morning of the change; others reprint only the pages that changed. Either way, the till should not change before the printed menu does.

If you raise prices, think about how to explain them, if at all. Most guests accept modest increases without comment, especially when the menu is otherwise unchanged. Our guide to menu pricing covers how to set prices in the first place.

The most urgent update of all is the dish that runs out mid-service. Kitchens call it an 86. On a printed menu, there is nothing to update; servers have to remember to tell guests. On a QR menu, the dish should disappear or be marked sold out at once, so guests do not order something that cannot be made.

An 86 that reaches only some copies causes the most frustration. A guest orders the sea bream from the QR menu, the order reaches the kitchen, and the kitchen sends it back. The server then has to return to the table with bad news, and the guest has to choose again, often after their companions have already been served.

Make the 86 a single action. Whoever marks a dish as sold out should mark it everywhere at once: the till, the digital menu and any screens. Brief the floor team at the same moment, so they stop recommending it. And decide when it comes back: tomorrow, automatically, or only when someone says so.

Printing menus is where updating the menu costs real money. Every price change or new dish can mean a new print run, and a venue that reprints every few weeks spends a surprising amount on paper and design time. Some venues end up living with an out-of-date printed menu to avoid the cost, which is how the copies drift apart.

There are several ways to reduce the cost. Design the printed menu so that the parts most likely to change, such as specials, are on a separate insert. Print smaller runs more often rather than large runs that go out of date. Print in-house on good paper for menus that change frequently, and keep professionally printed menus for the parts that rarely change.

Above all, print from the source of truth. A printed menu produced from the same dishes as the till and the QR menu will always be correct on the day it is printed. The remaining risk is that something changes after printing, so keep a record of what was printed and when.

Updating a QR menu should be the easiest change of all, because there is nothing to print. In practice, many QR menus are PDFs uploaded to a website, and changing them means editing the PDF, exporting it and uploading it again. That is barely faster than reprinting, and it is easy to forget.

A QR menu that is a live digital menu, rather than a PDF, can change the moment the source changes. A price updated once appears on every guest's phone immediately, and a dish marked sold out is off the menu straight away. That is one of the strongest reasons to choose a digital menu over a PDF.

Check the QR codes themselves too. A code printed on table cards that points to an old link, or to a PDF that has since been deleted, leaves guests with a broken menu. Use one stable link per table or venue, and change what it shows rather than the code.

Menu boards and screens in the room are another copy that is easy to forget. A board behind the bar showing last month's prices undermines the rest of the menu. If your boards are printed or written by hand, add them to the checklist for every change. If they are screens, they should read from the same source as the rest of the menu.

The website deserves the same attention. A PDF menu on a website is often the first version a guest sees, and it is often the most out of date. Replace PDFs with a live menu page where you can, and if you must use a PDF, update it as part of every change.

Do not forget listings. The menu link on your Google profile, the menu shown on booking platforms and any delivery app listings all need checking when the menu changes.

Groups with several venues face the problem many times over. A price change agreed centrally has to reach every venue's menus, tills and screens, and each venue may have local variations: a dish only one site serves, or a price that differs in one city.

Keep the group's dishes in one library, with local variations recorded as exceptions rather than separate copies. A change to a shared dish should reach every venue that serves it, while a local price stays local. Copying a menu to a new venue should copy its dishes, photographs, options and allergen information together, so the new site starts correct.

Agree who can change what. Central teams may own shared dishes and prices, while venue managers own local specials and sold-out dishes. Clear ownership stops a change at one venue quietly overwriting another.

Venues that sell through delivery apps carry another copy of the menu for every app, usually entered by hand in each app's own tools. These copies are often the furthest behind, because nobody in the dining room sees them. A price rise that reached the menu in January can still be missing from an app in March.

Add every app to the checklist for each change, and give one person the job of updating them. Check each app's menu as a guest would see it at least once a month. If an app's prices are deliberately different, for example to cover its commission, record those differences in the source of truth too, so they change in step with the main menu rather than drifting on their own.

A menu is only as current as the people who serve from it. A server who recommends last week's special, quotes an old price or cannot answer a question about a new dish undoes the work of updating every copy. Every change needs a short briefing as well as an update.

Make the briefing part of the pre-service routine. Before the first service after a change, tell the team what changed, why, and what guests are likely to ask. For new dishes, cover the main ingredients, the allergens and how the dish is served. For price changes, make sure servers know the new prices before guests see them.

Keep a short written note of each change where the team can see it, such as a printed sheet at the pass or a message in the team's channel. Staff who missed the briefing can catch up, and the note doubles as part of the change log.

Even with good habits, copies drift. A monthly check catches problems before guests do:

It takes about half an hour, and it finds the differences that would otherwise reach a guest first.

In servearound, dishes live in one library. Put the same dish on the lunch, dinner and bar menus and it stays one dish: change its photo or description once and every menu shows it, with a price of its own on one menu if you want. A whole selection of prices can move by a percentage or an amount in one go.

The QR code menu, the boards on the screens in the room and the point of sale read the same dishes, so a price changed once is right everywhere. Mark a dish sold out once and it is off every menu it is on, until tomorrow or until you say. Print designs come from the same live menu and are printed or saved as a PDF, and if anything changes after printing, the design says it is out of date and lists what changed.

Groups can copy one menu or all of them to their other venues, with sections, dishes, photos, tags, options and bundles together, and each copy arrives switched off until you turn it on. See the menus module, or get in touch to see how your menu would work.

Many venues review prices monthly or quarterly, and change them when costs move significantly. What matters more is changing every copy at once.

A live menu page is easier to keep current. If you use a PDF, update it as part of every change, and check it monthly.

One named person, usually the chef or general manager in a single venue. In a group, shared dishes may be owned centrally and local specials by each venue.

Mark it sold out once, everywhere at the same time, and tell the floor team. Decide when it comes back.

That depends on local consumer rules and your own policy. Many venues honour it as a goodwill gesture, then fix the menu immediately. Check the rules where you trade.

Update the recipe and its allergens in the source of truth first, then every copy, and brief the floor team before the next service.

Many venues keep both. A printed menu suits guests who prefer paper, while a live QR menu is the copy that can change in seconds. What matters is that both come from the same dishes.

Updating the menu goes wrong because the same dish lives in several places: the printed menu, the till, the QR menu, the website and the screens, each owned by a different person and updated at a different time. When the copies disagree, guests notice first, the team spends time explaining, and the business loses money quietly.

Keep one source of truth for every dish, give menu management one owner and a rhythm, change every copy at once, make the 86 a single action and print menus from the same source. Make updating a QR menu instant rather than a PDF upload, include the website, boards and listings in every change, and check five dishes across every copy once a month.