The menu changes on four clocks
“How often should we change the menu” is really four questions, because a menu has layers that move at different speeds. Treat them separately and the answer gets easy.
| Layer | Its usual clock | What triggers a change |
|---|---|---|
| Specials and the soup | Daily or weekly | What came in, what has to move |
| Prices | When costs move | An invoice that no longer matches the menu |
| Seasonal dishes | A few times a year | Produce, weather, holidays |
| The core menu | Rarely | A new chef, a new concept, a dish that stopped selling |
Most arguments about menu changes are about the core. Regulars want it left alone; the chef wants to cook something new. The answer is usually to give the chef the edges (specials and seasonal dishes) and protect the center.
Signs the menu is overdue
- The printed prices are wrong. If servers are quoting a different number than the menu, it is already late.
- Cooks are making substitutions nightly. A dish that is never made as written is not on the menu anymore.
- A dish has not sold in weeks. It still takes a line on the menu and a spot in the walk-in.
- The season is wrong. Heavy braises in July, tomato salad in January.
- The same three specials sell out every night. They are asking to join the menu.
- Staff are bored. A kitchen that has cooked the same menu for years usually shows it.
How often, by kind of restaurant
The kind of room sets the pace more than any rule:
- Tasting menus can change weekly or even daily, because the menu is the reason to come. See menus for fine dining.
- Neighborhood restaurants tend to swap a handful of dishes with the seasons and keep the rest.
- Diners, delis, and pizzerias sell familiarity; they change prices and specials and leave the core alone for years.
- Bars change the cocktail list with the seasons and the beer list with every keg.
- Cafés add a seasonal drink a few times a year and sell out of pastries daily.
Prices: in batches, not a drip
Prices are the layer that changes most without anyone planning it. A supplier raises the price of beef, then eggs, then cups, and each invoice is a small reason to move a number. Moving one price every week is honest, and it also means the menu your regulars read is different every time they come in. Many operators batch the changes instead: watch the costs, then move the prices that need it on one day, brief the staff, and leave the rest alone. The exception is a single item whose cost jumps hard, like market seafood, which is better priced by the day than frozen at a number that loses money.
Change a few dishes, not the whole menu
When it is time for a seasonal change, change the dishes that are not working first. Menu engineering sorts every item by how much it sells and how much it earns, which tells you which dishes to cut, which to reprice, and which to leave alone; see menu engineering. A dish that sells well and earns well stays, whatever the season.
A test run helps. Put the new dish on as a special for a week or two before it goes on the menu. If it sells and the line can make it fast, promote it. The mechanics of running those are in daily specials, and the full changeover, from three weeks out to the morning after, is the seasonal menu changeover checklist.
What each change costs
On paper, every change is a reprint, which is why printed menus change less often than kitchens want them to. Owners wait for a batch of changes to be worth the print run, and the menu is wrong in between. The cost of that is worked through in menu printing cost.
Once the everyday menu lives behind a QR code, the small changes cost nothing to make, so the question becomes what is right for the food and the guests, not what is worth reprinting. Big changes still deserve a plan and a staff briefing; the small ones can happen the day they are true. When the change is one guests will feel, tell them well: how to tell customers about menu changes.
What Gaslamp does and does not do
Gaslamp makes the small changes quick: edit a price, a dish, or a whole section from your phone, and the menu behind every QR code shows it about thirty seconds after you save. You can build next season’s dishes in a hidden section ahead of time and show it on the day. Version history keeps the last 50 saves, so last season’s menu is there if you want a dish back.
Gaslamp does not tell you when to change the menu, and it does not schedule a change for a future date. It does not read your sales data; for what sells, use your POS reports.