Once a year, a lot of businesses stop. Nobody ships, nobody receives, and everyone walks the shelves with a clipboard counting things they do not normally think about. It takes a day or two, it costs whatever a day of not trading costs, and the numbers come out wrong anyway, because people counting unfamiliar stock under time pressure make mistakes, and because a count is a snapshot of something that moves.
Cycle counting is the alternative. Instead of counting everything once, you count a small slice every day and never stop. The shelves get counted at least as often, the doors stay open, and the counting is done by people who handle that stock all the time.
The part that makes it work
The instinct is to divide the catalog by the number of working days and count an equal slice each day. That beats an annual count and is still worse than it should be, because it spends the same attention on the item you sell 400 of a week as on the one you sold twice in 2024.
Sort by what a mistake costs instead. The usual split is three groups: a small group that is high value or high volume, a middle group, and a long tail. The first group gets counted often, perhaps monthly. The middle group a few times a year. The tail once a year, or whenever somebody touches it.
The exact proportions matter less than the principle. Count the things where being wrong hurts more often than the things where it does not.
The variance is the output, not the count
A cycle count that matches the record tells you almost nothing, because you expected it to match. A count that does not match is the entire point, and the useful question is not what is the right number but why did it drift.
Miscounted at receiving. Picked and not recorded. Damaged and binned without an adjustment. Taken by someone who meant to write it down later. Each of those is a different problem with a different fix, and correcting the number without identifying which one it was means you will be correcting the same number next quarter.
The pattern across your variances is worth more than any single corrected count.
A realistic accuracy target
Perfect was never the target. Operations that take this seriously tend to land in the high nineties by unit and are right to be satisfied there.
The number that actually matters is not the headline percentage but where the errors are. Ninety eight percent accuracy across the catalog with the mistakes concentrated in your fastest movers is a worse position than ninety five percent with the mistakes sitting in the tail.
Keep it short or it will not survive
Cycle counting only lasts if each count is quick. Twenty minutes at the start of a shift happens every day. Two hours happens until the first busy week, and then it quietly stops.
In practice that means small batches, one location at a time, and a count sheet already sorted the way the shelves are physically arranged so nobody walks back and forth. It also means scanning rather than typing, because typing part numbers is where a good share of counting errors are born.
In Knowledge ERP
Cycle counts are part of the Inventory module. You count one bin or one location at a time rather than the whole site, and each line shows the variance between what was counted and what the system held.
Because stock is tracked as individual units rather than a single quantity, a variance points at specific items rather than at a number. The movement log for those units shows every transfer, sale, loan and adjustment they have been through, and who did each one, which is usually enough to answer the why did it drift question without opening a separate investigation.
Adjustments are recorded as movements like everything else, so a corrected count becomes part of the history rather than an overwrite of it.
Where to start
Take your twenty highest value or fastest moving items and count them this week. Not the whole catalog, not a schedule, just those twenty.
Whatever variance you find on that list is the number worth reacting to, and it will tell you more than the annual count ever did. If those twenty currently live on a spreadsheet, that is fine for the first pass, and the exercise is the same.
Count one bin at a time
Cycle counts, unit-level stock and a full movement log are part of the Inventory module. The trial runs 30 days on your real data.