COGS vs prime cost restaurant India — what each tells you and how to track both
COGS vs prime cost for Indian restaurants — what each metric tells you, the formulas, when each one is the right number to act on, and how to track both monthly.
Last updated 12 May 2026
About this piece. "Are you tracking COGS or prime cost?" is the wrong question — they're not alternatives, they're a pair. Each tells you something the other can't. Run only one and you'll keep getting blindsided. This piece sets out what each metric is, what it tells you, and how to track both monthly without the work doubling.
The two metrics — defined cleanly
COGS (Cost of Goods Sold)
= Opening stock + Purchases – Closing stock
Includes: food + beverage at cost
Excludes: labour, packaging (sometimes), aggregator commission
COGS % = COGS / Net sales
Prime cost
= COGS + Total labour cost
Total labour = wages + PF + ESI + bonus accrual + manager + staff meals
Prime cost % = Prime cost / Net sales
Both denominators are net sales — pre-GST, post-aggregator commission.
What COGS tells you that prime cost doesn't
COGS is the vendor and kitchen signal. When COGS moves out of band:
- Vendor pricing has shifted
- Yield is drifting (over-portioning, wastage)
- Closing stock is being under-counted
- Recipe specifications are being ignored at the line
- Theft or pilferage from the storeroom
COGS does not tell you anything about how efficiently your kitchen and service team are running. A perfectly-sourced, perfectly-counted kitchen with a bloated roster has a clean COGS and a terrible prime cost.
What prime cost tells you that COGS doesn't
Prime cost is the operational discipline signal. When prime cost moves out of band but COGS is in band:
- Roster is bloated
- Cross-training is missing (over-hiring to cover skill gaps)
- Manager structure is heavier than the outlet needs
- PF/ESI accrual was forgotten in prior months and now bunched
Prime cost is the ceiling for sustainable operations. Above the format's prime-cost band, the business cannot fund occupancy + other fixed costs + a return to the operator.
Which one to act on first — depends on the gap
The pair tells you where to start.
| Pattern | Diagnosis | First action |
|---|---|---|
| COGS in band, prime cost above band | Labour problem | Roster + cross-training |
| COGS above band, prime cost above band | Kitchen + maybe labour | Yield + supplier renegotiation |
| COGS above band, prime cost in band | Kitchen problem masked by under-staffed labour | Service quality is at risk; fix kitchen, then size labour up |
| Both in band | Healthy — focus on the next metric | Move attention to occupancy and contribution margin |
The most common red-zone pattern in Indian independent casual-dines is "COGS in band, prime cost above band". The temptation is to cut headcount. The right move is to rosterise first and only cut after rostering has been optimised.
Worked example — one outlet, two metrics, two problems
A composite NCR casual-dine outlet doing ₹17 lakhs net food sales:
| Month | COGS (₹) | COGS % | Labour (₹) | Prime cost % | Diagnosis |
|---|---|---|---|---|---|
| Jan | 5,30,000 | 31.2% | 4,80,000 | 59.4% | Both in band (casual-dine 30–35% / 52–60%) |
| Feb | 5,40,000 | 31.8% | 5,00,000 | 61.2% | Yellow — labour creeping |
| Mar | 5,80,000 | 34.1% | 5,30,000 | 65.3% | Red — both moving |
| Apr | 5,60,000 | 32.9% | 5,50,000 | 65.3% | Labour worse, COGS partially fixed |
| May | 5,30,000 | 31.2% | 5,60,000 | 64.1% | COGS recovered, labour stuck |
Reading the trend:
- Jan → Feb: Labour started drifting. If only prime cost was tracked, the operator would suspect kitchen or labour without knowing which. Tracking both tells them it's labour.
- Feb → Mar: A spice supplier hike pushed COGS up 2 points. The operator can act on COGS specifically (renegotiation, supplier swap) without confusing it with the labour issue.
- Mar → May: COGS recovered after supplier renegotiation. Labour stayed stuck because no rostering action was taken.
In May the operator knows exactly where to spend Sunday evening — on the roster, not on the storeroom. Without both metrics, the diagnostic clarity isn't there.
Tracking both without doubling the work
The numbers share most inputs. Set up the sheet once.
Inputs (you collect):
Net sales (food, pre-GST, post-aggregator)
Opening stock (food + bev at cost)
Purchases (food + bev at cost)
Closing stock (food + bev at cost)
Wages (kitchen + service + cleaning)
PF + ESI + bonus accrual
Manager salary (allocated)
Staff meals (at cost)
Outputs (computed):
COGS = Opening + Purchases – Closing
COGS % = COGS / Net sales
Total labour = Wages + PF/ESI + Manager + Staff meals
Prime cost = COGS + Total labour
Prime cost % = Prime cost / Net sales
Eight inputs, five outputs, one sheet. Updated on the first of every month after closing stock count and payroll close. Total time: 30–45 minutes including the count.
What to compare against — your trend, not someone else's number
The benchmarks below are useful as outer brackets, but the real comparison is your own outlet's trend. A casual-dine running consistently at 33% COGS / 56% prime cost is healthier than one swinging between 28% and 35%.
| Format | COGS % target | Prime cost % target |
|---|---|---|
| QSR / cloud kitchen | 28 – 33% | 48 – 56% |
| Casual dine | 30 – 35% | 52 – 60% |
| Fine dine | 32 – 38% | 60 – 68% |
| Bar / pub | 22 – 30% (food + bev blended) | 48 – 58% |
Track three things:
- Absolute level vs target band.
- Three-month rolling average — smooths out month-end stock-count noise.
- Variance vs prior month — anything above 2 points either direction is a flag to investigate.
Where operators conflate the two
Three confusions show up regularly:
1. "Food cost" used loosely
Some operators say "food cost" to mean COGS %; others mean it as kitchen-only labour + COGS; some include packaging. Be specific in your sheet. The operator's vocabulary matters less than the consistency of the calculation.
2. Aggregator commission moved between COGS and labour
Aggregator commission is neither COGS nor labour. It's a sales reduction — net it from gross sales to get net sales, then COGS and labour are on a clean denominator. Booking it as COGS inflates COGS %; booking it as labour inflates labour cost %. Both lie.
3. Owner draw inside labour
If the owner is operationally in the kitchen or on the floor, allocate a fair operational salary into labour. If the owner is purely a capital provider, owner draw stays out of labour. Mixing the two is the single biggest distortion in single-outlet P&Ls.
When COGS and prime cost agree — and when they don't
In a stable outlet, COGS and prime cost move together — both up in a cost-pressure month, both down in a high-sales month. When they diverge, you have a specific signal:
| Divergence | What it means |
|---|---|
| COGS up, labour flat | Vendor or yield issue |
| COGS flat, labour up | Roster or PF/ESI catch-up |
| COGS down, labour up | Mid-month staff hire absorbed before the kitchen efficiency caught up |
| COGS up, labour down | Possible service understaffing — check complaint rate |
Each divergence has a short list of causes. Knowing which side moved tells you which two or three things to investigate, instead of opening every drawer in the back office.
A note on the 60% rule
You'll see "60% prime cost rule" in restaurant operations literature — the idea that prime cost above 60% is a danger zone. In Indian casual-dine, that's roughly the upper edge of the target band. In QSR it's slack — 60% is already too high. In fine dine it's low — 60% is the lower edge. Use format-specific bands, not a universal 60.
What to do this month
- Close the books for last month with closing stock and payroll done by the 3rd.
- Compute COGS, COGS %, prime cost, prime cost % on your sheet.
- Compare each against the format target band.
- If both in band — look at occupancy and contribution per cover next.
- If only one out of band — apply the diagnostic table above and pick the single right action.
- If both out of band — fix COGS first (yield, count, supplier) for 30 days, then attack labour.
The discipline of tracking both is the single highest-yield monthly habit an Indian restaurant operator can build. The sheet takes 45 minutes. The clarity lasts the month.
Related on Restaurant Daily
One operator playbook a week, in your inbox.
Cash close, petty cash, payroll, compliance, unit economics — sent every Monday morning. No spam, no upsell drip. Unsubscribe in one click.
Sent from noreply@restaurantdaily.ai. We never share your address.
Related reading
Food cost percentage restaurant India — targets by format (QSR, casual, fine)
Food cost percentage benchmarks for Indian restaurants by format — QSR, casual dine, fine dine, bar, cloud kitchen — plus how to measure it correctly and where leakage hides.
Restaurant prime cost calculator India — formula + free worksheet
Restaurant prime cost calculator for India — formula, target bands by format, a worked example in INR, and a download-ready worksheet covering food cost + labour cost.
Occupancy cost restaurant India — rent, CAM, electricity benchmarks by city
Occupancy cost in Indian restaurants — rent, CAM, electricity benchmarks by city tier, what to negotiate at lease signing, and how to keep occupancy in the green band.
Menu engineering matrix for Indian restaurants — Stars, Plowhorses, Puzzles, Dogs
Menu engineering for Indian restaurants — Stars, Plowhorses, Puzzles, Dogs explained with a free template, worked example, and an action playbook for each quadrant.
Restaurant unit economics India — the full guide from prime cost to payback
Restaurant unit economics India — the full guide from prime cost and breakeven to four-wall EBITDA, contribution per cover, and payback period, with worked examples in INR.