How to Raise Menu Prices Without Losing Regulars: A Rollout Plan

Start with the reason, not the percentage

Before choosing new prices, write down what changed. It may be a supplier increase on a specific protein, a packaging cost, a wage adjustment, a platform commission, or simply years of drift while costs rose.

Writing it down does three things. It tells you which items are actually affected, it gives your team an honest answer when a guest asks, and it keeps the change proportionate. If the reason is a 12% increase on one protein, a blanket 12% across the menu is hard to defend and easy to over-apply.

Group items into three buckets: those whose costs moved, those that are underpriced relative to the rest of the menu, and those you will leave alone for now. Most successful price changes are narrower than the first draft.

Decide what moves, and by how much

Work item by item. For each candidate, note the current price, the new price, the reason, and what the change does to the contribution you keep per plate. Where your recipe costs are current, this is arithmetic. Where they are not, treat the new price as a working assumption and confirm the cost before you publish.

Two practical rules keep the change from looking arbitrary:

If a full increase is too much at once, consider rework before reprice: a smaller portion of an expensive garnish, a simpler side, or a different cut. That is a kitchen decision, not a menu decision, and it should be made before the price changes.

• Move items that are genuinely out of line, and leave the value leaders where they are. Guests notice when the dish they order every week changes and the rest of the menu does not.
• Avoid changing a price twice in a short window. One planned increase is easier to explain than two unplanned ones.

Pick the date and the wording

Choose a date that is not the busiest week of your year and not the day after a festival. A quiet Monday is easier to manage than a Saturday night, and it gives the team a full service to get comfortable with the new numbers.

Write two sentences your team can say out loud. Something like: "Yes, the price on the short rib went up this week — our supplier cost went up twice this quarter. Everything else is unchanged." That is enough. Guests do not need a lecture; they need a straight answer.

Decide in advance how you will handle the guest who is unhappy. A single comp, a smaller portion at the old price for one visit, or a simple apology are all reasonable. What matters is that every server gives the same answer.

Update every channel from one source

The most common failure in a price change is not the price. It is the menu that did not get updated: the printed copy in the drawer, the QR page, the delivery listing, the website, the specials board.

Before the change date, build a checklist and assign an owner to each line:

Keep one master menu as the source for all of them. If a channel cannot be updated on the same day, decide what you will do in the meantime — a printed insert, a note at the host stand, or a temporary pause on that item.

• Hosted QR menu, including the PDF download if you offer one
• Printed menus and any laminated table copies
• Delivery platform listings, including any duplicate listings for the same brand
• Website menu page and any online ordering widget
• Specials boards, chalkboards and window signage
• Staff-facing documents: prep sheets, station copies and till buttons

Brief the team before the change goes live

A short pre-shift briefing the day before the change is worth more than a memo. Cover four things: which items changed, the reason in one sentence, what to say if a guest asks, and who to fetch if the conversation gets difficult.

Ask the team what they expect to hear. Servers usually know which guests order which dish and which price is going to sting. That information is free and arrives before the change instead of after it.

Worked example: a modest, targeted increase

The numbers below are illustrative.

A bistro raises three of its twenty-two items: a steak dish from $28 to $31, a seafood pasta from $24 to $26, and a shared board from $19 to $21. The other nineteen items stay put. The reason is a documented increase in the cost of two proteins and one imported ingredient.

The team gets a one-page brief: the three items, the reason, the two-sentence answer, and a rule that any complaint goes to the manager on duty. The QR menu, the printed copies and the delivery listings are updated the same morning; the delivery listing for one item lags by a day, so the host explains it at the door.

Three weeks later, the mix shows the steak dish down about 8% in units and up in contribution per plate; the seafood pasta is flat; the shared board is flat. The next review is scheduled for the end of the month. No second change is made before that review closes.

Review the weeks after

Watch three things after the change: the units sold on the items you moved, the total revenue, and the questions your team is still getting. If a moved item drops sharply, ask whether it was the price, the placement or something else before you reverse course. If the questions have stopped, the wording worked.

Keep a dated record of the change. If you later raise prices again, the record is your evidence that the previous change was planned, explained and measured.

When the decisions are made, the MenuCrafters AI menu builder keeps the menu you edit as the single source for the hosted QR page and the print-ready PDF, so a price change lands in one place instead of being retyped into every channel.

Limitations and assumptions

This plan assumes you can identify the cost change that justifies the increase and that you control your own prices. It assumes you can update your main channels within a day. It cannot predict how your guests will respond to a specific increase, how competitors will react, or what a delivery platform will do to its commission. Contract pricing, franchise rules and platform agreements may limit what you can change and when. Where recipe costs are out of date, treat every new price as provisional and confirm the cost before publishing.