Most restaurants treat menu engineering like a yearly checkup when it should be monthly medicine. Your menu shifts constantly—seasons change, suppliers raise prices, and customers develop new preferences. Making menu engineering a standing agenda item keeps you ahead of dishes that quietly drain your profits.
What is menu engineering as a management tool?
Menu engineering breaks down each dish using two metrics: popularity and profitability. Monthly analysis catches trends before they hurt your bottom line. That profitable salmon from March? It might be bleeding money in April after your seafood supplier's price hike.
💡 Example:
Bistro De Eik reviews their 12 main courses monthly:
- Steak: 35% of sales, 42% profit margin → STAR
- Salmon: 8% of sales, 45% profit margin → PUZZLE
- Pasta: 25% of sales, 22% profit margin → PLOWHORSE
- Risotto: 5% of sales, 18% profit margin → DOG
Action: Remove risotto from menu, promote salmon more.
The 4 quadrants of menu engineering
Every dish lands in one of four buckets:
- Stars: Popular + profitable → Keep and promote
- Plowhorses: Popular + low profit → Lower cost or raise price
- Puzzles: Unpopular + profitable → Improve marketing or menu position
- Dogs: Unpopular + low profit → Remove from menu
Collecting monthly data
You'll need three data points for solid analysis:
- Sales numbers per dish (from your POS system)
- Current cost per dish (including recent price changes)
- Selling price per dish (excl. VAT for accurate margin calculation)
⚠️ Watch out:
Many restaurants forget to update dish costs after supplier increases. This creates phantom profits—the kind of thing you only learn after closing your first month at a loss.
Calculating popularity and profitability
Start by finding your averages:
- Average popularity: 100% ÷ number of dishes
- Average profit margin: Sum of all margins ÷ number of dishes
💡 Example calculation:
Restaurant with 10 main courses:
- Average popularity: 100% ÷ 10 = 10%
- Dishes above 10% = popular
- Average margin: 32%
- Dishes above 32% = profitable
Action items per quadrant
Each category needs different treatment:
- Protect stars: Monitor ingredient quality, avoid frequent changes
- Fix plowhorses: Reduce portion size, swap expensive ingredients, or increase price
- Push puzzles: Better menu placement, server training, feature as daily special
- Drop dogs: Replace with new dishes or remove entirely
Integration into management meeting
Schedule menu engineering as a permanent monthly agenda item. Review each dish systematically:
- Which quadrant is it in now?
- Has it shifted since last month?
- What's our action plan this month?
- Who owns the execution?
💡 Real-world example:
Restaurant Lotus meets every first Monday:
- "Prawns dropped from Star to Plowhorse—shrimp costs jumped 40%"
- "Action: Source new supplier or bump price from €28 to €32"
- "Owner: Sous chef, deadline: before next menu printing"
Digital support
Manual calculations eat up valuable time. Tools like KitchenNmbrs streamline menu engineering through:
- Automatic cost updates when supplier prices shift
- Direct connection between recipes and current margins
- Clear reports per dish
How do you integrate menu engineering into your management meeting?
Collect monthly sales and cost data
Pull the number of portions sold per dish from your POS system. At the same time, update all ingredient prices with recent supplier invoices. Calculate the current cost per dish including all ingredients, garnishes, and sauces.
Place each dish in the right category
Calculate average popularity (100% ÷ number of dishes) and average profit margin. Divide all dishes across the four quadrants: Stars (popular + profitable), Plowhorses (popular + unprofitable), Puzzles (unpopular + profitable), Dogs (unpopular + unprofitable).
Determine concrete actions per dish
Discuss per quadrant what action you'll take: keep Stars, lower cost or raise price for Plowhorses, promote Puzzles more, remove Dogs from menu. Assign a responsible person for each action with a clear deadline.
✨ Pro tip
Focus your first 3 months on analyzing just your top 8 dishes by sales volume. These represent roughly 70% of your revenue impact and give you the biggest bang for your analytical buck.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
What if a dish has sentimental value but performs poorly?
First try reducing costs through cheaper ingredients or smaller portions. If that fails, convert it to a seasonal special rather than keeping it permanently on the menu. Sentiment shouldn't sacrifice profitability.
How do I handle seasonal fluctuations in ingredient prices?
Calculate using current ingredient costs, not averages. During expensive seasons, temporarily move dishes to daily specials instead of the fixed menu. Plan menu changes around predictable seasonal price spikes.
Can I do menu engineering without a POS system?
Yes, but it requires more manual work. Track sales by counting receipts or having staff log orders manually. For small restaurants with simple menus, this approach remains manageable.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Engineer your menu for maximum margin
Menu engineering combines popularity with profitability. KitchenNmbrs gives you the data to strategically design your menu. Test it free for 14 days.
Start free trial →