What is ERP? What It Is Not (The Gap in Make-to-Order Manufacturing)

Yesterday we discussed how order arrival, work order creation, and fragmented information storage create problems. Today let’s examine the root: what does ERP contain, and what does it lack?

ERP: Strong Backbone, Weak Shop Floor

Look at any deployed ERP system (NetSuite, Odoo, SAP, Logo, Paraşüt), and you’ll find a common DNA:

Financial accounting: Revenue-expense, receivables-payables, tax, period closing.
Sales: Customer, order, invoice, shipment.
Procurement: Vendor, quotation, purchase order, receipt.
Inventory: Material receipt, issue, stock locations, count.
Reports: Profitability, cash flow, analysis.

In these domains, ERP has become nearly universal standard. Problems are solved, integration patterns are mature, calculations are correct.

But in operational execution—that real, dynamic, variable world—what can’t ERP do alone?

The ERP Gap in Make-to-Order Manufacturing

Think of a factory that builds to order. Every job is different:

Scenario: Where Is the Recipe Code?

Customer calls: “Aluminium frame, 1200×800, lead solder (not TIG), matt black powder coat.”

Operations planner opens the ERP: searching for a recipe code. None found. This specification hasn’t been manufactured before.

Option 1: Create new recipe in ERP. Time required: 2-3 days (accounting, planning, technician approval). But the order must ship in 5 days.

Option 2: Copy the closest recipe, paste into the notes field: “Special instructions: Use lead solder.” Time: 30 minutes. But that’s incomplete—the real instructions live in master technician Mehmet’s head.

Result: ERP has a recipe code, but the actual manufacturing recipe is elsewhere.

Operation Sequence: Who Decides?

In standard production, the sequence is fixed: cut → weld → paint → test. All documented in the recipe.

In make-to-order?

Customer: “But before paint, add a drum polish step for better surface quality.”
Technician: “Okay, so weld → drum polish → paint → test.”

Does this change get recorded in the ERP recipe, and if so, when? Does the technician read the recipe, or does he follow the work order notes?

Result: The actual operation sequence is a live agreement between decision-makers (plant manager, technician). The sequence written in ERP may not reflect reality.

Actual Time Data: Machine Downtime, Wait, Rework

Work order started at 08:00. Target finish: 17:00.

But in reality:

How much of this does ERP track? Start time, end time, status: complete. The rest is lost.

Actual Cost vs. Standard Cost

Customer quoted price: 1,500 TL

Breakdown:

ERP’s standard material price: 400 TL. Standard operation time: 7 hours.

But actual process:

Technician callout: 200 TL (maintenance).
Material (higher-quality than standard): +150 TL.

Actual cost:

But the quoted price was 1,500 TL. Loss: 350 TL.

Does ERP learn this? Only when the accountant closes the month and sees a bottom-line loss. The discovery is too late, and how the loss occurred remains unclear.

The World ERP Prefers

ERP works well when:

But in make-to-order manufacturing:

In this environment, ERP is paper. Real instructions, real data, real execution remain outside the system.

Conclusion: ERP Is Necessary, but Not Sufficient

Financial accounting, the money side of orders, overhead allocation—all in ERP. But “how do we make this order, how long will it take, what will it actually cost”—ERP can’t answer these questions alone.

That requires real-time data capture at the shop floor, dynamic recipe management, operation orchestration. In industry terminology: MES, MOM.

Tomorrow, Day 3, we’ll discover what MES is.