If you've spent any time around manufacturing technology, you've heard both terms: ERP and MES. They're often mentioned together, sometimes used interchangeably, and frequently the subject of debate when a plant is evaluating new software.

The confusion is understandable. Both systems touch manufacturing. Both deal with production orders, materials, and data. And in some cases, vendors on either side claim their product can do what the other does.

But ERP and MES are fundamentally different tools, designed with different purposes, operating at different speeds, and serving different audiences. Understanding the distinction, and more importantly where they complement each other, is one of the most valuable frameworks a manufacturing professional can develop.

The Short Version

ERP is the business brain of a manufacturing company. It manages planning, finance, procurement, inventory, and scheduling at an enterprise level. It answers questions like: What do we need to make? When? How much will it cost? Do we have the materials?

MES is the shop floor brain. It manages the real-time execution of production once work reaches the factory floor. It answers questions like: Is this machine running? Did this operator complete that step? Was this component the right lot number? Did this unit pass inspection?

ERP looks ahead and keeps score. MES executes and records in the moment.

ERP in a Manufacturing Context

ERP systems originated in the 1990s as an evolution of earlier MRP and MRP II systems. The core idea: integrate all of a company's core business functions into a single system with a shared database.

For manufacturing specifically, ERP handles:

  • Demand and supply planning. ERP receives customer orders or forecasts, runs MRP logic, and generates planned work orders and purchase orders. It answers: "Given everything we've sold and everything we have, what do we need to make and buy?"
  • Work order management at the planning level. ERP creates and releases production orders, tracks status in broad terms (released, in progress, complete), and manages the financial side of those orders.
  • Inventory management. ERP manages balances across warehouses, plants, and storage locations. It records receipts, issues, transfers, and provides financial valuation of inventory on hand.
  • Procurement. Generating purchase orders, tracking supplier delivery, receiving goods, and matching invoices.
  • Finance and costing. Standard costs, cost rollups, variance analysis, month-end close. ERP is the financial system of record for manufacturing.
  • Master data. Item masters, BOMs, routings, work centers, cost centers. The foundational data that everything else depends on.

What ERP is not good at: operating at the speed of the factory floor. Machines produce 200 parts per minute. Shift changes happen every 8 hours. Quality failures need to be caught before the next operation, not at the end of the day. Machine downtime events need to be captured in real time, not logged retroactively.

ERP also lacks the native ability to monitor machine status, guide operators through assembly steps, enforce component lot traceability, calculate real-time OEE, or trigger automated responses to production events. These aren't failures of ERP. They reflect the fact that ERP was designed to run a business, not a machine.

MES in a Manufacturing Context

Manufacturing Execution Systems emerged in the late 1980s and 1990s to fill the gap between the planning world (ERP) and the physical world (the factory floor). The term was formalized by MESA International and later standardized under ISA-95, the international standard for enterprise-to-manufacturing system integration.

MES operates in real time, on the factory floor, managing the actual execution of production from the moment a work order is released until finished goods are reported complete.

  • Work order execution and dispatch. When ERP releases a work order, MES takes over. It dispatches jobs to work centers, manages the queue at each station, and tracks real-time status. Supervisors and operators interact with MES on the shop floor, not ERP.
  • Operator guidance. Modern MES platforms deliver step-by-step work instructions to operators at their stations, with diagrams, torque specs, photos, or video. This replaces paper travelers and ensures the right instruction reaches the right operator for the right configuration.
  • Labor tracking. MES captures real-time labor: who worked on what, when, for how long. This feeds both productivity analysis and job costing.
  • Material tracking and traceability. MES enforces that the correct materials (right part, right lot, right quantity) are consumed at each step. It records which component lots or serial numbers went into which finished goods. This is the foundation of full genealogy traceability.
  • Quality at the point of production. In-process inspection results, measurement values, pass/fail determinations. MES can enforce quality gates, preventing an operator from proceeding until inspections are passed.
  • Machine and equipment integration. MES connects to PLCs, CNCs, test equipment, scales, and scanners to collect production data automatically. Cycle times, counts, machine states, and process parameters are captured without manual entry.
  • OEE and production performance. Because MES captures machine status, production counts, and quality data in real time, it calculates OEE (Availability x Performance x Quality) continuously. Live dashboards, not end-of-shift reports.
  • Genealogy and traceability. A complete record of what was used, who did what, which equipment was involved, and what quality results were recorded for every unit or lot produced. In regulated industries, this isn't optional.

