The short answer, up front
ERP plans, transacts and accounts. MES executes on the floor. An Enterprise Resource Planning (ERP) system is the business layer that decides what to make, buy and bill, and records the money and stock value behind it — orders, purchase, inventory accounting, planning and finance. A Manufacturing Execution System (MES) is the shop-floor layer that turns that plan into produced parts — it opens work orders, issues material, captures good and reject work-in-progress at every operation, and transfers finished goods back into stock.
The two overlap at the edges — both touch stock, both know about a work order — but they answer different questions. ERP answers “what should we make, buy and bill, and what did it cost?” MES answers “what is being made right now, against which order, how far down the route is it, and how much did we make good versus reject?” One is a system of record for the business; the other is a system of execution for the plant. For a fuller definition of the execution layer on its own, see our pillar guide to production management software.
What ERP does
An ERP is the transactional backbone of the business. It carries the master data that everything else references — customers, suppliers, items and units — and it records the commercial documents that move money and value: sales orders, purchase orders, goods receipts, invoices and the general ledger. Its job is to keep the business reconciled: what did we sell, what did we buy, what do we owe, what is our stock worth, and what should we produce next.
On the manufacturing side, an ERP is where planning lives. It nets demand against supply, suggests what and how much to make, and raises the work order with its target quantity and date. It also holds inventory as a valued, accounted quantity — so it knows the cost of stock and posts the accounting entries when material is consumed and finished goods are received. What an ERP typically does not do well is drive an operation-by-operation route in real time on the floor. It tends to record production as a transaction after the fact — “this quantity was produced, this material was consumed” — rather than track every operation, work center and reject as it happens.
That is a deliberate design choice, not a flaw: an ERP is optimised for the business rhythm — daily, weekly, monthly close — not the second-by-second rhythm of a machine. Improsys ships a dedicated business tier for exactly this role, Fast ERP, on the same platform that Fast Production executes on.
What MES does
An MES lives on the shop floor. It takes the released engineering definition — the Bill of Materials, the Bill of Resources and the process route sheet — and the work order the plan raised, and it drives that order through production as a chain of linked, recorded events. Where an ERP knows a work order exists, an MES knows exactly where it is: which operation it has reached, which work center it is on, how much good output has passed, how much was rejected and where.
Concretely, an MES does the work an ERP records only in summary:
- Drives the work order down its route — internal or sales work orders, job cards for the floor, and consumption tracked against BOM operation by operation.
- Runs a real reserve-then-issue material discipline — earmarking stock, issuing it to the line at source, and deducting stock only at the moment of issue.
- Captures good, reject and scrap WIP per operation — so quality loss is recorded where it happens, not lumped into a single end-of-line total.
- Transfers finished and semi-finished goods to stock and closes the loop with line rejection and a controlled rework route.
The result is traceability an ERP cannot reconstruct after the fact: which material and lot went into a work order, who ran each operation, what was rejected at which work center, and where the finished lot went. For a step-by-step tour, see the production management process and how production software works.
MES vs ERP, side by side
The clearest way to separate the two is to line them up against the questions a plant actually asks. Notice that in almost every row the answer is not “one or the other” but “different jobs at different altitudes.”
| Dimension | ERP — the business layer | MES — the execution layer |
|---|---|---|
| Primary question | What should we make, buy and bill — and what did it cost? | What is being made right now, against which order, and how much was good vs reject? |
| Layer / ISA-95 level | Level 4 business & planning | Level 3 shop-floor operations |
| Time granularity | Transactional — posts events after the fact, on a business rhythm | Real-time — operation by operation, as it happens |
| Data captured | Orders, POs, invoices, stock valuation, plans, ledgers | Work orders, material issue, good/reject WIP, scrap, FG transfer, defects |
| Typical users | Sales, purchase, planning, stores, finance, management | Operators, line supervisors, production and quality engineers |
| Work orders | Plans & raises the order and its target quantity | Executes the order down its route to completion |
| Material issue / WIP | Accounts for stock value; issue recorded as a transaction | Reserve then issue at source; good/reject WIP booked per operation |
| Traceability | Order-to-invoice, lot valuation, cost roll-up | Material → work order → operation → lot: who ran what, what was rejected |
| Rejection / rework | Seen mostly as a cost line | Line rejection at part/child level, controlled rework loop, defect↔work-center |
| Reporting / OEE | Financial and sales MIS, stock and ageing reports | Job-card status, process-cost & rejection MIS, OEE dashboards |
Read down the table and a pattern emerges: ERP is broad and slow-moving, MES narrow and fast-moving. ERP knows the whole business but only a summary of the floor; MES knows the floor in detail but leaves the money and the commercial documents to the layer above it.
The ISA-95 stack — where MES sits
The cleanest mental model for MES vs ERP is the ISA-95 reference model, an international standard that describes a manufacturing enterprise as a stack of levels, each with its own job and its own time horizon.
Reading the stack from the bottom up:
- Levels 1–2 — sensing and control. The physical machines, sensors and PLCs (Level 1) and the SCADA/HMI supervisory control that monitors and directs them (Level 2). This is milliseconds-to-seconds territory.
- Level 3 — manufacturing operations (MES). Work orders, material, WIP, routing, production records and shop-floor traceability. This is the shift-and-operation rhythm — the layer this whole comparison is about.
- Level 4 — business planning and logistics (ERP). Orders, purchasing, planning, inventory accounting and finance. This is the daily-to-monthly business rhythm.
Put that way, “MES vs ERP” is slightly the wrong framing: they are not rivals for the same slot but neighbours on the stack. The real question is whether your plant is complex enough to need the Level 3 layer at all, and how cleanly it hands off to Level 4.
Do you actually need both?
Not every manufacturer needs a distinct MES. The honest answer depends on how much real complexity lives on your shop floor. The split below is a good first filter.
- ERP alone may be enough when jobs are simple assemble-and-ship with little routing.
- There are few operations and no per-operation reject to trace.
- A single material issue and a production booking capture reality well enough.
- No customer or regulator demands lot-level shop-floor traceability.
- You need an MES when you run multi-level BOMs and a true Bill of Resources.
- Work routes across several operations and work centers with standard times.
- You need good/reject WIP per operation, line rejection and a rework loop.
- Customers, audits or field failures demand material-to-operation traceability.
In practice, most discrete manufacturers eventually land in the right-hand column and need both layers: ERP to plan, purchase and account, and MES to execute and record what actually happened. This is exactly why traceability-driven sectors — automotive components, fabrication job shops, engineered assemblies — reach for a dedicated execution layer. The benefits of production management software are almost all things a Level-4 ERP cannot see: operation-level yield, defect-to-work-center mapping, honest WIP and recovered rework.
Not sure whether your ERP's work-order screen is enough?
Show us one real part — its BOM, its route, its rejection — and in 30 minutes we will show you exactly where an ERP stops and an MES begins, on your own data.
How MES and ERP work together
When both layers are present, they run as a single relay rather than two islands. The handoff is what makes the difference between one continuous chain and a stack of disconnected spreadsheets.
Here is the part that matters most, and where the usual “MES vs ERP integration” headache disappears entirely in the Fast Suite. Fast Production is the MES tier of the same Improsys platform that also offers Fast ERP — so they do not integrate by file export at all. They share one item master, one stock ledger and one document engine. A work order, a material issue, a WIP posting and a finished-goods transfer are all records in the same tables the commercial and inventory side already use.
That single-engine design is why Fast Planning / MRP can generate a work order and its reservation and Fast Production can issue straight against it, and why every issue and transfer is immediately visible to Fast Inventory and Fast Quality without a nightly sync. There is no interface to maintain, no export to reconcile, and no window where the plan, the floor and the accounts disagree. It is simply one database with a shop-floor profile and a business profile switched on. See the full integrations overview for how the manufacturing core fits together.
Why the shared engine beats file-export integration
Consider an automotive component manufacturer running ERP for planning and accounting, and a bolt-on MES for the floor. Work orders export from one and reject data imports back into the other — and the two never quite agree, because a mid-shift issue or a rework recovery lands in one system hours before the other. On the shared Fast platform, the same work order planning raises is the one production issues against and transfers finished goods on. There is one number for stock, one for WIP, one for FG — because there is one engine. This is the profile behind real deployments such as Nikhtish Engineering and Solidus Hi-Tech.
Frequently asked questions
What is the difference between MES and ERP?
ERP (Enterprise Resource Planning) is the business and transaction layer — it manages orders, purchasing, inventory accounting, planning and finance, and answers what should we make, buy and bill, and what did it cost. MES (Manufacturing Execution System) is the shop-floor execution layer — it runs work orders, issues material, captures good and reject WIP at each operation, and transfers finished goods, answering what is actually being made right now, against which order, and how much did we make good and reject. ERP plans and accounts in transactions; MES executes and records on the floor in real time. In ISA-95 terms, ERP is Level 4 and MES is Level 3.
Do I need both an MES and an ERP?
Not always. If your plant runs simple assemble-and-ship jobs with little routing, few operations and no in-process rejection to trace, an ERP with a basic work-order screen may be enough. You need an MES the moment shop-floor execution has real complexity — multi-level BOMs and Bills of Resources, routed operations across work centers, a genuine reserve-then-issue material discipline, operation-level good and reject capture, line rejection and a rework loop, or customer-driven traceability. Most discrete manufacturers eventually need both: ERP to plan, purchase and account, and MES to execute and record what actually happened on the floor.
What is ISA-95 and where does MES fit?
ISA-95 is the international standard that describes the layers of a manufacturing enterprise as levels. Levels 1 and 2 are the sensors, machines and control systems (PLC and SCADA) on the equipment. Level 3 is manufacturing operations — the MES layer that manages work orders, material, WIP, routing and production records. Level 4 is business planning and logistics — the ERP layer that handles orders, purchasing, planning and finance. MES sits at Level 3, deliberately between ERP above it and the machines and controls below it, translating the plan from ERP into executed, recorded production.
Can an ERP handle shop-floor execution on its own?
An ERP can hold a work-order screen and a simple material issue, and for low-complexity shops that may suffice. But a pure ERP typically records production in transactions after the fact rather than driving it operation by operation in real time, so it struggles with routed multi-operation work, good-and-reject WIP at each step, defect-to-work-center mapping, line rejection and a controlled rework loop. When those things matter — and they do for automotive, engineered and regulated parts — you need the MES execution layer. The cleanest arrangement is an MES that shares one item, stock and document engine with the ERP rather than bolting on as a separate system.
How do MES and ERP share data in Fast Production?
Fast Production is the MES tier of the same Improsys platform that also offers Fast ERP, so they share one item master, one stock ledger and one document engine rather than integrating by file export. Planning or the ERP raises the work order and MRP reservation; Fast Production issues material against that reservation, books good and reject WIP through the route, and transfers finished goods — and because every one of those postings rides the same shared stock and document tables the commercial side uses, stock depletion, WIP and finished-goods receipt are immediately visible to the rest of the system. There is no interface to maintain and no export to reconcile; it is one database with a shop-floor profile and a business profile switched on.