BETA APP IN DEVELOPMENT HACCP and more are available in your dashboard — currently in beta, so minor bugs may occur. The updated app with full integration is coming soon.
📝 Menu psychology & menu engineering · ⏱️ 2 min read

How do I calculate margin when automatically recommending dishes based on table history?

📝 KitchenNmbrs · updated 16 Mar 2026

Restaurants using automated dish recommendations see an average 18% increase in check size, but 31% report lower profit margins due to poor recommendation calculations. The issue? Popular dishes aren't always profitable ones. Your recommendation system needs to calculate which suggestions actually boost your bottom line.

Why margin calculation for recommendations matters

Your POS remembers table 7's ribeye order and suggests it again. Sounds smart, right? But what happens if that ribeye carries a 47% food cost? You're actually earning less than if you'd recommended nothing at all.

⚠️ Watch out:

Higher revenue doesn't automatically mean more profit. A more expensive dish with poor margin can lower your total profit.

The core formula for recommendation profitability

Each automated suggestion requires this calculation:

  • Dish margin = Menu price (ex-VAT) - Raw ingredient costs
  • Margin percentage = (Margin ÷ Menu price ex-VAT) × 100
  • Acceptance rate = Percentage of guests who order the recommendation
  • Expected profit = Dish margin × Acceptance rate

💡 Example:

Your system suggests dessert after mains:

  • Chocolate tart: €9.20 incl. VAT = €8.44 excl. VAT
  • Raw costs: €2.35
  • Margin per serving: €8.44 - €2.35 = €6.09
  • Acceptance rate: 28%

Expected profit per recommendation: €6.09 × 0.28 = €1.71

Comparing recommendation scenarios

You've got three post-dinner options to suggest:

💡 Comparison:

Which generates the highest expected profit?

  • Scenario A - Premium digestif: €14.20 margin, 12% acceptance = €1.70 expected
  • Scenario B - Artisan dessert: €6.09 margin, 28% acceptance = €1.71 expected
  • Scenario C - Coffee + pastry: €2.85 margin, 67% acceptance = €1.91 expected

Winner: Coffee + pastry combo (€1.91 expected profit)

Factor in operational variables

Your recommendation logic must consider:

  • Stock levels: Never suggest items you're close to running out of
  • Price volatility: Ingredient costs change, so margins shift
  • Kitchen workload: Labor-intensive dishes cost more during rushes
  • Weekly patterns: Acceptance rates vary between weekdays and weekends

⚠️ Watch out:

Update your acceptance rates monthly. Guest behavior shifts with seasons, pricing changes, and market conditions.

Track and refine your recommendation performance

Monitor these metrics every week:

  • Acceptance rate by dish: Which recommendations guests actually order
  • Average profit per suggestion: Total extra margin ÷ recommendations made
  • Overall check impact: Are both revenue and profit margins climbing
  • Service speed: Do recommendations create kitchen bottlenecks

💡 Practical tip:

Customize recommendations by dining context:

  • Business lunch: Quick, lighter additions
  • Date night: Premium wines and shared desserts
  • Family dining: Kid-friendly sides and shareable options

Connecting recommendations to real-time costing

Accurate margin calculations demand current cost data. One of the most common blind spots in kitchen management is using outdated ingredient prices for recommendation algorithms. If your truffle supplier increases prices by 15%, your system needs that information immediately. Tools that automatically update cost prices ensure your recommendations stay profitable as market conditions change.

How do you calculate the margin of automatic recommendations?

1

Gather basic data per dish

Note for each dish you want to recommend: selling price incl. VAT, exact ingredient costs, and calculate the margin per portion. Always calculate with the price excl. VAT for your margin calculation.

2

Measure the conversion chance per recommendation

Track for at least 2 weeks what percentage of your guests say 'yes' to each recommendation. Break this down by guest type (lunch/dinner) and day of the week for more accurate figures.

3

Calculate the expected margin per recommendation

Multiply the margin per dish by the conversion chance. This gives you the expected margin per recommendation. Rank all options from high to low and choose the best one.

4

Update monthly and optimize

Conversion chances change due to seasonality, price changes, and guest behavior. Update your figures monthly and adjust your recommendation strategy for maximum profitability.

✨ Pro tip

Run A/B tests on your top 3 recommendation scenarios for exactly 21 days each, measuring both acceptance rates and kitchen efficiency. This timeframe captures weekend/weekday patterns while giving you statistically meaningful data to optimize your algorithm.

Calculate this yourself?

In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.

Try KitchenNmbrs free →

Was this article helpful?

Share this article

WhatsApp LinkedIn

Frequently asked questions

Should I always recommend the dish with the highest margin?

Not necessarily. Focus on expected profit instead - margin multiplied by acceptance rate. A lower-margin dish that more guests actually order often generates better returns than an expensive item most people skip.

How often should I recalculate my acceptance rates?

Monthly at minimum, plus immediately after menu changes or price adjustments. Guest behavior shifts with seasons, economic conditions, and your pricing strategy.

What if my most popular recommendation has terrible margins?

Either stop recommending it, adjust your cost structure, or raise the price. Popularity without profitability just increases your workload while shrinking margins.

Can I segment recommendations based on guest demographics?

Absolutely, and you should. Business diners, couples, and families have different preferences and spending patterns. Tailored recommendations typically see 20-30% higher acceptance rates.

How do I prevent recommendations from overwhelming my kitchen?

Build inventory levels and prep capacity into your algorithm. Set automatic cutoffs for complex dishes during peak hours and stop suggesting items when stock drops below service minimums.

Should I factor in labor costs for recommended dishes?

Yes, especially for items requiring significant prep or plating time. A dessert that takes 8 minutes to prepare during a dinner rush costs more in labor than your ingredient calculations show.

ℹ️ This article was prepared based on official sources and professional expertise. While we strive for current and accurate information, the content may differ from the most recent regulations. Always consult the official authorities for binding standards.

📚 Sources consulted

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.

JS

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.

🏆 8 years kitchen manager at 1NUL8 Group Rotterdam
Expertise: food cost management HACCP kitchen management restaurant operations food safety compliance

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 →
Disclaimer & terms of use

Table of Contents

💬 in 𝕏
Chef Digit
KitchenNmbrs assistent