Here’s a familiar scene: a restaurant group with 14 locations and a central kitchen has food cost hovering near 31%. The chef swears the recipes haven’t changed. The purchasing manager swears vendors raised prices. Everyone points at someone else, and the margin keeps slipping a point every year.
We ran a 90-day ERP Consulting review for a group exactly like this, and the finding was blunt: the recipes in the computer were 18 months old.
Old recipes leak money even with good cooks
Flour went up 11% in that period. The portion size for the signature chicken dish quietly grew, because a newer cook scooped a little fuller. The “standard” recipe said 140 grams of rice; the plate actually carried closer to 165. Multiply a 25-gram difference across 4,000 covers a week and you’ve lost roughly $21,000 a year on rice alone.
The ERP Consulting diagnostics compared purchase receipts against recipe math. For every menu item, the system calculated what the kitchen should have consumed, then matched that against what was actually bought. The variance told us exactly which items were leaking.
How to find your own leak in three steps
- Lock every recipe in the system with exact weights, and re-verify each one quarterly — a cook’s “generous scoop” is not a measurement.
- Run a monthly check comparing actual purchase quantities to theoretical recipe usage; any variance above 3% gets reviewed with the kitchen manager.
- Tie vendor price updates to recipe costing, so a supplier increase recalculates the true cost of every menu item the same day.
The group’s food cost went from 31% to 27.8% within five months. No menu price increase. No portion cut that customers noticed. Just accurate recipes and a measurement routine that people actually follow.
If your food cost is drifting, the answer isn’t a new menu. It’s a more honest look at what’s really on the plate — and a system that catches the drift before it reaches your bottom line.