Menu engineering is the discipline of deciding what stays on your menu, what gets repriced, what gets repositioned, and what gets cut — using two numbers for every dish instead of instinct. The two numbers are how much money the dish makes when it sells, and how often it sells. Plot every item against both and the menu stops being a list of food and becomes a portfolio you can manage.
The framework was first formalized by Kasavana and Smith at the Cornell School of Hotel Administration in 1982. The fundamentals have not changed since. What has changed is how fast the inputs move and how cheap they are to assemble — which is why the same analysis a property once commissioned once a year now belongs in a weekly cadence. This guide covers the whole thing: the two inputs, the math, the four-quadrant matrix, the mistakes that quietly cost margin, and how the discipline differs inside a hotel.
The two questions every dish has to answer
Every item on your menu is answering two independent questions, whether or not anyone is reading the answers.
How much does it make? Not what it costs, and not what it sells for — what it contributes. The honest figure is contribution margin: the menu price minus the cost of the ingredients that go on the plate. A dish that sells for €18 against a €6 plate cost contributes €12. One that sells for €26 against a €15 plate cost contributes €11. The €26 dish looks more premium and earns less per cover. Price is a vanity number; contribution margin is the one that pays the rent.
How often does it sell? This is popularity, measured as the item’s share of sales within its category — its sales mix. A starter that accounts for one in three starter orders is carrying its section. One that accounts for one in forty is occupying a line on the menu and a slot in the kitchen for almost nothing in return.
Hold those two questions in your head and a menu you thought you knew starts to look different. The dish everyone praises may be the one quietly dragging the section down. The dish nobody mentions may be the one paying for the others.
How to calculate it
You need two things, and a modern POS already has both.
Contribution margin per item. Take the menu price, subtract the plated food cost (the costed recipe — every ingredient at its current purchase price, in the portion you actually serve). What remains is the contribution margin. Do it for every item in a category so they are comparable.
Popularity per item. Count how many of each item sold over the period, then express it as a percentage of the category total. If your eight starters sold 1,000 plates between them last month, an item that sold 250 has a 25% menu share within starters.
The last step is to set the two thresholds that split the menu into quadrants. For popularity, the conventional line is a menu-share benchmark: if items were ordered evenly, each of N items in a category would take a 1/N share, and the standard practice is to treat roughly 70% of that even share as the cut-off between “popular” and “not.” For contribution margin, the line is usually the category’s average contribution margin. Above the line on each axis is “high”; below is “low.” Two axes, four boxes.
This is arithmetic, not a model. There is no forecast and nothing to believe — just price, recipe cost, and a sales count you already have. That is the point: it is a measurement, and a measurement can be checked.
The four quadrants
Crossing the two axes — high or low contribution margin, high or low popularity — gives the four-quadrant menu engineering matrix and four kinds of dish.
Stars — high margin, high popularity. These earn well and sell well. They are the menu’s identity. Protect them: keep the recipe and the portion stable, hold the position on the page, and resist the temptation to discount them. Your job with a Star is to not break it.
Plowhorses — low margin, high popularity. The crowd-pleasers that everyone orders and that barely pay. A Plowhorse is the most dangerous item on most menus precisely because it is loved — popularity hides the leak. The moves are surgical: a modest price increase the guest will not notice, a small portion or garnish adjustment, a cheaper component that does not change the experience, or a deliberate menu layout that nudges some of that demand toward a higher-margin neighbour.
Puzzles — high margin, low popularity. Profitable when they sell, but they don’t sell. The margin says keep them; the volume says nobody is finding them. Before you cut a Puzzle, ask why it is invisible: a flat name, a buried position, a price that reads as a risk, a description that doesn’t sell the dish. A repositioned Puzzle can become a Star. A Puzzle you give up on is a Dog.
Dogs — low margin, low popularity. They neither earn nor sell. The default is to remove them — but not blindly. A Dog can be a deliberate anchor (a high price that makes the dish beside it look reasonable), a signature the kitchen is known for, or a dietary necessity that keeps a table. If it is none of those, it is complexity you are paying to carry, and it should go.
The matrix is not a verdict; it is a starting question for each dish. The work is deciding which of the available moves fits — and that is where judgement, not arithmetic, takes over.
Where most menu engineering goes wrong
The framework is simple. The ways it fails in practice are consistent.
Confusing popularity with profit. The single most common error. The best-selling dish gets protected on instinct, and if it is a Plowhorse, every cover is a small loss you are defending. Popularity is not profit, and the two have to be looked at together or not at all.
Running it once a year. A menu reviewed annually is a snapshot of a market that has already moved on. Costs drift, your comp set repositions, and guest habits compound between reviews. By the time the bound report reaches the meeting, the dish it flagged in April has leaked margin every week since. The inputs refresh in your POS within a day; the analysis should keep that pace. (We make the longer version of this argument in why menu engineering belongs in a weekly cadence.)
Ignoring the market. A dish’s margin is set in your kitchen, but whether your price holds is decided in your market. If you never look at what comparable restaurants nearby are charging and changing, you are engineering the menu in a vacuum. The comp set is half the picture.
Acting on too much at once. A full matrix produces dozens of possible moves, and a menu rebuilt all at once teaches you nothing about what worked. A short, ordered list of changes — a few each cycle — is both easier to execute and possible to learn from.
Menu engineering for hotel F&B
Inside a hotel, the discipline is the same but the terrain is harder, and most properties run it worse than a standalone restaurant would.
The rooms side of a hotel reprices constantly — revenue management watches the market and adjusts daily. The F&B side, sitting in the same building, often reviews its menus twice a year. The same commercial rigour the rooms team takes for granted is rarely applied to the restaurant, the bar, the banquet menu, or room service — even though those outlets all share one bottom line.
Hotel F&B also multiplies the surface area. There isn’t one menu; there are several, across outlets with different cost structures, different covers, and different roles. The same burger is priced and costed separately in the brasserie, the bar, and room service, often with no common view of which version is actually working. Banqueting adds a contract-pricing layer that rarely meets the same scrutiny as à la carte.
The opportunity is exactly that gap. Applying ordinary menu engineering — contribution margin and popularity, per item, per outlet, on a tight cadence — to a hotel’s F&B is often the most under-managed margin in the building. It is the discipline the rooms team already lives by, pointed at the food.
From analysis to action
Menu engineering is only worth doing if it changes the menu. The throughline from numbers to decisions is short:
- Measure every item’s contribution margin and popularity from your real POS and recipe costs.
- Classify each into Star, Plowhorse, Puzzle, or Dog against the category thresholds.
- Prioritise a small number of moves — the few with the most margin behind them — rather than a wholesale rebuild.
- Act, then re-measure on the next cycle so you can see whether the move worked.
That loop is the entire job, and the cadence is what makes it diagnostic rather than archaeological. The structured version of how we run it — the layers of analysis, the classifications, the tier and role context, and the critic pass that checks it — is written up in full on our methodology page, and the Performance and Market views are where the measurement and the comp set live.
Where to go next
Go deeper on each part of the framework:
- The four quadrants in depth: the menu engineering matrix explained.
- The number to manage the menu by: contribution margin vs food cost percentage.
- The most common trap: your best-selling dish might be hurting your margin.
- How often to act: how often should a restaurant change its menu prices? and why menu engineering belongs in a weekly discipline.
- The wider picture: restaurant profit margins — what’s normal and what moves them and menu psychology: design that sells.
And to see it applied:
- Try it on your own dishes: the free Menu Profitability Calculator — enter price, cost, and units sold and see each dish’s quadrant instantly.
- A real, anonymized sample Verdict — one restaurant’s menu engineering and F&B performance audit, figures as measured.
- The glossary defines contribution margin, the four classifications, RevPASH, comp set, and the rest of the terms used here.
Menu engineering is not a once-a-year project or a software feature. It is a habit: two honest numbers for every dish, read often enough to act on while the answer is still true.