An MES runs and records production at the line. A WMS runs material in the warehouse: receiving, put-away, bin locations, picking and shipping. They meet at the line-side handoff, so a plant that moves a lot of material between the two usually needs both, joined by lot, quantity and location messages.
The MES vs WMS question often starts with one concrete problem: the line stopped, the warehouse says the pallet was picked, and nobody can prove what happened in between.
So this page follows one pallet across the boundary. Each system's job gets clear once you see where it hands over.
What each system is in charge of
A warehouse management system (WMS) knows where every lot and pallet is, down to the bin. It directs the people and machines that move them.
A manufacturing execution system (MES) knows which order runs on which machine, what it consumed, what it made and what stopped it.
The ERP sits above both. It holds the order, the stock value and the financial posting, and it thinks in days.
| ERP | MES | WMS | |
|---|---|---|---|
| Main question | What do we owe, buy and make? | What is running, and how is it going? | Where is it, and who moves it next? |
| Unit of work | Sales or production order | Operation on a machine | Pick, move or put-away task |
| Typical records | Costs, purchase orders, stock totals | Counts, stops, consumption, quality checks | Bins, lots, pallets, task times |
| Time scale | Days and weeks | Shifts and minutes | Hours and minutes |
In ISA-95 terms, both MES and WMS work at Level 3, under the business systems. Part 3 of the standard defines inventory operations management as Level 3 activity, and the ISA-95 levels page shows how the layers stack.
One pallet, start to finish
Example: a bottling line needs a pallet of caps, lot L-2207. Here is who does what.
The order needs caps. The MES, or a line-side bin signal, sends a replenishment request with item, quantity and line.
The WMS chooses the lot by first expired, first out, creates the task and sends a driver to the bin.
The driver scans the pallet into the line-side location. The WMS closes the task.
The operator scans L-2207. The MES checks that the item, the lot status and the order match.
The MES ties the lot to the order and the finished lot. This is the genealogy link.
The MES reports the finished pallet and its label. The WMS assigns a bin and creates the put-away.
The data that crosses the boundary
The interface is smaller than people fear. Five message types carry most of the load.
- Material request, MES to WMS: item, quantity, destination line, needed-by time.
- Delivery confirmation, WMS to MES: pallet ID, lot, quantity, location, time.
- Consumption and returns, MES to WMS or ERP: how much was used, and what went back to stock.
- Production receipt, MES to WMS: finished quantity, lot, pallet ID. A GS1 SSCC is a standard choice for that ID, since it identifies a logistic unit such as a pallet.
- Lot status, in both directions: released, on hold or quarantined, so nobody picks or runs a blocked lot.
Decide who owns each field, because a lot status with two owners will drift until a held lot gets used. The wider picture is in MES system architecture.
Why neither system sees the whole wait
This is where the comparison stops being theory and starts costing minutes. Each system holds half of the story of a line that waits for material.
Example: the request goes out at 09:40. The pick starts at 09:55, finishes at 10:12, and the pallet reaches the line at 10:14.
The line ran out of caps at 09:58, so it stood still for 16 minutes.
The WMS report shows a normal pick of 17 minutes. The MES report shows a 16 minute stop coded "waiting for material".
Only the joined view shows the real fix: the request sat for 15 minutes before anyone started it. The trigger should fire earlier, or the task should rank higher.
For OEE, that stop falls inside planned time, so it counts as an availability loss: 3.3 points on a 480 minute shift. See waiting for material downtime for how to code and reduce it.
Line-side stock, lots and labels: the grey zone
Three areas cause most of the arguments in a project.
- Line-side stock. Many MES products track material at the line, and many WMS products extend to it. Pick one owner for that location.
- Lot tracking. The WMS tracks lots moving between places. The MES tracks lots turning into other lots. A recall needs both chains, as MES traceability explains.
- Label printing. Either can print the finished pallet label. Choose one, or you will get two numbers on one pallet.
Which setup fits which plant
Both: you have a real warehouse with many bins, frequent line feeding, lot or expiry rules, and output that must be traced. Food, pharma and automotive suppliers often land here.
WMS only: your main pain is picking errors, lost stock or slow shipping, and the lines already run well enough on simple records. Distribution-heavy sites start here.
MES only: the warehouse is small and the ERP's stock module knows where things are, but you cannot say why the lines lose time. Start at the line, as in MES for small manufacturers.
Neither, for now: you have one or two lines, few parts and a clean stock count. A downtime log and the ERP may carry you until the questions outgrow them.
A quick test before you buy
Log every stop for two weeks and give waiting for material its own reason code. Then add up the minutes.
If waiting for material is the top loss, measure the warehouse side next, because a WMS or a better trigger may pay back first. If breakdowns, changeovers and short stops dominate, the warehouse is not your first problem.
Interface mistakes to design out
- Building the interface around files sent once a shift. A line that runs out in 20 minutes needs the request now.
- Two stock figures for line-side material. Agree which system is the truth, and reconcile the other to it.
- Forgetting returns. Half a pallet goes back to the warehouse after a changeover, and if nobody records it, the stock count breaks.
- Coding the wait as "other". The minutes then vanish from the argument with the warehouse. Use clear downtime reason codes.
If your lines keep waiting on material, start by putting a number on the wait. Fabrico is a light MES for OEE: it takes stops live from the machine, and operators tag the cause at the line, so waiting for material shows up per line and shift. See how Fabrico tracks stops and causes.
What people ask next
Can an ERP replace a WMS and an MES?
An ERP's stock module can cover simple warehouses, and its shop floor module can take order confirmations. It rarely directs individual picks or records machine stops. The MES modules page shows what the line side usually adds.
Does a WMS talk directly to the MES, or through the ERP?
Both patterns are common. Material requests that must move in minutes usually go directly or through middleware, while financial postings go to the ERP. See MES system architecture for the layout.
Which should we implement first, MES or WMS?
Start where the measured loss is bigger. Two weeks of stop data with a separate code for material waits will show it, and the OEE calculator turns those minutes into availability.
Is a warehouse control system the same as a WMS?
No. A warehouse control system (WCS) drives conveyors, sorters and automated storage in seconds, under the WMS. It is to the warehouse what machine control is to the line, one layer below the Level 3 systems.
Who owns lot genealogy, the MES or the WMS?
The MES owns which input lots became which output lot. The WMS owns where those lots moved and who received them. A full recall trace joins both, as covered in MES traceability.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.