← Back to Field Notes

April 25, 2025 · The Bloomfield Team

The Difference Between MES, ERP, and Custom Software

A 55-person CNC shop in Tennessee spent $220,000 on an MES platform after three years of running their operation on an ERP system supplemented by spreadsheets and whiteboards. Fourteen months after implementation, the shop foreman still used the whiteboard for scheduling, the MES duplicated 60% of the data already in the ERP, and the operators viewed the shop floor terminals as an administrative burden that slowed them down. The shop had purchased a system designed for a problem they did not have while ignoring the specific gaps that actually caused operational friction.

This happens because ERP, MES, and custom software sound like they do different things, and technically they do, but the boundaries blur at the exact points where manufacturers need clarity.

What Each System Actually Does

ERP (Enterprise Resource Planning) is a transaction system. It manages purchase orders, sales orders, invoices, inventory counts, job costing, and financial reporting. JobBOSS, Epicor, Global Shop Solutions, and E2 are the ERPs most common in small to mid-size manufacturing. The ERP answers questions about what happened: What did we spend on material? What did we charge the customer? How many hours were logged to this job? How much inventory do we have? The ERP is the financial and administrative backbone of the operation.

MES (Manufacturing Execution System) is a production tracking system. It sits between the ERP and the shop floor and manages what is happening right now: which jobs are running on which machines, how far each operation has progressed, what the actual cycle times are versus the planned times, and where production is falling behind schedule. Plex, ProShop, and IQMS are MES platforms commonly used in manufacturing. The MES answers questions about the current state of production in a way that the ERP, which only records transactions after they are complete, cannot.

Custom software fills the gaps that neither ERP nor MES was designed to address. It connects data from multiple systems, applies logic specific to one operation's workflow, and delivers information in the exact format that the people making decisions need to see it. A custom quoting tool that pulls historical job costs from the ERP, material pricing from a supplier database, and machine availability from the MES to generate a quote in 20 minutes instead of two days. A knowledge capture system that stores operator notes linked to specific parts, machines, and materials and surfaces them at the moment of need. A dashboard that answers the three questions the production supervisor actually asks every morning, pulled from both ERP and MES data, displayed on a single screen.

Where the Overlap Creates Confusion

Modern ERP systems have added scheduling, shop floor data collection, and production tracking features that overlap with MES functionality. Modern MES platforms have added quoting, inventory management, and financial reporting features that overlap with ERP. The result is that a manufacturer evaluating systems sees two platforms that both claim to handle scheduling, both claim to provide production visibility, and both require the same shop floor data entry.

The practical difference is in the depth and real-time capability of each function. An ERP's scheduling module typically works from planned capacity and standard cycle times. An MES scheduling module works from actual machine status and real-time production data. For a shop running 50 jobs across 15 machines with daily priority changes from customers, that distinction matters. For a shop running 10 jobs across 5 machines with stable schedules, the ERP's scheduling may be sufficient.

For a deeper look at how these systems connect, see our guide to ERP and AI integration.

How to Decide What You Need

Start with the decisions that are hardest to make in your current operation. If the hardest decisions involve financial accuracy, job costing, quoting, inventory valuation, and accounts receivable, the ERP needs attention first. If the hardest decisions involve real-time production tracking, schedule adherence, and machine utilization, an MES fills the gap. If the hardest decisions involve connecting information across systems, applying shop-specific logic, or delivering context to people who do not use the ERP or MES directly, custom software is the answer.

Many shops need all three, layered in sequence. The ERP comes first because it is the transactional foundation. The MES adds real-time visibility that the ERP cannot provide. Custom software connects the layers and fills the workflow-specific gaps that no off-the-shelf product was designed to address.

The mistake the Tennessee shop made was buying an MES to solve a problem that was actually a data quality issue in their ERP combined with a specific workflow gap in quoting that neither system was designed to handle. The $220,000 MES duplicated functions the ERP already performed while leaving the actual pain points untouched.

The Custom Software Question

Custom software makes sense when the gap between what your team needs and what your existing systems provide is specific enough to define and valuable enough to justify the build. The build-versus-buy decision depends on whether an off-the-shelf product addresses your specific workflow or whether your workflow is unique enough that generic tools will always require workarounds.

For most small manufacturers, the answer involves some combination of all three. Keep the ERP as the financial backbone. Add MES capabilities selectively based on specific visibility gaps. Build custom tools for the two or three workflow bottlenecks that neither system addresses because they are specific to how your operation works.

The goal is not to have the most systems. The goal is to have the right information reaching the right person at the right moment so they can make a better decision. Sometimes that requires a $500,000 MES. Sometimes it requires a $40,000 custom tool. The answer depends on the specific problem, not on the software category.