Last week, a restaurant owner called me because his app showed 28% food cost while his chef insisted it was closer to 35%. His team complained about running out of ingredients despite ordering what the system recommended. These mismatches between digital data and kitchen reality happen frequently - and they always signal a fixable problem.
Why data and reality don't match
If your team experiences something different than what your system shows, the problem usually lies in one of these areas:
- Input is incomplete: Not all ingredients are in the system
- Portion sizes don't match: The chef gives 250 grams of meat, you calculate with 200 grams
- Prices are outdated: Your supplier raised prices, but you haven't updated this
- Waste isn't counted: Trim loss, spoilage, and leftovers also count
💡 Example:
Your steak has a food cost of 32% according to the system, but your chef says: "This doesn't add up, we're losing money on this dish."
- System calculates: 200g steak at €24/kg = €4.80
- Reality: Chef gives 250g + extra butter = €6.50
- Difference: 8 percentage points higher food cost than expected
At 100 portions per month you lose an extra €170.
Check your basic data first
Before you draw conclusions, verify that your input is correct. Spend one full day checking everything your team does:
- Weigh portions: How many grams of meat, fish, pasta does the chef actually give?
- Count ingredients: How many mushrooms, how much sauce, which garnish?
- Check prices: Call your supplier and ask for current prices
- Measure waste: What gets thrown away due to trim loss, spoilage, mistakes?
⚠️ Note:
Do this on a normal workday, not on a quiet Monday. Your team's behavior varies with how busy you are.
Analyze the differences systematically
Make a list of what you find versus what's in the system. From tracking this across dozens of restaurants, you'll often see patterns:
💡 Example of differences analysis:
- Pasta carbonara: system 180g pasta, reality 220g
- Steak: system €24/kg, supplier now charges €28/kg
- Salad: system doesn't count dressing, reality does
- Fish: system doesn't account for trim loss, reality 40% loss
Conclusion: food cost is 6-8 percentage points higher than expected.
Involve your team in the solution
Your team often knows exactly where the problem is. Ask for their input and explain why accurate data matters:
- Explain why it matters: "If we calculate too low, we can't set good prices"
- Ask for their input: "What do you see that I'm missing in my calculation?"
- Make agreements: "From now on we'll give exactly 200g of meat, no more"
Often it turns out your team knows they're portioning more generously, but didn't realize how much this impacts finances.
Update your system with the actual numbers
Once you've found the differences, adjust your data to match reality. Not the other way around:
💡 Practical example:
Instead of asking your chef to give less, you update the system first:
- Old input: 200g steak, food cost 32%
- New input: 250g steak, food cost 38%
- Decision: raise price or reduce portion
Now you see the real impact and can make an informed decision.
Create a plan for consistency
To prevent this from happening again, build in controls:
- Weekly portion check: Weigh 5 random plates per week
- Monthly price update: Check supplier prices every month
- Daily waste note: What got thrown away and why?
In your system you can add notes to recipes about what you've adjusted and why. That way you won't forget why you made certain choices.
How do you solve data-reality differences?
Observe one complete service
Stand next to your chef during a normal workday and note exactly what happens. Weigh portions, count ingredients, watch for waste. Compare this with what's in your system.
Make a differences analysis
List the differences you found and calculate the financial impact. Focus on your 5 best-selling dishes - they have the biggest impact on your total food cost.
Update system to match reality
Adjust your recipes and prices to match what actually happens. Calculate the new food cost and decide whether you need to adjust prices or change processes.
✨ Pro tip
Start by auditing your 3 highest-volume dishes over the next 48 hours - if those calculations are accurate, you've solved roughly 60-70% of your variance problem.
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 my team won't cooperate with measuring portions?
Explain that it's not about control, but about being able to set fair prices. If you calculate too low, you'll eventually have to raise prices or lose money - and that affects everyone.
How often should I check if data and reality still match?
Check your supplier prices monthly and weigh a few random portions weekly. With major changes (new chef, new supplier) do a full check.
What if the actual food cost is much higher than I thought?
Then you have three options: raise prices, reduce portions, or find cheaper ingredients. Usually a combination of the first two is most realistic.
Can I trust my team to portion correctly on their own?
Trust is good, checking is better. Give clear guidelines (200g meat, not 'a generous portion') and check regularly. Inconsistency costs you money.
What if different cooks give different portions?
Make clear agreements and provide portioning tools like scales or measuring cups in the kitchen. Standardization is crucial for consistent quality and costs.
Should I prioritize fixing high-volume or high-cost dishes first?
Focus on your top 5 revenue-generating dishes first - they have the biggest financial impact. A 2% error on a dish you sell 200 times monthly costs more than a 10% error on something you sell twice.
📚 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.
Make better decisions with real numbers
Should you change your menu? Raise prices? Test a new concept? KitchenNmbrs simulates scenarios with your own data. Try it free for 14 days.
Start free trial →