Cycle counting software: what it should do

A cycle count is a small, regular count of part of your stock, done while the building keeps running. Instead of closing for a full physical inventory once a year, you count a few locations every day. Over a few weeks you have touched everything that matters.

Software helps in three places: choosing what to count, guiding the counter, and dealing with the differences. This page covers each, so you can tell what a cycle counting module should do before you ask a vendor.

Why count in cycles

A yearly full count stops work, takes many people, and gives you a number that is already going stale as you finish. Cycle counting spreads the work and, more usefully, finds problems close to when they happen. A wrong count found the day after a mispick is easy to trace. The same error found eleven months later is a mystery.

Ways to decide what to count

Good software supports more than one method, because different stock needs different attention.

By frequency class. Fast-moving or high-value items are counted more often than slow, cheap ones. Many teams sort items into three groups and set a count rhythm for each.

By location sweep. Count one aisle or zone per day, rotating until you have been everywhere.

By trigger. Count a location when something suggests a problem: a short pick, a negative balance, a zero that should not be zero, or a large adjustment.

By movement. Count a location right after it empties, when it is easiest to count.

Random. A few locations picked by the system. Useful as a spot check on top of the others.

Ask any vendor which of these are standard, which need configuration, and whether you can combine them.

What the counter should see

On the handheld, the counter should be sent to a location, scan the location label, and then count what is there. Many teams prefer a blind count, where the screen does not show the expected quantity. It removes the temptation to confirm instead of count. Where the item has a lot, batch or serial, the counter scans that too.

If the count matches, the task closes. If it does not, the system should ask for a recount before anyone touches the stock record.

What happens with differences

This part separates a useful tool from a toy.

• Tolerance rules. A difference of one unit on a cheap item and a difference of fifty on an expensive one should not be treated the same. Look for rules by item, value or quantity.
• Recount before adjust. A second count, ideally by someone else, before any change.
• Approval. Large adjustments go to a supervisor. Small ones may go through on their own.
• Reason codes. Damage, miscount, mispick, receiving error, theft suspected, unknown. Over time these show you where stock goes missing.
• Audit trail. Who counted, who approved, what changed, and when.
• Freeze option. Optionally stop picks from a location while it is being counted.

A worked example (hypothetical)

A small parts distributor has 1,200 locations. They split items into three groups by how often they ship. Group A is counted every week, group B every month, group C twice a year. The software builds each morning's list of counts from those rules, plus any location where a pick came up short yesterday.

On Tuesday, a counter finds 38 units in a bin where the system says 48. A recount confirms 38. The difference is over the tolerance for that item, so it goes to the supervisor. The supervisor checks yesterday's pick history, finds a ten-unit pick scanned to the wrong bin, fixes both bins, and records the reason as "mispick". No adjustment is lost in a pile of unexplained write-offs.

That chain of recount, approval, reason and trace is what you are buying.

Reports that matter

• Inventory accuracy by location, zone and item group, over time
• Count tasks done, open and overdue
• Adjustment value by reason code
• Items or locations with repeated differences
• Counter productivity, if you use it carefully and not as a punishment

Questions to ask before you choose

1. Which count methods are standard, and can I mix them?
2. Can I run blind counts?
3. How are tolerances set, and can they vary by item or value?
4. Is a recount required before an adjustment?
5. What approvals can I configure?
6. Does it work for lots, batches, serials and expiry dates?
7. What does the counter's screen look like on our devices?
8. Can I export count history and adjustments?
9. How does it handle counting while orders are being picked?

Starting without software

You can begin now with a spreadsheet and a printed list. Pick a rhythm, count every day, record the differences and reasons, and look at the pattern after a month. If the habit sticks and the spreadsheet starts to strain, you will know exactly what you need from software.

One option among several

Cycle counting modules ship with most subscription warehouse systems. A custom build is another route if your counting rules are unusual. Cargohold, which we make, is a one-time custom build, no per-seat, per-truck or per-client fees. Compare against the same question list either way.

Questions people ask

What is cycle counting?

Counting a few locations every day instead of closing for one full physical inventory. Over a few weeks you have touched everything that matters, and errors are found close to when they happen.

How do you do cycle counting?

The system sends a counter to a location, the counter scans the location label and counts what is there, ideally on a blind count. If the count does not match, a recount comes before anyone touches the stock record, and large differences go to a supervisor with a reason code.

What are the methods of cycle counting?

By frequency class, by location sweep, by trigger such as a short pick or negative balance, by movement such as a location that just emptied, and by random spot checks. Ask which are standard and whether you can combine them.

What is a blind count?

A count where the counter's screen does not show the expected quantity. It removes the temptation to confirm instead of count.

What should happen when a cycle count does not match?

A recount before anyone touches the stock record, tolerance rules by item or value, approval for large adjustments, a reason code and an audit trail of who counted, who approved and what changed.

Can I do cycle counting without software?

Yes. Use a spreadsheet and a printed list, pick a rhythm, count every day, record differences and reasons, and review the pattern after a month.