Inventory control: exact definition, formula, and before-after with Masterestaurant

Restaurant inventory control: the complete guide

How do you do inventory in a restaurant?

You do restaurant inventory by counting every item in its purchase unit, always in the same order, at the same time and with the kitchen closed, and valuing it at the last price paid.

Order matters: a count sheet organized by storage area (walk-in, freezer, dry storage, bar) that follows the physical path prevents missed and double-counted items. Ideally two people count, one counting and one recording, and the result is compared right away with the theoretical usage that sales in your POS system imply. A count that gets filed without being compared to anything is a snapshot, not control.

Restaurant inventory control methods: FIFO, ABC analysis and par levels

Three methods hold up almost any kitchen inventory control. FIFO, first in, first out, organizes storage so that what arrived first is used first, which cuts spoilage. ABC analysis recognizes that a handful of items make up most of your inventory value: those, the A items, get counted every week, and the rest less often. Par levels set a minimum and a maximum for each item, so every order is calculated to bring stock back to par instead of being eyeballed. Together they turn inventory from a month-end event into a routine you can delegate.

Restaurant inventory in a spreadsheet or in software

A single-unit restaurant with a short item list can run inventory control in a well-built spreadsheet, as long as the weekly count is entered and compared with theoretical usage. Inventory management software connected to the POS pays off when there are many items, several locations or recipes that change often, because it calculates theoretical usage automatically and flags the variances. Either way, the process decides the result: spot counts, controlled receiving, logged waste and someone accountable for explaining every variance. Expensive software without that process just measures the same mess faster.

Food waste: the part of inventory that hides the most money

Waste is food you bought that never reached a guest: it expired, it was spoiled during prep, it was left over from overproduction or it came back from the dining room. Between 4% and 10% of the food a restaurant buys is wasted before it reaches the plate, according to The Restaurant HQ. That is why good inventory control logs waste by cause at the end of every shift, on a simple sheet next to the scale, and gives it its own line on the P&L. Once waste has a name, a cause and an owner, it stops hiding inside food cost and can be reduced with specific actions.

Restaurant inventory sheet: the columns it needs

A useful restaurant inventory sheet lists, for every item: name and spec, purchase unit, storage location, beginning count, purchases for the period, ending count, unit cost, inventory value, actual usage and theoretical usage based on sales. The last column, the variance between the two, is what turns a count into control. Masterestaurant publishes a ready-to-use restaurant inventory template that works as the tool to start this routine. Whatever format you use, fill it in the same way every time and write down an explanation for every large variance.

What inventory control means in a kitchen?

Inventory control is the system that measures the gap between what cost SHOULD have been to deliver your sales (theoretical cost) and what cost ACTUALLY was (observed cost), expressed as a percentage.

It is not counting what sits on your shelf on a Friday at three — that is a spot audit. Control is the ongoing equation your monthly close runs: you record everything in (purchases), everything out (registered sales plus waste), and verify whether the math matches what remains physically. When it doesn't match, that difference is your leak, and fixing it takes eight to fifteen weeks of systematic work because the problem has been piling up unseen for four to eight weeks already. According to Masterestaurant, this reconciliation in your kitchen is what ties actual profitability to what you report on paper.

How it works: the concrete cash number?

A restaurant posts €10,000 in sales one month. For example, if your recipe standard says selling that should cost a set amount in ingredients (theoretical cost), the gap only shows up once you count.

For example, at month-end close, you count the shelf: a given amount in purchases came in, a portion went out (waste and registered adjustments), and the rest remains on hand. The equation is: Beginning inventory + Purchases − Ending inventory = actual outflow. But your registered sales promised a lower cost. The leak is the difference between actual outflow and registered cost, expressed as a share of sales. That gap is what you hunt for in operations: where food hit the trash without a ticket, where a dish was remade off-book, where something spilled or went to staff. Control numbers the problem so it becomes fixable; without it, you only know «something is broken».

Why it gets confused with counting: the conceptual mistake everyone makes?

Seventy-three percent of restaurants claiming they control inventory actually confuse it with «doing a count»: you walk to storage, write what you see, done.

A count is a snapshot, a still frame one Friday at three; control is video of the whole month. Counting needs you to stop service (close the kitchen, lose ticket sales that day) and only surfaces a problem already four or five weeks old — takes hours, costs throughput, always arrives too late. Control wired into your POS and month-end close costs fifteen to twenty minutes of daily management, does not interrupt service, and prevents your leak from growing because it surfaces it week by week. A count is what an outside auditor does when you already distrust your numbers; control is what keeps you from needing to distrust them because the close balances every month.

The piece no one builds: unregistered losses

For example, your recipe says one pasta plate costs a set amount in ingredients. For example, you sell it at a set price, registered in your POS. But that day one portion burned and went to waste with no ticket, and your inventory shows that ingredient left the shelf when no sale accounted for it. Inventory control CATCHES that loss because the equation breaks: flour came in for X portions, N portions registered as sales, but the shelf shows more flour left than those N plates consumed. Unregistered losses (waste, spillage, comp plates, seconds at no charge, chef tastings) run two to five percent of sales in normal operations according to Masterestaurant — money gone because nobody numbers it. An inventory control system is the only thing that makes them visible.

Speed of correction once you detect it

A restaurant leaking a share of sales each month (for example, if monthly sales are a set amount, a portion of that vanishes every month) takes several weeks to normalize because the fix is operational, not paperwork. You need to retrain kitchen staff on portions, supervise waste more closely, fix your storage (spills drop when everything is labeled and within reach), sometimes rewrite your recipe if it is unrealistic for your kitchen's pace. But once you attack the leak with data in hand («we lose money every month»), the correction is direct because you know where to look. Without control, you guess: «maybe it is payroll» or «maybe we sell less», and waste two more months seeing nothing improve. A detected leak recovers; an invisible one piles up until the business stops closing.

Practical difference: control versus counting in a real case

An eighty-cover restaurant, Italian kitchen, five cooks. Payroll stays within the normal range for full service per NRA 2024. Month one shows control data revealing a loss in ingredients off-book. Owner calls for emergency count: shuts kitchen early, takes several hours, finds missing rice, pasta, tomato — «someone took it or we threw it without ticket». But control already numbered the problem live, week by week. If instead of emergency close the owner had reviewed the system every Thursday (a short check), the leak would have surfaced early when the damage is fixable by tweaking portions or supervision, not later when it becomes a personnel integrity question. Control lets you make micro-corrections; counting forces an operational crisis.

What separates inventory control from just counting?

COUNTING is a one-time act: you look at the shelf on Friday and note what's there. CONTROL is a continuous system: every purchase, sale, and discard feeds into an equation that closes monthly.

Counting is a snapshot; control is the video. An audit finds money missing; control stops it from going missing in the first place by tracking WHERE it goes week by week. Counting stops operations (kitchen closure, lost sales). Control runs without pause: it's built into point-of-sale, receiving, and cash closing. One audit costs 3-6 hours of labor and detects a problem already 4-8 weeks old. Control takes 15-20 minutes of daily management and prevents the problem from growing. Counting dates the past (what happened last week). Control dates the present and allows REAL-TIME action: if Tuesday you spot missing expensive ingredient, Wednesday you switch supplier or adjust recipe.