Cycle count calculator

Turn an ABC cycle counting policy into a daily workload. Enter how many SKUs sit in each class and how often you want to count them, and see how many counts your team needs to finish each working day.

Plan your cycle counts

Enter how many SKUs sit in each ABC class and how often each class is counted per year.

Result
Counts per day
28
Counts per year
7,000

Calculated in your browser. Nothing you enter is sent or stored.

Track the stock behind your plan.

Keep warehouse quantities, locations and movements in one workspace. Explore sample stock in the demo or start with your own items for free.

Free during open beta. No card. No sales call.

The formula

Counts per year = (A SKUs × A counts per year) + (B SKUs × B counts per year) + (C SKUs × C counts per year); counts per day = counts per year ÷ counting days, rounded up

Number of A SKUs
Your highest-value or fastest-moving items, usually a small share of the catalog. Classify them with ABC analysis on value or movement.
Number of B SKUs
The middle group: items that matter but move or cost less than your A items.
Number of C SKUs
The long tail of slow or low-value items. Include every active SKU that holds stock.
Counts per year for A
How often each A SKU is counted. The default of 12 means once a month.
Counts per year for B
How often each B SKU is counted. The default of 4 means once a quarter.
Counts per year for C
How often each C SKU is counted. The default of 1 means once a year.
Counting days per year
Working days on which you actually count. The default of 250 is a five-day week less holidays; subtract peak weeks when counting stops.

Worked example

Take a catalog of 1,500 active SKUs split into 120 A items, 360 B items and 1,020 C items. Counting A monthly, B quarterly and C once a year gives 120 × 12 + 360 × 4 + 1,020 × 1 = 1,440 + 1,440 + 1,020 = 3,900 counts a year. Over 250 counting days that is 3,900 ÷ 250 = 15.6, which rounds up to 16 counts per day.

What counts as one count

This calculator counts SKUs, but the floor counts locations. A SKU stored in one pick face and three reserve pallets is four location counts, not one. If your items sit in several places, multiply by the average number of locations per SKU before you turn the result into labor hours.

Once you know the number of location counts, time a few real ones. A blind count of a small bin may take a minute; a pallet of mixed lots may take ten. Counts per day times minutes per count gives the hours you need to set aside.

Choosing count frequencies

The defaults of 12, 4 and 1 are a common starting point, not a rule. Count more often where errors cost more: items with high value, high movement, lot or serial control, or a history of variances. Count less often where the risk is small.

Class by what hurts when the count is wrong. A cheap part that stops a customer's production line may deserve A treatment even though its value is low. Review the classes at least once a year, because fast movers change with seasons and ranges. The cycle counting guide covers how to set up the program around these numbers.

Common cycle count planning mistakes

  • Planning on SKUs when stock sits in several locations per SKU, which understates the work.
  • Assuming counting happens on every working day, then skipping it during peaks and never catching up.
  • Counting only A items and leaving C items for years. Slow items are where lost and misplaced stock hides.
  • Treating a variance as done once it is adjusted. Each large variance needs a recount and a cause.
  • Counting while picks and putaways move stock in the same location, which creates variances that are not real.

Running cycle counts in a WMS

A plan only works if the counts are easy to do every day. In NextStock, cycle counts are location-first and follow the walk sequence, so a counter moves through the aisle in order. Counts can be blind, a soft freeze keeps new allocations out of a location while it is counted, and variances outside tolerance go to recount and approval before they post as an adjustment.

Every posted variance is recorded in the stock ledger with its reason, which is how you measure inventory accuracy over time. Count accuracy is also one of the KPI reports.

Frequently asked questions

Short, direct answers to the questions warehouse teams ask most.

How many cycle counts should I do per day?

Enough to meet your count frequencies over the days you actually count. Use this calculator to find the number, then check it against the hours your team can spare. If it does not fit, lower frequencies for B and C items before you drop A counts.

Does cycle counting replace a full physical inventory?

It can, if every location is counted over the year and your auditors or finance team accept the method. Many operations still do a full count at first and move to cycle counting once accuracy is proven. Confirm the requirement with whoever signs off your accounts.

Should C items be counted at all?

Yes. Counting C items once a year is cheap and catches stock that is lost, damaged or recorded in the wrong place. Slow items are where these errors sit longest without anyone noticing.

Your next warehouse move starts here.

Create your own workspace for free, or explore a stocked demo without an account.

Start freeTry the live demo — no signupFree during open beta. No card needed.