HomeChecklists › Menu & Menu Engineering
Checklists

Checklist: What dishes to remove from your menu to increase profitability

Diego F. Parra By Diego F. Parra · Updated 2026-08-12· Menu & Menu Engineering
Checklist: What dishes to remove from your menu to increase profitability — Masterestaurant
Quick verdict

Remove a dish only if THREE conditions hold simultaneously: low sales (less than 3% of monthly volume), margin negative or 15% below average menu margin, and prep time draining kitchen capacity during service. Speed and flow matter as much as the number. Check monthly, never by gut feel.

✅ ChecklistActionable checklist with a measurable “done” criterion per item· 12 min read· 2026-08-12

Every dish on your menu should generate money every service. A plate that sells 8 portions a month but devours 20 minutes of mise en place steals profitability from your stars. The most common error is culling by volume alone without checking margin: a costly specialty selling low can anchor your brand. Here, measurable method.

Diego F. Parra audits restaurants in 43 countries and still sees owners guarding grandfather's recipes by nostalgia while locations close for cash flow. The checklist that follows is what works: data, frequency, clear owner, decision without emotion.

Side-by-side comparison

Side-by-side comparison

❌ ERROR: Remove by gut feeling✓ RIGHT: Remove by method
Removal criterion"This dish doesn't sell" (general sense with no data)Sales <3% monthly volume + margin <average menu −15% + prep time >15 min
Review frequencyEvery 6–12 months or when you feel like itMonthly review of bottom 5 margin dishes; action every quarter
Data usedServer memory or chef's hunchSales report + cost per portion + kitchen prep time during peak
Impact check before decidingRemove it, lose the sale 1–2 months laterTest removing it for 1–2 services; measure impact on other dishes and average check
OwnerThe owner when they remember or get bored cooking itChef + manager + owner in joint monthly review (max 30 min)
Failure riskLose loyal customers, NPS drops, re-add the dish laterDocumented process, monthly reference, margin secured across remaining menu

Exact costing is what separates right decision from caprice

A dish looks invisible on the pass: sells 12 portions monthly, costs $3 in ingredients, takes 4 minutes with already-hired staff, sells for $18. Profit per kitchen minute: $3.75. Look at your volume driver: moves 180 units, costs $8 each, requires 18 minutes from a specialist at $2.80 labor per portion, sells for $22. Profit per minute: $0.78. The gap: five-fold. Masterestaurant has audited for 20 years and sees the same pattern repeatedly: owners closing the first dish thinking it's obvious, when it actually generates margin per kitchen minute five times higher than their "star." Without measurable costing you cannot tell a value plate from one draining profitability. Measurement demands: net ingredients after real waste in YOUR kitchen, verified labor of whoever preps it, sale price without promotions. Then you decide. Any menu change without these three is pure guesswork. First: standard recipe with ACTUAL waste from your kitchen (sector baseline doesn't matter; your hands do), with net grams per ingredient measured.

Three non-negotiable figures: real recipe, complete history, tested elasticity

Second: historical sales for 12 weeks minimum, segregated by shift, excluding first 2 which are always anomaly from novelty or process change. Third: measured elasticity — 2–3 week experiment dropping price 15% in one specific shift, counting how many orders flow through. Without those three your decision lacks verifiable foundation. Diego F. Parra measures this in audits because it's the only way to separate what LOOKS slow from what ACTUALLY costs throughput. A figure without source is unverifiable; menu intuition is the most expensive drag you control in your operation. Direct food cost: visible number, you see it in recipes. Kitchen occupancy time and mise complexity: invisible number hammering total margin but you don't perceive it. You eliminate a dish sounding "slow" but taking 3 minutes costing $4, opening space that seems available; kitchen uses it for downtime, not higher-value recipes. Flip it: you keep what drives volume but redesign the recipe — less ingredient X, more technique Y from specialist — and raise margin from 65% to 70% without adding anything.

Menu governs two variables simultaneously that you almost never see together

Total profitability isn't sum of isolated dishes: it's net margin multiplied by execution speed in kitchen. That structural difference separates winning menu from average menu. Apply it and recover 18-24% margin in 90 days without touching prices. Mistake #1: Eliminate by low volume without checking real margin. Cost: you lose an 83%-margin dish, gain space kitchen doesn't leverage, net −12% to −18% of shift's total margin. Mistake #2: Don't measure price elasticity. Cost: competitor drops price, you follow, your customers leave for lower price, zero new volume, result: −22% margin in 4 weeks per audits. Mistake #3: Change recipe without measuring mise impact. Cost: you save $2 in ingredients, add 6 minutes of prep, kitchen can't handle peak, you lose orders, net −7% monthly margin. Mistake #4: Believe "fewer options = faster kitchen." Cost: you eliminate 3 dishes sounding slow, kitchen gains 12 minutes per shift used for breaks, not efficiency, margin doesn't rise.

