What is cycle counting? Cycle counting is counting a small set of inventory locations on a rolling schedule while the warehouse keeps shipping, instead of shutting down for one full physical count. Over weeks, every location gets counted, fast movers most often, and each mismatch gets recounted and traced to its cause.
Cycle counting is counting a small slice of your inventory on a rolling schedule, a few locations a day, while the warehouse keeps receiving and shipping. Over a few weeks every location gets counted, so the count in the system stays tied to what is on the shelf without closing the building for a full physical inventory. If a 3PL ships your orders, cycle counts are the reason the stock your store shows is stock it can actually ship. This guide covers how cycle counting works at a 3PL handling ecommerce and retail fulfillment, which method fits which SKUs, how often counts should happen, and whether your 3PL should charge you for them. At KSP, scheduled cycle counts are included at no charge, because keeping your count right is the 3PL's job.
What is cycle counting in a warehouse?
A cycle count checks one location, or one SKU, against the warehouse management system. A counter goes to the bin, counts the units, and records the number. If the shelf matches the system, the location is done until its next turn. If it doesn't, the location gets flagged for a recount and an investigation.
Each count takes a few minutes, and the schedule does the real work: every location comes up again on a set cadence, so an error made on Tuesday gets found within days instead of at year end, when nobody remembers which receipt or which pick caused it.
A cycle count also differs from a spot check. A spot check happens when somebody suspects a problem. A cycle count happens whether anyone suspects one or not, which is how it catches the errors nobody noticed.
Should your 3PL charge you for cycle counts?
No. Keeping your count right is the 3PL's job. You pay a 3PL to store your units and ship them correctly, and it can't do either without knowing what is on the shelf. When a 3PL bills you to count, you end up paying for the time it spends finding its own receiving and picking errors.
Check your current invoice for it. A counting charge might show up as an annual fee per location, or as hourly labor inside a line called inventory management or miscellaneous warehouse services. A per-location fee grows with your SKU count, so the brands that need counting most would pay the most for it.
At KSP, scheduled cycle counts are included at no charge, and the counts on our rotation never show up as a line on your invoice. A one-off count you request on your own timeline, like a full count of one SKU before a product launch, isn't covered by the free schedule, and we'll tell you up front what it involves.
When you compare 3PL quotes, ask three things about counting:
- Do you cycle count every client's inventory on a schedule, and how often?
- Is there any charge for those scheduled counts, per location, per hour or inside another line?
- Which count requests from me cost extra, and what does each one cost?
If the answers aren't in the quote, they'll show up on the invoice.
How does a 3PL run cycle counts?
At KSP, counting is the last check in a chain of scans that starts at the dock.
Inbound cartons get counted and scanned against your ASN before any of the stock becomes available to sell. A short shipment or a mislabeled carton gets caught at the dock, which keeps a supplier's error from turning into a count error three weeks later.
Every unit is scanned when it's picked. More than 135 Locus robots carry order totes through the pick floor, and associates scan each unit from its location against the order. A pick from the wrong bin shows up at the scan instead of in your customer's box. That scanning is a big part of how KSP holds 99.999% order accuracy across 32.1M orders.
Then the inventory control team counts. Their day, in the words of the team: "Cycle counting, inventory tracking, variance verifying (inbound and outbound), SKU swapping per client request, misc inventory requests." Receiving and fulfillment flag anything that looks off, and the team investigates it the same day.
When a count doesn't match, nobody just types in the new number. The team recounts, then reads the recent history of the SKU: the last receipt, the last picks, any returns put away to that bin. Fixing the event that caused it keeps the same error from showing up at next month's count. If the mismatch touches your orders, you hear about it under KSP's 2-hour issue response SLA.
Cycle counting vs a full physical inventory audit
A full physical inventory, often called a wall-to-wall count or an inventory audit, counts every unit in the building at once. Receiving stops, orders stop shipping, and the whole team counts until every location is done. Accountants and lenders sometimes want one at year end.
The two methods answer different needs:
| Cycle counting | Full physical inventory | |
|---|---|---|
| How much gets counted | A few locations a day | Every location at once |
| Shipping during the count | Keeps running | Stops until the count ends |
| How often | Every day, on a rolling schedule | Once or twice a year |
| When errors get found | Days after they happen | Months after they happen |
| Root cause | Traceable, the history is recent | Hard to find, the history is long |
A full count stops shipping until the last location is counted, and orders that come in during it wait. It also gives you one accurate snapshot and then starts drifting the next morning. Cycle counting keeps the number right all year, and when a year-end audit is required, the counts from the year make it faster because few locations still hold surprises.
Which cycle counting method fits your SKUs?
Most warehouses mix several methods, because each one finds a different kind of error.
ABC counting. SKUs get ranked by how much they move or what they're worth. A-items, the small group of fast movers that make up most of your orders, get counted most often. C-items, the long tail that barely moves, get counted least. Fast movers are touched by more picks and more receipts, so they drift faster and cost the most when they're wrong.
Random sample counting. The system picks a set of locations at random each day. No SKU gets skipped for months because it fell into the wrong class, and the results give you an unbiased read on overall accuracy.
Control group counting. A small fixed group of locations gets counted over and over for a short period. It's how a warehouse tests its own counting process: if the same bin gives two different numbers a day apart with no activity, the problem is the count, not the stock.
Opportunity-based counting. A location gets counted when it's cheap or urgent to count it. A bin that drops near zero takes seconds to count. A pick that comes up short, or a bin that shows empty when the system says it holds stock, gets counted right then.
Brands with a few dozen SKUs and steady sales can live on ABC and opportunity counts. Brands with hundreds of SKUs, lot-tracked supplements or seasonal kits need random sampling too, because the slow SKUs are where expired lots and mis-slotted cartons sit unnoticed.
How often should a 3PL cycle count?
Often enough that every location gets counted on a set rotation, with fast movers counted most. Start with A-items monthly, B-items quarterly and C-items once or twice a year, with opportunity counts layered on top whenever a pick comes up short. The rotation should tighten for SKUs that carry more risk: high-value units, lots with expiration dates, and anything your retail accounts audit on arrival.
Ask your 3PL for its schedule in writing, and ask to see last month's counts by SKU. A warehouse that counts on a real rotation can show you which locations it counted, which ones didn't match and what it changed.
What do cycle counts catch?
When a count doesn't match, the cause sits somewhere in the SKU's recent activity. These everyday warehouse events produce most mismatches, and each one tells you what to ask a 3PL about:
- Receiving miscounts. A supplier ships 480 units on a packing list that says 500, and the warehouse receives 500. The bin is 20 short from day one.
- Wrong-bin picks. Two similar SKUs, such as the 8 oz and 16 oz of the same product, sit side by side. A picker grabs from the wrong one, so one bin reads high and the other reads low.
- Returns put away to the wrong location. The unit is in the building, but the system thinks it's somewhere else, so it can't be picked.
- Unit-of-measure mix-ups. A case of 12 gets recorded as one unit, or one unit gets recorded as a case.
- Kits built without adjusting components. Gift sets get assembled, but the components inside them are never deducted from stock.
- Unrecorded damage. A crushed carton sits in a bin and still counts as sellable stock because nobody wrote it off.
Each of these leaves a trail in the SKU's recent history, which is why a recount followed by an investigation finds the cause. Adjusting the number without that step fixes the count for a day.
How do you know your inventory counts are right?
Cycle counts produce the numbers you need to grade a warehouse. The useful one is location accuracy: the share of counted locations where the shelf matched the system exactly. Comparing total units against total units hides errors, because a location 12 short and another 12 over add up to a perfect total.
Our guide to warehouse inventory management walks through that calculation with a worked example, plus the receiving and putaway steps that keep the count clean before anyone counts it. Ask your 3PL for the location match rate from its cycle counts every month, with the adjustments listed by SKU. A 3PL that does real counts has that report already.
Frequently asked questions
How often should you do cycle counts?
Count fast-moving A-items monthly, B-items quarterly and slow C-items once or twice a year, and count any location right away when a pick comes up short. Tighten the rotation for high-value units and lot-dated products. At a 3PL, ask for the schedule in writing and last month's results by SKU.
What is an inventory audit?
An inventory audit checks that the inventory in your records matches the stock on the shelf. A full audit counts every unit at once and stops shipping until it ends. Cycle counting audits a few locations every day instead, so errors get found within days and the warehouse keeps shipping orders.
What is a good cycle count accuracy?
Measure it as location accuracy: the share of counted locations where the shelf count exactly matches the system. Fast movers and lot-tracked products need the highest match rate because their errors reach customers first. Ask your 3PL for the monthly rate and the adjustments behind it, listed by SKU, not only the total.
Do 3PLs charge for cycle counts?
Some 3PL invoices show counts as a per-location fee or as hourly labor inside an inventory line. KSP includes its scheduled cycle counts at no charge, because keeping your count accurate is the 3PL's job. One-off counts you request on your own timeline sit outside that schedule, and KSP tells you what they involve first.
Ask what counting will cost you at your next 3PL
At KSP, scheduled cycle counts are included at no charge, because keeping your count right is our job. Tell us how many SKUs you carry, which channels you sell on and how many orders you ship a month.
We'll show you how your inventory would be received, counted and reported, and walk you through an invoice line by line, so you can see there's no fee for scheduled counts hiding in it.