After ASN receipt and physical arrival confirmation (see EDI 856 route), trigger putaway task generation in the WMS by calling the putaway task creation API with the receipt ID and received item details.
The WMS slotting engine evaluates putaway rules: item velocity (A/B/C), zone affinity, storage type compatibility (pallet rack, case flow, bulk floor), weight and dimension limits per location, and proximity to shipping area for fast-moving items; the engine returns a directed putaway location for each handling unit.
Retrieve the putaway task list and dispatch it to forklift operators or pickers via RF devices or WMS mobile app; each task includes the SSCC or LP number, description, quantity, and directed put-to location.
As each putaway is confirmed by the operator scanning the location barcode, the WMS API records the put confirmation and updates the location's inventory balance in real time.
Handle putaway exceptions (location full, incorrect item in location, location damaged) by calling the exception reporting endpoint; the WMS reassigns the task to an alternate location and logs the exception.
Known gotchas
Directed putaway locations can become stale between task generation and task execution if another receipt is being put away simultaneously; the WMS must check location availability at task confirmation time, not just at task creation — confirm your WMS implementation handles this.
Putaway to a mixed-SKU location is efficient in terms of space utilization but complicates cycle counting and pick accuracy; mixed-location putaway should only be configured for items where SKU commingling is acceptable (e.g., no lot control required).
Some WMS implementations generate putaway tasks only for receipts with confirmed ASN matches; ad-hoc receipts (unscheduled deliveries without an ASN) may require a manual receipt creation step before putaway tasks can be triggered via API.
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