Warehouse Control System (WCS)
What a WCS does, how it differs from a WMS and a WES, and why the layer above it is the one that decides how well your equipment actually performs.
A Warehouse Control System is the software layer that drives material handling equipment in real time — conveyors, sorters, AS/RS, vertical lift modules, light-directed picking. It turns instructions expressed in business terms into device commands: divert at this scanner, present this tray, illuminate this display.
It works on a different timescale from everything above it. A WMS thinks in seconds and orders. A WCS thinks in milliseconds and motors.
WMS vs WES vs WCS
| WMS | WES | WCS | |
|---|---|---|---|
| Answers | What should happen, and why | What happens next, and in what order | How the machine does it, right now |
| Holds | Stock, orders, allocation, customers | Work queues, resource state | Device state, sensor inputs |
| Timescale | Seconds to days | Seconds | Milliseconds |
| Scope | Whole operation, all locations | One site, people and machines | One equipment set |
| You need one if | Always | Rarely as a separate product | You run high-speed sortation or a large automated system |
The layers
Where the boundary sits
The WMS names what is required and from where. How it gets there is the machine's.
A carton needs to reach lane four. Saying so requires the order, the carrier and the consolidation point — information that exists nowhere near the conveyor. The divert itself happens as the carton passes a scanner, in tens of milliseconds, and is entirely the machine's.
Same for a vertical lift module. We ask for a tray. How the lift travels to reach it is optimisation inside its own boundary — not business logic, just the machine doing its job well.
The layer that decides how well equipment performs
Most attention goes to the machine, and to the WCS that drives it. Neither is usually where the performance is won or lost.
A vertical lift module presents trays quickly no matter who asks. What decides whether the operation is fast is which trays, in what order, alongside the lines that are not in the machine, released against the right cut-off. Those are execution decisions, and they need the stock position and the order priority — information the machine does not have and should not be asked to hold.
That layer is the WES. It exists as a separate product category because most warehouse management systems cannot do it — middleware bridging an older WMS to modern equipment. If the WMS can sequence work across people and machines itself, the third system is unnecessary, and so is the third copy of your stock position.
Where we sit, stated plainly
BizBloqs provides the WMS and the WES. We do not sell a WCS and we do not drive machines. The equipment's own controller presents the tray, runs the motors and holds the interlocks. That is the manufacturer's work and it belongs with them.
What we do is hold the single stock position, make the decisions above it, and integrate to the equipment's host interface to issue the instruction. One stock position, one instruction set covering the machine and the racking together, and a change to the flow is a configuration change rather than a change request on someone else's roadmap.
Questions worth asking a vendor
- After this is installed, how many systems hold a stock quantity for the same item? Name them.
- When those two numbers disagree, which one is right, and who notices?
- What does this box need to be told, and what does it work out for itself?
- Can an order with lines inside the equipment and lines in racking be picked as one instruction to one operator?
- What happens to the rest of the operation when this machine is down and its stock is inside it?
The longer version
The full paper works through where the boundary genuinely has to sit and where it is vendor convenience, what it costs when it is wrong, why the WES category exists at all, and a worked example of the integration boundary on a Kardex vertical lift module.
The paper is in preparation — this page links to it on publication.
Common questions
What is a warehouse control system?
Software that drives material handling equipment in real time, converting business instructions into device commands. It operates in milliseconds, where a WMS operates in seconds.
What is the difference between a WMS and a WCS?
A WMS holds the business state — stock, orders, allocation, customer promises — and decides what should happen. A WCS holds device state and decides how equipment executes it.
What is the difference between a WES and a WCS?
A WES coordinates work across people and machines. A WCS controls the equipment itself. In practice the categories overlap: some products marketed as a WES are a WCS with added reporting, others are a WMS module.
Do I need a WES?
Usually not as a separate product. A standalone WES is a third system with its own database, which means a third place your stock position can disagree with itself.
Can a WMS replace a WCS?
Generally no, and it should not try. Device control belongs with the equipment manufacturer's controller. For high-speed sortation it is not arguable — divert decisions happen in tens of milliseconds.
Can a WMS replace a WES?
Frequently yes, and that is the more useful question. A WES releases work, sequences tours and balances load. Those decisions need the stock position and order priority, which the WMS already holds.
Is a WCS the same as a PLC?
No. A PLC controls a machine's physical function and safety interlocks. A WCS coordinates across machines and connects them to instructions from above.
Part of the material handling equipment reference. MHE integration is a paid add-on at SME+ and a further paid add-on at Enterprise, scoped per installation because the equipment differs on every site. It is not available at SME.