What MES is not good at: the broader business. It doesn't manage financials, run MRP, handle procurement, maintain master data, or manage enterprise-wide inventory. MES is fundamentally dependent on ERP for master data, demand signals, and financial integration.

The ISA-95 Framework

The ISA-95 standard provides the most widely accepted framework for understanding how ERP and MES relate to each other. It defines a five-level hierarchy:

  • Level 4: Business Planning and Logistics. Enterprise business management. This is where ERP lives.
  • Level 3: Manufacturing Operations Management. Production execution and management. This is where MES lives.
  • Level 2: Supervisory Control. Process monitoring and control (SCADA, HMI).
  • Level 1: Basic Control. Direct machine control (PLCs, DCS).
  • Level 0: Physical Process. The actual production equipment, sensors, and actuators.

The interface between Level 4 and Level 3 is where most ERP/MES integration work happens. Understanding that they occupy different layers makes it much easier to see why they need each other and why neither can fully replace the other.

Where They Overlap

The overlap is real, and it's the source of most of the confusion.

Work order status tracking. Both systems track production orders. ERP tracks them at a business level (released, in progress, complete). MES tracks them at an operational level (which operation is active, what quantity has been produced, what's in queue). MES provides the granular status; ERP reflects the summary.

Labor reporting. ERP has labor capture capabilities, but it's typically manual, end-of-shift, or end-of-order. MES captures labor in real time, at the operation level, through shop floor terminals. Most manufacturers with both systems use MES as the source of truth for labor and feed summaries back to ERP for costing.

Inventory and material consumption. ERP "backflushes" materials when a work order completes. MES can capture actual consumption in real time, at each operation, with lot/serial verification. In high-traceability environments, MES is the system of record for actual consumption.

Quality data. ERP quality modules handle inspection plans, quality notifications, and supplier quality. MES handles in-process quality capture, SPC, and quality gates on the shop floor. Many manufacturers use both for different purposes.

Production reporting. Some ERP systems offer basic production reporting. But the real-time, machine-connected OEE and analytics that operations leaders need to manage a shift live in MES.

Why Most Manufacturers Need Both

Three fundamental realities drive this.

They operate at different speeds. ERP operates at business speed: minutes, hours, days. MES operates at production speed: seconds, minutes. A quality failure needs to be caught before the part moves to the next operation. The architecture, database design, and integration patterns required for each are fundamentally different.

They serve different users. ERP users are planners, buyers, accountants, and managers in offices who think in terms of orders and costs. MES users are operators, supervisors, and quality technicians on the factory floor who think in terms of jobs and machines and need fast, touch-friendly interfaces that work in loud, dirty environments.

Their data has different lifecycles. ERP manages data relevant for months or years: customer orders, financial records, inventory valuations. MES manages data relevant in the moment: machine states, operator actions, in-process measurements. Combining these into a single system creates architectural tensions that are difficult to resolve.

The Integration Between Them

If manufacturers need both systems, they need them to work together. The core integration flows are well-defined.

ERP to MES (downward): work orders released for production, BOM and routing information, material master data, production schedules, engineering change notifications.

MES to ERP (upward): work order completions (quantities produced, scrapped, reworked), actual labor hours, actual material consumption, quality results, production performance data.

The standard for this integration is ISA-95 / B2MML (Business to Manufacturing Markup Language). In practice, it's implemented through native connectors built by MES vendors, middleware platforms like MuleSoft or Dell Boomi, direct database integration (common but discouraged), or flat file exchange (common in older environments).

The quality of this integration determines how much benefit you actually realize from having both systems. A poorly integrated ERP/MES environment means operators re-keying data, reconciliation taking hours, and the systems creating more work than they save.

Can One Replace the Other?

Can ERP replace MES? Major ERP vendors have built increasingly capable execution modules. SAP has Manufacturing Execution within its Digital Manufacturing suite. Oracle has extensive WIP modules. Microsoft D365 has production floor execution capabilities.

For simple discrete manufacturing with short routings, no regulatory traceability, and limited quality complexity, a capable ERP may be sufficient. But for manufacturers who need real-time machine integration, strict lot/serial genealogy, step-by-step work instructions, in-process SPC, complex dispatching, or regulatory compliance documentation (FDA, AS9100, IATF 16949), a purpose-built MES will almost always outperform an ERP's manufacturing module.

Can MES replace ERP? No, and this is rarely proposed seriously. MES has no business management capabilities. It can't manage financials, run MRP, handle procurement, or maintain enterprise inventory. Some MES vendors offer broader manufacturing operations management platforms, but even the broadest assume ERP handles the business layer above them.

The practical answer, developed over decades of implementation experience: ERP for the business layer, MES for the operations layer, and clean integration between them.

Do You Need an MES?

If you're evaluating whether your operation needs an MES, these are the questions that matter:

  • Do you have regulatory traceability requirements (FDA, AS9100, IATF 16949)?
  • Do you need lot or serial genealogy, knowing exactly which components went into which finished goods?
  • Do you have significant in-process quality requirements with real-time inspection and quality gates?
  • Do you need real-time OEE and machine performance visibility?
  • Do you have complex routings with multiple operations and real-time dispatching needs?
  • Is operator error a significant quality or safety risk that needs guided work instructions?
  • Is your ERP's shop floor module consistently failing to give supervisors the visibility they need?

If you answered yes to two or more, a purpose-built MES is worth serious evaluation.

Common Platforms

ERP platforms with manufacturing focus:

MES platforms:

  • Siemens Opcenter covers broad manufacturing industries, with strength in automotive and electronics.
  • Rockwell FactoryTalk / Plex is strong in automotive and food and beverage.
  • AVEVA MES (formerly Wonderware) is strong in process and hybrid manufacturing.
  • Tulip is a modern, no-code/low-code platform growing in discrete manufacturing.
  • Ignition (Inductive Automation) is a flexible platform popular for custom MES builds.
  • Aegis FactoryLogix is strong in electronics manufacturing.

Where NetSuite Fits

Since this is a topic I get asked about regularly, it's worth addressing NetSuite's manufacturing capabilities specifically.

NetSuite sits firmly on the ERP side of the ERP/MES divide. Its manufacturing modules cover the business layer well: BOMs and routings, work order management, MRP demand planning, inventory and warehouse management, and standard costing with variance analysis. For companies that need planning, procurement, financials, and basic production tracking in a single cloud platform, NetSuite handles the core ERP manufacturing functions.

NetSuite also supports assembly builds and work orders with component backflushing, phantom assemblies, and work-in-process tracking at the order level. For simpler discrete manufacturing operations, especially those without heavy regulatory traceability or real-time machine integration requirements, NetSuite's native manufacturing capabilities may be sufficient on their own.

Where NetSuite's manufacturing support reaches its limits is exactly where MES takes over. NetSuite doesn't natively connect to shop floor equipment. It doesn't capture real-time machine states or calculate live OEE. It doesn't provide step-by-step electronic work instructions to operators. It doesn't enforce in-process quality gates or maintain the kind of granular lot/serial genealogy that regulated manufacturers require.

For NetSuite customers who need those capabilities, the path is typically one of two approaches:

  • Integrate with a purpose-built MES. Platforms like Tulip, Rootstock (which runs on Salesforce but integrates with NetSuite), or industry-specific MES solutions can handle the shop floor execution layer. Work orders flow down from NetSuite, completions and actuals flow back up.
  • Extend NetSuite with SuiteScript and custom development. For manufacturers whose MES needs are modest, such as basic operator data capture, simple quality checklists, or barcode-driven material tracking, custom Suitelets and SuiteScript can bridge some of the gap without introducing a separate system. This approach works for targeted use cases but doesn't scale to the full breadth of what a dedicated MES provides.

In practice, I've found that NetSuite manufacturers tend to follow a predictable progression. They start with NetSuite's native manufacturing modules, which handle the planning and financial side well. As the operation grows in complexity, they run into the shop floor visibility gap. At that point, they either add a lightweight MES or build targeted SuiteScript extensions, depending on the scope of what they need.

The key is to recognize where the boundary is. NetSuite is a strong manufacturing ERP. It's not an MES. Knowing that distinction early saves you from trying to force NetSuite into a role it wasn't designed for, and helps you plan for the right complementary tools when the time comes.

The Bottom Line

ERP and MES aren't competitors. They're partners in a well-designed manufacturing technology stack, each operating in the domain it was built for.

ERP is your business command center: it plans what needs to be built, manages the resources and materials, captures the financial results, and maintains the master data. MES is your shop floor command center: it executes the plan in real time, guides every operator action, enforces quality at every step, tracks every component, and captures the performance data that tells you how well your factory is actually running.

The goal isn't to choose between them. It's to implement both thoughtfully, integrate them cleanly, and give each system the data and authority that matches its purpose. When ERP and MES work together as designed, planners have accurate data, operators have clear instructions, managers have real-time visibility, and finance has accurate cost data to close the books.

That's the manufacturing technology stack working the way it was meant to work.