Food cost usually leaks quietly. No single event, just a percent or two lost across thousands of plates — over-portioning, wastage, unrecorded staff meals, a supplier who slipped the rate up. Recipe-based inventory is how you make that leak visible. Here's the concept and the few reports that matter.

Ingredient inventory vs recipe (BOM) inventory

Ingredient inventory tracks what you buy: 40 kg onions in, count what's left. Useful, but it can't tell you why stock moved.

Recipe-based inventory (a bill of materials, or BOM) links each menu item to the quantities it consumes. One plate of paneer butter masala = 180 g paneer + 60 ml cream + 40 g butter + spices. Now every sale automatically deducts ingredients, and you can compare two numbers that should match:

  • Theoretical consumption — what your recipes say you should have used, given what you sold
  • Actual consumption — what a physical stock count says you did use

The gap between them is your variance. Small and steady is normal. Large or growing means something is wrong — and now you know which ingredient to look at.

Setting it up without boiling the ocean

You don't need every recipe on day one. Start where the money is:

  • Cost your top 20 selling items first — they're most of your consumption
  • Cost the expensive-ingredient dishes (paneer, chicken, cheese, dry fruits, seafood) — that's where variance hurts
  • Use standard portions and a kitchen scale to define quantities; "one ladle" isn't a unit
  • Enter current purchase rates so the system can value consumption in rupees, not just grams
Start small: 20 well-costed recipes covering 70% of sales beats 200 rough ones. You can always add the long tail later.

The reports that actually tell you something

  • Item-wise consumption — theoretical vs actual, per ingredient, for a date range. This is the one you read weekly.
  • Food cost % — ingredient cost ÷ sales, tracked over time. A rising line is an early warning.
  • Wastage / spoilage log — what was thrown, why, and its value. Enter it honestly or the variance report becomes noise.
  • Stock on hand vs reorder level — so you buy before you run out, not during service.
  • Purchase rate history — catches the supplier who raised paneer ₹20/kg without telling you.

Habits that keep it accurate

  • Count high-value stock on a fixed schedule — weekly for perishables, not "whenever"
  • Log wastage and staff meals the moment they happen
  • Update ingredient rates whenever a purchase comes in
  • Review the variance report with your head chef, not alone — they know why line 7 is off

Where software helps

The deduction-on-sale and the theoretical-vs-actual comparison are tedious by hand and trivial for a POS that supports recipe inventory. POSYatra links recipes to menu items, deducts ingredients on every bill, and produces the consumption, food-cost and wastage reports above. Details on the features page; it's part of the restaurant plans on pricing.