The direct answer: Reduce food cost by (1) costing every dish with a recipe BOM, (2) applying yield factors to every ingredient, (3) updating purchase prices when supplier costs change, and (4) engineering your menu to push high-margin items. Restaurants that do all four typically recover 4–8 percentage points of food cost within 90 days.
The national average food cost for Indian restaurants sits between 32% and 38%. Most kitchens operating above 42% don't know it — because they've never measured it dish by dish.
This guide fixes that.
₹3.8L
average annual margin recovered after implementing full recipe costing
What Is Food Cost % (and What It Should Be)
Food cost percentage is the simplest profitability ratio in your kitchen:
Food Cost % = (Cost of Ingredients Used ÷ Food Revenue) × 100
If you spend ₹38 in ingredients for every ₹100 of food revenue, your food cost is 38%.
Benchmarks by restaurant type
| Restaurant type | Target food cost % |
|---|---|
| Fine dining | 28–32% |
| Casual dining | 30–35% |
| QSR / fast food | 25–30% |
| Cloud kitchen | 30–36% |
| Café / bakery | 28–33% |
These are targets, not floors. A well-run kitchen should be at the lower end. Every percentage point above target costs real money — at ₹10L monthly revenue, the difference between 38% and 33% is ₹50,000 per month.
What your food cost is actually telling you
- Below target: Good margins — but check you're not under-portioning
- At target: Healthy — keep monitoring ingredient price changes
- 5pp above target: Investigate recipe adherence and portion control
- 10pp+ above target: Likely systemic — missing recipe costing, theft, spoilage, or all three
The 6 Most Common Causes of High Food Cost
Understanding the cause determines the fix.
1. No recipe costing
The most common cause by far. Without a cost card per dish, you have no baseline to measure against. Prices change, portions drift, and no alarm sounds.
2. Ignoring yield loss
You buy 1kg of chicken. After cleaning, trimming, and cooking, you get 650g of usable protein. If your recipe says "200g of chicken," you're actually using the cost of ~308g of raw chicken. Most restaurants price using raw weight. The gap destroys margins.
3. Purchase prices change, menu prices don't
Tomatoes at ₹25/kg in January, ₹120/kg by June — but the Dal Makhani is still priced at ₹220. The math stopped working months ago and nobody noticed.
4. Portion inconsistency
Three chefs, three different interpretations of "one portion." No standard weight, no portioning tools, no accountability. The result: unpredictable food cost that varies by shift.
5. Spoilage and waste
Over-purchasing, poor FIFO, improper storage, prep waste — all raise your effective food cost without any of it reaching a customer's plate.
6. Staff meal abuse and pilferage
Untracked staff meals can cost ₹15,000–₹40,000 per month in a mid-sized restaurant. Add informal pilferage and the number climbs further.
The Recipe BOM Method — Explained Simply
A Bill of Materials (BOM) is the complete ingredient list for a dish — with quantities, units, current costs, and yield factors applied.
Here's a worked example for Paneer Butter Masala (1 portion):
| Ingredient | Raw qty | Unit cost | Yield % | Costed qty | Cost |
|---|---|---|---|---|---|
| Paneer | 150g | ₹380/kg | 100% | 150g | ₹57.00 |
| Butter | 25g | ₹480/kg | 100% | 25g | ₹12.00 |
| Tomatoes | 120g | ₹50/kg | 75% | 160g | ₹8.00 |
| Cream | 30ml | ₹360/L | 100% | 30ml | ₹10.80 |
| Spices + oil | — | — | — | — | ₹8.50 |
| Total | ₹96.30 |
Selling price: ₹320. Food cost: 30.1% — right on target.
How to build a BOM for every dish
- List every ingredient — including oil, garnish, and accompaniments
- Record the raw quantity per portion (weigh it, don't estimate)
- Apply the yield factor (see next section)
- Enter current purchase prices from your most recent supplier invoice
- Calculate total cost and divide by selling price
Do this for your top 20 dishes first. That typically covers 70% of your revenue.
Tip
Don't try to cost 150 dishes at once. Start with your 20 highest-selling items. The data from those will tell you more than a rough estimate across the full menu.
Understanding Yield: The Number Most Restaurants Miss
Yield % is the proportion of a raw ingredient that becomes usable food.
Yield % = (Usable weight ÷ Raw weight) × 100
Common yield factors for Indian kitchens
| Ingredient | Typical yield % | What's lost |
|---|---|---|
| Chicken (bone-in → boneless) | 60–65% | Bones, skin, trim |
| Prawns (shell-on → cleaned) | 55–60% | Shell, head, vein |
| Paneer (block) | 98–100% | Negligible |
| Tomatoes (for gravy) | 70–75% | Skin, seeds, water loss |
| Spinach (after blanching) | 40–50% | Water loss |
| Onions (peeled and chopped) | 80–85% | Skin, ends |
| Fish (whole → fillet) | 40–55% | Bones, skin, head |
Applying yield to your cost card
If chicken costs ₹280/kg and your yield is 65%, the effective cost per kg of usable chicken is:
₹280 ÷ 0.65 = ₹430.77/kg
A recipe calling for 200g of boneless chicken doesn't cost ₹56. It costs ₹86.15. The gap — ₹30.15 per portion — is the yield loss most restaurants never account for.
Watch out
The compounding problem: Yield errors compound across a menu. If you're undercosting 60 dishes by an average of ₹22 each, and you sell 200 covers a day, you're losing ₹4,400/day — ₹1.32L/month — to yield miscalculation alone.
Menu Engineering — Star vs Plowhorse vs Puzzle vs Dog
Menu engineering places every dish in one of four quadrants based on popularity (how often it sells) and contribution margin (how much profit it generates per sale).
The four quadrants
| High popularity | Low popularity | |
|---|---|---|
| High margin | ⭐ Star | 🧩 Puzzle |
| Low margin | 🐴 Plowhorse | 🐕 Dog |
What to do with each
⭐ Stars — Protect and promote
High sales, high margin. These are your best dishes. Feature them on the first page of your menu, in the top-right position (where eyes land first), with photos and descriptive copy. Don't mess with the recipe. Don't reduce portions. Protect these.
Examples that often land here: Butter Chicken, Biryani (at right price points), Dal Makhani in casual dining.
🧩 Puzzles — Reposition and promote
High margin but low sales. These dishes deserve to sell more — you just haven't made them visible. Move them on the menu, train staff to recommend them, add a photo, rewrite the description. If they still don't sell after repositioning, consider dropping them.
Examples: specialty kebabs, regional dishes, chef's specials that customers don't order.
🐴 Plowhorses — Manage the cost
Popular but low margin. These dishes anchor your menu — customers come for them. Don't remove them. Instead: look for ingredient substitutions that don't affect quality, tighten portions to the gram, or raise price in small increments (₹10–₹20 at a time, test quarterly).
Examples: Gulab Jamun at ₹60, basic Dal Fry, Veg Fried Rice.
🐕 Dogs — Drop or dramatically reimagine
Low sales and low margin. These are wasting menu real estate and kitchen prep time. Remove them, or completely reinvent — new name, new presentation, repriced. If a Dog stays low-performing after reinvention, cut it.
How to calculate contribution margin
Contribution Margin = Selling Price − Food Cost
A Biryani at ₹380 with a food cost of ₹95 has a contribution margin of ₹285. A Gulab Jamun at ₹65 with a food cost of ₹30 has a contribution margin of ₹35. Even though the Gulab Jamun has a better food cost %, it contributes far less to covering your fixed costs and profit.
Menu engineering uses contribution margin — not food cost % — to rank dishes.
How Technology Helps (MarginMind™ Reference)
Manual recipe costing in spreadsheets works — until ingredient prices change, or your menu grows beyond 40 dishes, or you open a second outlet.
The challenges at scale:
- Updating 80 cost cards when onion prices spike takes hours
- Spotting which dishes crossed your 40% food cost threshold requires manual calculation
- Comparing food cost across outlets requires consolidating different spreadsheets
MarginMind™ is KhanaOS's managed margin intelligence service. The KhanaOS team builds your recipe BOM library, links it to live purchase prices, and configures threshold alerts — so when a dish's food cost crosses your set limit (say, 38%), you get a WhatsApp notification that day, not at month-end.
It's a managed service: KhanaOS sets it up and maintains it. You get the insight without the spreadsheet overhead.
MarginMind™
Managed ServiceKhanaOS's managed margin intelligence service. We set up your recipe costing, live food cost alerts, and menu engineering analysis — so you see exactly where margin is leaking.
See how MarginMind worksGetting Started Today
You don't need software to start. You need a process.
Week 1: Cost your top 10 selling dishes using the BOM method above. Apply yield factors. Use your most recent supplier invoice for prices. Compare each dish's food cost % to your target.
Week 2: Classify each dish into the Star/Puzzle/Plowhorse/Dog framework. Make one menu change — reposition a Puzzle, raise a Plowhorse price by ₹15, or drop a Dog.
Week 3: Set up a weekly stock take for your top 5 high-value ingredients. Compare theoretical vs actual consumption. Investigate variances above 5%.
Week 4: Review purchase prices against last month's cost cards. Update any ingredient that's moved more than 10%.
Four weeks of structured work can recover 3–6 percentage points of food cost in most kitchens.
FAQ
Q: What's a good food cost % for an Indian restaurant?
Target 30–35% for casual dining, 28–32% for fine dining, and 25–30% for QSR. Cloud kitchens typically run 30–36% due to packaging and aggregator costs. Anything above 40% needs immediate investigation.
Q: How often should I update recipe cost cards?
Whenever a key ingredient price changes by more than 8–10%. For volatile ingredients (onions, tomatoes, chicken), check monthly. For stable ingredients (spices, oils in bulk), quarterly is fine.
Q: My food cost is high but I don't know why — where do I start?
Start with a physical stock take today. Compare theoretical stock (opening stock + purchases − what recipes say you should have used) against actual stock. The gap tells you the magnitude of the problem. Then investigate portion sizes, supplier invoices for price changes, and staff meal logs.
Q: Should I raise prices to fix food cost?
Sometimes, but not always. First check if the cost can be reduced (yield, portioning, ingredient substitution). If not, a small, tested price increase is the right move. Raise prices in increments of ₹10–₹20 and measure the effect on order volume over 4–6 weeks.
Q: How do I handle seasonal ingredient price changes?
Build a seasonal menu. Dishes built around tomatoes should be priced differently in summer versus monsoon. Alternatively, design your recipes to allow for substitute ingredients (green peas vs frozen peas, for example) and maintain two versions of affected cost cards.
Ready to solve this for your restaurant? KhanaOS tracks recipe costs, ingredient price changes, and dish-level margins automatically. Start your 7-day free trial → or see how MarginMind™ works →
Related articles
Menu Engineering for Indian Restaurants: The Star, Puzzle, Plowhorse, Dog Framework (2026)
11 min
Margin & ProfitabilityInside MarginMind™: How KhanaOS Found 61 Loss-Making Dishes on a 130-Dish Bengali Restaurant Menu
14 min
Margin & ProfitabilityHow to Reduce Food Cost in Your Restaurant: A 2026 Guide for Indian Restaurateurs
9 min