What ERP Is and What It Is Not

An order arrives, a work order opens, and then what happens? In our Reverse Look at Work Orders post, we saw how work orders grow through confirmations, change on the floor, and eventually transform. We talked about the disconnect between planning and execution.

Today we are standing right at that disconnect: ERP.

What ERP Is

ERP — Enterprise Resource Planning — is a structure built to unite all of an organization’s resources in a single system. Finance, sales, purchasing, stock accounting, human resources… All rely on the same data pool.

It is excellent at this job. When an order is entered, stock decreases, it is posted to the ledger, collections are scheduled. A purchase proposal is created, a supplier is selected, a payment calendar is drawn. A journal entry is recorded in finance.

ERP exists to do this, and it does.

What ERP Is Not

ERP is not a tool for real-time data collection on the shop floor.

Saying this is easy, but for anyone working in a factory, this distinction is vital. ERP does not know — in seconds — how a work order is progressing on the floor, how long an operator has been idle, how many defects are in a part, or which machine went down and when.

Why? Because ERP was not designed for that. For ERP, data is a documented transaction. When a work order closes, all its costs are gathered, inventories are updated, and invoices are issued. This process happens after the work is done.

What happens on the floor has not yet reached ERP.

“Your ERP Is Not Lying, It Is Just Speaking Late and in Coarse Grains”

This frame lands right in the middle of the problem. ERP does not give wrong information. The information it provides is not a current photograph of reality.

Here is an example: An order for 100 parts. In ERP, that order appears as “completed.” Meanwhile, on the floor there were 10 defects and 5 second-quality parts. ERP does not know that. Because the work order has not yet been posted, defect records have not been entered, and the quality control form has not been keyed in.

Your ERP is not lying. It is just describing yesterday evening’s state.

It also speaks in “coarse grains.” ERP usually presents daily or weekly totals. Which shift had what issue, how much time was lost in which operation — these do not exist in ERP’s language.

What Do You Need for Real-Time Shop Floor Data?

This is where MES — Manufacturing Execution System — comes in. MES captures operation-level actual duration, downtime, and defect data from the moment a work order opens until it closes, in real time on the floor.

We will cover this in detail in What Is MES?. For now, this is enough to know: ERP and MES share the same data but speak at different time horizons and different levels of detail.

The Extra Layer Required for Integration with Local ERPs

Integrating with local ERPs like Netsis, Odoo, Logo, or Parasut is not as easy as with global brands’ APIs. These systems’ data structures, accounting logic, and reporting formats are shaped by local trade rules.

Embedding production data into these ERPs usually requires a dedicated integration layer. The data schema must be adapted, timing must be synchronized, and error handling must be established. infab.cloud’s ERP integration layer targets exactly this gap: it transfers the data collected by MES/MOM to the local ERP in a format it understands, through a natural flow.

Conclusion

This is not about saying ERP is wrong or insufficient. It is the heart of the company’s accounting and management world. But it is insufficient for understanding the production floor.

Acknowledging this insufficiency is the first step. Knowing what ERP can and cannot do is what is needed to place the right systems in the right places on the factory floor.

Real-time shop floor data, operational decisions, and actual costs — these are not in ERP’s vocabulary. That is why you should not mistake the interface. It simply speaks late.

In a future post, How the Layers Connect, we will discuss how we architect the data flow between ERP, MOM, and MES.