DEV Community

Hive80-lab
Hive80-lab

Posted on Originally published at hive80-lab.github.io

The Food Cost Percentage Tracker — The Friday Count That Tells You Where the Money Actually Goes

One page, ten minutes, every Friday: beginning inventory, purchases, ending inventory, food sales — one ratio that tells you whether a busy week made money or just moved it around. Food cost percentage is not paperwork; it is a leak detector. The count does not tell you what to cut. It tells you where to stand when you go looking.

Most independent restaurants run blind on food cost. The POS says sales were great, the bank account says the money never arrived, and the gap between those two facts is eating the business one over-portioned plate at a time. The tracker on this page closes that gap: a weekly ratio, a theoretical number from the recipes, and an investigation order for the weeks when the two disagree. It is the money-side twin of the refrigeration temperature log — the log keeps the stock alive, this one keeps the stock profitable.

The only math on the page

Food Cost % = COGS ÷ Food Sales × 100. That is the entire formula, and every argument about it is really an argument about the two inputs:

  • COGS = beginning inventory + purchases − ending inventory, all valued at current invoice prices (last cost, not what you paid in March — you will replace stock at today's price, so today's price is the honest one).
  • Food sales = POS food revenue for exactly the same window as the inventory window. A count from Friday to Friday with sales from Sunday to Saturday is not a ratio, it is a coincidence wearing a ratio's clothes.

Targets by service style: 25–30% for fast casual and QSR, 28–32% for full service — the number is a directional instrument, not a tax form. A point of food cost on $41,000 of monthly food sales is $410 a month. Four points is the profit.

The sheet — ten minutes, every Friday

One count sheet, one row per storage area (walk-in, reach-ins, dry store, freezer), four columns:

  • Beginning value — last week's ending value, carried forward. Never recounted; the carry-forward is what makes the weeks comparable.
  • Purchases — the week's food invoices, totaled. This is why the delivery receiving check matters before the math ever starts: a short weight accepted at the door is a leak the count will eventually find, but only after it has been leaking for a week.
  • Ending value — the Friday count. Same areas, same order, same person if you can get them.
  • Sales for the window — food only, from the POS.

The theoretical vs actual gap

The theoretical food cost is what your recipes should cost. The actual is what the count says you did cost. The gap between them has an address:

  • 1–2 points: normal kitchen friction — trim, over-portioning at the pass, staff meals. No investigation.
  • 2–3 points: forming. Portion audit on the five highest-volume plates, waste sheet review.
  • 3+ points: emergency. Walk the storage areas with the count sheet in hand the same day.

Worked example — the 40-seat restaurant

Week 32: the tracker reads 34.1% actual against a 29.6% theoretical — a 4.5-point gap on $41,000 of monthly food sales, ≈$1,845/month. The investigation order puts a dollar figure with an address:

  • Portions: burger patty drift of .5 lb ≈ $620/month. Fix: one scale at the grill station, one line on the prep list.
  • Waste sheet: $710 of spoilage in a week, most of it produce spoiling behind the leaking walk-in door gasket — the same door the Sunday cooler walk had flagged. Fix: the $45 gasket and a smaller produce par. ≈$700/month recovered.
  • Comps: the POS void report shows 62 unapproved voids in the week. Fix: manager code on voids, reviewed in the weekly ops review. ≈$400/month.

Six weeks later the tracker reads 30.9% — not the theoretical 29.6%, and that is fine; the remaining 1.3 points are the honest cost of running a real kitchen. The tracker's job was never zero. Its job was to make the leak visible while it was still a $30 scale problem instead of a $22,000 year.

5 traps (the ones that make the number lie)

  1. Counting monthly. A month is four weeks of drift averaged into one number — by the time the month-end count screams, the leak has a lease. Weekly, ten minutes.
  2. Pricing inventory at old cost. Valuing stock at what you paid in March while prices moved in August understates COGS and flatters the percentage until the cash is gone. Last invoice price, always.
  3. Mismatched windows. Inventory Friday-to-Friday with sales Sunday-to-Sunday invents a phantom week. The ratio is only true if both inputs cover the same seven days.
  4. The dead theoretical number. Plate costs from a menu that changed last spring make every actual look guilty. When the menu changes, twenty minutes of recipe costing — or the gap means nothing all year.
  5. Worshipping the percentage. 30% of a $12 salad is $3.60; 28% of a $30 steak is $8.40. Percentages steer; margin dollars pay rent. Track the ratio, decide on the dollars.

Related: the gross margin pricing review is what a stable food cost licenses; the price increase announcement is what you send when the count says inputs moved; the monthly close checklist is the month-end tie-out that keeps the weekly numbers honest.


Every page ships with a kit block — the paid tools behind the free advice:

Code HIVE-LAUNCH30 takes 30% off any kit at checkout.

Top comments (0)