Mistakes in menu engineering vs the right method
A 60-dish menu is not an offer: it's a confession that nobody has done the analysis. I have seen menus with 80 items where 70% of sales come from 12 dishes, and half of those 12 have a food cost exceeding 32%. The mistake is accumulating dishes out of fear of running short, keeping non-sellers 'just in case,' and setting prices by looking at competitors. The right method applies Masterestaurant menu engineering: each dish is a star, a cow, a question mark or a dog, and that classification decides what to promote, what to adjust and what to cut. What generates neither margin nor demand doesn't deserve a place on the menu.
The menu is a restaurant's most powerful sales tool and its most neglected one. In consulting I find menus where nobody knows the contribution margin of each dish, nobody knows which ones sell most, and the price hasn't been reviewed in years.
Did you design your menu, or did inertia dictate it? There's a huge difference between a menu that sells what suits you and one that sells what the customer happens to order.
Side-by-side comparison
| The common mistake | The right method (Masterestaurant) | |
|---|---|---|
| Menu size | ✕Huge menu without analysis: more dishes = more options = better | ✓Curated menu: each dish exists because it sells, leaves margin or both |
| Performance analysis | ✕No analysis; dishes kept 'because they've always been there' | ✓MR menu engineering matrix: star, cow, question mark, dog |
| Food cost per dish | ✕Unknown; assumed they 'all make money' | ✓Tech sheet per dish; maximum food cost 32% of selling price |
| Pricing | ✕Copied from competitors without considering own cost | ✓Price from real cost ensuring food cost ≤ 32% and positive margin |
| Menu design and psychology | ✕No price anchors, no highlighting of high-margin dishes | ✓Psychological design: anchors, star dish highlights, elimination of dog dishes |
| AI in menu | ✕No data analysis; menu decisions based on opinion | ✓AI automatically categorizes dishes by margin and popularity |
Why a 60-item menu is a profitability problem
A menu with 60 items is not a generous offering — it is a sign that no one has done the analysis. In 80% of the restaurants Diego F. Parra has audited across more than 43 countries, 70% of sales come from just 12 to 14 dishes. The rest of the menu exists out of inertia, out of fear of running short, or because a former chef requested it three years ago. Every extra item has a cost: additional waste, greater kitchen complexity, slower service times, and above all, visual confusion that disperses the customer's decision. A wide menu does not convey abundance — it conveys a lack of judgment. The first step in menu engineering is counting how many items have real sales volume and how many simply occupy space on the menu and in inventory. The most expensive mistake in menu engineering is having a high-volume dish with a food cost above 32%.
The ignored food cost error: when your best-selling dish is quietly draining you
Diego F. Parra and the Masterestaurant team detect this in nearly one out of every two restaurants during a first audit: the most frequently ordered item on the menu carries a raw material cost between 35% and 44% of its selling price. Customers choose it often because it is visually well positioned, but each sale generates less contribution margin than dishes that sell half as much. The rule is clear: food cost per dish should fall between 25% and 31% for full-service operations, with 32% as an absolute ceiling. Identifying those 'hollow stars' and redesigning their recipe or price is the fastest correction available — recovering between 3 and 6 gross margin points in fewer than 30 days. Menu engineering uses a four-quadrant matrix based on popularity and contribution margin, derived from the Kasavana and Smith model (1982) and updated for current operations. 'Stars' are high-selling dishes with a margin above 28%: protect them and place them in high-visibility zones.
Boston Matrix applied to the menu: how to classify every dish before acting
'Plowhorses' sell well but carry a margin below 24%: redesign the recipe or adjust the price by 8% to 12%. 'Puzzles' have a strong margin but low rotation: reposition them on the menu with more compelling descriptions or train the floor team to suggest them. 'Dogs' have low margin and low sales: eliminate them. Masterestaurant recommends running this analysis on at least 90 days of sales data so the sample is statistically relevant and does not reflect a one-time seasonal spike. A dog dish is not just an item that does not move — it is a hidden liability. Every dish that stays on the menu requires its ingredient to be kept in inventory, generating estimated waste of 6% to 12% of that ingredient's cost depending on product type (higher for fresh proteins, lower for dry goods). It also occupies visual real estate on the menu that could be guiding the customer toward a star dish.
The real cost of dog dishes: it is not that they do not sell — it is what they cost you
In a consulting engagement with a 4-location chain in Latin America, the Masterestaurant team identified 18 dog dishes on a 72-item menu. After eliminating them, weekly waste dropped 14%, average time-to-order fell 2.3 minutes, and average ticket rose 9% within 60 days — without changing a single price. Cutting dishes is not a risk of losing customers; it is freeing selling energy toward where real demand already exists. Where a dish appears on the menu largely determines how much it sells — this is not marketing theory but documented visual engineering. The highest-read area in a two-page menu is the upper-right corner of the right page, where the eye lands first. Dishes placed in that zone have between 15% and 27% higher odds of being ordered compared to the same dishes in the lower-left zone, according to eye-tracking studies on restaurant menus (Cornell University, 2013, replicated in real operations).
Visual design and menu architecture: the order in which dishes appear drives sales
Diego F. Parra applies this logic by placing the highest-margin dishes in prime zones and using specific descriptions — supplier name, cooking technique, ingredient origin — to increase perceived value without raising prices. The average result across Masterestaurant implementations is a ticket increase of between 15% and 30% in the first 90 days. Setting prices at opening and not reviewing them for years is one of the quietest ways to destroy profitability. If the cost of a key input rises 18% over 14 months — as happened with chicken and cooking oil across several Latin American markets between 2023 and 2024 — and the selling price does not move, margin erodes point by point without anyone noticing until the cash flow makes it undeniable. The Masterestaurant rule: review prices every quarter and adjust whenever a dish's food cost exceeds 30% sustained for more than 45 days. The adjustment does not have to be a straight price increase: it can be an 8% portion reduction, a switch to an equivalent ingredient, or a combination of both.
Pricing: the mistake of setting prices once and never revisiting them
Customers tolerate gradual adjustments of between 5% and 9% with no meaningful impact on demand, based on elasticity data documented across full-service operations. Menu engineering does not require closing or overhauling the entire menu at once. The method Diego F. Parra applies at Masterestaurant runs in four phases over a 60-day cycle. First: pull 90 days of item-level sales data and calculate the real contribution margin of each dish (selling price minus recipe cost). Second: classify every dish into the four-quadrant matrix and label stars, plowhorses, puzzles, and dogs. Third: execute changes in order of impact — cut dogs, adjust prices or recipes on plowhorses, reposition puzzles — and redesign the menu with prime zones occupied by stars. Fourth: measure the result at 30 and 60 days comparing average ticket, gross margin, and per-dish rotation. This cycle can be repeated twice a year to keep the menu aligned with real costs and actual demand.
What to expect: real numbers from operations that use menu engineering
Restaurants that implement menu engineering with rigorous methodology see measurable results in fewer than 90 days. Across documented implementations by Masterestaurant with more than 8,400 clients in 43 countries, average ticket rises between 15% and 30% without changing prices — driven purely by visual repositioning and noise elimination on the menu. Operational waste drops between 10% and 18% as the number of active ingredients decreases. Gross margin improves between 4 and 8 percentage points when out-of-range food cost dishes are corrected. And customer decision time — measured from when the menu is received to when the order is placed — falls between 1.5 and 3 minutes when menus are reduced from 72 to 28 items. The mistake Diego F. Parra sees again and again is waiting for the cash flow to hurt before running the analysis. The menu is the most direct sales tool available; working it with data is a profitability decision, not a design decision.
Why poor menu engineering is expensive
A well-designed menu using menu engineering can increase average ticket by 15–30% without raising a single price, simply by guiding the customer to the right dishes. I have seen that result replicated across +8,400 clients in 43 countries. The problem with dog dishes isn't that they don't sell: it's that they take up menu space, confuse the customer and reduce visibility for your stars. Removing them isn't risk-taking; it's freeing up sales energy.
Analysis: mistake (A) vs the right method Masterestaurant (B)
The mistakes eating your marginMistake
- Keeping a huge menu believing more options attract more customers.
- Keeping dishes that neither sell nor leave margin 'just in case'.
- Not knowing the food cost of each dish and assuming they all generate profit.
- Setting prices by looking at competitors instead of starting from real cost.
- Not using menu psychology to guide customers toward the dishes that benefit you most.
What the right method does differentlyMasterestaurant
- Curated menu with analysis: only dishes that sell, leave margin or build identity.
- Menu engineering matrix: star (sells + margin), cow (sells, low margin), question mark (margin, low sales), dog (neither sells nor leaves margin).
- Tech sheet per dish with calculated food cost: 32% ceiling of the price.
- Price set from real cost, not competition; clear contribution margin per dish.
- Menu designed with psychology: anchors, highlights and strategic positioning of star dishes.
Side-by-side comparison
| The common mistake | The right method (Masterestaurant) | |
|---|---|---|
| Menu size | ✕Huge menu without analysis: more dishes = more options = better | ✓Curated menu: each dish exists because it sells, leaves margin or both |
| Performance analysis | ✕No analysis; dishes kept 'because they've always been there' | ✓MR menu engineering matrix: star, cow, question mark, dog |
| Food cost per dish | ✕Unknown; assumed they 'all make money' | ✓Tech sheet per dish; maximum food cost 32% of selling price |
| Pricing | ✕Copied from competitors without considering own cost | ✓Price from real cost ensuring food cost ≤ 32% and positive margin |
| Menu design and psychology | ✕No price anchors, no highlighting of high-margin dishes | ✓Psychological design: anchors, star dish highlights, elimination of dog dishes |
| AI in menu | ✕No data analysis; menu decisions based on opinion | ✓AI automatically categorizes dishes by margin and popularity |
The numbers that matter
“We cut the menu from 74 to 32 dishes using Masterestaurant menu engineering. Sales went up 22% and food cost dropped 6 points. Less is more, when properly analyzed.”
How to apply menu engineering this week
For each dish you need two data points: units sold last month and contribution margin (price − food cost). From that you classify: star (high sales, good margin), cow (high sales, low margin), question mark (low sales, good margin), dog (low sales, low margin).
A dish that doesn't sell and doesn't leave margin doesn't deserve a spot on your menu. Remove it or redesign it. If it has emotional value for the owner, that's not a valid commercial argument.
If a dish sells well but margin is low (food cost >32%), you have two options: raise the price or reduce the cost. There's no third acceptable option: keeping it as-is means subsidizing it with your stars' margins.
Place star dishes in the highest visual-attention positions. Use price anchors (an expensive dish next to the one you want to sell makes it look accessible). The menu is a sales tool, not a catalogue list.
And with AI?
Optimize menu engineering, descriptions and the photos that sell most. Diego F. Parra is an expert in AI applied to restaurants.
Free tools to apply this now
Do it with Masterestaurant tools
The standard recipe and costing course are the starting points for menu engineering with real data, not intuition.
Frequently asked questions about menu engineering
What is menu engineering and what is it for?
How many dishes should my menu have?
Is it risky to remove dishes from the menu?
How do I know if my dish prices are right?
Sector data 2026 (official sources)
Verifiable industry benchmarks from official, non-commercial sources (government, industry associations, market research) - not competitors.
| Metric | Benchmark 2026 | Source |
|---|---|---|
| Índice de precios de alimentos | referencia oficial de food cost | USDA |
| Off-premise | ~75% del tráfico | Circana |
| Food cost por concepto | QSR 25–30% · casual 30–34% · fine dining 34–40% | National Restaurant Association |
| Ticket online alto | 34% de clientes gasta ≥$50 por pedido | Statista |
Related content
Turn your menu into a margin machine
The Masterestaurant method turns every dish on your menu into a strategic decision backed by real data. Stop guessing what to sell and start designing your menu to win.
By