Menu pricing that keeps up with your costs

Most menus get priced once, when the restaurant opens, and then drift for years while ingredient costs move underneath them. A dish that made sense at a nine dollar cost of goods can quietly turn into a loss leader eighteen months later if nothing on the menu ever changes. Keeping pricing current is a habit built on knowing what each dish costs, what margin each category needs to hold, and when a price is due for a move.

Cost out a dish

Start with the recipe as it's plated today, since the recipe card written at launch and the plate the kitchen sends out now have usually drifted apart. Weigh or measure every ingredient at the portion size in use right now, then price each one against the current invoice cost. Add them up and that's the plate cost. Divide the plate cost by the menu price and you get food cost percentage for that dish.

Garnishes, sauces, and the bread that hits the table before the order even arrives are easy to leave out of this math, and they add up faster than owners expect. A house-made sauce spooned onto six different dishes needs its own per-batch cost broken down to a per-portion figure, the same treatment as any other ingredient.

Target margins by category

Not every dish needs to hit the same food cost percentage. A restaurant averaging 30 percent food cost across the whole menu usually gets there by running some categories tighter and letting others run looser.

• 01Entrees carry the volume and often sit closest to the restaurant's overall target, since they're what most guests order.
• 02Appetizers and sides tend to run a lower food cost than entrees, since smaller portions and shared prep work stretch the margin further.
• 03Beverages, especially alcohol, usually run the lowest food cost of anything on the menu and cover a good share of the categories that run higher.
• 04Specials and limited-time items can run a higher food cost on purpose, since they're driving traffic or using up inventory rather than maximizing margin.

The category average matters more than any single dish's number. A steak that runs a higher food cost than the rest of the menu is fine as long as the category around it is pulling its weight, and someone is periodically checking that blend.

When a price is due for a move

The signal is usually simple: a dish's food cost percentage has drifted well past where the category normally sits, and the drift held across more than one bad week. Pull the cost-out again after two or three consecutive vendor price increases on the same ingredient, rather than after the first one. A single invoice spike is often temporary. A pattern across a season usually holds.

Reviewing the whole menu on a set schedule, once or twice a year, beats reacting to individual ingredients one at a time. A scheduled review catches the slow drift across everything at once, instead of only the ingredient that spiked loudly enough to notice on its own.

How to raise a price without losing regulars

Small, frequent adjustments read as normal. A large jump on one dish reads as a problem, even when the math behind it is sound. Moving a price by fifty cents to a dollar at a time, spread across a handful of dishes rather than concentrated on the one that hurt the most, tends to pass quietly with regulars who order the same thing every visit.

Timing helps too. Rolling changes into a menu reprint or a seasonal update folds a price change into something that already looks different. Servers who know a price moved and why can answer a question calmly if a regular asks, instead of looking caught off guard by their own menu.

What tends to backfire: freezing prices on a guest's favorite dish while raising everything around it, hoping nobody adds it up. Regulars notice patterns over a longer window than owners expect, and a menu that spreads its increases evenly reads as more considered than one that visibly protects a few favorites.

Getting vendor pricing under control first

Before touching the menu, check whether the cost increase is even worth passing on to guests. One vendor raising a single ingredient's price is sometimes a negotiation worth having before it becomes a pricing problem. Ask what a competing distributor charges for the same item, and ask your current vendor to match it or explain the gap. Distributors expect this conversation, and there's often room to move that never gets tested because nobody asks.

Substitution is the other lever worth pulling before pricing. A slightly different cut, a different pack size, or a seasonal swap can absorb a cost increase while the menu price and description stay the same. Not every increase can be absorbed this way, but checking costs a phone call and a few minutes.

Setting a cadence for costing

A cost-out done once at menu launch and never revisited creates false confidence in a number that stopped being true a year ago. Set a fixed check-in, quarterly works for most kitchens, and re-price every dish against current invoice costs rather than waiting for one ingredient to become an obvious problem. A quarterly habit turns pricing into routine maintenance instead of a stressful catch-up project every couple of years.

Keep the recipe costing sheet somewhere the kitchen updates as prices change, rather than buried in a folder only the owner opens. A shared spreadsheet that the chef or kitchen manager updates as vendor prices shift stays accurate in a way an annual project never does, and the next review starts from real numbers instead of a guess.

Telling staff before guests notice

A server finding out about a price change from a guest questioning their receipt undermines the change fast. Walk the front of house through what changed and roughly why, in plain terms, before the new menu goes out. "A few things went up this season, so we adjusted a handful of prices to keep up" is enough. Servers don't need the full cost breakdown, but they do need an answer ready before a guest asks for one.

This matters most for regulars, since they're the ones who'll notice a fifty-cent move on a dish they've ordered a hundred times. A server who can say "yeah, we bumped that one a bit this month" calmly, without apologizing, keeps the moment small. A server caught off guard turns a routine adjustment into something that suddenly needs an explanation nobody has ready.

Charm pricing and round numbers

Ending a price in ninety-five or ninety-nine cents is a habit pulled from grocery retail, and it reads differently on a restaurant menu than on a shelf tag. Full-service menus priced in whole dollars, or rounded to a clean quarter, tend to read as more considered than a menu covered in charm pricing. Counter-service and quick-casual concepts can go either way, best matched to whatever convention the rest of the menu already uses.

Whichever convention you pick, apply it across the whole menu at the same time other price changes happen. A menu with some prices ending in round dollars and others ending in ninety-five cents reads as pieced together over time, which is usually exactly what happened, worth fixing at the next reprint regardless.

What this doesn't fix

Pricing corrects for cost. It has no answer for a dish that's slow to make, hard to plate consistently, or rarely ordered in the first place. Those are menu engineering questions, usually solved by cutting or reworking the dish rather than pricing around a labor problem.

Going deeper

The full pricing playbook in KJDC membership walks through a recipe costing template you can run against your own invoices, a menu engineering matrix for spotting which dishes are worth keeping, and a script for rolling out price changes to staff so the front of house can answer questions with confidence.