How to put a menu price increase through quietly

Every venue has to raise its prices sooner or later. Ingredients, energy, rent and wages all rise, and a menu priced two years ago is quietly giving that money away on every plate. Most operators know this and still put off the decision, because a price rise feels like a risk: regulars will notice, reviews will mention it, and the dining room might be quieter the week after.

A menu price increase does not have to be an event. Done well, most guests barely notice it, the regulars who do notice accept it, and the venue recovers the margin it had been losing. Done badly, with every price up by the same percentage on the same day, it reads as a rise across the board and invites exactly the comparison you wanted to avoid.

Quietly does not mean dishonestly. This guide is about making a rise that is fair and visible on the menu, without hidden charges or shrinking portions behind guests' backs, and about using rounding, anchoring and timing so that it lands well. Every figure in it is an example.

A price rise should start with numbers, not with a feeling that prices are too low. Two figures tell you where you stand.

The first is the cost of each dish. If ingredient prices have risen since the menu was costed, every plate is earning less than it was designed to. Our guide to plate cost shows how to re-cost a dish from the current invoices. The second is the gross profit per dish, the cash each dish leaves after its ingredients, compared with what it left when the price was set. Our guide to why gross profit per dish beats food cost percentage explains why that cash figure, not the percentage, is the one to restore.

With both figures for every dish, the rise stops being a single decision about the whole menu and becomes a set of small decisions about particular dishes. That is the first and most important step towards making it quiet.

A flat increase of the same percentage on every dish is the simplest rise to calculate and the most noticeable. It changes every number on the menu, including the ones guests remember.

Some dishes can carry a rise easily:

Others are better left alone or raised least:

Our guide to menu engineering sorts dishes by popularity and by gross profit, which is a useful way of deciding where a rise belongs. A popular dish with a weak margin is often the first candidate; a dish that is neither popular nor profitable may need replacing rather than re-pricing.

Prices that change at the edges are less noticeable than prices that change in their first digit. A dish moving from 14.50 to 14.95 is a smaller jump in the guest's mind than one moving from 14.50 to 15.50, even though the second is only a little larger in money.

Three rounding habits help:

Rounding cuts both ways. Some venues use whole numbers throughout, without endings at all, as a deliberate style. If that is yours, keep it, and make the rise in whole steps on the dishes that can carry them.

Guests judge a price partly by the prices around it. A dish at 24 looks expensive on a menu where every other main is 16, and reasonable on one with a 34 steak at the top. This is the anchoring effect, a well documented bias in how people judge numbers, summarised in Wikipedia's article on anchoring.

Use it honestly. A premium dish at the top of a section makes the others look more moderate, and it is a genuine choice for the guests who want it. Placing a rise on a dish that sits next to a higher-priced one is quieter than placing it on the most expensive item in the section. And adding a new premium dish in the same week as a rise changes the frame the whole section is read in.

Do not invent a decoy that nobody is meant to order. A premium dish should be one you are proud to serve and happy to sell.

When a rise happens matters almost as much as how large it is.

If costs have risen sharply and a menu change is months away, a rise on a few dishes now is better than giving away margin until then. Make it on the dishes least likely to be noticed.

A price rise lands more quietly when the menu gives guests something else to look at. Consider, in the same week:

The point is not to distract guests from the rise. It is that a menu that improves at the same time as it costs more feels like a different menu, not the same menu at higher prices.

Some ways of raising prices are quiet only because they hide what is happening, and they cost trust when guests notice.

In the UK, the Price Marking (Food and Drink Services) Order 2003 requires prices to be shown to guests before they order, with displays at or near the entrance to an eating area, prices shown including VAT, and any additional or minimum charge shown at least as prominently as the food prices it relates to. Elsewhere, check the rules where you trade. Whatever the law requires, guests should see the price they will pay before they order.

An invented menu of eight mains, with ingredient costs that have risen by about 8 per cent across the board since the last price change. A flat 8 per cent rise would move every main, including the 12.50 burger to 13.50 and the 28 steak to just over 30.

A quieter plan:

The average price across the mains rises by a little under 5 per cent, but weighted by what guests order, it recovers most of the margin lost to the 8 per cent rise in costs, because the larger rises fall on the dishes that sell and whose costs rose most. Most guests see a menu with a new dish, one less dish and prices that look familiar.

A set menu has one price, so it cannot be re-priced dish by dish. It has other levers instead.

The courses can change. A set menu that is re-written each season can absorb rising costs in the choice of dishes, with a less expensive main balanced by a more generous dessert, without the price moving at all. The supplements can change: a premium choice within a set menu can carry its own supplement, which guests choosing it accept because they are choosing it. And the price itself can move with a new season's menu, when the menu is new and guests have nothing to compare it with.