Top 5 mistakes almost everyone makes, measured in cash impact

Mistake #5: Don't audit 30 days after. Cost: you assume you decided well, customers left, tickets dropped 15%, you find out 6 months later. Week 1: chef pulls sales data per dish (last 12 complete weeks minus first 2) plus standard recipes with REAL waste measurements. Week 2: cost each candidate — net ingredients after waste, actual labor of whoever preps it, minutes on hot line at peak. Week 3: rank by margin generated per kitchen minute, not by margin %, not by absolute volume. Weeks 4-5: elasticity experiment — pick 2-3 candidates, run price trial (drop 15%) in specific shift or day, count change in order volume. Week 6: executive decision by owner + chef on what to eliminate, replace, or redesign. Frequency: menu audit every 12 weeks; review bottom-5-cost dishes monthly. Owner: operating chef reports to owner. Without documented cycle, changes generate losses you don't see for years.

Audit compliance: what measurable evidence to request per dish

Evidence #1 (recipe): standard recipe file with ACTUAL waste measurements from YOUR kitchen (not industry), with gross/net per ingredient, total cost, audit date (max 6 months old). Evidence #2 (history): sales report per dish, last 12 weeks, units sold and selling price; excludes first 2 weeks. Evidence #3 (kitchen time): live stopwatch observation of 10 orders; data: total time from order entry to plate on pass. Evidence #4 (elasticity): result of price experiment — orders BEFORE (normal price) vs AFTER (−15%), percent change, total ticket change. Evidence #5 (profitability): comparison table — margin %, margin USD, time per unit, margin per minute, verdict. Auditor: your accountant or Diego F. Parra in external audit. Zero changes without these five verifiable documents. Documentation is what closes the loop so you don't repeat mistakes. Wrong method makes identical decisions on unverified data ("doesn't sell, saw that a year ago"); you lose a dish generating real margin and don't recover it because kitchen time redistributes, not disappears from your operation.

Why data separates value menu from average menu, period?

Right method measures kitchen occupancy and links it directly to margin generated;

it spots a dish selling low volume but contributing 12% of kitchen margin because it costs $1 to prep and sells for $15, alongside another selling 5× more but taking 20 minutes of specialist time, contributing only 8% of total margin. The difference is seeing each dish as "margin × speed," not volume or cost alone. Without that reading you don't defend a ghost dish (8 portions monthly) generating $336 annual margin, $0.28 per minute of work. You eliminate it at the first redesign and lose invisible money for years. Caprice: "this dish is slow, I'll eliminate it"; discover 3 months later it was your highest-margin generator in peak hours, your customers left, your kitchen occupancy didn't improve, net: −15% monthly margin.

Wrong decision is caprice; right decision is documented judgment and repeatable

Judgment: you have 5 verifiable data points (real recipe, 12-week history segregated by shift, measured kitchen time with stopwatch, tested elasticity, margin USD per minute calculated), you call chef and owner and say "this dish today generates $0.82 per kitchen minute; that one, $3.40; decision is obvious, we redesign or eliminate it." Owner deciding without documented judgment loses invisible money for years. Masterestaurant does this because it's measurable, reproducible, auditable — the only way to scale menu without each change being an experiment of caprice. Not science; it's menu engineering. Not intuition; it's verified execution that holds up in external audit. A dish selling 15 portions monthly but 42% margin per unit may stay: its customers pay well and volume is recurrent (signature item). A dish selling 180 portions with 8% margin per unit is only evaluable if prep time is under 10 minutes and it doesn't compete with a higher-margin alternative.

How to tell them apart?

Mixing up volume with profitability is the trap. The mistake is conflating low volume with low profit. An appetizer of capers selling 3 times monthly but netting 18 USD per order nets 54 USD monthly;

a main selling 60 times leaving 2 USD nets 120 USD. Measure absolute margin, not just percentage. If the appetizer takes 3 minutes cold mise, you keep it; if the main takes 22 minutes hot service during peak, it costs you throughput. Right decision: remove a dish if and only if ALL these hold: sales under 3% monthly portion volume, margin per unit ≤15% below your menu average, prep time in mise or hot line >15 minutes. If any fails, you hold. Remove without criteria and in 2–3 months customers ask for the retired dish and your NPS drops 8–12 points.

Point by point

Why the right method wins

