MES vs ERP: one plans, the other executes. And neither replaces the other.
«We already have an ERP — why would we buy an MES?» is one of the questions we hear most often, and it's a good one: the wrong answer is expensive in both directions. ERP and MES are not competitors: they work on different time horizons, granularities, and users, and they're at their best when integrated. This guide explains who does what, when the ERP's production module is genuinely enough, and how to build the integration without double data entry.
Written byStefano Brachet Contol — CTO & Founder, IOMA
Published
9 min read
Updated
Updated
1 · The ERP
What does the ERP do, and where does it stop in production?
The ERP (Enterprise Resource Planning) runs the business: customer orders, purchasing, inventory accounting, invoicing, costs, high-level requirements planning (MRP). It's the source of truth for the business side: what was sold, what to buy, how much to produce and by when. No structured company stands without one — that's not up for debate.
The point is where the ERP stops: at the shop-floor door. It knows 5,000 parts are due Friday, but not what's happening on the line right now: which order is on the machine, why station 3 has been down for twenty minutes, how many parts of the batch came out good. In the ERP, that data typically arrives by manual declaration — at the end of the shift, the day, or the job. It arrives late, aggregated, and with the accuracy of whoever transcribed it.
2 · The MES
What does the MES do? Execution, part by part.
The MES (Manufacturing Execution System) lives on the shop floor and governs execution: it takes the orders planned in the ERP and turns them into real work on the line — sequences, recipes, declarations, checks. It talks to the machines' PLCs, so it sees production as it happens: parts counted from the field, downtime with causes, process parameters, scrap attributed to the station and the moment it was born.
That field connection is the difference: part-by-part batch traceability, OEE computed on real data rather than estimated, order progress in real time. The MES answers questions the ERP can't even formulate: «why did line 2 produce 12% scrap last night?», «where did the 40 minutes lost in the changeover go?», «which batches contain the component from supplier X?».
3 · The comparison
What is the difference between MES and ERP, in practice?
The conceptual distinction — planning vs executing — becomes concrete along five axes. They're the same ones we use during assessments to tell whether a company actually needs an MES or whether a well-configured ERP is still enough.
Axis
ERP
MES
Time horizon
Days, weeks, months: deliveries, requirements, budgets. Asking it for real time is like asking the balance sheet what's happening at the till right now.
The part, the machine cycle, the single downtime event. Regulatory traceability — batches, genealogy — necessarily lives at this granularity.
Who uses it
Finance, purchasing, planning.
Operators, shift leads, quality and maintenance: people standing in front of a machine, often wearing gloves. Interfaces and response times must be designed for them.
Data source
Human input: the production figure is declared.
The field, read from the PLCs: the figure is measured.
Question it answers
«How much did I sell, buy, produce this month, and at what cost?»
«What's happening on the line right now, and why did yesterday go the way it did?»
On scrap and downtime the gap between the declared figure and the measured one is routinely double-digit: that's why the two systems don't replace each other. You need both answers, and they come from two different systems.
4 · The false friend
Why isn't the ERP's «production module» enough?
Almost every ERP has a production module, and for accounting production it works: it opens orders, receives declarations, backflushes materials. The trouble starts when you ask it to govern production: with no PLC connection it sees neither real stops nor real cycles, progress depends on manual declarations, and OEE — if present — is computed on data entered at the end of the shift.
The typical outcome is a double track: the ERP says one thing, the shop floor knows another, and parallel spreadsheets nobody controls flourish in between. It's not the ERP's fault: it's the symptom of using an administration tool for an execution job.
The honest test: if production data reaches your ERP at end of shift, transcribed from paper or Excel, you don't have an MES — you have an ERP with a declaration module. Which is fine, until someone asks for batch traceability, real OEE, or downtime causes.
5 · The integration
How do MES and ERP integrate, SAP included?
The integration almost always follows the same design. Downward (ERP → MES): product and routing master data, planned production orders, BOM versions. Upward (MES → ERP): progress, production declarations, material consumption, produced batches. The rule that holds it together: every piece of data is born once, in the system closest to where it happens — the order in the ERP, the declaration on the line.
Technically, SAP integrations typically go through the standard interfaces (IDoc, BAPI, or OData APIs depending on the version); other ERPs via APIs or structured exchanges. It is IT/OT integration in the full sense: the MES sits between the PLCs and the ERP, and that's exactly where the two worlds must talk reliably, traceably, and securely.
When is the ERP enough, and when is it time for an MES?
Not every factory needs an MES tomorrow morning. These are the practical criteria we use to steer the decision — in both directions.
The ERP is enough (for now) if…
Few machines and simple processes, no batch traceability obligations, rare stops with known causes, a single shift, customers who don't ask for production reports. In that scenario an MES would add cost without leverage.
You need an MES if…
Traceability is required by regulation or customers (food, medical, automotive), downtime and scrap must be attributed by cause, lines are multi-station and multi-shift, OEE is needed as a tool rather than a slide, or your Industry 4.0 investment requires documented interconnection.
Count the Excel sheets living between the shop floor and the ERP. If there are more than two, and someone spends hours reconciling them, the MES isn't a cost: it's the end of work you're already paying for, done badly.
7 · What to avoid
The mistakes we see in MES + ERP projects.
Four recurring mistakes when MES and ERP meet — all cheaper to avoid than to fix.
Taking the ERP vendor's MES «by default»
Sometimes it's the right choice, but it must be verified on the shop floor, not in the boardroom: the MES lives with operators and PLCs, and the convenience of native integration doesn't compensate for weak execution at the line. Judge the MES by what it does on the line — the integration gets built either way.
Duplicating master data
Products and routings maintained by hand in two systems always diverge — it's only a matter of time. Master data has one owner (normally the ERP) and the MES receives it: every exception must be designed, not suffered.
Integrating everything at once
Integration is done by flows, in order of value: orders and declarations first, then consumption, then the rest. A big bang where everything goes live together multiplies failure points exactly when people are still learning the system.
No data owner
When a declaration doesn't reconcile, whose problem is it: the MES's, the ERP's, or the interface's? If the answer isn't written down before go-live, the answer will be «nobody's» — for years.
FAQ
Frequently asked questions on MES and ERP
Questions Plant Managers ask before starting an MES/SCADA project.
My ERP already has a production module — do I still need an MES?
It depends on what you ask of it. For opening orders, receiving declarations, and backflushing materials, the ERP's production module is enough. If you need part-by-part batch traceability, OEE computed from field data, downtime with causes, and real-time order progress, you need a system connected to the PLCs — that is, an MES. The practical test: if data reaches the ERP by manual declaration at end of shift, you don't have an MES yet. That is the scope ARIA MES/SCADA covers: it reads the PLCs and hands the ERP data that is already consolidated.
How do MES and SAP integrate?
Through the standard flows: master data and production orders come down from SAP to the MES; progress, declarations, consumption, and batches go back up from the MES to SAP. Technically you use SAP's interfaces (IDoc, BAPI, or OData APIs depending on version and release), with agreed mappings on master data and statuses. It's a real integration project, but a well-trodden path: the critical part isn't the technology, it's deciding who owns which data.
Can I run an MES without an ERP?
Yes. The MES also works on its own: directly loaded orders, traceability, OEE, and supervision all function. It's a common scenario in companies that start from the shop floor and integrate the ERP at a later stage. Integration multiplies the value (no double entry, accounting aligned with real production), but it's not a prerequisite to start.
What data flows between MES and ERP?
Toward the MES: product and routing master data, BOMs, planned production orders. Toward the ERP: production progress and declarations, material consumption, produced batches with quality outcomes. Frequency depends on the flow: orders may come down in batches several times a day, declarations go up near-real-time or at end of shift. The design rule: every piece of data is born once, in the system closest to where it happens.
Will the MES replace my ERP, or vice versa?
No, in neither direction. They're different levels of the same pyramid: the ERP administers the business, the MES executes production. ERPs promising to «cover the shop floor too» without a PLC connection fall back into the declaration module; MES products attempting accounting step outside their trade. The strength is in the integration, not the substitution.
How much does MES-ERP integration cost?
It depends on the number of flows and the state of your master data more than on technology: an orders + declarations integration with clean master data is a contained project; master data to clean up and custom flows make it grow. Within a full MES project, ERP integration is one of the main items alongside installation — our MES and SCADA cost guide has the full ranges and a worked example with real numbers.
Go deeper
Related pages for anyone deciding how the shop floor and the ERP should talk.
Describe the line and the problem on a 30-minute technical call: we tell you straight away whether it's in our wheelhouse. We typically reply within 24 hours. From the first call to commissioning, you speak to the same person.