What does not work is quietly making the same set menu smaller. Guests who order a set menu often order it repeatedly, and they notice.

A group with several venues has a choice to make: the same prices everywhere, or prices that reflect each venue's location and costs. Both are defensible, but mixing them by accident is not. Guests who see one price in one venue and another price for the same dish down the road will ask why, and the answer should be a decision, not an oversight.

If the menus are shared, plan the rise once and apply it everywhere on the same day, with the same changes to descriptions and dishes. If each venue prices for its own location, document the difference so that managers can explain it.

The most common pricing mistake is not a badly handled rise but a rise that never happens. A venue that holds its prices for two or three years while its costs climb ends up needing a large rise all at once, and a large rise is exactly the kind guests notice.

Small, regular reviews avoid it. A menu reviewed every few months, with modest changes on the dishes whose costs have moved, rarely needs a dramatic correction. The guests who come every week see a price change now and then, alongside new dishes, which is what a living menu looks like.

Drinks have strong reference prices: guests know roughly what a pint, a glass of house wine and a coffee cost. Keep those stable where you can, and recover margin on the cocktails, the wines further up the list and the premium spirits, whose prices guests compare less. Our guide to pour cost covers how to price drinks from their cost.

The floor team will be the first to hear about the rise from guests. Brief them before it happens: what has changed, why, and what is new on the menu. A server who can say "the fish has a new garnish this season and the price reflects what we pay for it" handles a question far better than one who learns about the rise from a guest.

Do not ask the team to apologise for the prices. A short, honest answer is enough, and most guests who ask are curious rather than angry.

Watch three things in the weeks after a rise.

Give it a few weeks before judging. The first week after any change is noisy. If a dish's sales fall sharply and stay down, its new price may be above what guests will pay for it; review it rather than the whole rise. Our guide to menu pricing methods covers the alternatives when a price meets resistance.

Review the whole menu's costs and prices at least every few months, and whenever an important ingredient changes price significantly. Small, regular adjustments on the dishes that need them are quieter than a large rise every few years after margins have been eroded for a long time.

Keep a simple record of each change: the date, the old and new price, the reason and the effect on sales. Over time it becomes the best guide to how your own guests respond to prices, which is worth more than any general rule.

A price change is quick to make and easy to get wrong when the same menu lives in several places. In servearound, a dish's price is set once in menus and shows on the till, on every table's QR menu and on the venue's public menu page at the same time, so the price a guest reads is the price they pay.

The menu report in Analytics shows units sold, revenue and share of sales for every dish over any range of dates, so you can compare the weeks before a rise with the weeks after, dish by dish, and see whether guests moved to other dishes.

servearound does not hold dish costs today, so the costing that tells you which dishes need a rise stays in your own sheet. If you would like to see how menus and prices work, get in touch.

Enough to restore the margin each dish was designed to earn, which you find by re-costing the dishes at current prices. That usually means different rises on different dishes, not one percentage across the menu.

The prices themselves should always be clear before guests order. A separate announcement is rarely needed; a menu that changes with new dishes and the same honest prices speaks for itself. Brief the team so they can answer questions.

The ones guests use to judge your prices: often the cheapest main, the house wine, a pint, a coffee or a children's meal. Raise these least, or leave them, and recover margin elsewhere.

If a portion genuinely needs to change, change the description and the price to match. Reducing portions silently costs more in trust than it saves in food.

Review regularly, but change prices rarely: one considered rise a year, or two smaller ones, is easier for guests to accept than frequent changes.

On some dishes, a little, especially those near the top of what guests will pay. Measure units sold and gross profit per guest for a few weeks before judging, and review individual dishes rather than the whole rise.

Either works, as long as the menu is consistent. Endings such as .95 make small rises less noticeable, because the first digit changes less often. Whole numbers read as more confident and suit some formats better. Pick one style and keep it through every rise.

Regulars notice changes to the dishes and drinks they order every visit, especially when a price crosses a round number. Most guests notice little else, particularly when the menu also changes. That is why the dishes guests compare should move least.

Guests do judge prices against the ones around them. Use that honestly, with premium dishes you are happy to sell, rather than decoys nobody is meant to order.

A quiet menu price increase starts with re-costing every dish, so the rise is aimed at the dishes whose margins have been eroded rather than spread evenly across the menu. Leave the prices guests compare, raise the dishes they choose for what they are, avoid crossing round numbers on the dishes regulars watch, and let the rest of the menu frame each price.

Put the rise through with a menu change, not in the busiest week, and give guests something new at the same time. Keep it honest: no hidden charges, no silent shrinking of portions, and the same price everywhere the menu appears. Brief the team, then measure units sold and gross profit per guest for a few weeks before judging the result.