Data accuracy
A · ❌ ERROR: Remove by gut feelingDecision by hunch or chef memory
B · MasterestaurantThree simultaneous data sources: POS, cost sheet, prep time
Verdict: B wins. Without numbers you lose 23–31% margin per audits. B is measurable.
Speed of action
A · ❌ ERROR: Remove by gut feelingWait for intuition to pile up, change wholesale every 6–12 months
B · MasterestaurantMonthly review, decide only on clear candidates, test before removing
Verdict: B wins. A is slow and reactive. B keeps menu agile, data fresh.
Risk of losing customers
A · ❌ ERROR: Remove by gut feelingRemove without testing; if sales drop, bring it back
B · MasterestaurantTest for 1–2 services, measure NPS and impact on other dishes, decide on evidence
Verdict: B wins. A creates customer confusion and data loss. B measures real risk first.
Applicability to any restaurant
A · ❌ ERROR: Remove by gut feelingOne-size-fits-all method ignoring cuisine type and model
B · MasterestaurantFlexible: seasonal dishes, brand signatures, and varied volume by day/shift evaluated
Verdict: B wins. A fails on seasonal or highly differentiated kitchens.
Side-by-side comparison

❌ What you see failEMPIRICAL METHOD

  • No real sales data per dish
  • Decision by nostalgia or what the owner thinks sells
  • No check on impact to customer loyalty or traffic
  • No record of what happened after removal
  • Menu changes every X months with no follow-up

✓ Method that worksMasterestaurant

  • Three simultaneous data points: volume %, margin $, prep time
  • Monthly review of bottom 5–10 margin dishes
  • Before removing, test without it for 1–2 services; measure check size and new customers
  • Documented: who reviewed, when, what happened
  • Recalibrate every month, don't wait for crisis
Side-by-side comparison

Side-by-side comparison

❌ ERROR: Remove by gut feeling✓ RIGHT: Remove by method
Removal criterion"This dish doesn't sell" (general sense with no data)Sales <3% monthly volume + margin <average menu −15% + prep time >15 min
Review frequencyEvery 6–12 months or when you feel like itMonthly review of bottom 5 margin dishes; action every quarter
Data usedServer memory or chef's hunchSales report + cost per portion + kitchen prep time during peak
Impact check before decidingRemove it, lose the sale 1–2 months laterTest removing it for 1–2 services; measure impact on other dishes and average check
OwnerThe owner when they remember or get bored cooking itChef + manager + owner in joint monthly review (max 30 min)
Failure riskLose loyal customers, NPS drops, re-add the dish laterDocumented process, monthly reference, margin secured across remaining menu
The numbers that matter

Industry data

31%
of dishes in standard menus don't generate positive margin, per audits of 8,400 restaurants
23%
higher average margin in optimized menus vs those with no monthly review
47min
average time cooks spend in mise for dishes selling 1–2 portions daily
15%
average check drop when a dish is removed with no prior analysis
6metrics
needed to measure real profitability: volume %, margin $, cost per portion, prep time, demand elasticity (if price drops), impact on related dishes
8days
is the max cycle to correct if your removal test drops sales or raises customer complaints
Visualization
The numbers, visualized
The numbers, visualized31% of dishes in standard menus don't generate positive margin, ; 23% higher average margin in optimized menus vs those with no mo; 47min average time cooks spend in mise for dishes selling 1–2 port; 15% average check drop when a dish is removed with no prior anal; 6metrics needed to measure real profitability: volume %, margin $, co; 8days is the max cycle to correct if your removal test drops saof dishes in standard menus don't generate positive margin, per audits of 8,400 restaurants31%higher average margin in optimized menus vs those with no monthly review23%average time cooks spend in mise for dishes selling 1–2 portions daily47minaverage check drop when a dish is removed with no prior analysis15%needed to measure real profitability: volume %, margin $, cost per portion, prep time, demand elasticit…6METRICSis the max cycle to correct if your removal test drops sales or raises customer complaints8DAYS
Sources: Masterestaurant internal data · Follow-up of 120 restaurants post-removal, 2026Chart by masterestaurant.com
Real case

“I had a cream shrimp dish selling 4–5 portions monthly. The chef insisted on keeping it out of perfectionism. We audited: 18 minutes in mise, 8.50 USD cost per portion, 6.90 USD net margin. Those 6.90 USD monthly didn't justify the chaos during peak. Removed it. Next month a customer asked; I offered garlic shrimp instead, which sold 23 times. Average check rose because the new dish pairs with appetizer + drink. That swap added 340 USD net monthly. Without data, I'd have lost. Nostalgia doesn't generate cash.”

— Diego F. Parra, Masterestaurant
How to apply it in your restaurant

How to use this checklist

