Cycle counting in WarePulse: count modes, blind counts, recounts and accuracy
WarePulse includes cycle counting on every plan. Managers create counts by location, by ABC class or a mix of both, operators count blind on the mobile app by scanning the location and then the item, and a variance at or above a saved warehouse threshold opens a recount line.
Posted counts update stock immediately and leave an audit entry with the change and the variance percent, and accuracy is reported by location and by SKU. How often to count, who researches a variance and when an adjustment needs approval are procedure decisions; the cycle counting workflow page sets them out.
Connect workflow fit to rollout context earlier.
Posted counts update stock immediately and leave an audit entry with the change and the variance percent, and accuracy is reported by location and by SKU. How often to count, who researches a variance and when an adjustment needs approval are procedure decisions; the cycle counting workflow page sets them out.
Warehouses on any plan that want counts done on handhelds instead of paper.
Inventory leads who need blind counts and one recount rule for every shift.
Teams whose policy lets counted variances post directly with an audit entry; if approval must come first, plan that step before posting.
Keep the next commercial step visible.
Move from this page into pricing or implementation without losing the next step.
ImplementationCompare related WarePulse options
Compare the next topics buyers usually review: implementation, pricing, trust, field evidence, and operating fit.
What the feature delivers
What the team gets once scanning, ASN, or lot control stops running on memory.
Count modes per warehouse: by location, by ABC class or mixed, with a limit per generation on generated count lines (50 by default).
ABC classes (A, B, C) set by hand on each item; in ABC mode, generated counts take class A first, then B, then C.
Blind counting on iOS and Android: scan the location, then the item, and enter the quantity before the expected figure appears; counts queue offline.
Save the warehouse recount thresholds before use; the configuration starts at 5 units or 10 percent. Posting adjusts stock immediately and also opens one recount when the absolute variance reaches either saved threshold.
Posting applies the variance at once and writes an audit entry with the change and the variance percent; adjustments carry a reason (damage, cycle count or other) and a note.
Accuracy by location and by SKU, with a filter for counts that had a variance.
What this feature changes on the floor
The day-to-day friction that quietly eats margin, labor, and customer trust.
Counts are written on paper and keyed in later, so a variance is found after the stock has moved.
Counters can see the expected quantity, so they confirm it instead of counting.
Nobody knows which variance warrants a second count, so recounts depend on who is on shift.
Adjustments leave no trace of who changed a quantity, by how much and why.
Built for these teams
The operating profiles where this feature has the highest operational payoff.
Warehouses on any plan that want counts done on handhelds instead of paper.
Inventory leads who need blind counts and one recount rule for every shift.
Teams whose policy lets counted variances post directly with an audit entry; if approval must come first, plan that step before posting.
Operations that set ABC classes themselves and want counts generated in that order.
What WarePulse records at each step of a count
A count starts as lines for locations or items, generated by mode and capped by the limit per generation. Each counted line stores the quantity found, and posting writes the difference to stock, to the inventory ledger as a cycle count adjustment and to the audit log with the variance percent. A line at or above the saved threshold spawns one recount line, so the second count stays part of the same count.
Set the count mode and the line limit per generation for each warehouse.
Assign ABC classes to items before switching a warehouse to ABC mode.
Set recount thresholds in units and in percent to match your tolerance.
Review accuracy by location and by SKU after each week of counts.
Where to go next
Cycle counting process
The procedure: cadence by value and risk, blind counts, recounts, research and accuracy targets.
See detailsCycle count WMS
The solution page for teams replacing full physical counts.
See detailsBarcode scanning
The same location-then-item scan used for picking.
See detailsWarePulse vs spreadsheets
Use the comparison page if counts still live in side files.
See detailsPricing
Cycle counting is included on every plan, from $699 CAD a month for one warehouse.
See detailsRelated Resources
Learn more from our warehouse management guides
Cycle Counting vs Full Physical Inventory: Which Is Right for Your Warehouse?
Compare cycle counting and full physical inventory methods to find the best fit for your warehouse operations and accuracy goals.
How to Integrate a WMS With Shopify Without Overselling
How a WMS connects to Shopify: inventory states per location, fulfillment service apps, stock sync and webhooks, and the settings that stop overselling.
Cycle Counting Best Practices: The Complete Guide to Inventory Accuracy
Learn how to implement an effective cycle counting program that maintains inventory accuracy without shutting down operations for full physical counts.
Preventing Stockouts on A-SKUs: Reorder Points and Safety Stock in Your WMS
Prevent stockouts with WMS-driven reorder points and safety stock. Learn A/B/C classification, lead time buffers, and automated alerts for wholesalers.
Cycle Counting Strategies for Wholesalers: ABC vs Location-Based Counting
Cycle counting methods for wholesalers: compare ABC classification vs location-based counting. Learn frequency, recount workflows, and WMS audit trails.
How to Achieve 99% Inventory Accuracy with Cycle Counting
A practical framework for using cycle counting to pursue a defined inventory-accuracy target without relying only on annual shutdowns.
Frequently asked questions
Which plans include cycle counting?+
Are counts blind?+
When does WarePulse ask for a recount?+
Does an adjustment need approval?+
Does WarePulse assign ABC classes itself?+
Do cycle counts replace a full physical inventory?+
Turn the workflow costing you the most time into a measurable win.
For one warehouse, compare LOCATION and ABC generation with a small line limit, test the saved thresholds, and review posted adjustments before expanding the procedure.
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.