Approve Manufacturing-Order Changes: Keep Production Traceable

A manufacturing order says to build 500 units of part A by Friday, drawing components from lot 12. By Wednesday the line has built 700, the planned component was swapped for a substitute, and the due date moved to next Tuesday. Nobody approved any of it. The change happened at the machine, on a spreadsheet taped to the press, or in a side system nobody in production control can see. The order the ERP released no longer matches what the floor actually built, and the gap between plan and reality is exactly where production traceability collapses.

Manufacturing orders are the spine of any make-to-stock or make-to-order business, carrying the link between what sales promised, what engineering designed, and what the floor executed. As the core business system's document of record for production, the order is what every downstream control keys off. When it can be changed without a record, every downstream control loses its reference point: cost rolls pick up quantities that do not match the floor, inventory shows components issued that were never consumed, and lot traceability, the thing a recall or an OEM audit will demand within hours, breaks the moment a substitution or quantity change is not captured.

The fix is a manufacturing-order change approval step: a request, routed for sign-off, with a traceable, auditable record of what changed and why. The approval workflow and the audit trail are built and live today. Automatically updating the manufacturing order when a change is approved, the writeback step, is on the roadmap, not built. We will be precise about where that line sits, because this is a field where vendors routinely overpromise.

Why Uncontrolled Order Changes Destroy Traceability

Production traceability means being able to answer four questions about any unit that left your floor: what was built, from what, by whom, and to what specification. The manufacturing order is the document of record for those answers. It is the contract between the plan and the execution, and it is what an OEM customer, a regulator, or your quality team will ask to see when something goes wrong in the field.

The shop floor changes orders constantly, and most of the changes are legitimate: a tool wears out and a substitute clears the line, a customer asks to move 200 units to next week, a machine goes down and the order needs splitting across two cells. None is a problem on its own. The problem is that without an approval and a record, the change is invisible to the systems that depend on the order.

This invisibility has three costs. The first is traceability: when a field failure comes back on lot 12, the records show the order changed three times, none of it captured, and you cannot say which substitute went into which units. The second is cost accuracy: when the floor builds 700 against a 500-unit order and the change is never reflected, the standard cost roll and variance reporting are both wrong for the period. The third is schedule truth: when due dates move informally, the schedule the ERP sends to planning and the one the floor works from diverge, and nobody knows which is real.

The governance gap haunts every shop floor: the people closest to the work have the most accurate information and the least incentive to stop and record it, and the core business system that should hold the truth gets bypassed because the formal process is slower than the press cycle. The labor shortage sharpens this. According to Japan's 2025 edition of the Information and Communications White Paper (Reiwa 7), 48.7 percent of companies cite the labor shortage as the top barrier to digitalization. Leaner crews have less slack to record changes by hand, so the gap widens precisely where traceability matters most. The result is an ERP whose records look authoritative on a screen and tell you almost nothing about what actually happened.

What a Manufacturing-Order Change Approval Actually Governs

Not every touch on a manufacturing order needs approval. Releasing the order, printing the router, recording standard completions are normal execution. The changes that need governance are the ones that alter what the order commits the business to.

Quantity changes. Building more or fewer units than specified, or splitting one order into multiple lots. These flow into cost, inventory, and capacity reporting, and a quiet overbuild can sit in stock consuming working capital.

Component and bill-of-materials substitutions. Swapping a planned component for a substitute, often to clear a shortage. These are the most traceability-critical changes of all, because a substitute that fails in the field must be traceable to the exact units it went into. A silent substitution makes lot traceability a lie.

Schedule and due-date changes. Moving the completion date, reprioritizing, or pulling an order forward for a rush customer. These change the production schedule the rest of the business works from.

Routing and work-center changes. Moving work to a different cell or machine, often because of a breakdown. These affect standard cost, capacity, and the quality records tied to a specific process.

In every case the pattern repeats: one person makes the change, it propagates into cost, inventory, schedule, and quality, and there is no approver, reason, or record. The approval closes that loop by passing the change through the same discipline the business already uses for purchase orders and capital expenditure.

The Two Pieces: Approval Step, Auditable Record

A working change control has two pieces, and each earns its keep for a different reason.

The approval step. A proposed change enters as a request rather than a direct edit, carrying what is changing, the before and after values, and the reason. Routing follows the same rules as any other approval workflow: by role, by department, by the size or risk of the change. A routine quantity adjustment might route to the shift supervisor. A component substitution on a regulated OEM product might require parallel sign-off from production engineering and quality, because the cost of an untraceable substitute is so high. A due-date change that affects a customer commitment might add the production control manager and a sales watcher. The approval step is built and live today.

The auditable record. When a change is approved, the system freezes a traceable record of what was reviewed and decided: the change, the approver, the timestamp, the reason, and the attached evidence. This is the record that satisfies internal control and J-SOX evidence requirements, and the record that saves a recall. Weeks later, when a field failure points at a specific lot, you can pull the change history for the order that produced it and see in one place that a substitute was approved on a specific date by a named approver, with the engineering note attached. The auditable record is built and live today, and it is the difference between a traceable system and one whose records cannot be trusted.

Together these move the manufacturing order from a planning document the floor edits around to a governed record that still reflects reality but captures every deviation with proof.

A Scenario: The Precision Parts Maker in Shizuoka

