Scheduling cycle counts through a WMS

Plan cycle-count work by defining what each task covers, how often it recurs and how much work to release at a time. Review the open and pending-review work before increasing the schedule, so the queue stays manageable.

Choose the counting unit

Decide whether a task covers a whole location or selected products or variants within it. Record the scope so a completed partial task is not mistaken for a full location audit. Dynamics 365 Supply Chain Management's Warehouse management solution supports partial-location cycle counting for selected products or variants rather than all on-hand inventory in a location.

Use the cycle count plan's Select locations query to narrow the locations, then product and product variant queries to choose what is counted. Associate a work template with the plan; its Work line breaks option groups counting lines by item number or product variant number. For selected-product counts, the generated work has Partial cycle count selected and multiple counting lines as defined by the template.

Select Display item number on the mobile device menu item before processing partial work. If the menu item's Directed by setting is System directed, configure system-directed work sequencing as well. Without at least one system-directed work sequence query, the device returns No work available even when open cycle-count work exists.

Setting Up a Partial-Location Cycle Count in Dynamics 365

Set priorities and a workable volume

Cycle count plans and threshold parameters can create work automatically. Work can also be created manually from the Cycle count work by item or Cycle count work by location page; spot cycle counting is another way to count without first creating work. A plan can apply to items or locations.

In Dynamics 365, open Warehouse Management > Setup > Cycle counting > Cycle counting plans. Enter a Cycle counting plan ID and description, and optionally a Work pool ID. Set Maximum number of cycle counts, which controls how many count records are produced at a time, and Days between cycle count, which controls how often the plan generates counts; choose whether empty locations are included, excluded or counted only.

An ABC cadence can prioritise items by value and velocity: A-items, the highest-value items, are counted monthly; B-items, with moderate value, quarterly; and C-items, the lowest-value items, less frequently, typically annually. Separate plans can be used for ABC groups, with each plan applied to its items or locations.

Use the plan interval and maximum number of counts together to shape the workload. For example, a warehouse with 2,500 locations aiming to count each location every quarter can plan around 65 working days and a 90-day Days between cycle counts setting, then set the maximum number of counts per plan run to spread the work.

Choose locations for regular review using local risk and capacity. High-movement pick faces, locations with earlier differences and recently relabelled areas are possible priorities. Keep a route for an unexpected empty bin or misplaced pallet to trigger a spot count.

Estimate time for travel, counting, recording exceptions and reviewing pending work. Assign an owner and a due window. Review the open queue before increasing frequency, and reduce task volume, change the scope or add capacity if the team cannot keep up.

Track tasks created, completed, overdue and awaiting review. Count work with differences has a Pending review status on the All work page; the Cycle count work pending review page is used to resolve those differences.

ABC Cadence Prioritisation for Cycle Counts

Coordinate counts with live work

Choose a quieter window where practical and tell staff which locations are being counted. Record when the physical quantity was observed. The Allow pallet moves during cycle counting option enables workers to move pallets during a count; record movements between observation and review for later reconciliation.

Before adopting a plan, check representative locations in the configured workflow, such as a mixed-item location, a busy pick face and an empty location. Confirm what the task asks staff to count, how unexpected goods are handled and who receives a difference.

Pre-Implementation Validation for Cycle Count Plans