Think of menu engineering like a company's annual performance review - except instead of evaluating employees, you're assessing every dish's contribution to your bottom line. By tracking popularity and profitability, you create concrete data about which menu items truly drive revenue. Transform this analysis into a professional report that gives your accountant the insights needed for strategic financial planning.
What is menu engineering for your annual report
Menu engineering examines each dish across two critical metrics: sales frequency (popularity) and profit generation (profitability). Your accountant needs this data because it reveals which products actually fuel your revenue and margins - not just what you think performs well.
💡 Example annual report data:
Restaurant with 5 main courses, 12,000 covers per year:
- Steak: 3,600 sold (30%), margin €12 = €43,200 contribution
- Salmon: 2,400 sold (20%), margin €8 = €19,200 contribution
- Pasta: 4,800 sold (40%), margin €6 = €28,800 contribution
Total main course contribution: €91,200
The four categories for your report
Menu engineering sorts dishes into four distinct quadrants. This framework provides your accountant with immediate clarity on your menu's financial structure:
- Stars: High popularity, high profit - your revenue champions
- Plowhorses: High popularity, low profit - volume drivers with thin margins
- Puzzles: Low popularity, high profit - untapped potential
- Dogs: Low popularity, low profit - menu deadweight
⚠️ Note:
Focus on absolute margin per dish, not food cost percentages. Your accountant gains more actionable insights from actual euro amounts than ratios.
What figures do you collect for the report
A thorough menu report requires these specific data points for each dish:
- Units sold: Annual total plus percentage of overall sales
- Revenue per item: Quantity × selling price excluding VAT
- Cost per item: Ingredient costs plus direct expenses
- Margin per item: Selling price minus cost price
- Total contribution: Units sold × individual margin
💡 Example calculation:
Pasta Carbonara in 2024:
- Sold: 1,200 portions (25% of main courses)
- Selling price: €16.50 incl. VAT = €15.14 excl. VAT
- Cost of ingredients: €4.80
- Margin per portion: €15.14 - €4.80 = €10.34
Total contribution: 1,200 × €10.34 = €12,408
How to present this to your accountant
Build a clear overview table featuring essential metrics and brief analysis. Your accountant can then apply this information for budget planning and strategic decisions for the upcoming year.
Organize your report into three core sections:
- Data table: Complete dish lineup with sales numbers and contributions
- Classification: Stars, plowhorses, puzzles, and dogs breakdown
- Recommendations: Specific menu modification proposals for next year
What your accountant can do with it
From analyzing actual purchasing data across different restaurant types, this menu report enables your accountant to conduct several critical analyses:
- Budget forecasting: Revenue projections by product category
- Cost evaluation: Identifying largest margins and financial risks
- Investment planning: Determining which menu items warrant additional marketing spend
- Seasonal strategy: Timing promotional efforts for maximum impact
💡 Practical example action points:
Based on menu engineering analysis:
- Promote steak (star): can increase from 30% to 35% sales
- Raise pasta price (plowhorse): from €16.50 to €18.50
- Reposition fish (puzzle): better menu placement
- Remove vegetarian lasagna (dog): replace with more popular dish
How do you create a menu engineering annual report? (step by step)
Collect sales data per dish
Pull the number of portions sold per dish for the entire year from your POS system. Also calculate the percentage that each dish represents of your total sales.
Calculate margin and contribution per dish
Subtract the cost of ingredients from each selling price (excl. VAT). Multiply this margin by the number of portions sold to get the total contribution per dish.
Categorize dishes into four quadrants
Divide your dishes based on popularity (above/below average sales) and profitability (above/below average margin). This gives you stars, plowhorses, puzzles and dogs.
Create concrete action points for the coming year
Formulate per category what you're going to do: promote stars, raise prices on plowhorses, better position puzzles, replace dogs. Translate this into concrete revenue and margin forecasts.
✨ Pro tip
Pull your menu engineering data for the 12-month period ending in November, then present it to your accountant in December. This timing allows you to incorporate the insights into January budget planning while the holiday season performance data is still fresh.
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 create a menu engineering report?
A detailed annual report works perfectly for your accountant, but review key metrics quarterly. Menu performance shifts rapidly, especially with seasonal offerings.
Do I need to include all dishes in the report?
Concentrate on main courses and signature sides - that's typically 80% of revenue. Group appetizers and desserts as separate categories for cleaner analysis.
What if I don't have a POS system that tracks this data?
Work backwards from purchasing records and inventory counts. Calculate steak portions by dividing annual beef purchases by portion weight. Estimates work fine for strategic planning discussions.
How do I determine if a dish qualifies as popular?
Calculate your baseline: total covers divided by number of main courses on your menu. Dishes selling above this average count as popular, below average means less popular.
Can I automate these calculations somehow?
Food cost calculators like tools that integrate with POS systems can track cost prices and sales data automatically. This eliminates manual Excel calculations and reduces errors significantly.
Should I separate lunch and dinner items in my analysis?
Absolutely, especially if you offer different menus or pricing. Lunch items often have different popularity patterns and margin expectations than dinner dishes.
How do I handle dishes with seasonal ingredients that affect costs?
Use weighted average costs based on months served, or create separate entries for seasonal variations. Your accountant needs to see the full cost picture, not just peak season numbers.
📚 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 →