The best MES and ERP setup depends on how the plant makes things, not on which vendor is largest. A 30-person job shop is well served by a job-shop ERP alone; a high-volume OEM supplier needs an ERP plus a real MES with a named connector between them; a regulated plant needs traceability built into whichever system holds the floor record. Below, six plant types, the systems whose own pages claim the fit, one sourced fact per product, and where each setup still leaves a gap. No prices or ratings are invented: where a vendor publishes no price, the entry says so.
In this guide
How were these setups chosen?
What is the best setup for a job shop under 50 people?
What is the best setup for a 50 to 250 person make-to-order plant?
What is the best setup for a high-volume discrete OEM supplier?
What is the best setup for a regulated aerospace, defense or medical plant?
What is the best setup for a process or batch manufacturer?
What is the best setup for a multi-site manufacturer?
Which MES vendors name an ERP connector in public?
Where does Morsa fit in any of these setups?
Sources, Changelog
How were these setups chosen?
Every product below was placed by what its own website says it is for, read on 19 September 2026, and nothing else. Each entry carries one quoted fact, the URL, and the vendor’s published price or the words “no public price”. Vendors whose sites blocked automated reading that day (Epicor, Oracle NetSuite, SAP Business One, QAD, DELMIA Apriso) are included by name only where a sibling page verified the same fact on 12 September 2026, and the entry says which date applies.
Two market facts frame the choices. IoT Analytics counts more than 300 MES vendors with the leader under 10% share, and estimates only 8% of plants run a commercial MES. And in Rockwell Automation’s July 2026 survey of 1,560 manufacturers, 44% ranked integration as their top MES buying requirement and only 23% had full integration with ERP. The pairing matters more than either pick. The full comparison of the two system types is at MES vs ERP. Picking the ERP first? See the best ERP for manufacturing.
What is the best setup for a job shop under 50 people?
A job-shop ERP with its own shop-floor module, and no separate MES. High-mix, low-volume work needs quoting, routing and job costing far more than machine connectivity, and every system below publishes that fit in its own words.
Product | Sourced fact (vendor’s own page, 19 September 2026) | Price |
|---|---|---|
Built for “high-mix, low-volume job shops”; offers “a multi-tenant SaaS cloud, a private hosted cloud for enhanced security, and traditional on-premise installation”; “seamless integration with QuickBooks (both Desktop and Online versions)” | No public price | |
Names “Shop Floor Control (MES)” and “Quality & Compliance (QMS)” as modules of one cloud system | “$50 / user per month”, “5-user minimum” | |
“MRPeasy is built for small and medium-sized manufacturers and distributors (up to 200 employees).” | Starter $49 per user per month; above 10 users each bundle of 10 is a flat $79 per month | |
“MRP + MES + PLM + Quality + Shop Floor + Maintenance. All you need on one single platform.” Custom plan runs “Odoo Online / Odoo.sh / On-premise” | Standard $24.90 per user per month billed yearly or $31.10 billed monthly (12-month discounted; list $31.10 and $38.90); Custom $49.00 yearly (list $61.00), read 24 September 2026 (Odoo pricing) | |
Markets to the MES search term but does not call itself an MES on its product pages; lists a third-party product, Jikko, under “MES” on its integrations page | Core “Starts at $299/month”; Free plan capped at 30 SKUs |
What this setup still misses: the schedule lives in the owner’s head. When a customer pulls a job forward, the ERP records the new date and nobody re-sequences the other four jobs on that machine. See production planning software for the tools that do.
What is the best setup for a 50 to 250 person make-to-order plant?
An SMB ERP with a manufacturing edition, plus either that ERP’s shop-floor module or a composable MES on the lines that need machine data. This is the size band where the MES decision is genuinely open, and where Rockwell’s survey found 33% of manufacturers calling MES their biggest data integration problem.
Product | Sourced fact | Price |
|---|---|---|
Manufacturing “features described in this article are available only if you have the Premium experience” (Microsoft Learn); “trusted by 55,000 companies” | Essentials $80, Premium $110 per user per month, paid yearly | |
“built to support multi-modal discrete and process manufacturing”; names Shop Floor Kiosk and Manufacturing Data Collection | APEX for Manufacturing “starting price under USD 2,185 monthly”, implementation included, SaaS only | |
“purpose-built for small and midsize industrial manufacturers”; “Extend your ERP with modular capabilities like MES, WMS, PLM, and CPQ”; AWS-hosted multi-tenant cloud | No public price | |
Built for “make-to-order, batch, or mixed-mode” manufacturers; names Smart Scheduling and Quality Control modules | No public price | |
“Composable MES for Discrete Manufacturing”; on-premise connector host from the Professional tier; NetSuite connector documented at library.tulip.co | Essentials $100 and Professional $250 per interface per month, billed annually, 10-interface minimum | |
“Specialized for discrete, make-to-order manufacturing”; cloud, on-premises or hybrid (verified 12 September 2026; host blocked re-check on 19 September) | No public price |
What this setup still misses: the ERP’s shop-floor module records completions but rarely connects to machines or reschedules inside a shift. Check those before deciding the module is enough.
What is the best setup for a high-volume discrete OEM supplier?
An ERP plus a real MES, integrated both ways, with a connector the MES vendor will name. Automotive and appliance suppliers live on OTIF delivery, and the record of what ran on which line by lot is not optional.
Product | Sourced fact | Price |
|---|---|---|
“Tailored for discrete, hybrid, and regulated industries”; “A multi-tenant Software as a Service (SaaS) environment” | No public price | |
“Opcenter Execution Discrete is a dedicated manufacturing execution system (MES) for discrete manufacturing job shops and complex assembly operations.” | No public price | |
Names automotive, electronics, industrial machinery among its industries; integration page says “Your ERP, PLM, and shop floor. One conversation.” without naming an ERP | No public price | |
“42Q is a full featured, cloud-based MES solution.”; “can be easily integrated with ERP systems such as SAP, Oracle and NetSuite using 42Q’s certified adapters” | No public price | |
“Modern ERP for small to mid-size manufacturing businesses”, sold as ERP with MES | No public price | |
“has both public and private deployment options”; SAP states “approximately 80% of SAP’s customers are small and medium enterprises” | No public price | |
Fit “companies of every size”; annual platform, module and user fees plus a one-time implementation fee (verified 12 September 2026; host blocked re-check on 19 September) | No public price |
What this setup still misses, even fully integrated: the two systems agree that 96 parts are short and nobody is told before the truck. GE Appliances’ Bill Good told Manufacturing Dive what integration buys: “I literally have visibility to every single assembly line, every piece of equipment in my plants.” Visibility is the input; the response is still a person.
What is the best setup for a regulated aerospace, defense or medical plant?
A system where traceability and document control are native to the floor record, and a deployment option the compliance regime allows. For ITAR and CMMC plants that usually means on-premise or a government cloud, which rules out several cloud-only products.
Product | Sourced fact | Price |
|---|---|---|
“Every other ERP is a system of record, but ProShop is a system of execution”; names aerospace, defense, medical and space; pricing “customized to match the unique needs of your shop”, with a government version offered | No public price | |
“Complex discrete manufacturing is our business.”; integration page names SAP, Deltek, IFS and Oracle | No public price | |
“MasterControl’s cloud-based manufacturing solution is cost-effective and fast to deploy.”; industries include pharmaceuticals, medical device, cell and gene therapies | No public price | |
Semiconductor, electronics, medical devices; enterprise integration data sheet documents receiving SAP IDocs and calling BAPIs | No public price | |
“built for job shops and mixed-mode manufacturers”; “Microsoft Azure Government Cloud” for ITAR | No public price | |
“industry-specific capabilities tailored to the unique needs of asset-intensive and mission-critical sectors”; names aerospace and defense; “MES integration and interactive lobbies” | No public price |
What this setup still misses: a quality hold that stops material in the MES does not, by itself, tell the customer’s program manager that Thursday’s shipment moved.
What is the best setup for a process or batch manufacturer?
A batch-aware ERP with recipe and lot management, plus an MES built around batch integrity rather than discrete work orders. Most discrete MES products model a routing, not a recipe.
Product | Sourced fact | Price |
|---|---|---|
“an all-in-one batch manufacturing ERP” with “Manufacturing execution system (MES)” and “Advanced planning and scheduling (APS)” named as modules; chemical, food and beverage, pharma, coatings | No public price | |
“Support GMP compliance, batch integrity, and full traceability in regulated pharma and biotech environments.”; integrations list runs from ABB to Blue Yonder | No public price | |
“Use AVEVA Manufacturing Execution System on premises or through a hybrid-cloud deployment.”; food and beverages, consumer goods, specialty chemical | No public price | |
“SYSPRO Cloud ERP is a flexible business solution offered as a service and ready to be deployed”; names chemicals, food and beverage, pharmaceutical, packaging, plastics | No public price |
What this setup still misses: yield variance. A batch that comes out 4% short is recorded correctly in both systems, and the customer allocation it affects is worked out by a planner the next morning.
What is the best setup for a multi-site manufacturer?
One ERP as the company record and one MES standard rolled out site by site, which is exactly what most manufacturers have not finished: Rockwell’s July 2026 survey found 93% have an MES somewhere and only 28% have deployed it enterprise-wide. Paul Andrews, Assistant Vice President of Systems at Kumi North America, is quoted in that release: “Before Plex, our operations struggled to synch and some locations didn’t have any software.” (Vendor case study.)
Product | Sourced fact | Price |
|---|---|---|
Enterprise edition “purpose-built for large industrial manufacturers with complex multi-site, multi-company, and multi-country operations” | No public price | |
Multi-tenant SaaS; the release above is Rockwell’s own evidence for multi-site rollout | No public price | |
“Leverage hosted infrastructure with easy scaling that lets you focus on strategy, not IT management.” | No public price | |
“integrates easily with other enterprise applications with SAP Business Technology Platform (BTP) and SAP Integration Suite” | No public price | |
Offers Cloud ERP, On-Premise ERP and Government ERP; “Customers in over 25 countries and 30 industries” | No public price |
Which MES vendors name an ERP connector in public?
Four of the eleven MES vendors whose integration pages we read on 19 September 2026 name a specific ERP; the rest describe ERP connectivity generically.
MES | Names an ERP? | Which |
|---|---|---|
iBase-t Solumina | Yes | SAP, Deltek, IFS, Oracle |
42Q | Yes | SAP, Oracle, NetSuite (“certified adapters”), others via Xchange APIs |
Tulip | Yes | Oracle NetSuite (connector documentation) |
Critical Manufacturing | Yes | SAP (IDocs, BAPIs) |
Parsec TrakSYS | List truncates at B on the page; none visible above the fold | ABB, Arena PLM, Autodesk, AWS, Azure, Benchling, Blue Yonder visible |
Rockwell Plex | Generic | “full connectivity to your ERP and third party external systems” |
AVEVA MES | Generic | “AVEVA Enterprise Integration automates the exchange of production planning and results data” |
Aegis FactoryLogix | Generic | “Your ERP, PLM, and shop floor. One conversation.” |
MasterControl | Generic | Categories only |
Siemens Opcenter | Generic | Only Siemens’ own Teamcenter named |
Epicor Advanced MES, SAP Digital Manufacturing, DELMIA Apriso | Not readable | Hosts blocked or served no content |
This is a statement about the pages read that day, not about the vendors’ full documentation. Ask for the connector by name and version before you sign.
Where does Morsa fit in any of these setups?
Morsa, the AI that operates the factory for you, is not an MES and not an ERP, and it is not a category winner on this page. It sits above whichever pair a plant chooses and handles the part no pairing above covers: what happens when the plan changes. It reads the ERP, the MES and the other plant systems, plus the places people talk, whatever they are; works out what a change affects downstream; decides the next step within the plant’s approved rules; gets it done through the tools the plant already uses; and closes work on proof. At J4S, a 120-person glass plant, on-time completion of operational commitments rose from about 30% to about 75% in four weeks with no new software (how the plant did it). At JRG Automotive, it caught 5 of 8 production-stopping shortages early enough to act and saved the plant $2 million. Every system above stays where it is. How the loop works: AI copilot for manufacturing. The wider map of plant systems is at manufacturing management software.
Whichever pairing fits your plant, the two systems will agree with each other and still drift from the floor, because both stop at the record. The ERP says 500, the MES says 462, and the person who has to do something about it finds out tomorrow. Morsa is the layer that catches the drift in whichever setup you run: it reads both records and the group chats, connects the gap to the customer order it puts at risk, routes the fix to its owner, and closes it on evidence. Every system above stays where it is. It is the only product on this page that guarantees the outcome, “We’ll catch a shortage in your plant, or you don’t pay,” and it prices on the value a pilot proves, not on users or interfaces. How Morsa is priced.
Sources
Vendor pages read 19 September 2026, all linked inline; Odoo pricing re-read 21 September 2026, when both tiers had moved up a step. Market and survey sources: IoT Analytics, 15 December 2025, https://iot-analytics.com/mes-vendors-replace-pen-paper-spreadsheets/; Rockwell Automation, 14 July 2026, 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; Manufacturing Dive, 22 May 2026 (Bill Good quote), https://www.manufacturingdive.com/news/mit-manufacturing-data-automation-ford-amgen-ge-arcelormittal/820681/; Microsoft Learn, https://learn.microsoft.com/en-us/dynamics365/business-central/production-manage-manufacturing. Epicor and NetSuite facts were verified on 12 September 2026 on the sibling page /guides/manufacturing-management-software; both hosts returned 403 to automated re-checks on 19 September 2026. Full verification notes are in the sources listed on this page.
Changelog
24 September 2026: Odoo prices re-read. Billed yearly, Standard is $24.90 and Custom $49.00 per user per month for the first 12 months (lists $31.10 and $61.00); billed monthly they are $31.10 and $61.10 (lists $38.90 and $76.20). Every current Odoo price on this page now names its billing term.
Prices re-read 21 September 2026: Odoo’s published ladder moved up a step, so Standard is $31.10 per user per month on yearly billing against a $38.90 list and Custom is $61.00 against a $76.20 list, correcting the $24.90 and $49 figures this page carried. Katana’s $299 Core plan needs a $199 per month manufacturing management add-on, which this page had not recorded. No other price on this page changed.
21 September 2026: added a closing paragraph to the Morsa section on the plan drifting from the floor whichever tool is chosen, the guarantee, and the pricing model, with a link to /pricing.
