· Orqestra Team · 7 min read

Restaurant Inventory Spreadsheet: Free Count Sheet Template

A free restaurant inventory spreadsheet and count sheet template with the columns you need, weekly count steps, the usage formula and a worked example.

A restaurant inventory spreadsheet is a count sheet with one row per item and seven columns: item, unit, par, on hand, unit cost, extended value, and reorder quantity. You walk the storage areas once a week, write down what is on hand, and the sheet tells you what your stock is worth and what to order. The same sheet, counted at the same time each week, is what lets you calculate real food usage and food cost.

You can download the sheet described below as the restaurant inventory count sheet template. This article explains the layout, the weekly routine, the formulas, and the mistakes that make counts useless.

The count sheet layout

Keep the sheet simple. Seven columns are enough for a one to three location restaurant. Every extra column slows the count and gets skipped by week three.

ColumnWhat goes in itExample
ItemThe name your kitchen uses, not the vendor's codeChicken thighs
UnitThe unit you count in, written once and never changedCase (40 lb)
ParThe amount you want on hand right after a delivery4
On handWhat you counted this week, in the same unit1.5
Unit costThe latest invoice price for one unit$78.00
Extended valueOn hand × unit cost$117.00
Reorder qtyPar minus on hand, rounded up to a whole unit3

Two formulas drive the sheet:

  • Extended value = On hand × Unit cost
  • Reorder quantity = Par − On hand (if the result is zero or negative, order nothing)

Group rows by storage area in the order you walk it: walk-in, reach-ins, dry storage, bar, then paper goods. That order matters more than alphabetical order, as the next section explains.

If you have not set pars yet, start with last week's typical usage plus a small buffer, then tighten them. The par levels guide walks through the formula.

How to do the weekly count

Follow these steps every week. The count only becomes useful when it is consistent, so the routine is the product, not the numbers from any one week.

  1. Pick a fixed day and time, after close or before the first delivery. Restaurant365's store-level inventory guide puts it plainly: counting "consistently on the same day at the same time can generate useful, comparable numbers" (Restaurant365).
  2. Receive and put away every delivery before you start. A pallet on the floor during the count gets counted twice or not at all.
  3. Arrange the sheet shelf to sheet. The rows on the page follow the shelves in the room, left to right and top to bottom, so you never backtrack or hunt for an item.
  4. Count in the unit on the sheet. If the unit says case, count cases and fractions of a case. Do not switch between pounds one week and cases the next.
  5. Use the same person, or the same pair, every week. One counts, one writes. A different counter each week introduces more variance than real usage does.
  6. Do not move product while counting. Counting is not the time to reorganize the walk-in.
  7. Fill in unit costs from the most recent invoice, then let the sheet compute extended value and reorder quantity.
  8. Total the extended value column. That total is your ending inventory for the week.

A full count of 150 to 250 items takes a trained pair around 45 to 90 minutes once the sheet matches the shelves. Most of the time saved comes from step 3.

How often to count

Weekly is the standard. In a Backbar survey of 11,240 restaurant and bar workers, weekly was the most common cadence at 52%, with monthly second at 26% (Backbar). MarketMan's count schedule guide recommends a tiered approach: daily or per-shift counts for beef, seafood, poultry and premium liquor, a weekly full count of proteins, dairy, produce and prepped items, and monthly counts for canned goods, dry goods, oils and paper (MarketMan).

A weekly full count is the one to protect. The daily spot checks on expensive proteins are an add-on once the weekly routine is stable.

How to compute inventory value and usage

Inventory value is the total of the extended value column. Usage (what you actually consumed, wasted, or lost) comes from two consecutive counts plus the invoices between them.

  • Ending inventory = sum of (On hand × Unit cost) across all rows
  • Usage = Beginning inventory + Purchases − Ending inventory
  • Food cost % = Usage ÷ Food sales × 100

Beginning inventory is last week's ending inventory. Purchases are all food invoices dated between the two counts. This is the actual food cost, as opposed to the theoretical cost built from recipes, and the gap between the two is where waste, over-portioning and theft show up. The food cost percentage guide covers the full calculation and targets.

Worked example: seven items, one week

Here is a filled-in slice of the sheet for a single-location Indian restaurant doing about $88,000 a month in sales. The count was taken Monday at 8 a.m., before the Monday produce delivery.

ItemUnitParOn handUnit costExtended valueReorder qty
Chicken thighsCase (40 lb)41.5$78.00$117.003
Basmati rice20 lb bag64$22.50$90.002
Paneer5 lb block83$19.00$57.005
TomatoesCase (25 lb)32$28.00$56.001
Heavy creamQuart2415$3.40$51.009
Cooking oil35 lb jug31$42.00$42.002
Yellow onions50 lb sack20.5$24.00$12.002
Total$425.00

Notes on the arithmetic:

  • Chicken: 1.5 × $78.00 = $117.00 extended. Reorder is 4 − 1.5 = 2.5, rounded up to 3 cases because the vendor sells whole cases.
  • Onions: 0.5 × $24.00 = $12.00. Reorder is 2 − 0.5 = 1.5, rounded up to 2 sacks.
  • Heavy cream: 15 × $3.40 = $51.00. Reorder is 24 − 15 = 9 quarts, no rounding needed.

Now the whole sheet, not just these seven rows. Suppose the full count totals come out like this:

  • Last Monday's ending inventory (this week's beginning): $4,860
  • Food invoices received during the week: $6,240
  • This Monday's ending inventory: $4,920
  • Food sales for the week: $20,400

Usage = $4,860 + $6,240 − $4,920 = $6,180.

Food cost % = $6,180 ÷ $20,400 × 100 = 30.3%.

If the theoretical food cost from your recipes was 27.5%, the 2.8 point gap on $20,400 of sales is about $570 of product that week that did not turn into a sale. That number is why the count is worth 90 minutes on a Monday morning.

Once pars and counts live in software instead of a printed sheet, the reorder column turns into a purchase list and the usage math runs itself. The inventory feature in Orqestra does this against the same count structure shown above.

Why the count matters beyond ordering

Food that is bought and not sold is the biggest controllable cost in the building. ReFED's 2023 figures put US surplus food at 73.9 million tons, or 31% of the food supply (ReFED). That is a national number across the whole food system, not a restaurant-only figure, but the mechanism is the same in your walk-in: over-ordering, spoilage and prep waste all show up as usage without matching sales. A weekly count is the only way to see it before the month-end statement does.

Common mistakes

  • Changing units between counts. Pounds one week and cases the next makes the usage number meaningless. Fix the unit on the sheet and leave it.
  • Counting during service. Product is leaving the shelf while you count it. Count when the kitchen is closed.
  • Counting before putting deliveries away. Items on the receiving floor get double counted or missed.
  • Skipping the unit cost update. An extended value built on prices from three months ago understates inventory and distorts usage. Pull the latest invoice price each week.
  • Rotating the counter. Different people count open cases, partial bags and prepped containers differently. Keep the same person or pair.
  • Rounding reorder quantities down. If par minus on hand is 2.5 cases, order 3. Ordering 2 means running out before the next delivery.
  • Treating the sheet as the order. The reorder column is a starting point. Check it against the next week's events, catering orders and the weather before sending the order.
  • Not totaling the sheet. The count exists to produce an ending inventory number. If nobody adds up the extended value column, there is no usage, no food cost, and no reason to have counted.