Extract pick activity data from the WMS for the desired period: per-SKU pick frequency, units picked per visit, weight and cube per pick, and current slot location for each active SKU.
Classify SKUs into velocity buckets (A: top 20% of picks, B: next 30%, C: remaining 50%) and compare current slot locations against ideal zones — A items should reside in primary pick zones (ergonomic height, closest to packing), B in secondary, C in reserve.
Identify suboptimal placements: A items slotted in reserve aisles, C items occupying primary pick slots, items with high velocity but small slot size causing frequent replenishment, or items with complementary order profiles that could be collocated.
Submit slot change requests via the WMS slotting API: for each SKU reassignment, specify the current location, target location, and proposed slot dimensions; the WMS validates that the target location is compatible with the item's storage type and dimensions.
Schedule slotting moves during low-activity periods (off-shift or weekend) to minimize interference with active picks; trigger the physical slot move tasks via the WMS task management API and confirm completion via put-confirmation events.
Known gotchas
Slotting analysis based on historical pick velocity can be misleading if seasonality is not accounted for; a SKU that ranks as C-velocity in aggregate may be A-velocity during peak season — use rolling 90-day windows and adjust for seasonal patterns.
Slot moves require physical movement of inventory; during the move, the inventory is in transit between locations and may not be available for allocation — coordinate slot move scheduling with order release windows to avoid allocating inventory that is being relocated.
Not all WMS platforms expose a slotting API; in some implementations, slotting changes are made in the WMS configuration layer rather than via transactional API calls, which requires a different integration approach than run-time inventory transactions.
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp