A restaurant food cost spreadsheet is useful when it connects three things: what ingredients cost, how much each recipe uses, and what inventory actually moved. Tracking only one of those gives you a number, but not much explanation.
Ingredient cost comes first
Every recipe calculation depends on a clean ingredient cost. Record the vendor pack cost and convert it to one consistent base unit such as ounce, pound, each, milliliter, or gram.
If a $40 case contains 160 ounces of usable product, the base cost is $0.25 per ounce. That base-unit cost is what the recipe sheet should reference.
Changing pack sizes without updating the quantity inside the pack is one of the easiest ways to quietly break a costing spreadsheet.
Recipe cost should use actual quantities
For each dish, list the quantity of every ingredient used and multiply it by the ingredient's base-unit cost. Add those lines together for recipe cost.
Then compare recipe cost with selling price. The basic food-cost percentage is Recipe Cost ÷ Selling Price.
A low percentage is not automatically a good menu item and a high percentage is not automatically bad. Portion size, popularity, labor, waste, and contribution dollars still matter. The spreadsheet gives you a starting point for the decision.
Inventory explains what recipe costing cannot
Recipe costing shows what food should cost. Inventory usage helps show what the operation actually consumed.
A simple usage calculation is Beginning Inventory + Purchases − Ending Inventory. Multiply quantities by current unit costs to put a dollar value on that movement.
If actual usage keeps climbing while sales stay flat, look at waste, portion control, receiving errors, unrecorded transfers, staff meals, or incorrect counts before assuming menu prices are the only problem.
Count consistently
Inventory data gets much more useful when counts happen at roughly the same point in the operating cycle. Counting before one week's delivery and after the next week's delivery makes the comparison noisy even if the kitchen did nothing wrong.
Use the same units, the same storage order, and the same basic counting rules every time.
Make the sheet tell you what needs attention
A practical workbook should do more than store counts. Reorder points, low-stock flags, estimated order spend, recipe food-cost percentage, inventory value, and a short KPI summary turn raw rows into decisions.
Keep the system lightweight. A spreadsheet works well for a small operation when one person can maintain the item list, pricing is updated regularly, and staff use consistent units. Once locations, vendors, recipes, and purchasing become too complex to keep current, dedicated inventory software may be a better fit.
If you want a ready-to-edit workbook that ties ingredient costs, recipe costing, inventory, reorder flags, and an order guide together, see the Restaurant Food Cost & Inventory Tracker. The Kitchen Manager Pro Bundle adds prep, closing, shift logs, maintenance, and manager KPI tools.