Operations

Inventory Cycle Counting

Cycle counting is a stock-checking method that counts a different portion of products each day or week, instead of carrying out a full periodic stocktake. It reduces errors and frees up operational time.

Full definition

Cycle counting is an inventory control methodology that consists of physically checking a fraction of the stock on a continuous, rotating basis, instead of carrying out full periodic stocktakes that bring operations to a standstill. In a typical restaurant with 150–200 product lines, a full weekly stocktake takes 4–6 hours of work and tends to get pushed back to the end of the month, leaving whole weeks without any real control. Cycle counting solves this by splitting the inventory into groups that are counted on different days according to a set schedule. The most effective way to implement cycle counting is to combine it with ABC analysis: category A products (high value — 15–20% of lines but 80% of cost) are counted weekly or even twice a week; B products (medium value) every fortnight; and C products (low value) monthly.

That way, a small group of products is counted each day (15–30 minutes of work), but the critical products are checked frequently. Cycle counting has several advantages over the traditional periodic stocktake: it detects errors and variances much sooner (days instead of weeks), it does not require stopping operations to count everything, it spreads the workload over time, it keeps the team focused on stock control as an ongoing activity (not a one-off event), and it produces more reliable data for calculating actual food cost. To work, cycle counting needs discipline: a clear schedule of what to count each day, a named person responsible, a recording system (ideally digital) and an investigation process when the physical count differs from the theoretical one. Typical variance tolerances are 2–3% for A products, 5% for B and 10% for C; larger variances should be investigated immediately.

Formula

Counting frequency = Value/criticality of the product according to ABC classification

Explanation

Cycle counting is planned by assigning counting frequencies according to each product's ABC classification. A typical set-up is: A products (20% of lines, 80% of value) are counted every week, which means that if you have 30 A products, you count about 6 a day (30 ÷ 5 working days). B products (30% of lines, 15% of value) are counted every 2 weeks, so 45 B products are counted at around 4–5 a day. C products (50% of lines, 5% of value) are counted monthly, about 75 products at around 3–4 a day.

The result: each day you count 13–15 products (6 A + 4 B + 4 C), a 20–30 minute process compared with 4–6 hours for a full stocktake. The formula for daily counts is: (Products in the category / Frequency in days) = products of that category to count each day. For example: 25 A products ÷ 7 days = 3–4 A products a day.

Worked example

Your restaurant has 160 product lines. After ABC analysis you have: 25 A products (meat, fish, premium olive oil, main cheeses), 50 B products (vegetables, dairy, pasta, rice, main wines) and 85 C products (spices, condiments, small items, cleaning products). You implement cycle counting with the following schedule: A products (25): weekly count = 5 products a day, Monday to Friday. B products (50): fortnightly count = around 3–4 products a day.

C products (85): monthly count = around 4 products a day. Daily total: 12–13 products, about 25 minutes of the head chef's time each morning before service. In the first week, the cycle count reveals that 2 kg of sirloin is missing compared with theoretical stock (value: €56). You investigate and discover that a cook has been portioning 200 g instead of 180 g.

You correct it immediately. With the old monthly stocktake, you would have lost 8 weeks of over-portioning (about €450) before spotting it.

Why does it matter?

Cycle counting turns inventory control from a stressful, infrequent event into a continuous, manageable process. Restaurants that only do a full stocktake at the end of the month have a huge blind spot: any error, theft, excessive waste or portioning problem can build up for weeks before it is detected. By the time the variance is finally discovered, it is too late to work out exactly what happened and the money is already gone. With cycle counting, variances are detected in days, not weeks.

This has a direct impact on profitability: industry studies estimate that restaurants using cycle counting have 40–60% smaller inventory variances than those relying only on periodic stocktakes. Cycle counting also improves the accuracy of purchasing forecasts (because theoretical stock is more reliable), reduces stock-outs (because discrepancies are spotted earlier) and builds a culture of accountability for stock across the whole team. Combining cycle counting with ABC analysis is especially powerful: it focuses control effort where it really matters (high-value products) without wasting time constantly checking products with little economic impact.

How does Zindra help?

Zindra automatically generates the cycle counting schedule based on the ABC classification of your products. Each day it shows which products need counting, records the results, compares them with theoretical stock and alerts you immediately to any variance outside tolerance so you can investigate before losses build up.

Download the complete dictionary

Every hospitality term with formulas, examples and benchmarks in a handy PDF.

Want to run your restaurant on data?

Try Zindra free and keep food cost, staff, inventory and much more under control from a single platform.