WMS × WCS Integration
The WMS defines what needs to happen in the warehouse. ABNET WCS translates those needs into physical flow control, connecting management systems and automation.
Explore the flow
One order. Four stages.
Select a stage to follow the exchange between systems and the movement of a load.
1 / 4 · WMS
Order
The WMS specifies what needs to happen: which load to move and its requested destination.
Illustrative logical flow. Interfaces and responsibilities are defined for each project.
From decision to movement
1. WMS
Decides what needs to happen
Manages inventory and process logic, defining orders, tasks, and operational priorities.
2. ABNET WCS
Decides how to execute the physical flow
Saga coordinates routes, sequences, and material destinations, translating WMS requirements into automation actions.
3. MFC / PLC / MHE
Executes the movement
In the execution layer, the MFC coordinates material flow, PLCs control devices, and material handling equipment (MHE) performs the physical movement.
The allocation of functions between WCS, MFC, and PLCs depends on each project’s architecture. The MFC may be integrated into the WCS or implemented as a separate layer.
A two-way integration
The WMS sends requirements and priorities. The WCS coordinates execution and returns statuses, confirmations, and events so that management can track operations. Messages, interfaces, and exception handling are defined in the integration project.
Example: routing a carton to shipping
The WMS specifies the carton and its destination. ABNET WCS organizes its route through the automation. The execution layer activates conveyors and diverters; tracking and completion events return to the systems for monitoring.
Illustrative specification model. Responsibilities and mechanisms are defined for each project.
Task contract: intention, execution and inventory
A movement task identifies the load, origin and condition that proves delivery. WMS may use orders, lines or handling units; WCS must map those objects to the identity observed by automation. An order split into three cartons is not three duplicate submissions of one task.
Specify identifier ownership, uniqueness scope and reuse rules. Distinguish business destination from physical position: a shipping door may use several buffers, but selecting a buffer does not automatically change the shipping commitment.
| Information | Reference authority | Validation before acceptance |
|---|---|---|
| Load / handling unit | WMS or agreed identification process | Recognized identity unambiguously linked to the task. |
| Business destination | WMS / orchestration | Existing destination eligible for this flow. |
| Route and intermediate position | WCS/MFC as designed | Capacity, restrictions and physical observations. |
| Inventory movement | WMS | Execution evidence and a deduplicable event identity. |
Cancelling a task that has already started
Cancellation is a state-dependent request. Decide against the physical commitment point, not merely when WMS transmitted the message. If execution starts while cancellation is in transit, accepting it without checking execution can leave inventory inconsistent with reality.
Define explicit outcomes: cancelled before execution, rejected after commitment, or an authorized compensating task linked to the original. Compensation preserves history; it does not retroactively erase a physical movement.
WMS → WCS
Request cancellation of T42 at the known version.
WCS → execution state
Check version, acknowledged command and physical commitment.
WCS → WMS
Return cancelled, rejected or pending decision with a reason.
Operations / WMS → WCS
If needed, authorize a compensating task linked to T42.
A cancellation timeout does not prove acceptance. Query the outcome before releasing incompatible work for the same load.