Ask ten restaurant owners their food cost and most will say “around 32 percent”. Ask what it was last Tuesday, for the tandoor section, and why it was two points higher than the Tuesday before — and the room goes quiet. That gap between knowing the number and knowing the cause is where margin disappears.
This guide lays out a practical, recipe-level system for food cost control that a single café or a twenty-outlet chain can run. It covers the calculation, the data you need, the two reports that matter, and how menu engineering turns cost data into pricing decisions.
Start with the right formula
Food cost % = Cost of goods consumed ÷ Food sales × 100, where cost of goods consumed = opening stock + purchases − closing stock. Two things trip people up:
- Using purchases instead of consumption. A big weekly delivery makes purchases spike; consumption is what you actually used.
- Mixing beverage and food. Track them separately; bar margins are different and will hide kitchen problems.
Typical healthy ranges in India: 28–35% for casual dining, 25–32% for QSR, 30–38% for fine dining, 22–30% for cloud kitchens with tight menus. The range matters less than the trend and the variance.
Build recipe costs — every item, every modifier
Recipe costing means recording, for each menu item, the exact ingredients and quantities, so the system can compute a theoretical cost per plate from current purchase prices. A butter chicken recipe that lists 180 g chicken, 40 g butter, 60 g cream, 90 g gravy base (itself a sub-recipe) and so on yields a cost that updates automatically when the chicken price changes.
Do not skip modifiers and add-ons. “Extra cheese” and “make it large” are where costed recipes drift from reality if they are not defined.
The two reports that matter
1. Theoretical vs actual (variance)
Theoretical cost is what your sales should have consumed, based on recipes. Actual cost is what the stock count says you consumed. The difference is variance, and variance is a map of your leakage: over-portioning, wastage, theft, unrecorded staff meals, or recipes that are simply wrong. A variance below 2 percentage points is excellent; above 5 needs immediate attention.
2. Wastage log
Every item thrown away — spoiled, dropped, sent back, over-prepped — should be logged with a reason. Within a month the log tells you which ingredients to buy in smaller quantities, which prep to move later in the day, and which dish gets sent back most.
Weekly routine that keeps it honest
- Daily: high-value items counted at close (meat, seafood, paneer, cheese, alcohol). Wastage logged in real time.
- Weekly: full stock count, variance report reviewed with the head chef, top five variance items get an action.
- Monthly: purchase price review by supplier, recipe costs re-checked for items where price moved more than 10%, menu engineering pass.
Menu engineering: turning cost data into pricing
Plot every item on two axes — popularity (units sold) and contribution margin (price minus recipe cost). You get four groups:
| Group | Popularity | Margin | Action |
|---|---|---|---|
| Stars | High | High | Feature them; protect the recipe |
| Plough-horses | High | Low | Re-cost, re-portion or raise price gently |
| Puzzles | Low | High | Rename, reposition on the menu, staff upsell |
| Dogs | Low | Low | Remove or replace |
Run this quarterly. Restaurants that do typically lift gross margin by three to five points in the first year, without raising prices across the board.
Multi-outlet and central kitchen considerations
With more than one outlet, the game changes in two ways. First, compare food cost by outlet for the same recipe: a two-point gap between branches with identical menus is almost always execution, not price. Second, a central kitchen or commissary needs its own bill of materials and production records, so that stock transferred to outlets carries the right cost and the outlet’s variance is measured against what it actually received.
Doing it without spreadsheets
All of this is possible in spreadsheets, and most restaurants start there. It breaks down at scale because the data lives in three places: sales in the POS, purchases in accounting, and recipes in a sheet. Recipe-based inventory inside the POS closes the loop — every sale deducts ingredients automatically, purchases update prices, and the variance report is a click rather than a weekend.
Restro Sarthi’s inventory suite works this way: recipe and BOM costing, live food-cost percentage, stock takes with variance, wastage logging, purchase orders and supplier pricing, central-kitchen MRP and inter-branch transfers, plus a menu-engineering report built in. See the Run & Supply suites or book a demo and bring your current food-cost number — we will show you where it is coming from.
