A popular Italian restaurant discovered their bestselling pasta dish was actually bleeding money - despite generating €3,600 monthly revenue. Your POS system holds similar secrets about which dishes truly drive profits versus those that just look busy. Smart analysis of this data reveals exactly which items deserve prime menu real estate and which need immediate fixes.
What you need from your POS system
Effective menu engineering requires two critical data points: sales volume (how many portions moved) and revenue per item. Your POS captures both, though finding the right reports isn't always obvious.
💡 Example:
POS data from last month:
- Steak: 120 sold × €32 = €3,840 revenue
- Pasta carbonara: 200 sold × €18 = €3,600 revenue
- Salmon: 80 sold × €28 = €2,240 revenue
The steak generates highest revenue, but does it deliver the best profit margins?
The 4 quadrants of menu engineering
Every dish on your menu fits into one of four categories based on popularity and profitability. This framework guides your next moves.
- Stars: High sales and high profit - your money makers
- Plowhorses: High sales but low profit - revenue traps
- Puzzles: Low sales but high profit - untapped potential
- Dogs: Low sales and low profit - menu dead weight
Calculate popularity from POS data
Pull sales reports covering at least 6 weeks for reliable patterns. You'll want portion counts, not just dollar amounts. Seasonal items need their own analysis periods.
💡 Example calculation:
Total main courses sold: 1,000 portions
- Steak: 120 portions = 12% of total
- Pasta: 200 portions = 20% of total
- Salmon: 80 portions = 8% of total
Pasta dominates sales volume, while salmon lags behind.
Determine profitability per dish
Here's where it gets tricky - your POS shows selling prices but not ingredient costs. You'll need to calculate food costs separately or use tools like KitchenNmbrs for accurate costing.
⚠️ Note:
Calculate using prices excluding VAT. A €32.00 steak including VAT equals €29.36 excluding VAT (divided by 1.09).
Focus on gross profit per dish: selling price minus ingredient costs. Higher gross profit beats better percentages - you can't deposit percentages at the bank.
💡 Example profitability:
- Steak: €29.36 - €12.50 = €16.86 gross profit
- Pasta: €16.51 - €5.10 = €11.41 gross profit
- Salmon: €25.69 - €9.20 = €16.49 gross profit
Steak delivers the highest profit per portion.
Divide your menu into quadrants
Calculate average popularity and profitability across all dishes. Items above average score 'high', below average get 'low'. This creates your strategic quadrants.
- High popularity + high profit = Stars: Feature prominently and promote heavily
- High popularity + low profit = Plowhorses: Increase prices or reduce ingredient costs
- Low popularity + high profit = Puzzles: Improve menu placement and staff training
- Low popularity + low profit = Dogs: Remove or completely redesign
Actions per quadrant
Data without action is just expensive trivia. Each quadrant demands specific strategies to maximize profitability. One of the most common blind spots in kitchen management is treating all popular dishes equally - but Plowhorses can actually hurt your bottom line despite strong sales.
💡 Real-world example:
A restaurant discovered their popular burger (Plowhorse) only generated €8.50 gross profit. Actions taken:
- Raised price from €16.50 to €18.50
- Switched to cheaper cheese (same quality)
- Gross profit jumped to €12.20
Result: €3.70 additional profit per burger, with 150 monthly sales = €555 extra monthly profit.
Stars deserve premium menu placement: top sections, staff recommendations, and bundle deals. But don't neglect your Puzzles - they often need better positioning, not complete overhauls.
How do you do menu engineering with POS data? (step by step)
Pull a sales report from 4-8 weeks
Get from your POS system how much of each dish you sold. Make sure it's a representative period without holidays or special events. Note the number of portions sold per dish.
Calculate ingredient costs per dish
Add up all ingredients that go into each dish: meat, vegetables, sauces, garnish, everything. Calculate with current purchase prices from your suppliers. This is often the most work, but crucial for reliable results.
Determine popularity and profitability per dish
Popularity = percentage of total sales. Profitability = selling price excl. VAT minus ingredient costs. Calculate the average of both to create your quadrants.
Place each dish in a quadrant
Above average popularity and profit = Star. Above average popularity, below average profit = Plowhorse. And so on for all four quadrants.
Create an action plan per quadrant
Promote Stars, make Plowhorses more expensive or buy cheaper, position Puzzles better on the menu, consider removing Dogs. Start with your biggest Plowhorses - that's where the most profit is.
✨ Pro tip
Focus your initial analysis on the top 12 dishes from your last 8 weeks of POS data. These items typically represent 75-80% of your total food revenue, so optimizing them delivers immediate impact.
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
How often should I analyze my POS data for menu engineering?
Review your numbers every 8-10 weeks, or immediately after major ingredient cost changes. Seasonal menus need analysis at each season transition. Once you establish the routine, quarterly reviews become second nature.
What if my POS system doesn't provide detailed item reports?
Basic POS systems often show only total revenue without item breakdowns. You can manually track portions sold, but that's time-intensive and error-prone. Upgrading to a system with robust reporting pays for itself quickly.
Should I always remove Dogs from my menu?
Not automatically. Some low-performing dishes serve specific dietary needs or complete your concept. However, if a dish consistently underperforms in both sales and profit, question its value. Often those ingredients work better in profitable dishes.
How precise do my ingredient costs need to be?
Every component matters - cooking oil, garnishes, seasonings, even the parsley on the plate. Check supplier invoices and calculate per-portion costs meticulously. A 75-cent error per dish can cost hundreds monthly across volume sales.
Can I apply menu engineering to my beverage program?
Absolutely, though beverages use 'pour cost' instead of food cost. Remember that alcoholic drinks carry 21% VAT in most regions. Cocktails often emerge as Puzzles - high profit margins but disappointing sales volume.
What's the minimum sales volume needed for reliable menu engineering?
You need at least 30 sales of each item for meaningful analysis. New menu items require 6-8 weeks of data before drawing conclusions. Low-volume specialty items might need longer observation periods.
How do I handle dishes with seasonal ingredient cost fluctuations?
Track ingredient costs monthly and adjust your calculations accordingly. Asparagus in spring versus winter shows dramatic cost differences. Some restaurants run separate analyses for high-season and low-season periods to capture these variations.
📚 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 →