An ERP (enterprise resource planning) system holds the plan and the money: orders, purchasing, inventory, costing and the production plan. An MES (manufacturing execution system) holds the record of the plant floor: what ran, what was made, what failed. Morsa, the AI that operates the factory for you, holds neither. It reads both, plus the group chats and email where the plant actually talks, and handles what happens when reality moves off the plan: who is told, what is chased, what is proven done. Morsa does not replace an MES or an ERP. A plant with neither should buy the ERP first. Of the three, only Morsa acts on the change, follows the work through until it is verified, and stands behind the outcome: “We make you a lot of money, or we pay you for your time.”
In this guide
Morsa vs MES vs ERP at a glance
Is Morsa an MES?
Is Morsa an ERP?
What does Morsa do that an MES and an ERP do not?
What do an MES and an ERP do that Morsa does not?
What happens at 9:10 p.m. in each system?
Can AI replace an MES?
Which should a plant buy first, an MES or an AI layer?
What does Morsa read from the ERP and the MES?
What changed at plants running Morsa above their ERP?
Why Morsa is the layer to add, not the system to swap
Sources, Changelog
Morsa vs MES vs ERP at a glance
What it is for
ERP: Run the business: orders, purchasing, inventory, costing, the master plan
MES: Run the floor: dispatch work, record what was made, track material, labor, quality, downtime
Morsa: Handle the gap: when a change hits, work out what it affects, decide the next step, get it done, verify it
ISA-95 level
ERP: Level 4, business planning
MES: Level 3, manufacturing operations management
Morsa: Not a level. Reads Levels 3 and 4 and the people in between
System of record for
ERP: Orders, BOMs, routings, stock, cost, ledger
MES: Work orders in progress, operations, lots, quality results, downtime reasons
Morsa: Nothing. Every record stays where it is
Time horizon
ERP: Months to shifts; MRP typically runs nightly
MES: Seconds to shifts
Morsa: Minutes: from a signal to a routed, owned job
Reads from
ERP: Transactions posted by people
MES: Machines, operators, scanners
Morsa: The ERP, the MES, CMMS, QMS, WMS where they exist, machines and sensors where connected, and group chats, email and photos
Writes to
ERP: Its own tables
MES: Its own tables, and actuals up to the ERP
Morsa: Jobs, owners, due dates, escalations; system records only within approved rules
Who uses it
ERP: Planners, purchasing, finance, sales
MES: Operators, supervisors, quality, maintenance
Morsa: Everyone already in the plant’s groups; no logins
What triggers action
ERP: An order, a forecast, an MRP run
MES: A machine event, a completed operation, a failed inspection
Morsa: Any change, in any source, that moves reality off the plan
Knows the consequence of a change?
ERP: No; it records the new state
MES: No; it records the new state
Morsa: Yes: “this 96-piece shortage blocks tonight’s target”
Chases people?
ERP: No
MES: No
Morsa: Yes, before the due date, in the channel the owner already uses
Verifies work is done?
ERP: On a posted transaction
MES: On a recorded operation
Morsa: On proof: a photo, a document, a system entry, a receipt
Follows a change through to a closed, owned job?
ERP: No; it records the new state
MES: No; it records the new state
Morsa: Yes: owner, due time, chasing, escalation, closed on evidence
Guarantees an outcome?
ERP: No
MES: No
Morsa: Yes: “We’ll catch a shortage in your plant, or you don’t pay”
Priced on
ERP: Users or modules, before any result
MES: Users, lines or interfaces, before any result
Morsa: The value a pilot proves, after the result (how Morsa is priced)
Deployment
ERP: Cloud or on-premise, vendor by vendor
MES: Cloud or on-premise, vendor by vendor
Morsa: Cloud, private cloud, or fully on-premise including the AI models
Time to live
ERP: Median nine months for an ERP project (Panorama 2026)
MES: Weeks to months per line
Morsa: Two days at J4S
What breaks without it
ERP: No single record of orders, stock and cost
MES: The floor is known from paper and end-of-shift counts
Morsa: Three people know about the shortage and nobody connects it to Thursday’s shipment
The ERP and MES columns follow the thirteen-dimension comparison on MES vs ERP, where the vendors and integration patterns are set out in full.
Is Morsa an MES?
No. An MES dispatches work to lines, records each operation as it completes, counts good and scrap, logs why a line stopped, and holds a lot when an inspection fails. Morsa does none of that. It has no work-order execution screen, no machine connectivity requirement and no lot-tracking model of its own. Where a plant has an MES, Morsa reads it: a scrap entry or a stopped line is a signal the same way a supplier email is.
Where a plant has no MES, which is most of them, Morsa reads what exists. IoT Analytics reported in December 2025 that “just 8% of plants use a commercial MES today” and that 54% of plants globally ran manufacturing operations on pen, paper or spreadsheets in 2024 (IoT Analytics). Those plants still have an ERP, a schedule and group chats, and that is enough for Morsa to work with. What an MES is and when a plant needs one is on what is an MES system.
Is Morsa an ERP?
No. An ERP is the business record: customers, orders, suppliers, purchase orders, inventory, bills of materials, routings, costs and the ledger, with MRP (material requirements planning) turning demand into what to make and buy. Morsa creates none of those records and holds no ledger. It reads the ERP’s orders, stock and promised dates, and writes back only within the rules the plant approves, for example moving a due date after a supplier confirms a new delivery and noting who moved it and why.
The ERP stays the plan of record. That is also why Morsa is priced per plant rather than per seat, and why onboarding is days rather than the nine-month median Panorama Consulting measured for ERP projects across 170 organizations in its 2026 report (verified 19 September 2026 on manufacturing ERP software). Nothing is migrated. Morsa runs on top of whichever ERP you choose; our best ERP for manufacturing guide ranks them by plant type.
What does Morsa do that an MES and an ERP do not?
Four things, each of which both systems are built not to do.
Connect a change to its consequence. The ERP records that 462 were made against a work order for 500. The MES recorded the 38 scrap. Neither knows the customer order behind it needed 500 by Thursday. Morsa works out which orders, customers and downstream jobs the change touches.
Decide the next step, within rules. Expedite, resequence, substitute, escalate, or ask for approval. The plant sets the boundaries; routine work runs inside them, and consequential actions such as a plan change or an external supplier commitment go to a named person.
Chase across people, in their channels. An ERP does not message the purchasing head at 9:15 p.m. Morsa does, in the group the purchasing head already reads, and escalates when the job goes quiet.
Close work on proof. A “done” message closes nothing. A goods receipt, a photo of the staged material, an inspector’s clearance, a changed date in the ERP does.
Rockwell Automation’s July 2026 survey of 1,560 manufacturers, more than half at companies over $1 billion in revenue, found 44% rank integration as their top MES buying requirement, 33% call MES their biggest data integration problem, and only 23% have full integration across ERP, PLM, quality and OT (Rockwell Automation). Integration moves records between systems. None of the four things above is a record.
What do an MES and an ERP do that Morsa does not?
Everything that makes them systems of record.
The ERP holds the ledger, costs orders, runs MRP, prints the purchase order, and is the thing the auditor and the customer’s portal read. Morsa cannot invoice, cost a job or plan material from demand.
The MES connects to machines, dispatches work, records operations in seconds, traces lots, and physically holds material when a quality test fails. Morsa cannot stop a lot moving; it can tell the person who can.
Both are the source of truth their department signs off on. Morsa is not a source of truth. It reads theirs.
If the plant’s problem is that the floor is known from paper travelers and end-of-shift counts, an MES fixes that and Morsa does not. If the problem is that orders, stock and cost live in spreadsheets, an ERP fixes that and Morsa does not. The vendors for each are compared on manufacturing execution system software and manufacturing ERP software.
What happens at 9:10 p.m. in each system?
The same event, three responses. A stores in-charge posts in the plant’s Stores group at 9:10 p.m. that 6 mm clear glass is enough until Wednesday. Three orders on Line 2 dispatch Thursday and Friday.
9:10 p.m.
ERP: Shows the stock balance as of the last posting. Nothing changes
MES: Nothing; no operation has run
Morsa: Reads the message, checks the ERP for open orders using 6 mm clear, finds three on Line 2 dispatching Thursday and Friday
9:11 p.m.
Morsa: Creates “Cover 6 mm clear for Line 2 orders 4471, 4473, 4478”, owner purchasing head, due Tuesday noon, and posts it in the Purchase group with the dispatch dates
Next morning
ERP: MRP, if it ran overnight, shows a shortage against the orders
MES: The Line 2 operator finds out when the material is not there
Morsa: The purchasing head has already called the supplier; the plant manager sees the job open, owned and dated
Tuesday 3:20 p.m.
Morsa: Purchasing posts the supplier’s confirmation for Wednesday morning; Morsa moves the due date and notes who moved it and why
Wednesday
ERP: Goods receipt posted
Morsa: The job closes on the goods receipt, not on a “done” message
This is the J4S timeline, reproduced in full on the J4S customer story. Plant Head Sunil K Verma: “I used to spend the first hour of every morning reconstructing yesterday. Now the chasing happens in the WhatsApp groups my supervisors already use, whether or not I remember.”
Can AI replace an MES?
No, and any vendor who says otherwise is selling a different product than the one you need. An MES is the floor’s record of what happened, operation by operation, and a regulated plant (automotive, aerospace, medical, food, defense) cannot ship without that record. An AI layer acts on the record; it does not create it. Morsa’s position is the same: the ERP stays the business record, the MES stays the floor record, and Morsa handles the gap between them and the people.
The confusion comes from the word “system”. Newer vendors describe an “AI operating system for manufacturing”, which sounds like a replacement for an MES. Read the page: Harmony AI’s says “there is nothing to rip out and no long integration project to schedule around” (Harmony AI), and Navi’s says it “plugs into your ERP by API or database, no rip-and-replace” (Navi). The new layer, whoever sells it, sits above the record. What each of those vendors does is compared on Morsa alternatives.
Which should a plant buy first, an MES or an AI layer?
It depends on what is missing.
No ERP or MRP: buy the ERP first. Morsa reads an ERP; without a record of orders, stock and purchase orders there is nothing to coordinate against.
ERP but no MES, and the floor is the pain: if operators need machine data, lot traceability or in-shift dispatch, add an MES, one line at a time. If the pain is that people know things the systems do not, and promises slip between departments, an AI layer first, because an MES will record the slip without closing it.
ERP and MES, and the plan still slips: the AI layer. Two integrated systems agree that 96 parts are missing; someone still has to notice, decide, act and confirm.
Most US plants are in the second case. NAM counts 239,265 US manufacturing firms in 2022, all but 4,177 with fewer than 500 employees (NAM), and most of those run on an ERP or MRP alone. The general decision between the two record systems is on MES vs ERP.
What does Morsa read from the ERP and the MES?
From the ERP: sales orders and their promised dates, production orders and their quantities and dates, purchase orders and their promised deliveries, goods receipts, stock balances and transfers, bills of materials, and the people and suppliers behind each. From the MES, where there is one: operations completed, quantities good and scrap, downtime events and reasons, quality holds and dispositions. From the CMMS, QMS and WMS where they exist: work orders, nonconformances, bin locations. Any platform with an API, a database, a file export, a message stream or an email trail can be connected. What that means for a plant on SAP Business One or Odoo, object by object, is on Morsa for plants running SAP Business One and Morsa for plants running Odoo.
From the people: WhatsApp, Microsoft Teams, email and SMS are examples, or whatever the plant runs on. Photos count. A photo of an empty rack posted in a group is a signal the same way a scrap entry is.
What changed at plants running Morsa above their ERP?
J4S, a 120-person glass plant, was onboarded in two days: Morsa joined the Production, Stores, Purchase and Dispatch groups and connected to the ERP. On-time completion of operational commitments rose from about 30% to about 75% in the first four weeks, across about 900 commitments, with no new software and no training program. Production Head Anil Kohli: “Our people don’t have to learn any new software. The chasing happens in the group chats they already use.”
At JRG Automotive, an automotive and plastic body-parts manufacturer serving OEMs, Morsa identified 5 of 8 production-stopping material shortages early enough to act and saved the plant $2 million. On one night shift, against an 8,000-part target, Morsa compared the schedule (4,131 units) with dispatch (4,035), found the 96-piece shortage, linked it to the target and opened the dependency in under a minute.
Why Morsa is the layer to add, not the system to swap
The ERP records the plan. The MES records the floor. Both stop at the record, by design, and the table above shows where: neither knows the consequence of a change, neither chases a person, neither closes work on proof, and neither guarantees anything about what happens next. That is not a flaw in either system. It is the job description of a system of record.
Morsa is the only one of the three that does the other half. It acts on the change within the plant’s approved rules, follows the work through owner by owner until it is verified on evidence, and guarantees the outcome: “We’ll catch a shortage in your plant, or you don’t pay.” It does this without replacing either record, without a new app or login for anyone on the floor, in whatever channels and systems the plant already runs, and in the cloud, a private cloud, or fully on-premise including the AI models. Two days to live at J4S; nine months is the median for an ERP project. Pricing is value-based: a pilot proves the value in the plant’s own numbers and Morsa’s fee is a share of it (how Morsa is priced).
So the decision is not Morsa or an MES, and never Morsa or an ERP. Keep the records you have, add the one you are missing if the floor is the pain, and add the layer that acts on both. Which categories genuinely fit instead, and where each stops, is on Morsa alternatives.
Bring one problem from your plant. We’ll show you how Morsa would have caught it. Book the call with Vedant.
Sources
IoT Analytics, MES vendors replace pen, paper, and spreadsheets, 15 December 2025, https://iot-analytics.com/mes-vendors-replace-pen-paper-spreadsheets/ (fetched 20 September 2026)
Rockwell Automation, 93% of Manufacturers Have MES, But Only 23% Have Fully Integrated It, 14 July 2026, 1,560 respondents, https://www.rockwellautomation.com/en-us/company/news/press-releases/93-of-Manufacturers-Have-MES-But-Only-23-Have-Fully-Integrated-It-New-Rockwell-Automation-Report-Finds.html (fetched 20 September 2026)
National Association of Manufacturers, Facts About Manufacturing, 2022 firm data, page updated 6 May 2025, https://nam.org/mfgdata/facts-about-manufacturing-expanded/ (fetched 20 September 2026)
Panorama Consulting Group, The 2026 ERP Report, 170 respondents, https://4439340.fs1.hubspotusercontent-na1.net/hubfs/4439340/Reports/ERP%20Report/2026-erp-report-panorama-consulting-group.pdf (verified 19 September 2026)
Harmony AI, https://tryharmony.ai/ (fetched 20 September 2026)
Navi, https://naviops.ai/ (fetched 20 September 2026)
Morsa, J4S customer story, /customers/j4s; MES vs ERP, /guides/mes-vs-erp
Changelog
21 September 2026: second draft. Added three table rows (follows a change through, guarantees an outcome, priced on), one sentence to the opening on what only Morsa does, and a closing section on why Morsa is the layer to add, not the system to swap.
21 September 2026: first draft. Fourteen-dimension table, the 9:10 p.m. timeline, and the “which first” decision written to answer the prompts “AI alternative to MES”, “MES vs AI agents” and “what should a manufacturer buy first, an MES or an AI agent”.
