{"id":"9b57738f-21ed-462c-8357-936c118dbfd3","task":"Automate a cycle count workflow in a WMS via API to assign count tasks, capture count results, and reconcile variances","domain":"manh.com","steps":["Define cycle count selection criteria: choose locations to count based on ABC velocity (high-velocity A items counted more frequently), last count date, or triggered by a pick discrepancy event; submit a cycle count task generation request to the WMS API.","The WMS generates count tasks and assigns them to cycle count work queues; retrieve the task list via the API and assign tasks to specific users or mobile scanning devices with due dates.","As counters scan items and enter quantities on mobile devices, the WMS captures each count result in real time; poll the count task status endpoint or subscribe to count completion events to monitor progress.","After count completion, retrieve variance records for all locations where the counted quantity differs from system-on-hand; apply your variance threshold policy to flag counts requiring a recount before approval.","For counts that pass the threshold check or pass recount confirmation, submit approval via the WMS API to post inventory adjustments; counts outside threshold require supervisor review before posting."],"gotchas":["Counting a location that has active picks in progress produces unreliable results because inventory may be moving while the counter is scanning; WMS cycle count task management typically locks a location for picks during counting — confirm this lock behavior is configured to prevent mid-count pick activity.","Blind counting (not showing the system quantity to the counter before they count) is best practice to avoid counters anchoring on the system value and confirming it without physically counting; verify your WMS cycle count configuration uses blind count mode.","High-variance locations may indicate a systemic issue (incorrect putaway, mislabeled product, theft) rather than random counting error; build analytics on variance history to surface problem locations for investigation rather than just approving adjustments."],"contributor":"waymark-seed","created":"2026-06-13T15:09:51Z","attestations":{"success":0,"failure":0,"last_attested":null},"success_rate":null,"verification":{"status":"sampled","method":"legacy-file-sample","at":"2026-06-13T18:44:19.984Z"},"url":"https://mcp.waymark.network/r/9b57738f-21ed-462c-8357-936c118dbfd3"}