Inventory Without the Chaos: Weekly Partial Counts Instead of Once a Quarter

It's a familiar picture: once a quarter the restaurant closes for a night or a whole day, the entire team counts jars, sacks and bottles, and in the morning you discover a shortage worth a painful sum. Where did it come from over three months? Nobody remembers. A delivery that wasn't fully checked? Extra grams on every plate? A write-off nobody recorded? The trail is cold.

The problem isn't your people, it's the interval. The less often you count, the more each discrepancy costs: the cause is forgotten and the amount has piled up. The fix is to count a little, often.

Why a full quarterly count fails

• Too late. A three-month gap can't be tied to a specific shift or delivery.
• Too heavy. Recounting the entire storeroom in one go takes hours, so it's done in a rush, and the counting itself becomes error-prone.
• Too rare to act on. A food cost figure you learn once a quarter can't steer purchasing or pricing.

How a partial count works

The idea is simple: split the storeroom into groups and check only one part each week. You don't close the kitchen. A count takes 20–40 minutes before opening or after closing.

Step 1. Rank items by importance

1. Group A, expensive and fast-moving: meat, fish, cheese, alcohol. Count weekly.
2. Group B, mid-value: vegetables, dairy, dry goods. Count every two weeks.
3. Group C, cheap small items: spices, disposables, salt. Monthly is enough.

Step 2. Count at the same time every time

The best moment is before opening, when nothing is moving. If you count mid-service, the numbers drift simply because something has already gone to the line.

Step 3. Compare the actual to the book balance

A discrepancy is the difference between what the system expects (deliveries minus sales through recipes minus write-offs) and what's on the shelf. It comes in two kinds: shortage (less on the shelf) and surplus (more on the shelf). A surplus is a signal too, such as a wrong recipe card or a delivery that was never posted.

Step 4. Investigate immediately

While it's been a week, not a quarter, you can still find the cause. Ask three questions:

• Were all of this week's deliveries posted and received by actual weight?
• Was every write-off (spoilage, expiry, staff meals, tastings) documented?
• Does the portion weight on the recipe card match what the cook really plates?

An illustrative example

Say the books show 12 kg of beef, but the shelf holds 10.5 kg. That's a 1.5 kg shortage. You check the week's deliveries: one was accepted without weighing. Another cause: a cook adds 15 g more per portion than the recipe says. Without the weekly check, those two small things would quietly become a quarter's worth of loss. With it, you fix the process next Tuesday.

Rule of thumb: the shorter the gap between counts, the easier it is to find the cause of a discrepancy and the less it costs.

Making it a habit

• Assign an owner to each group and weekday.
• Use a prepared count sheet that follows the order of the shelves, which makes counting faster.
• Record discrepancies in writing and revisit them at the next count.
• Don't punish every small gap. The goal is to find systemic causes, not a culprit.

How RestIQ makes this easier

In RestIQ, stock counts run with barcode scanners, tablets or printed count sheets. The system detects discrepancies, both surplus and shortage, levels the balances and generates a write-off act. The book balance is built from deliveries, recipe-based sales and write-offs with reason codes, so reconciliation takes minutes. More in the Inventory Control section.

Conclusion

A partial count isn't extra work, it replaces one heavy procedure with several light ones. You see losses sooner, find causes faster and get a real food cost instead of a quarterly guess. Try RestIQ: 14 days free.