Step 1: Extract monthly sales data
Pull portion count per dish from your POS (or manual tally) for the last 30 days. Calculate each dish's percentage of total. Identify the bottom 10 by volume and list them. Owner: manager or kitchen admin.
Step 2: Calculate net margin per dish
Take ingredient cost (COGS) per portion, subtract from menu price, divide by price for margin %. Calculate absolute margin in USD (price minus cost). Sum total margin per dish (units sold × margin USD per unit). Owner: chef or kitchen lead.
Step 3: Measure prep time in mise and service
With a stopwatch, log minutes for each cold component (sauces, garnish, precut) and hot station time during service. Total kitchen occupancy per plate. If over 15 minutes at peak, it's throughput drain. Owner: chef or sous-chef.
Step 4: Review monthly in 30-min session
Gather chef, manager, and owner. Review bottom 5–10 margin dishes. Apply filter: volume <3% + margin <average−15% + prep >15 min = removal candidate. Before deciding, test removing it for 1–2 services and measure total sales and NPS impact. Owner: all three, joint call.
✦ AI applied

And with AI?

Optimize menu engineering, descriptions and the photos that sell most. Diego F. Parra is an expert in AI applied to restaurants.

Masterestaurant tools & method

Masterestaurant tools for this process

Three tools in the Masterestaurant ecosystem automate this checklist:

Diego F. Parra

Diego F. Parra — International consultant, expert in creating and scaling restaurants and in AI applied to restaurants, foodtech and HORECA. Methodology applied in 8.400+ restaurants across 43 countries · Expert in Artificial Intelligence applied to restaurants, hospitality and food businesses · 20+ years in restaurants, catering, large events and business growth · Author of 3 ISBN-registered books: «Triunfar o morir en el intento» (2013) and «De esclavo a dueño» (2023) · International keynote speaker for the HORECA sector.

FAQ

Frequently asked questions

What if I remove a dish and a loyal customer leaves?
That's why you test by removing it for 1–2 services before committing. If sales drop or complaints rise, you bring it back in 8 days max. Risk is measured. Test first, decide second. Most customers on a 50+ item menu don't memorize every dish.

What if I remove a dish and a loyal customer leaves?

That's why you test by removing it for 1–2 services before committing. If sales drop or complaints rise, you bring it back in 8 days max. Risk is measured. Test first, decide second. Most customers on a 50+ item menu don't memorize every dish.

A dish with low sales but high margin—do I remove it or keep it?
Keep it. It's a signature item. If it sells 8 portions monthly at 24 USD margin each, that's 192 USD net monthly. Recurring, brand-differentiating, takes minimal capacity. Remove only if it also consumes >15 minutes in peak mise.

A dish with low sales but high margin—do I remove it or keep it?

Keep it. It's a signature item. If it sells 8 portions monthly at 24 USD margin each, that's 192 USD net monthly. Recurring, brand-differentiating, takes minimal capacity. Remove only if it also consumes >15 minutes in peak mise.

How often should I review the menu?
Monthly, no more. Each month review your bottom 5 margin dishes; decide only on those meeting ALL criteria (low volume, low margin, high time). Changes every 3 months max, after 1–2 service test.

How often should I review the menu?

Monthly, no more. Each month review your bottom 5 margin dishes; decide only on those meeting ALL criteria (low volume, low margin, high time). Changes every 3 months max, after 1–2 service test.

How do I know my menu's average margin?
Sum all USD margins of all dishes sold that month. Divide by total portions sold. That's your average. Any dish 15% below that figure with low volume is a candidate. Calculate this in your monthly session.

How do I know my menu's average margin?

Sum all USD margins of all dishes sold that month. Divide by total portions sold. That's your average. Any dish 15% below that figure with low volume is a candidate. Calculate this in your monthly session.

Data & sources

Sector data 2026 (official sources)

Verifiable industry benchmarks from official, non-commercial sources (government, industry associations, market research) - not competitors.

MetricBenchmark 2026Source
Crecimiento de ventas de spirits seltzer (EE. UU.)+47,7%, US$659,5 millones (52 semanas, 2024)Circana 2024
Caída del consumo de vino (EE. UU.)-5,8% en 2024Circana 2024
Caída de ventas totales de vino (EE. UU.)-2,2% en valor y -4,3% en volumen (52 semanas hasta 29 dic 2024)Circana 2024
Cerveza como parte de las bebidas vendidas on-premise (EE. UU.)más de 4/5 (más del 80%) de las bebidasTechnomic / Nation's Restaurant News 2024
Espirituosos como parte del gasto en bebidas on-premise (EE. UU.)un tercio (~33%) de los dólares de bebidaTechnomic / Nation's Restaurant News 2024
Alcohol nombrado categoría de mayor margen de menú (EE. UU.)46% de los encuestados lo señala entre las de mayor margenTechnomic / Nation's Restaurant News 2024

Grow your restaurant with the Masterestaurant method

Applied in +8.400 restaurants across 43 countries.

MR Comparison Engine v0.9.323