The Customer Asked Where the Order Is. Which Answer Is True?
Delivery confidence depends on connected evidence across material supply, internal production, subcontractors, quality release and logistics—not a collection of optimistic dates.
The short answer
Credible electronics order visibility comes from agreed milestones backed by current operational evidence. The customer should not receive the most optimistic date from sales, the oldest date from ERP or the latest informal estimate from production.
Connect material readiness, internal and subcontract production, quality release and logistics to one order promise. Then every customer answer can explain what is complete, what remains constrained and why the delivery date is still credible—or why it must change.
Five teams give five correct answers
Sales says the order is in production. Planning says it is scheduled. Warehouse says the kit is short. Production says SMT is complete. Quality says the lot cannot be released until one failed unit is resolved.
Each statement may be true. None answers the customer’s question alone.
Order visibility fails when status words describe departmental activity rather than the customer promise. “Started” and “complete” need a shared operational meaning tied to quantity and remaining risk.
Begin with the promise
The customer promise should identify product, revision, quantity, requested date, committed date, delivery terms and any agreed partial shipment.
Changes need reason and authorisation. A salesperson should not overwrite the committed date merely to reflect a request, and planning should not change it without making the customer consequence visible.
Keep requested, planned and committed dates separate. Their difference reveals whether the business is accepting demand, proposing an operational plan or making an external promise.
Define milestones customers can understand
Useful internal milestones may include engineering released, critical material secured, kit ready, production started, assembly complete, test complete, quality released, packed, dispatched and delivered.
Not every customer needs every internal event. The external view should use a small set of meaningful states with stable definitions. Internally, each state should be earned by evidence.
For example, “production complete” should specify whether all ordered quantity completed the route or only the current batch left SMT. “Ready to ship” should require quality release and logistics readiness, not just finished quantity.
Quantity belongs inside status
An order of 10,000 units cannot be represented by one word if 6,000 passed, 2,000 await test and 2,000 lack components.
Show quantity by milestone and disposition. This supports partial shipment decisions, realistic recovery and clearer customer communication.
Avoid double counting when work orders split or merge. The order view should reconcile planned, completed, held, scrapped, released and shipped quantities.
Material coverage must reflect eligibility and time
A purchase order acknowledged by the supplier is not the same as a component ready for production. Arrival, inspection, approval, transfer and allocation still matter.
Order visibility should distinguish secured material, expected supply and unresolved shortage. Critical components deserve attention based on production need and recovery options.
If an alternate requires customer approval, the order remains constrained until that decision is obtained. Optimistic planning should not silently assume approval.
Internal production needs current execution evidence
Work-order release is not production progress. Capture actual start, quantity completed, current operation, hold reason and expected recovery.
MES, barcode and machine integration can improve timeliness, but definitions remain essential. A machine cycle does not always equal a good completed unit. A reported operation completion may still leave mandatory inspection or test.
Where automatic data is unavailable, provide a disciplined simple update. A reliable manual event is better than an impressive but stale dashboard.
Subcontract work is part of the same order
Electronics and EMS routes often include external coating, specialist assembly, testing or finishing. Visibility commonly breaks when material leaves the site.
Create a subcontract milestone with dispatch quantity, partner acknowledgement, expected completion, current exception and received-back quantity. Preserve the relationship to the original work order and product identity.
Supplier portals, integrations or structured updates can improve frequency. The minimum requirement is a clear owner and evidence date. “With subcontractor” is not a useful status for two weeks.
Quality release can redefine available quantity
Production completion creates output; quality release determines what can safely move. If one failure holds the lot, the order view should show completed quantity separately from releasable quantity.
Disposition matters. Some units may be accepted, some require rework and some await investigation. Customer communication should reflect the approved release strategy.
The articles Does the Serial Number Survive the Rework Bench? and The Yield Looks Good. The Rework Cost Says Otherwise. explain why final pass and repair evidence matter to promise confidence.
Logistics closes the operational story
Packed does not mean dispatched, and dispatched does not mean delivered. Connect packing list, carrier, shipment time, tracking and delivery confirmation to the customer order.
If export documentation, booking or consolidation affects departure, represent it as a real milestone rather than an informal note.
Partial shipments should reduce the remaining promise correctly. Customer service should see what moved, what remains and the next evidence-based date.
Use confidence, not false certainty
A single date can hide different levels of risk. Add a simple confidence view based on unresolved engineering, material, capacity, quality and logistics conditions.
Confidence should not be a subjective colour chosen by sales. It should derive from known gates and exceptions. A committed date with one unconfirmed critical component is different from a date whose kit, capacity and route are secured.
When confidence falls, require owner, recovery action and communication decision. Early transparency gives the customer options that late certainty cannot.
One status owner, many evidence owners
Customer service or account management may own the external answer, but the evidence comes from engineering, purchasing, warehouse, production, quality and logistics.
Each milestone needs a source and owner. The order view should aggregate results without allowing one department to declare another department’s work complete.
Escalation should focus on overdue exceptions and promise impact. A daily meeting becomes shorter when participants see the same evidence before it begins.
Multi-site orders need shared identity
When production crosses plants, one site may treat an intermediate assembly as finished goods while another treats it as purchased material. Intercompany transactions can obscure the end-customer order.
Preserve a common demand and product relationship across sites. Show transfer, receipt and local execution as parts of the same fulfilment chain.
Currency, ownership and local planning can remain site-specific. Customer visibility still needs a consolidated quantity and milestone view.
The pillar One Product, Hundreds of Decisions. Can Your Factory See Them All? describes the shared identities that make this possible.
Design the customer answer
A useful update contains five elements:
1. the quantity and revision in scope;
2. the latest completed milestone;
3. the current constraint, if any;
4. the recovery action and owner;
5. the evidence-based shipment expectation.
This structure is more valuable than forwarding a screenshot full of internal codes. It gives the customer clarity without exposing unnecessary operational detail.
Templates can improve consistency, but the underlying facts must come from the live order record.
Measure promise quality
Track on-time delivery, date changes, promise confidence at confirmation, late-discovered constraints, milestone update timeliness and customer enquiries caused by missing status.
Review orders whose date changed repeatedly. Identify whether the original promise ignored engineering, material, capacity, subcontract or quality evidence.
Also review apparently successful orders that required expediting. On-time delivery achieved through premium freight and emergency intervention is not the same operating performance as a stable fulfilment process.
Run a status reconstruction
Choose one open order crossing at least three departments. Ask sales, planning, production and quality for the current status independently.
Compare their answers by revision, quantity, milestone, constraint and expected shipment. Then trace each statement to its source and update time.
The disagreements reveal ambiguous definitions and broken relationships. Agree a small milestone model and test it on the next order before building a large dashboard.
Frequently asked questions
Should customers see the internal production dashboard?
Usually not directly. Provide a customer-appropriate view with clear milestones and quantities, supported by internal evidence and access controls.
How often should order status update?
At every meaningful event and exception. The required frequency depends on lead time and customer need, but the displayed status should always show its evidence time.
Is the ERP promised date enough?
Only if the date is maintained from current material, capacity, quality and logistics evidence. A static field does not create confidence.
How should partial shipment be shown?
Separate shipped, releasable, completed, held and remaining quantities, with dates for each agreed shipment where applicable.
Who should tell the customer about delay?
The designated account owner should communicate, using an authorised recovery plan and evidence from operational owners. Systems support consistency; commercial judgement remains human.
Replace status chasing with shared evidence
Customers do not expect a factory to eliminate every exception. They expect early, coherent and credible communication.
Connect each promise to the milestones and quantities that support it. Then the answer to “Where is my order?” no longer depends on who happens to pick up the phone.