Order Received, Work Order Issued — Then What?

A customer places an order. The sales team enters it into the ERP: product code, quantity, delivery date. Planning reviews it and creates a work order. The process engineer and production manager exchange messages on WhatsApp, along with Excel files (but which version is current?). The first operator sits down at the machine, maybe picks up a scribbled note, maybe just gets verbal instructions. Production begins. But where did the information go in between? Who has it? In what form?

In make-to-order (MTO) manufacturing environments we observe, this information chaos that occurs between order receipt and shop floor readiness is one of the root causes of production uncertainty.

Information in Fragments

An order, when it first appears as a single ERP record, fragments as soon as it moves toward execution:

In the ERP: Product code, size/color variants, unit, delivery date, customer details. A work order number is generated, but which machine will it be assigned to on the shop floor? Which operator? Unknown. The ERP’s logic flow shows the standard recipe (BOM) and routing for the product, but when the order is make-to-order: “Is this exact recipe mandatory for this job?” “Is this sequence rigid, or is there operational flexibility?” These questions remain unanswered.

In Excel spreadsheets: The planning manager maintains a table of this week’s work orders, estimated start dates, days remaining to meet demand. But this is manual, prone to staleness. The production supervisor may keep a separate table; planning never sees it. Who tracks the status of a work order as it progresses from open to in-progress to paused to closed? Often, rough headcount; no formal system, just “ask the guy running that job.”

In the shop supervisor’s memory: The actual floor operation plan lives in the head of the factory supervisor. Which machines are free, which are running, seasonal adjustments (e.g., fast-track weekends, standard-pace workdays), how many shifts will this order take, which operator excels at this type of work, interpersonal dynamics — all this is unwritten tribal knowledge. If the supervisor retires or transfers, 15 years of embedded planning walks out the door. The work order remains a work order; its integration into the floor plan is never documented.

In WhatsApp and voice messages: A critical change arrives — the customer changed colors, wants expedited delivery. The sales manager texts the planner. The planner tells the production manager. The production manager maybe informs the shop supervisor directly or via a colleague. Information transforms into hearsay; no written change record exists. When is this reflected in the work order? If at all. Does the operator know? Only if they happen to be there when word spreads.

On scribbled notes and verbal instruction: A work order is about to start. An operator arrives at the machine. On the table lies a hastily written note: “Product XXX, qty 50, color blue, leak-test max 0.5%.” Who wrote this note? How old is it? If the product has been updated, was the note? The supervisor gives voice instructions: “This blue batch needs a light touch this time” — why? Did the customer request it, or is this based on past experience? Neither the instruction nor its reasoning is recorded.

Information Lost Before Operations Begin

This fragmentation creates gaps before execution even starts:

1. Recipe and routing ambiguity: Is the recipe in the work order the exact specification for this particular job, or a generic template? Is it outdated? Were there customer-specific requests? When the operator notices a discrepancy between the work order and what the supervisor said, which do they follow?

2. Resource (machine/operator) assignment is not documented: Which machine was this work order meant to run on? Which shift? Once production begins, someone says, “We need that machine for something else — where did this order go?” Replanning happens, the job is reassigned to a different machine. But the transition from Plan A to Plan B is never recorded; the shop floor follows whichever plan is still taped to the wall.

3. Change management falls through the cracks: Customer changes color, operation duration varies from our standard playbook, an alternative resource must be used. These changes — their nature, reason, approval, impact — are not logged. Later, when we want to analyze why this job cost more or took longer than expected, we have no paper trail.

4. Management layers become disconnected: The sales engineer quoted a price based on material option A (cheaper). The operator uses material option B (higher quality, slightly costlier), because the supervisor recommended it. Financial records get muddled; true job cost cannot be traced. Profit and loss calculations become fiction.

Why This Matters

In make-to-order production, every order is different and condition-dependent. When information is scattered, the operation flow is chaotic. Resources—machines and labor—are not allocated efficiently. Promised delivery dates slip. Quality standards are applied inconsistently. Cost traceability vanishes. When a complaint arrives (e.g., quality issue) and you ask “Why did you do it that way?”, the answer is often “That’s what I was told,” and you cannot dig deeper.

Manufacturing software is built specifically to prevent this information fragmentation. But software is not merely a filing system; it provides infrastructure. The real challenge is breaking deeply rooted habits built on decentralized, informal communication.

The Path Forward

A factory must ensure that all information about a work order—from order entry to shop floor execution—reaches the operator from a single, authoritative source. To achieve this, a layer beyond ERP is required: a real-time shop floor operations management system (MES / MOM). This layer captures every change, every alternative resource, every deviation, along with its reason and outcome.

Next time, we explore what these layers are and what they actually do.