Food & beverage · 10 min read

Restaurant Inventory Management: Control Food Cost & Wastage

In a restaurant, inventory is your margin. Food cost is usually the single largest controllable expense on the P&L, and most of it leaks quietly — through over-portioning, spoilage, theft and dishes that are priced below what they actually cost to make. This guide shows how ingredient-level kitchen inventory, recipe costing and FEFO turn that leak into a number you can manage every week.

Why restaurant inventory is uniquely hard

Retail inventory is comparatively forgiving: a bottle of shampoo scanned at the till is one unit removed from stock, and it keeps for months. A restaurant breaks almost every one of those assumptions at once, which is why generic stock software struggles here and why restaurant inventory management is its own discipline.

• Perishables with a clock. Paneer, curd, leafy greens, seafood and pre-cut vegetables expire in days. Stock you bought on Monday can be a write-off by Thursday, so time — not just quantity — is part of the count.
• You don't sell what you buy. You buy onions, tomatoes and atta; you sell butter masala and rotis. What leaves the kitchen never matches a purchase line item, so stock has to be deducted by recipe, not by SKU sold.
• Yield and portioning drift. A 5 kg chicken doesn't yield 5 kg of usable meat, and two cooks portion a biryani differently. Small, invisible variances compound across hundreds of covers a day.
• Multiple outlets and kitchens. A cloud kitchen brand or a chain runs several stations and locations, each with its own stock, transfers and par levels — but head office needs one consolidated view.
• Theft and wastage are silent. Unlike a missing cash-register total, a few extra portions of paneer or a bag of prawns walking out the back door leaves no obvious trace unless you are reconciling ingredient stock against sales.

The upshot: effective kitchen inventory has to track ingredients at the raw level, understand how dishes consume them, and account for expiry and wastage as first-class events — not afterthoughts.

Track ingredients, not menu items

The foundation of restaurant stock control is an ingredient master: every raw item you buy, in the unit you actually store and use it in. Get the units right and everything downstream — costing, deduction, reorder — falls into place. Get them wrong and every report lies.

• Stock in a base unit. Hold paneer in grams, oil in millilitres, eggs in pieces. Buy in one unit (a 15 kg tin of oil) and consume in another (30 ml per dish) by defining a purchase-to-base conversion once.
• Cost per base unit. If paneer lands at ₹320/kg, that is ₹0.32/g. Recipe costing depends entirely on an accurate, current per-unit cost, so update it as supplier prices move.
• Separate prep items. House-made items — onion paste, tandoori marinade, sugar syrup — are ingredients too. Give them their own recipes so a batch of gravy consumes its raw inputs when produced.

Recipe costing and BOM consumption

A recipe is simply a bill of materials (BOM) for a dish: the list of ingredients and the quantity of each. This is where recipe costing lives, and it does two jobs at once — it tells you what a plate costs to make, and it tells the system what to deduct when that plate is sold.

Take a paneer butter masala priced at ₹280 on the menu:

• 150 g paneer @ ₹0.32/g = ₹48.00
• 80 ml cream @ ₹0.28/ml = ₹22.40
• 60 g onion-tomato gravy @ ₹0.18/g = ₹10.80
• Spices, butter, garnish (standard allowance) = ₹12.00

Plate cost ≈ ₹93.20, so this dish carries a theoretical food cost of about 33% at its ₹280 price. Now the important part: when the POS rings up one paneer butter masala, the system explodes that recipe and deducts 150 g paneer, 80 ml cream and 60 g gravy from kitchen stock automatically. Sell 40 plates in a service and you have consumed 6 kg of paneer without a single manual entry. This recipe-driven deduction keeps on-hand quantities and your theoretical food cost continuously up to date — the number your actual count is measured against.

The gap between what your recipes should have consumed and what your physical count says you actually consumed is the single most valuable number in a kitchen. That variance is your over-portioning, spoilage and theft — measured in rupees.

The food cost percentage formula

