F&BosFood cost is the largest single variable expense in a restaurant P&L. For most Indian food businesses — dine-in restaurants, cloud kitchens, cafes, sweet shops, and small eateries — it consumes 28-35% of every rupee of revenue. A restaurant doing Rs 8 lakh per month with a 34% food cost and a 28% food cost is not running the same business: the 6-percentage-point difference is Rs 48,000 per month — Rs 5.76 lakh per year — the equivalent of a senior cook's annual salary, or the entire net profit difference between a marginal operation and a healthy one.
The gap between a well-controlled food cost and a poorly managed one is not usually a sourcing problem or a pricing problem. It is an operations problem — specifically, the absence of systems that enforce consistency at the production level, track what is being used against what should be used, and make waste visible before it accumulates into a monthly loss that appears only when the accounts are reconciled.
The eight methods in this guide are ranked by typical impact and ease of implementation. None of them require expensive equipment or specialist knowledge. All of them have been applied successfully by Indian restaurant operators across formats — from dine-in restaurants and cafes to cloud kitchens and street food counters. Each method includes a concrete how-to, a realistic impact estimate, and at least one India-based example of what the improvement looks like in practice.
Target food cost for Indian restaurants: 28-35% of revenue (varies by format and cuisine).
4-10% of food purchased by restaurants globally never reaches a customer's plate — wasted in production, storage, or preparation.
India: food waste in the restaurant and food service sector is valued at approximately Rs 92,000 crore annually.
A Bengaluru cloud kitchen reduced food cost from 42% to 30% solely by implementing grammage-specific recipe standards.
Restaurants using inventory management software report 20% reduction in food wastage. Just-in-time ordering with local suppliers cuts wastage by up to 20% in Indian setups.
Supplier negotiation and purchasing consolidation saves 10-15% on ingredient cost for most Indian restaurants that have not previously formalised their procurement.
Before diving into the eight methods, one framing principle: food cost is a percentage, not just a number. A restaurant that spends Rs 2.8 lakh on food in a Rs 8 lakh revenue month has a 35% food cost. If revenue grows to Rs 10 lakh but food spending rises to Rs 3.6 lakh, the food cost has climbed to 36% — even though absolute spending rose because revenue grew. Always track food cost as a percentage of revenue, not as an absolute monthly figure, because absolute spending naturally increases with revenue and disguises cost control problems.
Cost of Ingredients Used = Opening Stock + Purchases - Closing Stock
The formula above is the starting point for all eight methods. Every method below either reduces the numerator (the cost of ingredients used) or ensures the denominator (revenue) grows without a proportional increase in the numerator.
Method 1 | Standardise Recipes to the Gram
Typical impact: 2-8 percentage point reduction in food cost
Recipe standardisation is the single highest-impact food cost control method available to any restaurant, and the one most frequently overlooked by operators who believe their kitchen team 'knows' the recipes. Knowing a recipe and following a grammage-specific written standard are not the same thing. A cook who 'knows' that a chicken biryani requires 'a big handful of rice' may use 220 grams one day and 280 grams the next — a 27% variation in the most expensive component of the dish, invisible to anyone who is not weighing it.
A standardised recipe specifies every ingredient by weight or volume for a defined number of portions, including oil quantity, spice quantities, and garnish. It defines cooking method, cooking time, yield after cooking, and plating quantity. It removes the cook's discretion from the cost equation — not to restrict creativity, but to ensure that the food cost the owner calculated when pricing the dish is the food cost that actually occurs when the dish is produced every day.
How to Implement Recipe Standardisation
Start with your top 10 dishes by order volume — these account for the majority of your food cost exposure. For each dish, cook it once yourself or with your head cook, measuring every ingredient precisely with a kitchen scale. Record the quantities. Calculate the cost of those quantities at current supplier prices. This gives you the theoretical food cost per dish — the cost the dish should produce when made to standard.
Print the recipe cards with grammage and laminate them. Post them at the production station where each dish is prepared. Train every cook on the standard using a demonstration portion — cook it once to standard while the team watches, produce the plate, weigh it, and show them what a correct portion looks like. Repeat monthly, especially for new staff.
Once recipe standards are in place, the next step is a weekly variance check: compare the actual ingredient quantities used (from your purchase and stock records) against the quantities your recipe standards say you should have used for the orders produced that week. Any dish where actual usage exceeds theoretical usage by more than 5% requires investigation — is it over-portioning, production waste, or a theft issue?
A Bengaluru cloud kitchen was running food cost at 42% of revenue. Investigation revealed that the kitchen team was eyeballing sambar, rice, and dal portions — standard Indian home-cooking instinct that does not translate to commercial cost control.
The operator introduced grammage-specific recipe cards for all 14 menu items and conducted a weekly usage-versus-standard reconciliation.
Food cost dropped from 42% to 30% over 8 weeks — a 12-percentage-point improvement. At Rs 4 lakh monthly revenue, this represented Rs 48,000 per month in recovered margin.
No menu changes, no price increases, no supplier changes. The entire saving came from kitchen production consistency.
Use a simple kitchen scale (Rs 800-1,500) at every production station. Weigh before cooking, not after — cooked weight varies with cooking time and water loss.
For liquid components (oils, gravies, sauces), use measured ladles rather than estimation. A standard ladle size for each component removes decision-making from the cook.
Recipe cards should include a photo of the finished plated dish. Visual standards are as important as weight standards — a cook who produces the right weight but wrong presentation is not following the full standard.
Method 2 | Enforce Portion Control at the Service Point
Typical impact: 1-4 percentage points; prevents per-order food cost variance
Recipe standardisation controls food cost at the production stage. Portion control ensures those standards survive all the way to the customer's plate or package. The gap between the two is where a second category of cost variance lives: the cook who follows the recipe correctly but whose colleague at the service counter adds 'just a little extra' because a customer asks, or because the counter staff member has a generous instinct, or simply because there is no measurement system at the counter.
In an Indian restaurant context, the primary targets for portion control are: rice (measured by ladle or portioning cup), dal and curries (measured ladles), protein components (pre-weighed before cooking), bread (counted, not estimated), and garnishes (measured or standardised as single items rather than 'a pinch').
Implementation Without Expensive Equipment
Portion control does not require sophisticated equipment. At the counter level, the most effective tools are: a standardised ladle set where each ladle is colour-coded for a specific item (blue ladle for dal, green ladle for raita, orange ladle for curry), portioning cups in defined sizes for rice and staples, a counting protocol for bread items (2 rotis per portion, counted before plating), and a written 'service standard' card at each service station showing the quantities and vessel to use for each item.
The critical management step is the random portion check: once or twice per shift, a supervisor or the owner weighs a prepared plate before it reaches the customer. If the plate weight is more than 5% above the standard, the team is retrained. This check need not happen every service — its value is in the deterrent effect and the signal that portions are monitored.
For delivery formats (cloud kitchens, tiffin services), weigh your packaging before and after packing once per shift to verify that the quantity dispatched matches the recipe standard. A delivery order consistently over-packed is a daily food cost leakage that adds up to significant monthly loss without any individual incident being large enough to notice.
| Item | Standard Portion | Tool to Use | Over- Portion Risk | Annual Cost (Rs 8L/mo) |
|---|---|---|---|---|
| Basmati rice | 180g per serving | Portioning cup, weighed | High | Rs 24,000-60,000 |
| Paneer (protein) | 80g per dish | Pre-weighed before cooking | Very high | Rs 36,000-90,000 |
| Dal / curry | 150ml per serving | Fixed-size ladle, colour-coded | Medium | Rs 12,000-36,000 |
| Cooking oil | 15-20ml per dish | Measured dispenser bottle | High | Rs 18,000-48,000 |
| Bread / roti | 2 per portion | Count protocol | Low | Rs 6,000-18,000 |
The annual cost figures in the right column represent the estimated annual saving from eliminating over-portioning of 10-25% above standard on each item, at a restaurant doing Rs 8 lakh per month in revenue. Even capturing half of these savings adds Rs 48,000-1.26 lakh to annual net profit from portion control alone.
Method 3 | Manage Inventory with Daily Counts and FIFO
Typical impact: 2-5 percentage points; eliminates expiry waste and over-ordering
Restaurant inventory management in India is often handled by the head cook or store manager using a combination of visual inspection and experience — 'I can see we need more onions, I'll order tomorrow.' This approach produces two predictable problems. Over-ordering: ingredients are ordered based on a fear of running out, resulting in stock levels that exceed the kitchen's consumption capacity and produce expiry waste. Under-ordering: a key ingredient is not ordered in time, runs out during service, and either menu items are 86'd or the kitchen sends someone to buy at retail prices, destroying the unit economics of those dishes.
Daily Stock Count — the Foundation
A daily closing stock count takes 15-20 minutes and is the single most powerful tool for inventory cost control. Count every perishable ingredient at the end of each day: vegetables, dairy (paneer, curd, cream), proteins (chicken, mutton, fish), and cooked preparations that have shelf life constraints. Record the counts in a stock register or a POS-integrated inventory system. Compare today's closing count against yesterday's opening count minus today's production quantities. Any variance that is not explained by normal production shrinkage or returns requires investigation.
FIFO — First In, First Out
FIFO is a storage and usage protocol: the oldest stock is always used first. Every incoming delivery is placed behind existing stock, never in front of it. This ensures that no item sits at the back of the refrigerator for three days while fresh stock is used from the front. In an Indian restaurant context, FIFO is particularly critical for: milk and dairy (1-2 day shelf life), prepared chutneys and pastes (2-3 days), marinated proteins (1-2 days once marinated), and cooked curries carried over from the previous service.
Implementing FIFO requires physical labelling. Every item entering storage should be marked with the date received using a waterproof marker or label. When a cook reaches for an ingredient, they always take the item with the oldest date first. This sounds simple because it is — but most Indian restaurant kitchens do not practise it consistently, and the result is daily waste from items that expire before they are used.
Par Level Ordering
Par level ordering replaces guesswork with a system. For every ingredient, set a par level: the minimum quantity that must be in stock at the start of each day. When the closing count falls below par level, an order is placed to bring stock back to par. Par levels are calculated from 7-14 days of production data — the average daily usage of each ingredient, plus a safety buffer of 1-2 days. This eliminates both over-ordering (stock never builds far above par) and under-ordering (an alert triggers before stock reaches zero).
A 40-seat North Indian restaurant in Pune was wasting approximately 15% of its weekly vegetable order due to expiry — tomatoes, onions, and coriander ordered on Monday that were not fully used by Wednesday.
The owner implemented daily closing counts and FIFO labelling. Within 3 weeks, the kitchen team was using oldest-labelled stock first and ordering based on daily consumption data rather than visual estimation.
Vegetable wastage dropped from 15% to 4% of the vegetable purchase budget in 6 weeks. Annual saving: approximately Rs 1.2 lakh on a Rs 1.8 lakh annual vegetable spend.
FIFO only works if all team members follow it consistently. One cook who grabs the freshest tomatoes from the front of the rack breaks the system for everyone.
Refrigerator layout matters: FIFO-compliant storage requires that new stock can be loaded from the back. If your refrigerators are not set up for this, reorganise them before implementing FIFO.
Daily counts should be done by the same person at the same time each day to ensure consistency. Rotating the counting responsibility without clear handover creates discrepancies.
Method 4 | Engineer Your Menu to Remove Hidden Margin Drains
Typical impact: 2-6 percentage points; ongoing discipline, quarterly review
Menu engineering is the practice of analysing every item on your menu by two dimensions — how often it sells (popularity) and how much profit it generates (contribution margin) — and making management decisions based on which quadrant each item falls into. Most restaurant menus contain items that are actively destroying margin: dishes that sell occasionally but require expensive ingredients, dishes that are popular but priced too low relative to their food cost, and dishes that nobody orders but whose ingredients must be stocked regardless.
The Four Categories of Menu Performance
| Category | Popularity | Profit Contribution | What to Do |
|---|---|---|---|
| Stars | High | High — your most profitable sellers | Feature prominently. Give them the best menu real estate. Never compromise on their quality or portion — customers are ordering them for a reason. |
| Plow Horses | High | Low — popular but food cost is too high | Reduce food cost without changing the dish: substitute lower-cost ingredients, reduce protein weight by 5-10g, or raise the price modestly. Do not remove — popularity is valuable. |
| Puzzles | Low | High — profitable but nobody orders | Reposition on the menu (move to a more visible location), retrain servers to recommend it, improve the item description, or add a photo. If it still does not sell after 60 days, consider removing it. |
| Dogs | Low | Low — rare orders and unprofitable | Remove. Every dog on your menu requires ingredients that must be stocked for occasional orders, adding inventory complexity and wastage risk for zero margin contribution. |
How to Run a Menu Engineering Analysis
Pull the previous 30-60 days of sales data from your POS for every menu item. Record the number of times each item was ordered (popularity) and the contribution margin per item (selling price minus food cost of the recipe). Plot every item on a simple 2x2 grid: high/low order count on one axis, high/low contribution margin on the other. The midpoint for each axis is the average — items above average on both are Stars, below average on both are Dogs.
The most impactful menu engineering decisions for Indian restaurants are typically: identifying the 3-5 most expensive-to-produce items that have low order counts (Dogs and Puzzles using expensive proteins like prawns, lobster, or premium cuts that sit in cold storage for days between orders) and removing them, and identifying the 3-5 most popular dishes where food cost exceeds 40% (Plow Horses) and finding one cost reduction lever for each without changing what the customer tastes.
Common Plow Horse fixes in Indian restaurant menus: reduce the paneer quantity in a popular paneer dish by 10 grams while adding an additional vegetable element to maintain visual fullness; substitute a portion of premium basmati with a quality medium-grain rice in a biryani that is ordered primarily for its masala and not its rice variety; standardise the oil quantity in high-oil dishes (many Indian gravies use 2-3 times the oil the dish actually needs). Each of these changes is invisible to the customer but measurable in the monthly food cost.
Method 5 | Negotiate with Suppliers and Consolidate Purchasing
Typical impact: 10-15% reduction in ingredient purchase cost
Most Indian restaurant operators have not formally negotiated their supplier relationships. They have informal arrangements — the same vegetable vendor, the same dry goods supplier, the same dairy delivery — that have accumulated over time with pricing that drifts upward without scrutiny. Food cost volatility increased by nearly 21% globally between 2021 and 2025, and many Indian restaurant owners absorbed these increases without challenging their supplier pricing or exploring alternatives.
The Three Negotiation Levers
Volume commitment: suppliers offer better prices when they know they have a committed buyer. A restaurant that commits to purchasing 50 kg of onions per week from one supplier and can demonstrate this through consistent orders has meaningful negotiating power for a discounted per-kg price. Most vegetable and dry goods suppliers will offer 5-10% off the market rate for a committed weekly volume buyer who pays on time.
Payment terms: suppliers who are paid in cash or within 7 days consistently receive better prices than those who pay in 30-60 days. A restaurant that currently pays suppliers in 30 days can often negotiate an immediate 2-4% price reduction by committing to weekly cash settlement. The supplier's cost of credit is eliminated, and they pass part of that saving to a reliable prompt payer.
Seasonal and local sourcing: procurement costs in India typically drop 15-30% when buying seasonal ingredients from local markets rather than importing out-of-season produce. A menu that adapts to seasonal availability — featuring tomato-heavy dishes in the winter peak season when tomatoes are Rs 15-20 per kg, and substituting other vegetables in summer when prices reach Rs 60-80 per kg — can reduce vegetable costs substantially without reducing menu quality.
What to Ask Vendors
Most Indian restaurant operators have never asked their regular suppliers for a price review. The conversation is simpler than it sounds: 'We are buying Rs X per month from you consistently. We would like to stay with you for the next 6 months. What is the best price you can offer us if we commit to this volume?' Most suppliers respond positively — they value predictable revenue — and the conversation typically produces a 5-10% reduction on key ingredients without any change in quality or delivery frequency.
List your top 10 ingredients by monthly purchase value. These represent 60-70% of your total food spend.
For each ingredient, identify at least one alternative supplier and get a price quote. Use this as leverage in negotiations with your primary supplier.
Set a quarterly price review date with every major supplier. Mark it in your calendar and prepare a simple spreadsheet showing your monthly purchase volume before the meeting.
Compare your current prices against local mandi (wholesale market) prices monthly. If your supplier's price is more than 15% above mandi price, investigate why or source directly.
For ingredients you use in large quantities (rice, dal, oil), evaluate bulk purchasing from wholesale distributors. Buying a 25 kg sack of dal instead of 5 kg at a time typically saves 8-12% per kg.
A multi-location North Indian restaurant chain in Delhi NCR discovered its food cost was 5 percentage points higher at one outlet than the others.
Investigation revealed the outlet manager was purchasing vegetables from a local market at retail prices rather than from the chain's negotiated wholesale supplier.
Centralising all purchasing through the negotiated supplier contract immediately reduced that outlet's food cost from 36% to 31%.
The chain then formalised a quarterly price review with all suppliers across all outlets, achieving an additional 3-4% reduction on dry goods through volume aggregation.
Method 6 | Cross-Utilise Ingredients Across Dishes
Typical impact: 1-3 percentage points; enables bulk buying, reduces unique SKU count
Every ingredient on your purchase list that is used in only one menu item is a cost and waste risk. If that item sells poorly one week, the ingredient sits in cold storage approaching expiry. If the dish is removed from the menu, the ingredient has no home. Cross-utilisation — designing your menu so that each key ingredient appears in multiple dishes — reduces your unique ingredient count, enables higher-volume purchasing of each ingredient (improving your negotiating position), and creates flexibility to use excess stock productively rather than waste it.
The Indian Menu Advantage
Indian cuisine is structurally well-suited to ingredient cross-utilisation because many dishes share a common base: the same onion-tomato-ginger-garlic masala serves as the foundation for chicken curry, mutton curry, dal makhani, and paneer butter masala. The same marinated paneer that goes into paneer tikka also becomes the filling for paneer kathi rolls. The same chicken preparation that forms the basis of butter chicken is the foundation of chicken biryani with a different spice layering.
Operators who consciously design their menu around shared ingredients can typically reduce their unique ingredient SKU count by 20-30% compared to a menu built around individual recipes. Each removed SKU is an ingredient that no longer requires storage, no longer has expiry risk, and no longer needs separate purchasing and counting. The operational simplification also reduces kitchen complexity during service and training requirements for new staff.
Practical Cross-Utilisation Examples
| Core Ingredient | Menu Items It Can Support | Purchasing Benefit |
|---|---|---|
| Paneer (500g block) | Paneer butter masala, palak paneer, kadai paneer, paneer tikka, paneer kathi roll, paneer biryani | Buy 5 kg/week vs 2 kg; negotiate 12-15% volume discount |
| Chicken thighs (boneless) | Butter chicken, chicken biryani, chicken tikka masala, chicken kathi roll, chicken fried rice | Single protein specification; buy 15 kg/week at wholesale rate |
| Onion-tomato base | All gravy dishes. Batch-prepare 10 kg base | Single batch preparation |
| masala | daily; portion as needed for each dish during service | saves 30% of daily prep labour cost; reduces oil and spice usage |
| Fresh coriander | Garnish on all curries, chutneys, raita, biryani topping, salads | Buy 1 kg daily; nothing is wasted because it goes across all dishes |
| Whole spices (cinnamon, cardamom, cloves) | Biryani, masala chai, kheer, pulao, chole, all complex curries | Buy 2 kg bags vs 200g packets; 20-25% per-gram cost reduction |
Method 7 | Track Wastage Daily and Assign Accountability
Typical impact: 1-4 percentage points; converts invisible cost into manageable line item
Food wastage is the most universally underestimated cost in restaurant operations, precisely because it disappears without creating a transaction. A plate of uneaten food from a dine-in table, a batch of dal that was over-prepared and discarded at closing, vegetables trimmed more aggressively than the recipe requires — none of these appear as line items in the P&L. They are absorbed into a food cost percentage that is higher than it should be, with no attribution to specific causes.
Industry data consistently shows that 4-10% of food purchased by restaurants never reaches a customer's plate. At Rs 8 lakh monthly revenue with 32% food cost (Rs 2.56 lakh in ingredients), a 7% wastage rate means Rs 17,920 per month — Rs 2.15 lakh per year — discarded. Making this waste visible through daily logging is the first step to reducing it.
Three Categories of Restaurant Food Waste
Production waste is generated during food preparation: vegetable peelings, trim from protein, oil used for deep frying, broken biscuits and bread, and over-prepared batches of mise en place that are not used in service. This category is the most controllable — most production waste is created by recipes that specify more trim than necessary or by over-preparation that habitually produces more than service demand requires.
Service waste is food that is cooked and prepared but not sold: dishes that are prepared in advance for a service that is slower than expected, items that are rejected by the kitchen quality check before leaving the pass, and complementary items (bread, poppadums, chutneys) that are left uneaten at tables. Service waste is reduced by production-on-demand systems rather than batch cooking in advance, and by forecasting daily covers accurately and adjusting preparation volumes accordingly.
Expiry waste is unused ingredients that pass their safe use date in storage: vegetables that wilt, dairy that sours, proteins that are not used within their safe refrigeration period. This category is addressed by Methods 3 (FIFO and daily counts) and 5 (par level ordering). But the only way to know how much you are wasting to expiry is to log it — every item discarded as expired should be recorded with its weight and cost.
The Daily Waste Log
A daily waste log is a simple notebook or digital record at the kitchen with three columns: item discarded, quantity (in grams or kg), reason (over-preparation, expiry, quality rejection, service return). The kitchen team fills it at the end of each service. The owner or manager reviews it weekly.
The value of the log is not the daily numbers — it is the weekly pattern. If the same item appears in the waste log every Tuesday and Thursday, there is a systematic over-preparation problem on those days. If a specific ingredient consistently appears as expired, the par level or ordering frequency for that ingredient needs adjustment. Patterns are only visible across multiple days of data — a single day's waste is noise; a week of data is a signal.
Assign waste logging responsibility to a specific kitchen team member, not to whoever is available. Accountability improves compliance.
Make the weekly waste cost visible to the kitchen team — total wastage in rupees per week, not just grams. Kitchen staff who understand that Rs 3,000 of food was thrown away last week respond differently than those who see abstract weights.
The fastest-payback production change most Indian restaurant kitchens can make is reducing the quantity of chapati dough that is rolled and cooked in advance, before service demand is known. Cook to order for bread wherever possible.
Method 8 | Use Technology for Real-Time Food Cost Visibility
Typical impact: Enables all other methods; catches variance within days not months
The first seven methods in this guide are operational practices — things your team does differently every day in the kitchen. Method 8 is the management layer that makes all the other methods work at scale: a technology system that tracks what is being used against what should be used, in real time, and alerts you when the two diverge beyond acceptable bounds.
Without technology, food cost is a monthly rearview mirror: you learn what your food cost was last month when you reconcile your accounts this month. By the time you know that last month's food cost was 38% instead of the 30% you targeted, the overage has already occurred across 30 days of production. With a real-time food cost tracking system, a food cost variance is detected within 48-72 hours of it beginning, while the cause is still recent enough to investigate and the loss is still small enough to be recoverable.
What a Food Cost Technology System Must Do
At minimum, a restaurant food cost technology system must: maintain a costed recipe for every menu item; track daily production counts and link them to ingredient consumption; compare actual ingredient usage against theoretical usage (recipe standard multiplied by production count) and flag variances above 5%; integrate with purchase records to track ingredient cost changes and update theoretical food cost automatically when supplier prices change; and produce a weekly food cost report that shows food cost percentage, variance from standard, and which dishes are creating the largest variances.
The variance between actual and theoretical food cost is the most important number in food cost management. Theoretical food cost is what your food cost would be if every dish was made exactly to recipe standard with zero waste. Actual food cost is what you actually spent. The gap between them — the variance — is the total of over-portioning, wastage, theft, and recipe deviations. Knowing this number weekly, rather than monthly, compresses the response time from 30 days to 7 days.
Revenue x 100
Variance = Actual Food Cost % - Theoretical Food Cost %
A variance above 3% requires immediate investigation of portioning, wastage, and
purchasing records.
F&Bos costs every dish from gram-level recipes with yield percentages, and purchase price history means an ingredient price rise shows up in your dish costs the same week. Ideal vs actual usage exposes over-portioning and pilferage, wastage is logged with a rupee value, and MarginMind AI shows which dishes to reprice, promote or retire.
Summary — Impact and Implementation Order
Apply all eight methods in sequence for maximum cumulative impact
The eight methods below compound when applied together. A restaurant that implements all eight typically achieves a total food cost reduction of 8-15 percentage points over 3-6 months — a transformation that can turn a marginal operation into a healthy one, or a healthy one into an exceptional one. Implement them in the order listed: Method 1 (recipe standardisation) first because everything else depends on having a standard to measure against.
| # | Method | Typical Impact | Time to See Results | Effort to Implement |
|---|---|---|---|---|
| 1 | Recipe standardisation | 2-8 percentage points | 2-4 weeks | Medium — requires time to write and train recipes |
| 2 | Portion control at counter | 1-4 percentage points | 1-2 weeks | Low — ladles, cups, and counting protocol |
| 3and FIFO | Inventory management | 2-5 percentage points | 2-4 weeks | Medium — daily count routine and labelling system |
| 4 | Menu engineering | 2-6 percentage points | 4-8 weeks (after removal or repricing) | Low effort, high discipline — quarterly review |
| 5 | Supplier negotiation and bulk buying | 10-15% on purchase cost | Immediate on new pricing | Low — one conversation per supplier, quarterly review |
| 6 | Cross-utilisation of ingredients | 1-3 percentage points | 4-8 weeks (after menu redesign) | Medium — requires menu redesign discipline |
| 7 | Daily waste tracking | 1-4 percentage points | 4-6 weeks to see patterns | Low — notebook or digital log, 10 min/day |
| 8visibility | Technology for real-time | Enables and accelerates all other methods | Immediate visibility; ongoing improvement | Low — software setup 1-2 days; ongoing is automated |
| C | (all 8 methods over 3-6 | 8-15 percentage | Full benefit in | Cumulative — builds |
| omonths)mbined | points total | 3-6 months | month on month | |
| impact |
A restaurant that reduces food cost from 35% to 22% on Rs 8 lakh monthly revenue saves Rs 1.04 lakh per month — Rs 12.48 lakh per year — without changing its menu, its prices, or its customer count. The food was always being prepared; it is now being prepared to a consistent standard, tracked against that standard, and purchased at better prices with reduced waste. The improvement in profitability comes entirely from operational discipline, not from additional revenue.