Cycle counting process: cadence, blind counts, recounts and variance research
Cycle counting uses smaller recurring counts and can complement or reduce full physical counts when the records and controls support it. GAO’s 2002 study covered 12 sites at seven companies; its examples describe those sites, not universal accuracy targets or audit requirements.
The procedure below follows the practices GAO documented: counts scheduled by value and risk, blind counts, a second count for any variance, research before the record changes, and accuracy measured the same way every month. WarePulse’s part is narrower and is named at each step; the cycle counting feature page describes it in full.
Connect workflow fit to rollout context earlier.
The procedure below follows the practices GAO documented: counts scheduled by value and risk, blind counts, a second count for any variance, research before the record changes, and accuracy measured the same way every month. WarePulse’s part is narrower and is named at each step; the cycle counting feature page describes it in full.
Inventory leads replacing an annual wall-to-wall count with a counting program.
Inventory teams setting their own accuracy measures, tolerance and count cadence with the responsible finance or audit team.
Teams whose policy lets counted variances post directly; if approval must come first, plan that step before posting in WarePulse.
Keep the next commercial step visible.
Move from this page into pricing or implementation without losing the next step.
ImplementationWatch the floor app run the workflow
See receiving, task execution, picking, confirmations, and exception context move from the floor app into the operating view.
Compare related WarePulse options
Compare the next topics buyers usually review: implementation, pricing, trust, field evidence, and operating fit.
Plan the next warehouse step
Bring one week of count results and your current tolerance, and we will set up the locations, classes and recount thresholds in WarePulse with you.
Workflow steps
- For one warehouse, compare LOCATION and ABC generation with a small line limit and inspect the selected location/item pairs.
- Save the warehouse recount thresholds, then test a known variance. Posting adjusts stock immediately and can also open a recount line.
- Post the recount, then read the audit entry and the accuracy report.
Implementation planning
- Set the recount thresholds per warehouse, 5 units or 10 percent by default, to match your tolerance.
- Decide who posts counts: operators post from mobile, and posting from the web portal is limited to managers.
- If your policy requires approval before an adjustment posts, keep that step outside WarePulse and post after approval.
Questions to resolve
- Do we still need a wall-to-wall count? GAO’s case site went back to an annual one whenever accuracy fell below 95 percent.
- How large a tolerance is normal? The GAO sites used 0 to 5 percent, and some researched every variance.
Expected business impact
- GAO’s case site reduced full counting cycles from four a year to one over about six years as accuracy held.
- Four cycle-count locations in GAO’s study used an average of 22 cause codes, including receipt, location, picking and shipping errors; these were documented categories, not a prevalence ranking.
What WarePulse delivers inside this workflow
How WarePulse changes execution, handoffs, and reviewability inside this workflow.
Count configuration per warehouse: by location, by ABC class or both, with a limit per generation on generated count lines (50 by default).
ABC classes are set by hand on each item, and ABC mode orders generated counts A, then B, then C.
Blind counting on mobile: the expected quantity stays hidden until the count is confirmed.
A variance meeting a saved warehouse threshold, 5 units or 10 percent by default, opens one recount line.
Posting a count applies the variance at once and writes an audit entry with the change and the variance percent; WarePulse has no approval step.
Adjustments carry a reason (damage, cycle count or other) and a note, and accuracy is reported by location and by SKU.
What this workflow usually gets wrong
The process friction that quietly extends lead time, hides exceptions, and stretches labor.
Counts are scheduled by aisle convenience instead of value and risk, so high-value items go months without a count.
Counters see the expected quantity and confirm it instead of counting; GAO found blind counts at 10 of the 12 sites it studied.
The record is adjusted on the first count, before a recount or any research, so errors are written into the books.
Variances are corrected but never coded to a cause, so the same receipt or picking error repeats.
Built for warehouses where this station is the bottleneck
The teams and roles this workflow impacts first.
Inventory leads replacing an annual wall-to-wall count with a counting program.
Inventory teams setting their own accuracy measures, tolerance and count cadence with the responsible finance or audit team.
Teams whose policy lets counted variances post directly; if approval must come first, plan that step before posting in WarePulse.
Set the cadence by value and risk
One site in GAO’s study ranked items by value and activity: the top 10 percent were counted four times a year, the next 20 percent three times, the next 30 percent twice and the last 40 percent once. Other sites chose items by value, by past accuracy or from a list of items not yet counted. In WarePulse, classes are set by hand and ABC mode orders the generated counts; the frequency itself is your schedule.
Rank items by value and activity, then set a count frequency for each class.
Keep a list of items not yet counted this cycle so nothing is skipped.
Count in slow periods, or stop movement in the locations being counted.
Review the procedure every one to two years, as the GAO sites did.
Where to go next
Cycle counting in WarePulse
What the product does at each step: count modes, blind counts, recount lines and accuracy.
See detailsCycle count WMS
The solution page for teams replacing full physical counts.
See detailsLot and expiry control
The procedure for lots, expiry alerts and holds.
See detailsPricing
Cycle counting is included on every plan, from $699 CAD a month for one warehouse.
See detailsImplementation
How locations, items and opening stock are loaded before the first count.
See detailsTrust Center
Audit logging, roles and data handling behind posted counts.
See detailsHow to roll it out
Plan the day’s counts
A named supervisor picks the day’s locations or items from the schedule and from the list of items not yet counted.
Count blind
Counters get the item, location and unit, never the recorded quantity; WarePulse hides it on mobile until the count is confirmed.
Recount every variance
Arrange any required independent recount and research before posting. WarePulse’s threshold-triggered recount follows a posting that has already adjusted stock.
Research before adjusting
Check receipts, picks and shipments since the last count, and code the variance to a cause.
Approve and post
Route large adjustments to a more senior approver before posting; a posted count updates stock and writes an audit entry.
Measure accuracy
Report the share of items counted within tolerance, with gross and net adjustments, the same way every month.
Frequently asked questions
What is the difference between cycle counting and a wall-to-wall count?+
How often should each item be counted?+
Should counters see the expected quantity?+
What happens when a count does not match?+
Does WarePulse require approval before an adjustment posts?+
Does the historical 95% example define our target?+
Start with the station creating the most operational drag today.
Start with the schedule and the recount rule; the counting itself is the easy part. WarePulse handles the count, the recount line and the audit entry.
Plan the next evaluation step
Free WMS Tools & Resources
Use these public resources to plan migration, compare vendors, benchmark KPIs, and estimate ROI before the next walkthrough.
WMS migration checklist
Use a sequenced checklist to scope data, workflow, and cutover risk before switching systems.
WMS RFP template
Shortlist vendors with questions that expose implementation, workflow, support, and integration fit.
Warehouse KPI worksheet
Turn receiving, picking, inventory, and shipping metrics into a buyer-ready baseline.
ROI calculator
Estimate labor savings, payback period, and rollout economics before the trial planning conversation.