How to raise menu prices without losing customers

After a price increase, sales usually go up, and that's the number that gets reported. It can hide the one that matters more: how many people came. A store with ticket up 6% and orders down 4% grew sales about 1.8% while serving fewer customers.

Fewer customers paying more can still be a good trade for a while. It stops being one when the customers who left don't come back, or when the next increase pushes more of them out. This guide covers how to measure an increase properly, how to work out how much traffic you can afford to lose, which items to move, and how to take the next increase more carefully.

The formulas

Three formulas cover most of what you need.

• Sales change = (1 + ticket change) × (1 + order change) − 1.
• Contribution per order = average ticket − food and paper cost per order.
• Break-even order loss = price increase ÷ (contribution margin + price increase), where contribution margin is contribution as a share of the old ticket.

The first shows why sales alone mislead. A 6% ticket rise and a 4% order fall give 1.06 × 0.96 − 1 = 1.8%. Sales went up. Customers went down.

The third tells you how many orders you can lose before the increase leaves you with less contribution than before. It assumes food and paper cost per order stays the same, and it is before hourly labor and other costs, so treat it as a ceiling, not a target.

A worked break-even

Say a store's average ticket is $12.00 and food and paper run 30%, or $3.60 per order. Contribution is $8.40 per order, a 70% contribution margin.

A 5% increase takes the ticket to $12.60 and contribution to $9.00. To earn the same total contribution, the store needs $8.40 ÷ $9.00 = 93.3% of its old orders. It can lose up to 6.7% of orders before the increase stops paying for itself. The formula gives the same answer: 0.05 ÷ (0.70 + 0.05) = 6.7%.

That sounds like plenty of room, but it isn't free room. A guest who stops coming loses you every future visit, not just one order. So the goal is not to use up that 6.7%. The goal is to lose as few as possible, and to know the ceiling so you can tell a costly increase from a mild one.

Measure traffic, not sales

Compare orders with the same weeks last year, 364 days back so weekdays line up, for four to eight weeks after the change. Put it beside the change in ticket and beside local restaurant price inflation. If orders fell faster than your market, the increase likely cost customers.

On sales, Castle Rock looks fine. On orders, it served 384 fewer guests over eight weeks. If local restaurant prices rose about 3% over the same year, Castle Rock's ticket rose roughly twice as fast as its market, and the order loss is likely tied to the price change rather than to the neighborhood.

A few checks before concluding that:

• Did the store run a promotion last year in the same weeks that it didn't run this year?
• Did a competitor open or close nearby?
• Did delivery orders shift between channels? Look at total orders, not counter orders alone.
• Did the store have staffing gaps or long waits that would cost orders on their own?

If none of those explains it, the price change is the most likely cause.

Use menu engineering

Sort items by how often they sell and how much they contribute after food cost. A common way to set the lines: an item is high popularity if its share of item sales is above about 70% of an even share (for 20 items, above 3.5%), and high margin if its contribution in dollars is above the menu's weighted average.

• High popularity, high margin: protect these. Small moves only.
• High popularity, low margin: candidates for a small increase or a cheaper build.
• Low popularity, high margin: promote them. Placement and description often matter more than price.
• Low popularity, low margin: rework or remove.

The second group is where most pricing work happens. A popular item with thin contribution, often a combo built around a costly protein, can take a modest increase or a smarter build. For the build side, see how to lower food cost, and for where food cost sits in the larger picture, how to calculate prime cost.

Take increases in smaller steps

• Hold the few prices everyone knows, and move items customers price-check less.
• Watch the value tier. If the cheapest meal crosses a round number, traffic tends to notice.
• Change a few items at a time, so you can tell which move cost customers.
• Prefer two small increases a year apart to one large one, where your costs allow it.
• Raise add-ons, sides and premium options before the base items people compare across brands.
• Keep delivery and in-store pricing decisions separate, and check each channel's order count on its own.

Protect value on the day of the change

Guests notice a price change most when nothing else about the visit feels better. The day the new board goes up is a good day for the basics to be right: hot food, a correct order, a short wait. A store that raises prices during a week of long waits gives guests two reasons to try somewhere else. Brief the crew so they can answer a question about prices calmly, and keep the menu board and online menus in step so nobody is charged a different price than the one they saw.

A step-by-step price review

1. Pull item sales and plate cost for the last 8 weeks and sort the menu into the four groups.
2. Pick a short list of candidates, mostly from high popularity, low margin items and add-ons.
3. Work out the break-even order loss for the proposed change.
4. Check your franchise agreement and brand guidance on who sets menu prices.
5. Make the change on a known date and note it, so you can measure from it.
6. Each week for four to eight weeks, compare orders and ticket with the same weeks last year.
7. Compare the order change with the break-even figure and with local price inflation.
8. If orders fell well past what you expected, adjust the value tier or the most visible items first.
9. Write down what happened, so the next increase starts from evidence rather than memory.

Common mistakes

• Reporting sales growth as proof the increase worked.
• Comparing with last month instead of the same weeks last year, which mixes seasonality into the result.
• Raising every item by the same percentage, including the few prices every guest remembers.
• Pushing the cheapest meal across a round number.
• Changing a lot of items at once, so nobody can tell which move cost customers.
• Measuring for two weeks, when habits take four to eight weeks to settle.

For franchisees

How much of the menu price is yours to set differs by brand and agreement. Follow your agreement and your brand's current guidance before changing the menu board. Some brands set a suggested range and let owners choose within it. Others set prices for all stores or for a promotional tier only. A single-store owner and a multi-unit operator in the same brand may still face the same rules, so check before you change anything. More for owners running one store is at single-store operators.

Where Franlever fits

Franlever compares each store's orders with the same weeks last year beside its ticket, and says plainly when fewer customers are paying more. It reads this from the POS, measures each store against its own normal range and the brand's median, and on mornings when nothing has moved, it says so.

General information for restaurant and franchise operators, not legal, tax, accounting or financial advice. Figures in examples are illustrations, not predictions or promises of results. Laws and platform policies change and differ by location, so check the current rules and talk to a qualified advisor about your situation.