Menu simplification and SKU reduction: how to choose which dishes to cut without losing customers

1. Why the editorial criterion for this list is demand elasticity, not turnover

When a manager decides his menu has too many dishes, the instinct is always the same: count which one sells least and cut it. It turns out that's the most expensive way to make a mistake in a small restaurant. I've spent fifteen years measuring which dishes actually make money, and again and again I find that the plate selling eight servings a month — seemingly a dead item — generates 44% net margin because it sells for USD 28 with a food cost of USD 7. Meanwhile, the one selling 120 servings monthly generates just 18% margin because it sells for USD 12 and costs USD 8 to make. When we kill the first one for being low volume, we lose USD 93 annually in gross contribution, and that money never comes back. The right criterion isn't turnover. It's net margin per plate, real demand elasticity — what happens if you raise the price 15% — and stolen prep time from the kitchen.

1. Why the editorial criterion for this list is demand elasticity, not turnover — in practice

That's the list that follows. It sounds contradictory, but the plate that sells little but earns plenty is often the most valuable on your menu. A good sirloin with mise-en-place reductions might cost USD 10 in ingredients and sell for USD 38, generating USD 28 contribution — nearly 74% margin on price. Even selling only 12 servings monthly, that totals USD 336 toward break-even. The Masterestaurant rule is to keep every plate exceeding 35% net margin as long as demand elasticity is below −1.2 — meaning it won't lose more than 20% of sales if you raise price 15% (this is measured in live operation; it requires minimum three-week price testing). If the plate falls below 35% margin OR elasticity exceeds −1.5, it enters analysis territory: maybe you keep it because it retains a regular customer, maybe you reformat it — size, sides — to recover margin, maybe you kill it without sentiment.

3. Plates in the red zone: margin <12% and rotation <3 times monthly

Here is where most restaurants leak money and keep printing menus with those dishes included. A plate selling 40 servings monthly at USD 14, with food cost USD 11, generates just USD 120 monthly contribution — USD 1,440 annually — and eats all the prep time that could go to higher-margin plates. Masterestaurant classifies this as red zone: net margin under 12% on price and rotation below three times monthly. In that zone live the dishes a restaurant makes because 'they've always been there,' not because they make money. The analysis is clear: either raise margin without losing clientele — by cutting food cost or raising price — or replace it entirely. Keeping it for the sake of keeping it is as bad as not measuring at all: you're spending equipment, chef time, and menu space on a dish barely paying its electricity. A plate can seem barely profitable in isolation and turn out to be the key to selling two other items.

4. The cross-sell that nobody measures: what sells after each dish

The traditional method counts servings sold: if it's low, it dies. The Masterestaurant method cross-references the data with cross-selling — which customers who ordered that plate we then suggested something pricier to, and what percentage bought it. A shrimp appetizer at USD 12 with 22% margin looks ordinary. But if 67% of those who order it then buy a second plate, and that plate averages USD 28 with 58% margin, then that appetizer generates USD 28 in indirect contribution that never shows on its own line. Knowing this requires two things restaurants don't do: first, line-by-line ordering logs by server — what each diner ordered in sequence — and second, lifetime value calculation per appetizer type. If your 'low-margin' appetizer is what attracts the customer who spends USD 120 on a bottle, that appetizer isn't a problem. It's a magnet. Most managers don't time their kitchen by station and by dish, so when they say 'cutting the menu wouldn't save us anything,' they're guessing.

5. Stolen prep time: the number that changes the verdict on a dish

I measure this in audits: there are plates that look profitable and eat 18 minutes of mise en place — peeling, cutting, emulsifying — when rational would be 6 minutes. If that plate sells 15 servings monthly, it consumes 270 minutes monthly — 4.5 hours — just in prep. Multiply that by 12 months and it's 54 hours annually of chef time on a plate contributing USD 240 in margin. At USD 22 per hour (chef's total cost), that's USD 1,188 in time cost: meaning the plate isn't profitable; it's a hole. Cutting the menu isn't random deletion. It's identifying real prep time per plate — a task requiring a stopwatch, weekly logging, and 12-week averaging — then calculating net return: plate profit minus its prep-time cost. When a plate has to go — red zone confirmed — the most expensive execution is telling the customer 'we don't have it anymore.' It's better if a regular exists, a house friend or partner who orders it by tradition.

6. The trauma-free retirement method: format change, not amputation

The Masterestaurant method doesn't kill dishes. It replaces them. If that low-rotation, high-margin sirloin loses clientele because it's pricey, reimagine it as a 'cut of the week' where price can vary, or as an 80-gram appetizer instead of 200. If the red-zone dish is a cream pasta consuming 12 minutes at station and selling only 8 servings, change the sauce — to one needing no cooking, that mounts in seconds — or retire it for just three months, announce 'we're in recipe maintenance,' and when it returns, it returns redesigned. This costs a team conversation and one menu line; brutal deletion by simply removing it costs a customer who walks to the competitor because 'they don't make my dish here anymore.' Here's the invisible risk owners don't see until it's late. When you reduce your menu from 68 dishes to 28, it sounds like executive logic: fewer SKU, more efficiency.

7. Average ticket drops when you cut menu without substitution strategy

Turns out it also means fewer road dishes on the menu — those plates diners ordered 'because they were there' and generate USD 8 of pure margin. If those low-margin, high-volume dishes vanish without a substitution plan, the customer enters with no appetite to try something new at similar price, and ends up ordering cheaper than before. The Masterestaurant method compensates with 'suggested selling by station': train servers to suggest a high-margin complement after each main — spiced bread, a citrus sorbet, fresh cheese. That's not forced upsell; it's recovering the ticket that the reduced menu left on the table. The typical number: well-planned reduction leaves ticket 8-12% lower in month one. With the suggested-selling protocol, that deficit recovers by month two and ticket ends 4-6% higher than baseline. If you have the mental and time budget for just one menu change, don't reduce everything.

8. The verdict: what to kill first if you can only make one change

Hit the maximum-return point: identify your red-zone plates — net margin <12%, rotation <3 times/month, prep time >10 minutes — and kill them outright. That frees you 6 to 12 hours of kitchen time weekly depending on how many you cut, time you can redirect to higher-quality mise en place on winning plates, to server training in upselling, or to testing new high-margin recipes. Don't touch high-margin plates even if they sell little; don't touch low-margin ones if they generate cross-sells or retain a regular. What you kill is what eats time without generating revenue — that's pure math, and that's the lever Masterestaurant pulls first. Do it right and in 90 days you'll see average ticket rise 3-8%, operating margin grow 2-4 percentage points, and the kitchen report for the first time there's no 'bottleneck' at lunch service.

Core difference

Traditional method: cuts by volume. Kills high-margin low-volume dishes. Risk: loses standing customers. Masterestaurant method: cuts by net margin + demand elasticity. Retains high-margin dishes even if volume drops. Makes money on EVERY cover. Traditional method: doesn't measure real prep time; discovers savings by chance. Kitchen stays just as saturated because *processes* don't change, only items. Masterestaurant method: times each station and dish; knows 8 hours freed = one less chef OR predictable shift + house-made dessert daily. Traditional method: menu shorter but no cross-sell strategy. Average check drops 8-12%. Masterestaurant method: menu retains "strong" items; suggested sale lifts check 18-26%. Example: 60 covers × $42 ticket = $2,520 → 58 covers × $52 ticket = $3,016.