Every manufacturing software evaluation eventually arrives at the same question: if I have SAP, do I need an MES? If I have an MES, do I still need ERP? The answer to both is yes. But understanding why requires understanding what each system was actually designed to do. --- What ERP Was Built For ERP systems were designed in the early 1990s to solve a specific problem: how do you manage the financial and procurement complexity of a large manufacturing organisation across multiple sites, currencies, and legal entities? The answer was a unified system of record. One place where every purchase order, invoice, work order, and inventory transaction is recorded accurately. One source of financial truth for reporting, compliance, and auditing. This is what ERP does well. SAP, Oracle, and Microsoft Dynamics 365 are exceptional systems of record. They handle financial transactions with full audit trails, procurement and supplier management, GST/VAT compliance and e-invoicing, MRP planning cycles, and multi-entity consolidation. ERP's architecture is optimised for accuracy over transactions that have already occurred. It runs in batch cycles. It is designed to be auditable, not fast. --- What MES Was Built For Manufacturing Execution Systems emerged in the late 1980s and early 1990s to solve a different problem: how do you ensure a production plan actually gets executed — and how do you surface deviations from that plan fast enough to do something about them? The answer was a system of coordination. A layer between the ERP's plan and the shop floor's reality that captures events in real time, routes exceptions to the right people, and keeps the planning system updated with current operational truth. MES does things ERP cannot: MES Capability Why ERP Cannot Do This Capture floor events within minutes of occurrence ERP's posting model requires manual data entry — events backfill at end of shift Route exceptions across functions within minutes ERP has no native workflow for real-time exception routing across quality, production, and materials Validate WhatsApp orders and push to ERP automatically ERP expects structured data inputs — unstructured WhatsApp messages require an intake layer Propagate quality holds to inventory status immediately Quality and inventory modules in ERP sync on a cycle — holds take hours to appear in MRP Keep schedule data current throughout the shift ERP's scheduling runs on a cycle against batch data — real-time schedule updates require an execution layer --- Why the 'ERP vs MES' Frame Is Wrong Manufacturers often frame the decision as ERP vs MES — as if choosing one eliminates the need for the other. This framing is wrong, and it consistently produces bad decisions. ERP and MES are not substitutes. They are complementary systems with different jobs: Dimension ERP MES / Execution Layer Primary job System of record System of coordination Time horizon Batch (daily, weekly cycles) Real-time (minutes from event to update) Data model Transactional, accurate, auditable Operational, current, actionable Primary users Finance, IT, procurement, planning Planners, supervisors, quality, dispatch, commercial Optimised for Accuracy over settled transactions Speed over current operational state Replaces the other? No — needs execution layer above it No — needs ERP for master data and transactions A manufacturer who has ERP but no execution layer has a planning system that runs on stale data, a coordination layer managed through informal channels, and an operations team spending their mornings reconciling what ERP thinks happened with what actually happened. --- What Happens When Manufacturers Rely on ERP Alone The execution failures that result from relying on ERP as a sole operational system are consistent across industries, ERP versions, and company sizes. The morning reconciliation meeting. When ERP data is hours behind floor reality, operations teams start every day with a reconciliation meeting to establish what actually happened yesterday and what the real state of production is today. This meeting typically takes 30–60 minutes. It exists entirely because the execution layer is missing. The WhatsApp coordination layer. When ERP has no real-time exception routing, the informal coordination layer fills the gap. Quality holds communicated via phone. Priority changes via WhatsApp group. Machine breakdowns managed through supervisor calls. None of this reaches ERP — creating a permanent divergence between the plan and operational reality. Schedule adherence below 75%. When production planning runs on incomplete demand data, stale inventory positions, and no visibility of quality holds — the schedule is wrong before the first machine starts. Experienced planners know this and adjust informally. Those adjustments don't reach ERP. The next planning cycle ignores them. Schedule adherence stays below 75% regardless of how many times MRP parameters are tuned. --- The Modern Answer: Execution Layer Above ERP For mid-market manufacturers (₹200–2,000 crore), the answer is not to replace ERP. It is to deploy an execution layer above the existing ERP that fills the coordination gaps ERP was never designed to fill. This execution layer reads from ERP master data (customer, item, pricing, BOM), handles the coordination events ERP cannot (WhatsApp order intake, exception routing, real-time floor data), and writes confirmed outcomes back to ERP as standard transactions. The ERP continues running compliance, financials, and procurement exactly as before. The execution layer adds the real-time coordination capability above it. For most mid-market manufacturers, this combination produces the same operational outcomes as a traditional enterprise MES — but deploys in 6–10 weeks rather than 18 months, at a fraction of the cost, without touching ERP configuration. The debate about MES vs ERP is the wrong debate. The right system for mid-market manufacturers is an ERP execution layer above existing SAP or Oracle ERP. The right question is: what is your ERP not doing, and what is the fastest path to closing that gap?