Ever wondered if raising that popular pasta dish by €3 will actually boost your profits? Menu engineering shows you which dishes win and which drain your wallet, but the real challenge comes next. You need to predict what happens to your revenue before making any changes.
Why calculating impact beforehand matters
You've analyzed your menu and found that popular pasta carbonara delivers just a 15% profit margin. Raising the price from €18.50 to €21.50 seems logical. But how many customers will walk away? Does that higher price actually increase or decrease your bottom line?
Skip the calculations, and you're gambling with your revenue. Get the numbers right, and you make smart decisions.
The 4 quadrants of menu engineering
Before calculating impact, know where each dish sits:
- Stars: Popular + profitable → Promote
- Plowhorses: Popular + not profitable → Raise price or lower costs
- Puzzles: Not popular + profitable → Improve marketing
- Dogs: Not popular + not profitable → Remove
💡 Example menu analysis:
Restaurant with 1,000 covers/month:
- Pasta carbonara: 200 portions (20%), profit margin €2.80
- Steak: 50 portions (5%), profit margin €8.50
- Fish of the day: 30 portions (3%), profit margin €9.20
The pasta is a Plowhorse: popular but not very profitable.
Calculating the impact of a price increase
Price increases create two opposing forces:
- Positive: More profit per portion
- Negative: Fewer portions sold
The trick? Estimating how many guests you'll lose. Here's what I've seen cost restaurants €200-400 monthly: they skip this calculation entirely and price themselves out of sales. In hospitality, expect this: 10% price increase = 5-15% fewer sales (varies by dish type and competition).
💡 Calculation example price increase:
Pasta carbonara from €18.50 to €21.50:
- Price increase: 16.2%
- Estimated sales decline: 10% (conservative)
- New sales: 180 portions instead of 200
- Old revenue: 200 × €18.50 = €3,700
- New revenue: 180 × €21.50 = €3,870
Result: +€170 per month (+4.6%)
Impact of removing a menu item
Remove a Dog (unpopular + unprofitable), and you win twice:
- Buy and store fewer ingredients
- Guests choose alternatives (hopefully more profitable ones)
Figure out which dish absorbs that demand. Usually customers pick the most similar option.
⚠️ Note:
Test price changes for just one day or week first. Track sales, then make permanent moves. Some dishes react more sensitively to price changes than you'd expect.
Factoring in seasonal effects
Menu changes hit differently depending on season:
- Winter: Guests accept higher prices, comfort food sells better
- Summer: More price pressure, lighter dishes dominate
- Holidays: Premium pricing works
Schedule major changes for January (fresh habits) or September (post-vacation reset).
💡 Example seasonal effect:
Soup from €8.50 to €9.50 in October:
- Expected sales decline: 5% (season helps)
- Same change in May: 15% decline expected
Timing dramatically affects results.
Calculating total menu impact
For complete menu engineering, add up every change:
- Price increases for Plowhorses
- Promotion of Stars (expect higher sales)
- Removal of Dogs
- Repositioning of Puzzles
Calculate each change's impact separately, then sum for total effect.
How do you calculate menu change impact? (step by step)
Analyze current sales per dish
Gather from the last 3 months: number of portions sold per dish, selling price, and profit margin per portion. This becomes your baseline for the calculation.
Estimate sales decline per change
At 10% price increase: calculate with 5-15% less sales (depending on competitor prices). When removing a dish: distribute sales across alternatives. When promoting: expect 10-30% more sales.
Calculate new monthly revenue per dish
Multiply new expected sales × new price = new revenue. Compare with old revenue (old sales × old price) for the difference per dish.
✨ Pro tip
Track your revenue impact exactly 28 days after implementing changes. Customers need 2-3 visits to adjust to new pricing, so earlier measurements give false readings.
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 do I predict customer loss from price increases?
Test small-scale first. Try new prices one day weekly and track sales. Generally expect 5-15% fewer sales for every 10% price bump, but this varies by dish type and local competition.
What if my calculations don't match reality?
That's normal - customers sometimes surprise you. Monitor sales closely for the first month after changes and adjust accordingly. Menu engineering is ongoing, not a one-shot deal.
Should I raise all prices simultaneously?
No, start with your 2-3 most popular dishes and measure results. Too many changes make it impossible to see what's working and what isn't.
How do I calculate revenue impact when removing unprofitable dishes?
Track which dishes customers choose instead of the removed item. Multiply those substitute sales by their profit margins to see your net gain. Most guests pick similar alternatives.
What's the minimum time between major menu engineering sessions?
Review numbers quarterly, but limit major overhauls to 1-2 times yearly. Small price tweaks can happen more often, especially when ingredient costs shift or seasons change.
How do I factor in staff training costs for menu changes?
Add 2-3 hours of training time per server at their hourly rate, plus any new ingredient familiarization. This typically adds €50-150 to your change costs depending on team size.
Can I use the same price sensitivity estimates for all dish categories?
No - appetizers and desserts are usually less price-sensitive than mains. Specialty items (like dry-aged steaks) can handle bigger increases than everyday dishes like pasta or burgers.
📚 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 →