Back to all posts
Control Systems7 min read·October 25, 2026

How Should ERP Orders Reach the Shop Floor?

TB
ThynkBlox Automation Team
Automation Engineering

To integrate ERP production orders with the shop floor, agree who releases work, exchange a defined order record, and return confirmed production results against that same record. Give each order, revision and progress message a clear identity. Keep business release separate from permission to start equipment: an accepted order should become available for controlled execution, not act as a direct machine command.

Who should own order release and execution?

Start with a written ownership decision. A practical arrangement is for the ERP to own the authorised production requirement and for a manufacturing execution system (MES), or another agreed shop-floor application, to own dispatch and execution records.

Business release means that an order is authorised for production. Local dispatch means choosing when and where to execute it within that authorisation. Machine start remains a separate action governed by the equipment controls and operating procedure.

Use an ownership table before discussing software connections:

Decision or recordProposed ownerBoundary to agree
Order identity, product and required quantityERPWhich fields can change after release
Business releaseERP or named planning authorityExact state that permits dispatch
Line assignment and local sequenceShop-floor application or supervisorWhether reassignment needs approval
Execution events and actual quantitiesShop-floor applicationWho can correct recorded results
Business posting and closureERPWhich results must arrive before closure
Equipment start and permissivesLocal control system and authorised operatorSeparate from order acceptance

Treat this as a proposal to resolve, not a rule that every plant must follow. Record one authoritative owner for each decision, including any manual approval.

What information should an order contain?

Define the smallest order record that production can interpret without guessing. Include the order identifier, revision, product identifier, required quantity and unit, intended operation or route, and any production instructions needed at release.

Where execution depends on a recipe or specification, reference its approved version. Decide whether the receiving system stores that version or retrieves it before accepting the order. Do not allow a reference to silently resolve to whichever version happens to be current.

For materials, distinguish these identifiers:

  • Material code: which material is required.
  • Lot or batch identifier: which specific stock may be used.
  • Unit of measure: how its quantity is expressed.
  • Approved substitute: what may replace it, and under whose authority.

Agree whether the ERP supplies permitted lots or the shop floor selects them. Keep leading zeros and other meaningful characters in identifiers. Define conversions explicitly; do not infer that a quantity in packs means the same quantity in pieces.

An unknown material, missing unit or unapproved substitute should enter a visible exception queue before dispatch.

How should the shop floor acknowledge an order?

Separate message delivery from business acceptance. Design distinct responses so the sender can tell whether an order arrived, passed validation and became available for execution.

For example, define these states in the interface contract:

StateMeaning
ReceivedThe message has been stored
AcceptedRequired checks passed for this revision
RejectedThe order needs correction before acceptance
DispatchedThe accepted order has been assigned for execution
StartedExecution has begun
CompletedExecution results have been recorded
ClosedRequired business reconciliation is finished

Choose terms that fit the plant, but define each transition and its owner. In particular, acceptance must not imply that production has started.

Include the order identifier, revision and message identifier in each response. Define duplicate handling: receiving the same release again should return its recorded outcome without creating another executable order.

What happens when a released order changes?

Treat a revision as a proposed change to an identified order. Do not silently overwrite instructions that an operator may already be following.

Set rules according to execution state. Before dispatch, the receiving system may accept a validated replacement revision. After dispatch, require acknowledgement of the changed instructions. After production starts, route changes affecting materials, quantity, recipe or quality requirements through a defined review.

Specify what happens to work already completed, issued material and work in progress. A revision should not rewrite historical consumption or production records.

Illustrative example: an order initially requests 500 pieces. After 200 pieces have been reported, planning reduces the total to 350 pieces. The interface should make clear that 350 is the revised total requirement, leaving 150 pieces to produce. It should not interpret the revision as a request for 350 additional pieces.

Return the accepted revision in progress reports. If an older revision arrives late, reject it or flag it for review according to the agreed rule.

How should cancellations reach the floor?

Send cancellation as a request with its own identity and acknowledgement. Define when the floor can accept it automatically and when a supervisor must review it.

For an order that has not started, cancellation may remove it from the dispatch queue. For an order in progress, define a controlled stopping point, how remaining work is handled, and how actual production and consumption are reported.

Keep the business request separate from equipment stopping. Do not use an ERP cancellation as an emergency-stop command. Review any safety-related design with a qualified assessor.

The response should state whether cancellation was accepted, is awaiting a controlled stop, or requires intervention. Preserve the record of what happened before cancellation.

What progress should return to the ERP?

Agree which execution events the business needs and what each quantity means. A useful starting set is started, good output, rejected output, material consumed, held, completed and cancelled.

Define whether quantities are incremental events or cumulative totals. Do not mix the two without an explicit field that distinguishes them. Include units, the relevant operation, the accepted order revision and any required lot references.

For each event, record when it occurred separately from when it was received. Decide how late events affect an already completed or closed order.

Design correction messages deliberately. A correction should identify the original record and explain the adjustment, rather than erase the history.

Keep production completion separate from quality release where the process requires both. Likewise, decide whether physical completion can be recorded while a business posting remains unresolved.

For a related measurement question, read what an OEE number can hide.

How should rejected messages and outages be handled?

Give every rejection an actionable reason: unknown material, unsupported unit, invalid revision, disallowed state change or missing required information. Include the affected field and assign a person or team to resolve it.

Distinguish temporary delivery failures from business validation failures. Define retries for temporary failures; require correction or approval for rejected business content.

Specify duplicate protection for both orders and progress events. A repeated production message must not post the same output twice.

During an outage, make the permitted operating mode explicit. Decide whether accepted work can continue, whether new releases are blocked, and where pending results are retained. Show operators when information is stale.

After reconnection, reconcile open orders and unacknowledged events. Do not assume that restoring the connection resolves every disagreement. See alerting when ERP-to-shop-floor handoffs fail.

What common mistakes should the design prevent?

Watch for these shortcuts during review:

  • One “success” response: delivery, acceptance and execution need separate meanings.
  • Silent revision replacement: changed instructions need an agreed acceptance path.
  • Name-based material matching: use controlled identifiers and explicit mappings.
  • Blind retries: define how repeated messages avoid repeated business actions.
  • Cancellation as deletion: retain actual production, consumption and disposition.
  • Completion without reconciliation: define who resolves missing or rejected postings.

These decisions belong in the functional design specification, alongside responsibilities and acceptance tests.

What should be tested before handover?

Run representative orders through release, acceptance, execution and closure. Then deliberately test duplicates, missing materials, incompatible units, older revisions, changes after start, cancellation during work and lost acknowledgements.

For each case, inspect both systems and the operator’s view. Confirm that quantities agree, exceptions are visible and recovery does not require guessing what happened.

Define acceptance criteria before testing. A useful criterion is that every test order ends with matching business and execution records, or a visible unresolved exception with a named owner.

Frequently asked questions

Does this require a full MES?

Not necessarily. Scope the required dispatch, validation, reporting and recovery functions first. A smaller application may suit the agreed process, provided ownership and exception handling remain explicit.

Should the ERP send commands directly to a PLC?

For the order exchange described here, send authorised production requirements to the execution layer. Keep equipment commands within the agreed control design, with local permissions and operating conditions checked separately.

How quickly should progress reach the ERP?

Set the interval from the business decision it supports. Agree acceptable delay for planning, stock and closure separately, then test that behaviour during normal operation and recovery.


Planning an order interface? Explore our automation services or contact us to discuss release ownership, execution reporting and failure handling.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.