Revenue looks great until you pay suppliers. Food cost percentage—ingredient cost divided by food sales—tells you if menu pricing and portion control still work. For fast food, aim to know this weekly, not at year-end when the damage is done.
This guide covers the formula, realistic targets, how POS recipe data helps, and what to do when your percentage drifts above baseline.
The simple formula
Food Cost % = (Opening inventory + Purchases − Closing inventory) ÷ Food sales × 100. Target ranges vary by concept—burgers and fries often land 28–35% when operations are tight. Pizza with high cheese cost may run higher; beverages sold separately can improve blended margin.
Why weekly beats monthly
Monthly averages hide bad weeks. A supplier price jump, portion creep, or theft spike can burn margin for twenty days before anyone notices. Weekly snapshots with the same count methodology make drift visible while you can still fix it.
How POS and recipes help
- Recipe cards per menu item with ingredient quantities
- Theoretical usage vs actual stock variance reports
- Top sellers ranked by profit, not just revenue
- Deal and discount impact on margin visible before you launch promos
Menu engineering beyond the star items
Your bestseller might be a margin killer if protein portions grew quietly. Rank items by contribution margin—price minus true food cost—not popularity alone. Sometimes the number-two seller funds the marketing hero.
Portion control in the kitchen
Scales and ladles beat eyeballing during rush. Train line cooks on standard weights; spot-check randomly. A ten-gram overrun on protein across four hundred covers is real money.
When food cost spikes
Check price changes, waste logs, comp/discount abuse, unrecorded staff meals, and recipe drift first. Then compare channels—delivery promos often carry higher food cost if packaging and free sides are included.
EatsDesk and margin visibility
EatsDesk ties menu sales to inventory consumption so managers see which items erode margin and which modifiers save the ticket. That visibility turns food cost from a finance mystery into a weekly ops meeting agenda.
Putting it into practice
Pick one bottleneck this week, measure it for seven days, then change one control—modifiers, handoff rules, or reporting cadence. Restaurants that improve fastest run tight feedback loops, not annual overhauls.
Export a weekly top-twenty items report ranked by margin—not revenue—and discuss one change per meeting.
When supplier prices rise, update recipe costs the same day so menu decisions use current data.
Labour and rent matter, but food cost is the lever kitchen touches daily. A one-point improvement on Rs 2,000,000 monthly food sales is real money—track it visibly.
Combo deals need margin math before marketing launches them. A popular bundle that loses money on every ticket is a volume trap.
Vendor substitutions during shortages should trigger temporary recipe cost updates. Using premium oil for a week without repricing skews the month.
Operational detail worth getting right
Compare food cost by channel if packaging and free sides differ on delivery. Blended averages hide delivery promos eating margin.
Operators who treat technology as a daily habit—not a one-time install—see compounding returns. A ten-minute morning review of yesterday's voids, stock alerts, and delivery delays prevents the fire drills that ruin guest experience during tonight's peak.
Training is the multiplier on every feature you buy. POS buttons nobody uses, KDS screens nobody bumps, and reports nobody opens are indistinguishable from not having software at all. Short pre-shift huddles that reference real data beat lengthy manuals staff never read.
Guest expectations keep rising even when your margins feel squeezed. Faster replies, clearer modifiers, and accurate bags are no longer premium service—they are the baseline that earns repeat orders and five-star reviews on busy weekends.
Operational detail worth getting right
When counter, kitchen, and delivery share one ticket path, managers stop mediating between systems. That coordination tax shows up as remakes, late riders, and owners stuck on the floor instead of growing the brand.
Document one standard for each handoff—counter to kitchen, kitchen to expo, expo to rider—and review it when error rates spike. Most ops problems are broken handoffs, not broken recipes.
Seasonality, school holidays, and local events shift volume faster than annual budgets predict. Weekly dashboards let you staff and prep for next Friday instead of reacting to last Friday.
Direct channels you control—website, WhatsApp, QR—compound when CRM remembers who ordered. Aggregators rent you traffic; owned channels rent you nothing once the guest saves your link.
Operational detail worth getting right
Security and permissions matter even for small teams. Shared admin passwords and unaudited discount overrides create losses that look like shrink until someone reads the audit log.
Frequently asked questions
What is a good food cost percentage for fast food?
Many QSR concepts target 28–35% food cost, but your ideal number depends on rent, labour, and average ticket. Track your own baseline.
Should beverages be included?
Some operators track food and beverage cost separately. Be consistent week to week so trends mean something.
How do discounts affect food cost percentage?
Discounts lower sales in the denominator, which can inflate food cost % even when waste is flat. Review promo impact before extending deals.
Can I calculate food cost without inventory software?
Yes manually, but POS-linked recipes and automatic deduction reduce errors and save hours.
What is theoretical food cost?
Expected cost based on recipes and sales mix. Comparing theoretical to actual reveals portion issues, waste, or unrecorded usage.