WMS, WES and WCS describe different responsibilities in a warehouse: managing stock and warehouse work, coordinating its execution, and directing automated equipment. The names help explain who makes which decision. They do not mean every warehouse needs three separate products.

For a warehouse systems lead, the distinction matters when an order becomes work for people and machines. Knowing which stock an order needs does not tell you when a workstation can receive it. Sending a movement request does not tell the operator that the goods have arrived. The system design has to connect those decisions and make their progress visible.

WMS: managing stock and warehouse work

A warehouse management system maintains warehouse inventory and supports activities such as receiving, putaway, picking and dispatch. Its responsibilities commonly include where stock is held, what is available and how it is allocated to orders. It can also direct people through warehouse tasks.

WMS therefore covers more than a stock list. Microsoft’s warehouse management overview, for example, describes configurable work templates and picking strategies alongside inventory status and receiving. A WMS may already provide much of the execution behaviour a manual warehouse needs.

WES: coordinating what should happen next

A warehouse execution system coordinates work across the resources needed to complete it. That can include choosing which orders to release, balancing work between stations and adapting the sequence to available people or equipment capacity. It connects the plan with what the warehouse can usefully do now.

Dematic’s software overview describes WES work release in relation to priority, resource availability and downstream capacity. This is the coordination problem: releasing more work into one area is not necessarily helpful when the next area cannot accept it. The exact sequencing rules and optimisation capabilities depend on the product and implementation.

WCS: directing automated material movement

A warehouse control system coordinates equipment routing and material flow. It communicates with the relevant equipment controls so conveyors, sorters or storage systems can carry out the requested movement, and makes equipment information available to the systems around it.

The WCS and machine-control boundary also needs specifying. Honeywell’s Momentum overview identifies warehouse control, execution and machine control as modules within its suite. Selecting software called a WCS does not settle the control interfaces, mechanical constraints or response times for a particular installation. Those belong in the equipment design and testing scope.

These are common functional distinctions, not a shared specification for every supplier. Dematic describes its WES as combining management and control functionality and operating alongside an existing WMS. Compare the actual responsibilities in your proposed system; products can overlap or combine them.

Follow a tote to a workstation

Consider an illustrative warehouse using automated tote storage and staffed picking stations. For clarity, this example assigns management, execution and control to separate systems.

The WMS identifies the stock allocated to an order and the tote containing it. The execution system considers the work waiting at the picking stations. Station one is occupied; station two can accept the task. It sequences the work for station two and requests the required tote. The WCS coordinates its route through the equipment controls.

The operator at station two needs more than a message that a tote has been requested. They need to know when the tote is ready, which item to take, how many units belong to the order and where to place them. A completed picking task can then update the order’s progress. The implementation must also account for any remaining picks before it treats the order as complete.

Four facts have appeared along that journey: the movement request was accepted, the tote arrived, the operator confirmed a pick, and the order’s required work was completed. Each answers a different question. Treating acceptance as arrival could present a task before its materials are ready. Treating one confirmed pick as order completion could hide remaining work.

This is why responsibility includes both issuing work and interpreting its result. For each handoff, identify the order or task reference, the receiving system and the event that authorises the next useful step. The aim is to keep people supplied with work they can perform and give the operation an accurate picture of what remains.

What happens when confirmation is missing?

If the tote movement has no completion result, the software cannot establish its physical location from an acknowledgement alone. Keep that movement unresolved and give the designated support owner the original request reference and known status. The equipment team needs to establish what happened before the integration owner decides whether to reconcile the result or submit further work.

Agree those responsibilities with the software and equipment suppliers, including how cancelled or partially completed work is represented. A repeated request must not accidentally create duplicate work. The supported protocol and recovery procedure require testing for the installation; a general category diagram cannot define them.

Choose the combination your warehouse needs

In a manual warehouse, the existing WMS may already provide the task sequence, operator instructions and progress information required. A separate WES needs a specific coordination problem to solve. Identify the missing decision and the people or equipment it needs to coordinate.

With substantial automation, coordination has to account for the equipment that receives and completes the work. Compare the supplier’s work-release and routing capabilities against the actual layout, resources and interfaces. Confirm what is already supplied together and what the integration project must connect. Equipment timing belongs with the specialist control requirements, not an assumption about a general business application.

Keel is an operations platform for shaping the human work around these systems. For example, an implemented preparation workflow could show the next job when the necessary material-readiness information is available, guide the person through that job and show the lead which work is waiting or underway. The team could change how preparation is organised while preserving the distinction between requested material, material ready to use and completed work.

Keel’s flows combine operator steps and processing; tools can present views of that work. Keel leads implementation of the agreed operational scope and arranges handover with your team. These capabilities do not establish native conveyor or PLC control, packaged warehouse-optimisation algorithms or guaranteed equipment response times. Assess any equipment integration separately with the relevant supplier. The platform and implementation guide explains what Keel supplies and what the project develops.

Discuss your execution workflow and systems boundary with Keel. Bring the work you want to organise and the WMS or equipment systems that already own part of it, so the discussion can establish what should connect and what should remain their responsibility.