Key takeaways
- An ERP plans the business in orders and days; an MES executes production in operations and minutes.
- The gap between them is where plant data goes missing — into paper, spreadsheets and institutional memory.
- ERP production modules assume the BOM was followed. An MES records what really happened.
- You need both once material variance, traceability or downtime become questions you cannot answer.
The short answer: an ERP plans and accounts for the business, while an MES executes and records production on the floor. ERP works in orders and days; MES works in operations and minutes. Most manufacturers past a certain size end up needing both, because neither system does the other’s job well — and the gap between them is where plant data quietly goes missing.
That is the summary. The useful part is understanding why the boundary sits where it does.
What an ERP is for
Enterprise resource planning software integrates the commercial side of a manufacturing business into one record: purchasing, inventory, sales orders, costing, finance, planning, sometimes HR.
Its natural unit is the order and its natural cadence is the day. It answers questions like:
- What did we agree to deliver, and when?
- What do we need to buy to make it?
- What is this order costing us?
- What is on hand, on order, and committed?
ERPs are very good at this. Where they struggle is the moment you ask something that requires knowing what physically happened during a shift.
What an MES is for
A manufacturing execution system manages production as it runs. Its natural unit is the operation and its natural cadence is the minute. It answers a different class of question:
- Which operation is this order on right now, on which machine?
- What material was actually consumed, from which lot?
- Why did the line stop, and for how long?
- Did this batch pass its checks — and if not, what else is affected?
Note that none of those are financial questions, and none of them can be answered from a planned quantity. They require capturing reality as it occurs.
The gap between them
Here is the practical problem. Your ERP integrates the supply chain beautifully, and your machines, SCADA and HMI systems know a great deal about the physical process. But everyday plant operations sit in between, and in most factories that space is filled by paper, spreadsheets, a handful of local databases, measuring systems that export to nothing, and the operator who has been there nineteen years.
In practice
The data usually exists. It is just scattered, entered twice, contradictory across sources, and available too late to act on. That is the gap an MES is built to close — not to replace the ERP, but to give it something true to consume.
A worked example
Say a customer order for 5,000 units lands.
The ERP checks stock, explodes the bill of materials, raises purchase orders for what is short, schedules the production order against capacity and books the commercial commitment.
The MES takes that production order and drives it: releases it to the right line, sequences the operations, tells the operator what to do, records which raw material lots were actually issued, reads cycle counts and downtime from the machines, prompts the quality checks at the right frequency, and captures scrap and rework as they occur.
Then it reports back. The ERP learns that the order is complete — but also that it consumed 4% more of one component than the BOM assumed, that 90 minutes were lost to a changeover, and that 60 units were scrapped at final inspection.
Without that return path, your ERP’s cost figure is a plan wearing the costume of an actual.
You will only discover the difference at stock-take, months later, with no way to attribute it to a shift, a machine or a material lot.
“Doesn’t our ERP have a production module?”
Usually, yes — and for some businesses it is enough. ERP production modules handle order release, basic routing and backflushing of materials against a BOM.
The limits show up in three places. Granularity: backflushing assumes the BOM was followed; it cannot tell you what really happened. Latency: ERP modules are typically updated by people, after the fact, which means the floor is always reporting the past. Machine data: most ERP production modules have no meaningful path to reading equipment directly, so downtime, cycle time and process parameters stay invisible.
Watch out for
“Our ERP already does production” is true right up until it isn’t. If your products are simple, your runs are long and your material variance is small, an ERP module may genuinely be sufficient. If any one of those three changes — more variants, shorter runs, tighter margins — the gaps appear quickly and all at once.
Do you need both?
A reasonable test. You probably need an MES alongside your ERP if:
- You cannot explain material variance without an investigation.
- You need lot-level traceability, whether for regulation or for customers.
- Downtime is a known problem that nobody can quantify by cause.
- Quality results live somewhere other than production records.
- Your plant reporting is rebuilt by hand every month.
You probably do not, yet, if you run a small number of long, stable jobs, material consumption is predictable, and nobody is asking you to prove where anything came from. Being honest about which side you are on saves a great deal of money.
How the two systems talk
The integration is less exotic than it sounds. The ERP passes down production orders, BOMs, routings and item master data. The MES passes back completions, actual material consumption, scrap, downtime, labour and quality results.
The thing worth getting right is direction of truth. Planned quantities come down from the ERP; actuals come up from the MES. When both systems believe they own the same field, you get two numbers and an argument. Integration design is mostly the discipline of deciding, per field, which system is authoritative.
Where Capitán fits
Capitán MES is built for exactly this layer: managing the manufacturing flow through work orders, BOMs and processes, reading data directly from your machines to surface progress and anomalies, and carrying end-to-end in-process traceability including in-process inventory, waste management and quality control. It sits alongside your ERP rather than competing with it — and because it runs on a no-code platform, the process model bends to your plant instead of the other way round.
If you are trying to work out which side of the line your operation is on, talk to our team. It is usually clear within one conversation.