Consider a precision parts manufacturer in Shizuoka, about 280 staff, supplying automotive and industrial-machinery OEMs from a head office in Tokyo and a factory on the coast. Their orders run in mixed lots against tight OEM schedules, and a single line might build parts for two customers against two orders in a shift. Traceability is not optional. An OEM audit or a field-return investigation can demand lot-level component traceability within hours.

Before they governed order changes, the pattern repeated every week. A shortage on a planned component would send a buyer to the floor with a substitute, and the line would switch over without telling production control, the substitute consumed while the original component sat in the order as issued. A machine breakdown would push work to a backup cell, the routing change living only in a notebook. A customer would call to pull an order forward, and the due date would move on a whiteboard the ERP never saw.

The symptoms showed up downstream. An OEM field return on a specific lot came back as a substitute-component failure, and the investigation took days because the order showed only the planned component. Month-end cost variance swung because the floor had built to quantities and routings the standard cost roll never reflected. The schedule planning published each Monday and the schedule the floor actually worked bore little resemblance, and expediters spent their week reconciling the two by hand.

Moving order changes into an approval step changed the operating model. A component substitution now enters as a request naming the order, the planned component, the substitute, and the reason, routing to production engineering and quality in parallel for any part bound for a regulated OEM, with the substitution lot captured for traceability. A quantity change routes to the production control manager above a threshold. A due-date change adds a sales watcher so the customer commitment is visible. When the next field return arrives, the change history for that lot is a single traceable record, not a reconstruction from whiteboards and memory. The factory that used to explain its traceability gaps after the fact now governs them as they happen.

What Is Built Today, and What Is on the Roadmap

Manufacturing-order change control is exactly where vendors blur the line between live and planned, so an honest accounting matters.

Built and live today: the change approval step and the traceable, auditable record of each approved change. You can route a quantity, component, schedule, or routing change for approval by role and threshold, capture the approver, reason, and evidence, and hand an auditor or recall investigator a frozen record of what changed, when, and why.

On the roadmap, not yet built: automatically updating the manufacturing order when a change is approved. Today the approval and record are captured, and an authorized user then applies the approved change to the live order under the same governance. The fully automatic path, where approval directly updates the order, is the next milestone. The registry and change-type definitions are in place, so adding the writeback handler is contained work, but it is not implemented today. If a vendor claims their manufacturing-order writeback is fully built, ask to see the actual change handlers and the audit trail for a substitution.

That shapes the rollout. You get the approval gate and the traceable audit record immediately, and full automatic update of the order as the practice matures. For a shop floor moving from whiteboards and taped spreadsheets, that is the right order: prove the discipline first, then automate the last step. And because the approval and the auditable record live inside the same ERP that holds the order, inventory, bill of materials, and cost, governance and the records it protects are never separated: the approver sees the real order, the audit record is tied to the real lot, and traceability is one system holding the truth rather than a second system reconciling to the first.

Frequently Asked Questions

Will an approval step slow down the shop floor?

It changes who is involved, not whether the line runs. Most order changes are decisions a supervisor was already making, just unrecorded. The workflow supports delegation, so a traveling manager does not block the line, and watchers let production control and sales follow a change without being approvers. Genuine emergencies, a breakdown reroute or a safety substitution, can use fast-track routing. Routine changes take minutes longer and gain a record, and risky substitutions finally get the second pair of eyes a recall would later demand.

We trust our supervisors. Why add approval to order changes?

Trust is not the issue. Traceability and segregation of duties are. The supervisor who substitutes a component should not be the only person whose record says it happened, because when a field failure comes back six months later, that supervisor may be on a different shift, at a different site, or gone. Internal control rests on the idea that no single person both initiates and completes a sensitive change, and a substitution on a regulated product is exactly that. The auditable record exists so trust is supported by evidence, not substituted for it.

What about the automatic manufacturing-order update gap?

The approval step and the auditable record are built. The automatic update of the manufacturing order from an approved change is on the roadmap. Today the approved change is applied to the live order by an authorized user under governance, with the approval and the record captured. This is the field where the gap between vendor claims and reality is widest, so it is worth asking to see the actual change handlers before buying.

Does this satisfy lot traceability and J-SOX evidence?

The auditable record is designed for exactly this. Lot traceability asks what went into a specific unit, and the change record captures every approved substitution with its lot and approver. Internal control and J-SOX reviews ask who initiated a change, who approved it, and what was approved, and the record locks all three so they cannot be revised after the fact. Whether your auditor or OEM customer signs off depends on your control environment, but the record provides the evidence the framework asks for.

Key Takeaway

A manufacturing order is the document of record for what your shop floor built, from what, and to what schedule. When it can be changed without approval or record, production traceability collapses and the cost, inventory, schedule, and quality systems that depend on it lose their reference point. The answer is not to freeze the floor so nothing can move, but to give every meaningful order change an approval step and a traceable, auditable record. The approval control and the audit trail are live; the automatic manufacturing-order update is on the roadmap.

Get Started With Kikan System

If uncontrolled manufacturing-order changes have ever broken your traceability or your cost variance, look at Kikan System. The manufacturing-order change approval step and the traceable audit record are built to govern quantity, component, schedule, and routing changes inside one ERP, alongside the approval workflows, expense reimbursement, leave applications, purchase orders, inventory with lots, and bill-of-materials modules. You can start on the free plan with up to 2 users, no credit card required. Begin at /#get-started.