What ERP Is and What It Isn't

ERP has been the data backbone of manufacturing companies for many years. The question “No ERP?” is now about as common as “No internet?” Few places today operate without one.

But as years pass, a curious paradox emerges: in a factory with ERP installed, what actually gets done, and what doesn’t?

What’s Inside ERP

When you examine ERP packages (Netsis, Odoo, Logo, Paraşüt, SAP, Oracle, etc.), they all share a similar spine:

Financial accounting: Receivables, payments, calculations, taxes, period closure.

Sales: Customer order entry, invoicing, shipment tracking, returns.

Procurement: Supplier selection, quotes, purchase orders, receipt control, payment.

Inventory/Warehouse: Goods receipt, dispatch, location assignment, transfers, stock counts.

Accounting transactions: Journal entries, end-of-day reconciliation, financial reports, period finalization.

In these domains, ERP has become nearly universal. Needs are understood, solutions mature, integration patterns established.

What’s Outside ERP

But let’s create a scenario close to the shop floor.

Monday morning, plant manager Hakan receives a new order. Customer-specific. From Heavy Fabrication Ltd: custom-welded metal frames. Not standard. Every time a different size and material combination.

Hakan enters it into ERP and records the order. “Start production,” he says.

But the problem begins here.

What’s the Recipe?

Standard products have a recorded recipe in ERP: cut steel, weld, paint, test. Every step has machine, time, and scrap rate.

But for this order?

Customer: “This time use aluminum instead of steel, size 2300x1400, and do TIG welding.” This combination has never been made. Where’s the recipe? Does it come from machine documentation or from the manager’s head?

Adding a new recipe to ERP takes 2-3 days. But this order must ship in one week.

Production planner Çetin calls manager Hakan at 10:00 that day: “Want to write out the recipe and try one as a pilot?”

Hakan: “Sure, I’ll write it down.”

On paper. Not in ERP.

The Work Order Container

They try to put the hand-written recipes into the ERP work order. But the form is designed for standard products, so special conditions get pasted in:

• In the Notes field: “Special material combo, manager to review”
• In a WhatsApp group: “Hey, this time do double welds at that step”
• On a hand-written note taped to Foreman Yusuf’s clipboard

Result: The work order is one piece of information, but not all of it. The real instructions flow through parallel channels.

Actual Time, Delays, Scrap

In standard production, we expect ERP to record every update. Work order started, finished, product found defective, rework begun.

But in custom orders?

• 10:30 AM: Machine breaks down (1 hour). Work stops.
• 11:45 AM: Technician arrives, restarts the machine.
• 2:00 PM: Product comes out but first test fails. 12 pieces bad.
• 2:30 PM: Rework of pilot starts.
• 4:00 PM: Rework done, testing begins.

During this sequence:

• Machine value-adding time: 2.5 hours
• Waiting and setup: 1.5 hours
• Defects and rework: 2 hours
• Downtime/breakdown: 1 hour

Can ERP see this?

No. ERP records start and finish times, marks the work order “Complete.” The rest lives in Foreman Yusuf’s mind with “We’ll settle up later.”

The Cost Question

The customer got a price quote: 2,500 TL.

Breakdown:

• Material: 800 TL (standard rate)
• Labor: 1,200 TL (12 hours × 100 TL/hour)
• Overhead: 400 TL
• Profit: 100 TL

During production, 12 pieces failed and were reworked, the machine broke down (service call + 1 hour lost), the foreman worked overtime.

What was the actual cost?

• Material (including scrap and rework): 1,200 TL
• Labor (actual + rework): 1,800 TL
• Technician service: 400 TL
• Overhead: 400 TL

Total: 3,800 TL. Not profit, but a 1,300 TL loss.

ERP doesn’t see this gap. What got entered was “12 hours labor” and “1,200 TL,” and the real cause of this cost overrun is never recorded. The next custom order will get the same quote, and it will lose money again.

ERP’s Natural Limitation

There’s a fundamental design constraint: ERP works like a librarian. It expects every resource to be pre-cataloged and systematically recorded:

• Recipe (BOM): Assumes it’s defined beforehand
• Work order: Closed scope, start and end dates known
• Machines, workers: In a pool with fixed, unchanging information

In custom manufacturing there is dynamism. The recipe crystallizes after work starts, the operation sequence changes based on floor conditions, resource allocation is fluid.

In this environment, ERP:

1. Receives information late (via paper, WhatsApp, worker memory)
2. Tries to impose standardization (but can’t enforce it)
3. Misses actual costs and loss drivers
4. Can’t generate actionable data for decisions

Conclusion

ERP gets deployed, purchased, implemented. But for production planning and cost control, it falls short.

Excellent for finance: Customer invoiced, payment received, books closed, everything crystal clear.

Incomplete for operations: Work orders lack detail, floor state isn’t tracked, rework and defect rates vanish, dynamic decisions aren’t supported.

MES (Manufacturing Execution System) is where real-time, non-standard, floor-truth data gets captured and used. MES is designed to be the bridge between ERP and the foreman’s mind.

In the next post, we’ll see what MES actually does.