Everything comes back to one metric. Food cost control is the practice of measuring, and then closing the gap on, your food cost percentage:

food cost % = COGS ÷ food sales × 100

Where COGS = opening stock + purchases − closing stock for the period. COGS is what you actually consumed, not what you bought — which is exactly why an accurate closing count matters. Here is a worked example for a mid-size thali-and-curries restaurant over one month:

That 2.7-point gap is not rounding — it is roughly ₹75,600 a month, or over ₹9 lakh a year, walking out of one outlet. You cannot fix what you do not measure, and you cannot measure theoretical cost without recipe-level deduction. This is the entire business case for proper kitchen inventory.

FEFO and expiry for perishables

Because kitchen stock is perishable, which unit you use matters as much as how much. The rule is FEFO — first-expiry-first-out: always consume the batch that expires soonest, not simply the oldest or whatever is nearest the front of the fridge. Track each delivery as a batch with its own expiry date, and the system steers consumption to the batch closest to expiry while flagging what is about to lapse.

• Batch on receipt. When 20 kg of paneer arrives, record it as a batch with an expiry date. The next delivery is a separate batch — never a merged pile.
• Consume FEFO. Recipe deductions draw from the earliest-expiring batch first, so nothing quietly ages out at the back.
• Expiring-soon alerts. A daily list of batches within, say, two days of expiry lets the chef push a special or prep ahead instead of writing stock off. For a deeper walkthrough, see our guide to FEFO & batch/expiry tracking.

Par levels, reordering and supplier orders

Ordering by gut feel is how kitchens end up both out of tomatoes and drowning in coriander. A par level is the target quantity of an ingredient you want on hand to cover demand until the next delivery, plus a small buffer. Set a par (and a reorder point) per ingredient per location, and the system flags what to buy before you run out — without over-ordering perishables you can't sell in time.

• Par by ingredient and outlet. A high street QSR and a cloud kitchen burn onions at different rates; their pars should differ.
• Reorder suggestions. When on-hand drops to the reorder point, generate a purchase order for the shortfall — the mechanics are the same as any reorder point & safety stock setup, just tuned tighter for short shelf lives.
• Supplier ordering and GRN. Raise POs to your sabziwala and distributors, receive against them (goods-received notes), and let the receipt both update stock and refresh per-unit cost — so recipe costing always reflects today's prices, not last quarter's.

Log wastage — don't let it hide

Every kitchen has food wastage: spoilage, trimming loss, dropped plates, expired batches, staff meals. The difference between a controlled kitchen and a leaking one is that the controlled kitchen records it. Make wastage a first-class stock movement with a reason code — spoiled, over-portioned, expired, complimentary — so the loss is deducted from stock and quantified in a report you review weekly. Once wastage is visible, it becomes manageable: teams that combine FEFO with disciplined wastage logging routinely cut perishable losses by 20–30%, and the reason codes tell you exactly where to act.

Multi-kitchen and multi-outlet control

Chains, franchises and cloud-kitchen brands run several kitchens that share a menu but not a fridge. Good restaurant stock control at scale means per-location stock, validated inter-kitchen transfers (the central commissary sends gravy to three outlets), and a head-office view that rolls up food cost %, wastage and variance across the whole network — while each outlet manager sees only their own stock. The same recipes, pars and FEFO rules apply everywhere; only the numbers differ. Our multi-location inventory guide covers the mechanics in depth.

Put it together

Restaurant inventory management is not about counting for its own sake — it is about protecting the thinnest margin in the business. Track ingredients in real units, cost every recipe, deduct on sale, consume perishables FEFO, hold sensible par levels, log wastage honestly and reconcile theoretical against actual food cost every period. Do that consistently and a 2–3 point food cost improvement — often ₹8–10 lakh a year per outlet — is not optimistic, it is ordinary. Explore how BPIN supports it across restaurant and F&B solutions, or see the full feature set.

FAQ

← Back to all guides