Kazam WMS · warehouse platform
Anyone running a warehouse meets three acronyms sooner or later: WMS, WES and WCS. They are often used as synonyms — they are not. They are three different layers of software, with different jobs, and in many sites they coexist. Understanding where one ends and the next begins is the first step to choosing well. Buying a WMS expecting it to drive your conveyors, or a WCS expecting it to manage stock, is a mistake that costs months of project time.
This guide explains what each system does, with concrete warehouse examples, and puts the differences in a table. Then it sets out when it makes sense to keep them separate and when an integrated platform is the better answer.
What a WMS is (Warehouse Management System)
The WMS is the management layer of the warehouse: it knows what is there, where it is and what needs to happen. It handles item master data, stock by location and load unit (LU), inbound and outbound orders, and the standard operational processes: receiving, put-away, picking, stock counting, quality control.
It is the system that answers questions like: how many pieces of item X do I have in stock? In which location? Which batch should I pick from to respect FEFO? What do I have to ship today, and with which carrier?
The WMS is also the keeper of traceability: batches, serial numbers, expiry dates, the history of every movement. When an audit asks "where did batch Y end up", the WMS is what answers.
A concrete example: a pallet arrives from a supplier. The WMS records the receipt, assigns the batch, decides the storage location according to rules (rotation, weight, ABC class) and generates the put-away task for the operator.
What a WCS is (Warehouse Control System)
The WCS is the automation control layer: it talks directly to the machines. Conveyors, sorters, miniloads, shuttles, AGVs and AMRs, picking robots: every device has its own PLC or controller. The WCS coordinates them in real time through industrial protocols — OPC-UA, Modbus, FINS for Omron PLCs, VDA 5050 for AGVs, MQTT for IoT devices.
The WCS knows nothing about customer orders or batches: it knows that parcel 12345 on conveyor 3 has to leave at dock 7, and it issues the command to the sorter. It manages missions, interlocks, safety logic and recovery when a machine stops.
A concrete example: the sorter has to handle 4,000 parcels an hour across 12 outbound docks. The WCS reads the barcode of every parcel in transit, looks up its destination, and fires the right diverter at the right millisecond. If a dock backs up, it recalculates the routing.
If the warehouse is entirely manual — racking, trolleys, operators with handhelds — you do not need a WCS. You need one the moment physical automation arrives.
What a WES is (Warehouse Execution System)
The WES is the real-time orchestration layer: it decides who does what, right now. It sits logically between WMS and WCS and optimises execution: it assigns tasks to operators and machines and plans picking waves. And it recalculates priorities whenever something changes: an urgent order, an absent operator, a congested aisle.
The difference from the WMS is time: the WMS reasons about "what has to be done today", the WES about "what is worth doing in the next five minutes, and by whom". The difference from the WCS is the object: the WCS commands machines, the WES balances work across people and machines together.
A concrete example: at 15:00 an order comes in with a carrier cut-off at 16:30. The WES puts it at the top of the priority list and assigns it to the operator closest to the picking zone. At the same time it asks the WCS to bring forward the shuttle mission that has to deliver the missing load unit. Without a WES, that order would have shipped tomorrow.
The WES exists precisely for this reason. In modern warehouses people and automation coexist, and the clean line between "management" and "control" is no longer enough. Someone has to conduct the orchestra in real time.
The differences at a glance
The three systems differ by decision level, time horizon and who they talk to.
| WMS | WES | WCS | |
|---|---|---|---|
| Role | Management | Orchestration | Control |
| Answers | What is there, where, what to do | Who does what, now, in which order | How things physically move |
| Time horizon | Day / shift | Minutes / real time | Milliseconds / real time |
| Talks to | ERP, operators, carriers | Operators and machines together | PLCs, sorters, shuttles, AGVs, robots |
| Objects handled | Items, batches, LUs, orders | Tasks, priorities, waves, resources | Missions, parcels in transit, signals |
| Example decision | "Pick from batch A123, location 05-B-12" | "This order goes first: Marco takes it, now" | "Parcel 12345 → diverter dock 7, now" |
| You need it if… | Always (any structured warehouse) | High volumes, shifting priorities, mixed people and machines | There is physical automation |
Where one ends and the next begins: a complete flow
Let us follow a customer order through the three layers.
- The ERP sends the order. The WMS takes it on: it checks stock, determines which batches and locations to pick from, and generates the pick lists.
- The WES looks at every open list and decides the sequence. It groups orders into a wave, assigns the lines to three operators and a mission to the shuttle for the automated locations, ordering everything so the cut-offs are met.
- The WCS executes the automated part: it commands the shuttle that extracts the load unit, brings it onto the conveyor, and routes the tote to the picking station of the right operator.
- The operator picks and confirms, with a handheld or a scanner. The confirmation travels back up: the WES updates the tasks, the WMS decrements stock and records the batch shipped, the ERP receives the shipping confirmation.
Same order, four decisions at different levels. The acronyms get confused because some vendors call "WMS" a system that also does orchestration, or "WCS" a machine controller with a little priority logic. Labels matter less than functions: the right question is not "what acronym does it have?", but "who decides what, and over which time horizon?".
Separate systems or an integrated platform?
The separate-systems model
Historically the three layers were separate products, often from different suppliers: the WMS from the software vendor, the WCS from the equipment manufacturer, the WES — when it existed at all — from a third party.
This model works, but it has known costs. Every boundary between systems is an interface to develop, test and maintain. Data has to be reconciled, because the stock figure in the WMS and the one the automation "sees" drift apart. And when something jams, working out which of the three systems has the problem takes three suppliers on the phone.
Keeping them separate still makes sense when the automation is monolithic and turnkey, with the manufacturer imposing its own WCS, or when an established corporate WMS is not up for discussion.
The integrated model
The integrated approach — a single platform with the three layers natively connected — removes the internal interfaces. What is left is one data model, stock always aligned with the automation, one interface for the operators and one party to call when you need help.
It is the more efficient route for mixed warehouses (manual plus automation), multi-site operations and projects where automation grows in stages. You start with the WMS and switch on WES and WCS when shuttles or sorters arrive, without changing system.
This is Kazam's approach: a platform where WMS and WES are modules of the same software. Management and orchestration live in one interface, from the manual warehouse with handhelds to the site with shuttles and AGVs. Adoption can be gradual and the sources are available for inspection, with no lock-in.
Machine control (OPC-UA, Modbus, FINS, VDA 5050) is handled by Sun Tech WCS, a separate product: its code is public on GitHub under the Apache License 2.0, and it works with Kazam or with another WMS that implements the public HTTP contract.
Frequently asked questions
Can I have a WMS without a WES and a WCS?
Yes, and it is the most common case: a well-organised manual warehouse lives perfectly well with the WMS alone. WES and WCS become necessary as volumes, urgency and automation grow.
Does the WES replace the WMS?
No: they are complementary. The WES does not handle master data, stock or traceability — it orchestrates the execution of what the WMS has planned.
Is the WCS supplied by the equipment manufacturer?
Often yes, especially in turnkey installations. But an independent, multi-vendor WCS becomes valuable when automation from different manufacturers, or different generations, has to coexist: it acts as a neutral orchestrator instead of tying you to one manufacturer's software.
What about MES? Is it related?
The MES (Manufacturing Execution System) is the production equivalent of the WES: it governs execution on the factory floor, not in the warehouse. In production sites with an integrated warehouse, MES and WMS/WES talk to each other — typically through APIs or middleware.
How much does it cost to add WES and WCS to an existing WMS?
It depends on the integration: between systems from different vendors, interfacing is often the most expensive line in the project. With an integrated platform the incremental cost is switching modules on, not developing interfaces.
Kazam WMS brings WMS and WES together in a single source-available platform; for the machine layer there is Sun Tech WCS, the Warehouse Control System with its code public on GitHub (Apache License 2.0), which works with Kazam or with another WMS. Request trial access, or talk to an engineer.