How to build cycle count plans in F&SCM that keep your numbers honest and push directed counts straight to the warehouse floor.
Full physical inventory counts have a way of eating a weekend. You freeze the warehouse, pull people off their normal work, count everything at once, and still end up chasing discrepancies for days afterward. The larger your operation, the more painful that annual or quarterly ritual becomes, and the longer your on-hand numbers drift out of sync in between. That drift is expensive. IHL Group puts the yearly cost of inventory distortion, out-of-stocks and overstocks together, at $1.73 trillion across global retail [1]. Cycle counting in Dynamics 365 Finance & Supply Chain Management (F&SCM) takes a different approach: you count small, defined portions of inventory on a rolling schedule, so accuracy stays high and operations never stop. This walkthrough covers how to set up and run cycle count plans in F&SCM using the warehouse management (WMS) module.
Everything starts under Warehouse management > Setup > Cycle counting > Cycle count plans. A cycle count plan is a reusable set of instructions that tells F&SCM which locations to count, how often, and how much work to generate for your warehouse team. Below are the fields that matter and how to think about each one.
Create the plan ID and description
Give every plan a unique cycle counting plan ID and a clear description. You will almost always maintain more than one plan, whether that is different zones, different count frequencies, or different product groups, so a naming convention you can read at a glance saves confusion later. The ID is what you will reference when you trigger the plan or review the work it created.
Assign a work pool (optional)
Work pool is optional, but it is worth using. A work pool lets you group warehouse work by type, in this case cycle counting work, so it can be filtered, prioritized, and assigned separately from picking, put-away, and replenishment. If you want cycle count tasks to land with a specific team or show up in their own queue on the mobile device, set the pool here.
Set the maximum number of cycle counts
The maximum number of cycle counts controls how many work orders F&SCM creates each time the plan runs. A practical way to set this: use the maximum number of locations you would want counted in a single cycle count pass. That keeps each run at a size your team can realistically clear before the next one, instead of flooding the queue with more work than a shift can handle.
Configure the schedule with Days between cycle count
Days between cycle count defines how often the plan reruns automatically. This is what turns cycle counting from a one-off task into a standing rhythm. Set it to the cadence that fits the value and volatility of the inventory in scope. Fast-moving or high-value locations warrant a shorter interval, while slow, stable stock can go longer between counts.
Decide how to handle empty locations
The empty locations option tells the plan whether to generate counting work for locations the system currently shows as empty. It matters more than it looks. If you include empty locations, F&SCM will direct workers to verify every physical location in the warehouse. That is useful when you suspect on-hand inventory has drifted out of sync with what is physically on the shelf and you want a true wall-to-wall check. That kind of drift is common: average inventory accuracy across businesses sits around 83%, and only 69% of companies even track it [2].
There is an important dependency here. If empty locations are included, you cannot set up a product selection on the plan. There will be no product filters, because the point is to count everything. If empty locations are excluded, you get the option to build a product query, letting you target the specific products you want the cycle count activity to cover.
Select the warehouse and locations
The last setup step is choosing the warehouse and the specific warehouse locations the plan applies to. This is where the plan gets its scope, whether that is a single zone, a range of aisles, or an entire site. Once this is in place, the one-time configuration is done.
Trigger the plan and let the WMS app do the rest
With the plan built, you can trigger it manually or let it run on the schedule you defined. Either way, F&SCM automatically generates work tasks for your warehouse operators. Using the WMS mobile application, the system guides each worker to the right location and the right items. No manual spreadsheets, no printed count sheets, no guesswork about what to count next. That shift from manual to directed counting is where the accuracy gains show up. Auburn University's RFID Lab has documented inventory accuracy above 95% with modern, system-driven tracking, compared with 60 to 70% under manual methods [3]. Counts are recorded against the work, and discrepancies surface in the system where you can act on them.
Where this fits beyond the basic example
The real value shows up when you stop thinking of cycle counting as a single plan and start using it as a framework. Because plans are reusable and independently scheduled, you can run an ABC-style approach. Count your A-items every couple of weeks, B-items monthly, and C-items on a longer cycle, all from separate plans pointed at different locations or product queries. You can also stand up a dedicated wall-to-wall plan that includes empty locations for the times you need a full reconciliation, while keeping your routine product-filtered plans running in the background. The setup is the same each time. Only the scope and cadence change.
Which operations benefit most
Cycle counting earns its keep anywhere inventory accuracy directly affects the ability to promise and ship, but a few operations feel it most:
- Distributors: With thousands of SKUs turning constantly, a distributor cannot afford to freeze the DC for a full count, or to quote availability off numbers that are three months stale. Rolling counts keep the pick faces honest without touching throughput.
- Manufacturers: Accurate on-hand for raw materials and components is what keeps MRP and production schedules from planning against phantom stock. Cycle counting catches the drift before it becomes a line-down surprise.
- Third-party logistics (3PLs): When you are counting inventory you hold on behalf of clients, accuracy is a contractual expectation, not just an internal metric. Location-level cycle counts give you defensible, continuously verified numbers per client and per zone.
- Food, beverage, and other lot-controlled operations: Where stock moves fast and traceability matters, frequent counts of high-velocity locations keep on-hand tight and reduce the shrink and write-offs that quietly erode margin.
- Food, beverage, and other lot-controlled operations: Where stock moves fast and traceability matters, frequent counts of high-velocity locations keep on-hand tight and reduce the shrink and write-offs that quietly erode margin.
Watch the walkthrough
The video below walks through building a cycle count plan from start to finish and shows how the work flows to the WMS mobile app.
Western Computer has spent more than 40 years and completed over 1,750 implementations helping distributors, manufacturers, and logistics operations get the most out of Dynamics 365. If you want help right-sizing cycle counting for your warehouse, we are happy to talk it through.
