The single most common “food cost” mistake is treating the recipe as a static document. The reality: ingredient cost moves weekly. Suppliers change pack sizes. New seasonal availability shifts the mix. A recipe costed in January is fiction by April.
Recipe costing only works if it’s a loop, not a snapshot.
The supplier–ingredient–recipe loop
Three pieces in a continuous cycle:
- Supplier price feeds. Each ingredient maps to one or more supplier SKUs. Prices update when invoices land (via IntelliFlow) or when the supplier’s scraped catalogue refreshes.
- Ingredient normalisation. Cost is stored per unit-of-recipe-use (per gram, per ml, per each). Pack-size changes don’t break recipes.
- Recipe recalculation. Sub-recipes (sauces, stocks, pickles) re-cost first; finished dishes re-cost from there. The whole menu has live GP at any moment.
The edge cases that derail homemade systems
Unit conversion
Supplier sells beef in 5kg cases at €42.50; your recipe uses 180g. The system has to know that’s €1.53 per 180g, and update when the case price moves. Trivial in theory; surprisingly fiddly across hundreds of ingredients.
Pack-size changes
The 5kg case becomes a 4.5kg case at the same headline price. Per-gram cost has just moved 11% and nobody told anyone. A good system catches this on the next invoice.
Substitute SKUs
The supplier’s usual chicken thigh is out; they ship a similar SKU. Cost moves; allergen profile might too. Recipe needs to handle the substitution — or flag it for human review.
Sub-recipes
A dish uses sauce A; sauce A uses stock B + cream + butter. If butter goes up 12%, sauce A’s cost moves, and every dish using sauce A moves with it. Sub-recipes need to be first-class citizens, not flattened.
Yields
A whole chicken yields ~65% usable meat. A recipe’s effective cost has to include the yield, not just the input weight. Otherwise you’ll underprice every dish using by-product ingredients.
What this looks like in practice
Once the loop is wired, three things change:
- Margin amber/red surfaces. Supplier prices move → recipe re-costs → dishes that drop below target margin appear on the dashboard.
- Menu engineering is on tap. Stars / plowhorses / puzzles / dogs (see our 30% rule piece) are visible, not a quarterly project.
- Decisions get faster. Re-price, re-engineer, drop, or accept — data is there, no spreadsheet rebuild required.
What it doesn’t do for you
The platform doesn’t set the price you charge or decide what to drop — those are still the chef’s + the owner’s calls. It just removes the friction of seeing the situation clearly.
Read next
- Recipe Management product page — the technical detail.
- IntelliFlow — how supplier prices flow in.
- The 30% rule — what to do with the data.
“Illustrative scenarios based on industry benchmarks and our pilot rollouts. Named case studies available under NDA on request.”