The confusion between ERP and Manufacturing Execution Systems (MES) is one of the most costly systems misunderstandings in manufacturing. It shows up as manufacturers who implement ERP expecting it to manage shop-floor execution, find that it does not, and either accept the gap or invest in a second implementation to fill it. The right frame is not which is better, or which to implement first. The right frame is: what problem does each system solve, and how do they need to work together to produce outcomes that neither can produce alone. --- What ERP Actually Does ERP is a system of record. Its core function is to capture the authoritative record of what happened — what was ordered, produced, shipped, and invoiced. ERP excels at four functions: master data management (items, customers, suppliers, BOMs, routings), financial integration (direct connection between operational transactions and financial postings), supply chain planning (MRP-driven demand-supply balancing), and compliance and reporting (audit trail and structured reporting for regulatory and management requirements). ERP does these things well because it was designed for them. The properties that make ERP good at record-keeping — structured transactions, mandatory field validation, batch processing — are exactly the right properties for these functions. --- What MES Actually Does A Manufacturing Execution System is a system of execution at the work-order level. Its core function is to manage the real-time flow of production work on the shop floor. MES excels at work order management (dispatching to work centres, tracking status in real time), quality data capture (inline checks, inspection results, nonconformance records), genealogy and traceability (complete record of what materials, equipment, operators, and conditions produced a specific batch), and performance monitoring (OEE and throughput at work centre level in real time). --- Why Manufacturers Confuse Them The confusion arises because ERP and MES share a boundary — the production order. ERP creates it and receives the completion confirmation. MES executes against it and produces the events that eventually update ERP. Manufacturers who implement ERP expecting it to handle both sides discover that ERP handles planning and record-keeping well but cannot manage real-time execution without unacceptable friction. Manufacturers who implement MES without ERP integration create a data silo disconnected from planning, procurement, financial, and customer-facing processes. The resolution is neither system alone. It is both systems, connected at the production order boundary, each doing what it was designed to do. --- The Integration Architecture That Makes Both Systems Work The integration between ERP and MES should be narrow, well-defined, and stable. Four data flows are sufficient. ERP to MES: Production orders flow from ERP to MES when released for execution, carrying item, quantity, routing steps, target dates, and material requirements. MES to ERP: Production confirmations flow from MES to ERP when work orders are completed, carrying actual quantities, materials consumed, actual times, and quality results. ERP to MES — master data: Item masters, BOMs, routings, and work centre definitions flow from ERP to MES as reference data. MES does not maintain its own master data — it uses ERP's. MES to ERP — quality holds: Quality holds affecting inventory status flow from MES to ERP as inventory status changes, keeping the authoritative inventory record accurate. --- Where the Gap Between ERP and MES Still Lives Even with a well-functioning ERP-MES integration, a coordination gap remains: the space where cross-functional decisions happen in real time but are not supported by either system. A quality hold requiring coordinated response from production, quality, planning, and customer service simultaneously. A machine breakdown requiring immediate notification to maintenance, planning, materials, and logistics. A priority change needing to propagate to production sequencing, materials staging, and dispatch scheduling in real time. Neither ERP nor MES was designed to route these cross-functional decisions. This is the gap that a Manufacturing OS addresses — the cross-functional coordination and exception routing layer that sits between ERP and MES, connecting both systems to the real-time decision workflows that shop-floor execution requires.