What is ERP, and What Isn't?

What is ERP, and what isn’t?

In a demand-driven manufacturing environment, this question sits at a crossroads where the simplest problem has the most complex answer. ERP (Enterprise Resource Planning) is designed for accounting, sales, procurement, and inventory management. Billions of dollars have been invested. Software like Netsis, Odoo, Logo, and Paraşüt serve this purpose well. So why, when an order arrives and a work order is issued, is information still scattered across the shop floor?

What ERP Does Well

ERP excels at these:

Accounting: Invoices, receivables, payables, expenses, revenue. Every transaction is recorded. Every account must balance to the penny.

Sales: Customers, orders, quotes, payment terms. Who did we sell to, how much is owed, how much are we owed.

Procurement: Suppliers, requisitions, orders, receipts, and invoice matching. Who owes us, what arrived, why didn’t it arrive.

Inventory Accounting: Receipts, issues, transfers, daily closing. How many units in the warehouse, what is the intended cost.

Within these four walls, ERP is strong. Managing the flow of products worth billions of dollars is ERP’s core job, and it does this very well.

What ERP Cannot Do

But what happens on a busy Monday morning?

09:00 — A sales representative is on a call with a customer. “Can we do this part differently?” The answer is yes. This decision never enters the ERP. There is no written record. It lives in the sales rep’s memory, the customer’s memory, and the production manager’s incomplete notes.

10:15 — Production planning begins. The manager sees the original work order. He was not aware of the morning’s phone call. Not by negligence—the system does not provide this information.

11:00 — A machine breaks down. An alternative is found. The decision happens between the shop supervisor and the production manager in a quick phone call. The work order is not updated. The system still shows the broken machine. Reports are wrong.

14:00 — The part is manufactured. But which work order it belongs to, how many labor hours were actually spent, why a different machine was used instead of the standard route, where the components sit now and what this means for cost—these answers were never entered into the system. They exist in handwritten notes, to be manually entered after lunch (perhaps).

Why Does This Problem Persist Even After ERP is Deployed?

ERP was designed to give finance an accurate picture. An accountant pulls a receivables report from the ERP, sees every product invoiced to a customer, and matches it against bank deposits. This works.

But ERP does not drive real-time operational decisions on the production floor. Why?

First reason: Flexibility. In demand-driven manufacturing, recipes are not fixed. When a customer requests a change, the design updates quickly. In the ERP, a product definition is stored, but these definitions are static, installed, heavy, and slow to change. Pushing quick, verbal changes into the ERP can take a week.

Second reason: Control points. In shop-floor operations, machine selection, operation sequence, labor allocation, and quality checkpoints change hourly, sometimes by the minute. The ERP records these when the work order is issued, but it does not capture intraday changes. Its design cycle is oriented toward financial closing periods, not floor operations.

Third reason: Structural boundary. By its nature, ERP tries to fit all industries, all product types, all business models. Because of this, very specific shop-floor decisions—the actual hours a machine spends on this job this hour, and scrap data—have no central place in the system’s architecture.

So What Should Be Done?

Do not turn off the ERP; keep using it for finance and inventory. But for shop-floor operations, to capture real-time decisions, to track every change from work order open to close, and to calculate true cost, a separate layer is needed.

This layer is called MES (Manufacturing Execution System).

We will explore MES in detail tomorrow.