Cycle counting for small warehouses: count a little every week

Many small warehouses count everything once a year: the store closes for a day or two, everyone counts, the differences are adjusted, and the records drift again until the next year. Cycle counting replaces that with a small count every week, rotating through the stock so every product is counted several times a year. This article explains why it works better for a small store, how to plan the rotation, how to count so the numbers can be trusted, and where OpenBoxes supports it.

The warehouse and figures below are invented examples.

Why count a little often#

• Errors are found sooner. A wrong quantity found three weeks after it happened can usually be explained: a receipt keyed twice, an issue never recorded, a lot put in the wrong bin. Found eleven months later, it can only be adjusted.
• The store keeps working. A few dozen products a week fits around normal work. A full count usually does not.
• The records stay good enough to act on. Minimum levels, reorder decisions and stock alerts all start from the quantity on hand. If that is wrong, every decision built on it is wrong too.
• Counting becomes a skill. A team that counts every week gets faster and more careful than one that counts once a year.

Plan the rotation#

1. List every product you hold. This is your counting universe.
2. Choose how often each product is counted. A simple rule: every product at least once a quarter, and the products that matter most more often.
3. Decide which products matter most. The usual approach is ABC classification: a small number of products (A) account for most of your value or use, and are counted most often. For a health store, add anything where a stock-out is dangerous, whatever its value.
4. Divide by the weeks in the cycle to get a weekly target.

An example#

A district store holds 520 products. It counts every product once a quarter, which is 13 weeks:

• 520 ÷ 13 = 40 products a week.

It also marks 60 products as class A and counts those once a month instead. That adds about 60 × 2 = 120 extra counts a quarter (each A product is counted three times instead of once), or about 120 ÷ 13 ≈ 9 a week. The weekly target is about 49 products.

Group each week's products by area or bin, so the counter walks a route instead of crossing the store for every product.

Count so the numbers can be trusted#

• Count everything for the product at once. All lots and all bins in the location, in one session. Counting some lots and not others leaves a difference that looks like a loss.
• Count by lot and bin. Record the lot number and expiry date with each quantity. A count is a good moment to catch a lot in the wrong bin or a missing expiry date.
• Avoid counting while stock is moving. Count a product before or after the day's issues and receipts for it, not while an order is being picked.
• Recount before you adjust. When a count differs from the record, a second count, ideally by someone else, separates a counting mistake from a real difference.
• Find the cause of real differences. Look at the product's recent transactions. A pattern, such as the same product short every month, points to a process to fix, not only a number to correct.

Cycle counts in OpenBoxes#

OpenBoxes has a dedicated workflow under Inventory, Cycle count:

• Manage Cycle Count opens a list of your products on its All products tab, with columns including Last Counted and ABC Class, and filters including ABC class. Choose the products to count and start a count for them.
• Perform Cycle Count opens the To count tab, where staff record the counted quantities, lot by lot. A count form can be printed for use on the floor.
• Differences between the counted and expected quantities appear on the To resolve tab, where they are recounted and resolved before the count is completed. Completing the count records the adjusting transactions.
• Reporting, in the same menu, shows completed counts and their differences.

The Last Counted column is useful for the rotation above: scanning it shows which products have gone longest without a count. See Inventory for the cycle count steps and for stock adjustments.

Seeing your counts on OpenBoxes Lift#

On OpenBoxes Lift, the Activity by week card on the portal's Reports page shows the last 12 weeks by category, including stock counts and count corrections. A stock count is shown as a count, and any change it made to stock is shown as a count correction. Two things to look for:

• Weeks with no counts show where the rotation slipped.
• Count corrections that keep growing suggest a problem in receiving, picking or recording that counting alone will not fix.

Accurate quantities also matter for alerts. The optional daily stock alert email reports products below the minimum you set, from a daily check of your quantities on hand. A quantity that is wrong in the records produces an alert that is wrong too, or no alert when one was needed.

Summary#

• Count a fixed number of products every week, so every product is counted at least once a quarter and the important ones more often.
• Group each week's products by area to keep the counting quick.
• Count all lots and bins of a product at once, by lot, while stock is not moving, and recount differences before adjusting.
• In OpenBoxes, use Inventory, Cycle count: Manage, Perform, then resolve and review.
• On OpenBoxes Lift, watch the counts and count corrections on the Reports page to see whether the routine is holding.

More on the OpenBoxes side is in Inventory, and OpenBoxes Lift features covers what the hosted service adds.