Recipes for dishes: how to build them, store them, and maintain them as prices move.
A recipe built once and left for a year starts lying after month two. Here is what makes a recipe a management tool rather than a document for inspectors.
Published 22 April 2026
What a recipe must actually contain
A spreadsheet labeled 'recipe' with only an ingredient list and a comment is half the job. A real recipe has six columns: ingredient, net quantity per portion, waste percentage, gross quantity, unit of measure, and supplier price per unit.
Without waste, food cost is off by 5 to 15% because the actual quantity leaving the storage is not represented. Without supplier price, the recipe is a recipe, not a calculation.
Weighing portions is the required first step
A recipe that says 200 g of pasta and a kitchen serving 240 g produce different recipes. A 40 g per-portion difference means 20% more ingredient per dish, which on 50 portions a day becomes a hidden loss of around a hundred euros a month.
The first round of weighing is done with the head chef across two shifts, dish by dish. After that the recipe becomes a serious input, not a guess.
Bind supplier price to the ingredient, not to the dish
Typical mistake: the price 18 EUR/kg salmon is written directly into the salmon tartare recipe. When the price moves to 21 EUR/kg, the dish has a wrong food cost until someone manually updates every recipe that contains salmon.
Correct model: supplier price is tracked per ingredient, recipes reference the ingredient. A price change automatically updates every recipe that contains it.
Reuse and leftovers, how to account for them
Restaurants that use leftovers daily in soups and sides rarely account for it. The result: a side recipe shows 0.40 EUR food cost, the real one is 0.10 EUR because it comes from already-paid material.
Realistic approach: sides made from main protein leftovers are tracked through an internal ingredient transfer. That way Sunday's beef margin is accurate and Tuesday's risotto using the leftover meat is also accurate.
Versioning, not deletion
When you change a recipe because of seasonality, supplier price hikes, or a new recipe, the old version is not deleted. The old version stays archived, the new version gets an effective date.
The reason: when five months later you look at why margin on a special dropped, knowing what the recipe looked like back then is the difference between analysis and guessing.
Takeaway
A recipe is a management tool, not a document for inspections. When it tracks real quantities, linked prices and versions, it becomes the source of truth for food cost that an owner can defend monthly to anyone.
Apply this in your venue.
30-minute demo on your data. We will show you exactly where you can close the gap described in the article.