Cycle counting: a rotating schedule instead of one big count

One big count a year locks the warehouse for days, tires the team and brings out in one go the variances that built up over the year. By then nobody remembers where and when the error began. Cycle counting spreads that load across the year: a few items from a list are counted each week, variances are investigated at once and the warehouse keeps running. Here is how to build such a routine by grouping items by speed of movement.

Why cycle counting?

• Variances are caught early, while the people who remember the cause are still there.
• The warehouse does not close; counting is done in small pieces within an ordinary working day.
• The count team works regularly and learns the process.
• Recurring causes (a wrong unit, a duplicate record) show up without waiting for year end.
• A warehouse closed for an annual count can delay dispatches; small counts carry no such risk.

A warning: whether cycle counting can replace the annual full count depends on accounting and audit requirements. Ask your accountant and, if needed, your auditor. In most businesses cycle counting does not abolish the full count; it lightens it.

Split the items into three groups

In Excel, work out the issue value of each item over the last twelve months, sort from largest to smallest and follow the cumulative share. For example the items making up the first 70 per cent might be A, the next 20 per cent B and the rest C. You can use movement frequency instead of value. A suggested frequency:

• group A (few items, high value or movement): monthly;
• group B: every three months;
• group C (many items, low value or movement): once a year.

The threshold shares vary by business; the above are only a starting point.

Worked example

An illustrative warehouse has 1,000 items: 100 in group A, 300 in B and 600 in C. Counts per year:

• A: 100 × 12 = 1,200;
• B: 300 × 4 = 1,200;
• C: 600 × 1 = 600.

That is 3,000 lines in total. Assuming 50 working weeks a year, it is 3,000 ÷ 50 = 60 lines a week and 60 ÷ 5 = 12 lines a day. If a team counts 25 lines an hour, 12 lines take about half an hour (12 ÷ 25 = 0.48 hours). Compare a single annual count: 1,000 lines, but over several days and often with the warehouse restricted. In the cycle routine the lines counted triple (3,000), yet no single day passes half an hour; fast items are checked monthly, slow ones yearly. This is an average; in a busy season the weekly list can be shortened and lengthened in quiet weeks.

How the weekly list is built

Keep the group and the date of the last count for each item in Excel. Each week the list receives:

1. the A-group items whose turn has come (those with the oldest last count);
2. the B and C items whose turn has come;
3. trigger items: those whose balance fell to zero, went negative, showed a difference at goods receipt or were the subject of a customer complaint.

Counting is done in the first hour of the day, before movement starts, and the result is compared with the record the same day. If the difference exceeds the set threshold a second person recounts and the cause is written down within the week.

Before a difference is cleared from the record with a correction document, write down its cause. Correcting without a cause turns cycle counting into a tool that silently erases differences, and the same difference returns a few weeks later.

Limits

If the same person always counts, independence suffers; rotate the counters. If the last-count date is not updated, the grouping breaks. The strength of this routine comes from discipline: a list that does not run for a month means a return to the annual count.

In short

Cycle counting keeps accuracy up in small steps without waiting for year end. An independent count can also test the figures of your in-house cycle counts; StockSystem places the counted quantity next to the balance in the records and delivers an item-level variance table.