Recipe version history tracks how your dish costs evolve over time, revealing exactly when and why prices jumped. Most restaurant owners discover their margins have tanked only after closing a bad month. Version history shows you the culprit immediately.
Why recipe version history matters for your bottom line
Your carbonara cost €4.80 in ingredients last year. Today it's €6.20. But you don't know when it happened or what caused it. Was the cheese price hike in March? Did your chef start adding extra bacon without telling you?
Without version history, you're playing detective with your own recipes. With it, the answer's right there.
💡 Example:
Carbonara food cost development:
- January 2024: €4.80 (food cost 28%)
- March 2024: €5.20 (cheese +€0.40)
- July 2024: €5.60 (bacon +€0.40)
- October 2024: €6.20 (eggs +€0.60)
Total increase: €1.40 per portion
What version history reveals
A solid version history shows you:
- Date of change: Exactly when the food cost shifted
- Old vs. new food cost: The difference per portion
- Reason for change: Which ingredient drove the increase
- Impact on food cost: How it hit your margin
- Who made the change: Which team member adjusted the recipe
⚠️ Watch out:
Without version history you don't know if your selling price still makes sense. A dish that had 28% food cost last year could now be 35% due to price increases.
Spotting food cost increases in your data
Look for these patterns in your version history:
- Sharp jumps: Food cost suddenly increases by €1+ per portion
- Gradual creep: 10-20 cents added every month
- Seasonal swings: Vegetables pricier in winter, cheaper in summer
- Recipe drift: Chef uses more or premium ingredients
💡 Example signal:
You see a jump in March from €5.20 to €5.60 on your pasta. Check:
- Which ingredient was adjusted on that date?
- Was it a price increase from your supplier?
- Or did your chef adjust the recipe?
This way you know immediately what happened and can take action.
Your three options for handling cost increases
Version history shows an increase? You've got three moves:
- Raise selling price: Adjust your menu to match reality
- Find another supplier: Maybe there's a better deal elsewhere
- Tweak the recipe: Replace expensive ingredients with alternatives
The version history helps you calculate what each option means for your margin. It's the kind of thing you only learn after closing your first month at a loss – having data beats guessing every time.
Digital systems vs. paper recipes
Paper recipes don't track changes. You'll never know when something shifted or why. Digital systems automatically save every change with date and reason.
💡 Real-world example:
Restaurant De Smaak saw their profit margin drop from 12% to 8% without a clear reason. By checking the version history they discovered:
- Beef had become 25% more expensive in 6 months
- Their 3 most popular meat dishes now had 38% food cost
- By adjusting prices they got their margin back
How do you use version history to track food cost increases?
Open your recipe overview and sort by date
Go to your recipe database and sort by 'last modified'. This way you see which recipes have been recently adjusted and may have become more expensive.
Compare old and new food costs per recipe
Click on the version history of each recipe. Note the food cost from 3 months ago versus now. Calculate the difference per portion.
Identify the cause of each increase
Check which ingredients became more expensive on which date. Was it a supplier price increase or a recipe adjustment by your chef?
Calculate the impact on your food cost percentage
Divide the new food cost by your selling price (excl. VAT) and multiply by 100. If you go above 35%, you need to take action.
Create an action plan per increased recipe
Decide per recipe: raise selling price, find another supplier, or adjust recipe. Document your decision in the version history.
✨ Pro tip
Check your version history every 14 days for dishes that moved more than €0.30 per portion. Small changes add up fast, and catching them early saves you from sticker shock at month-end.
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 check my version history?
Check your 10 best-selling dishes monthly. During major supplier price increases (for example energy-related) you can check weekly instead.
What if I don't have digital version history?
Start now by recording food costs per date. Create a simple list with dish, date, food cost. After 3 months you'll already see trends.
Can I predict when prices will increase?
Seasonal products are predictable (strawberries expensive in winter). For other ingredients: follow news about commodity and energy prices.
Do I need to pass on every small price increase?
Not necessarily. Focus on increases of €0.50+ per portion or if your food cost goes above 35%. Small increases you can absorb in your margin.
How do I explain version history to my team?
Show them it's not about control, but about having a grip on things. When ingredients become more expensive, your team needs to know that to make good decisions.
What's the biggest red flag in version history data?
Multiple dishes jumping 20%+ in food cost within the same 2-week period. This usually means a major supplier hiked prices across the board and you need to act fast.
📚 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.
Related questions
All your recipes in one place, forever
Recipes in heads, on notes, in folders — that doesn't work. KitchenNmbrs centralizes all your recipes with costs, allergens, and portions. Try it free for 14 days.
Start free trial →