Cycle Counting: Replace the Annual Stocktake

The annual stocktake has a certain ritual to it. The warehouse shuts, everyone counts, the numbers get adjusted, and three months later accuracy is back where it started. Cycle counting is the alternative: count a small part of your stock every week, all year round.

Why it works better

• Problems get found while they're fresh. If a location is wrong this week, someone may remember why.
• No shutdown. Counting happens alongside normal work.
• Accuracy improves over time, because you fix causes, not just numbers.
• It's measurable. You get an accuracy figure every week.

Step 1: Decide what to count, and how often

Use ABC classification by value or movement:

Add trigger counts too:

• When a location hits zero (it's quick to confirm an empty bin)
• When a picker reports a shortage
• After a big adjustment or a returns batch

Step 2: Count blind

Counters should see the product and location, but not the expected quantity. Otherwise they find what they expect to find.

On a scanner, that means a screen with just the location and product, and a field for the count.

Step 3: Set tolerance rules

Not every variance needs an investigation. Set a threshold, for example more than 2% or more than a certain value. Below it, accept the count. Above it, recount, then investigate.

Step 4: Investigate, don't just adjust

This is where the real gains come from. For each significant variance, look at recent movements on that product:

• A receipt booked into the wrong location?
• A unit of measure error (boxes vs units)?
• A pick confirmed but not actually done?
• A return never put away?

Write down the cause. After a month, the causes cluster, and you'll know which process to fix.

Step 5: Measure accuracy

Location accuracy = locations counted with no variance / total locations counted.

Track it weekly. Share it with the warehouse team. People improve what they can see.

Doing it in Odoo

In Odoo, you can:

• Set a counting frequency per location (for example, every 30 days for an A-zone) and schedule counts
• Generate count requests by product, location or category
• Count on the barcode app in Enterprise, or with OCA barcode modules on Community
• Apply counts, which posts adjustments with the accounting entries

Keep the adjustment reason codes consistent. "Damage", "Miscount", "Wrong location" and "Unknown" are a reasonable start.

A realistic start

Week one: pick 50 locations in your fastest-moving zone and count them blind. Investigate everything off by more than one unit. You'll learn more about your warehouse in that week than in the last annual stocktake.

More in the inventory management guide and barcode warehouse operations.