Order Visibility: Knowing Where the Batch Is

An order that disappears into a factory for two weeks creates its own problems, and they are not only emotional. A customer who does not know whether the material has arrived cannot decide whether to tell their own customer that the date is safe, and an engineer who cannot see which operation the boards are in cannot plan the work that follows.

Order visibility is therefore a practical requirement rather than a comfort. Its value is highest on a small order, where a single missing part or an unresolved question has a large effect on the schedule and where there is no inventory to absorb a surprise.

What Should Be Visible

The minimum useful set is small. Whether the data has been reviewed and what the review found. Whether the material is complete or which items are outstanding. Whether the boards have been fabricated. Where the order is in the assembly sequence. And whether it has shipped, with the reference that identifies it.

Each of those is a discrete state rather than an estimate of progress, which is what makes it trustworthy. A percentage is an opinion; the fact that the material is complete is a fact.

The states also correspond to the points at which the customer may need to act. Where a material shortage is identified, the customer may need to approve a substitute or supply the part. Where the review produces a question, the answer is needed before the stencil is ordered. Visibility is most valuable exactly where it enables a decision.

Why Problems Are Announced Late

The reason a problem becomes a surprise is usually a delay in the internal information rather than in the work. The material shortfall is known when the parts are picked, and it becomes visible to the customer when someone has time to write.

Breaking that delay does not require a system. It requires an agreement that a question will be sent when it is found rather than when the schedule is threatened, and a named person on each side who receives it. In practice, most of the value comes from the first day of a problem rather than from a tracking screen.

An explicit threshold helps. Where the parties agree that anything that could affect the date is reported as soon as it is identified, without waiting to see whether it resolves itself, the awkward conversations become smaller and more frequent, which is a considerable improvement on fewer and larger ones.

<img src="https://www.gopcba.com/wp-content/uploads/2026/05/smart-logistic.jpg" alt="order visibility and status tracking for an assembly batch” />

Status Tracking and the Customer’s Own Planning

Inside the customer’s organisation, the effect of visibility is a change in planning. Where the states are known, the work that follows the boards — programming, test definition, the mechanical fit, the demonstration, the next revision — can be scheduled against them rather than held in reserve.

That is a real gain on a compressed project. A week saved in knowing that the boards will arrive on Thursday, rather than in the boards arriving a day earlier, is often worth more than an expedite charge, because it allows the customer’s own engineers to be committed with confidence.

Visibility also improves the record at the end of the order. Where each state was reached on a known date, the delivery can be explained afterwards, and the next order can be planned on the intervals actually observed rather than on the intervals assumed.

The Change Notification Problem

A related question concerns changes, and it is the one that causes the most expensive surprises. Where the customer issues a revision during the work, the change has to reach the material list, the stencil, the programme and the inspection criteria, and each of those has an owner.

A single stated revision in the order is what makes this manageable. Everything that follows refers to it, and a change is a new decision rather than an amendment carried out implicitly in one place and not others.

The supplier’s changes belong to the same topic. Where a substitution is proposed, a process parameter is altered or a delivery is split, the customer should hear about it while it is still a proposal rather than after it has happened. That is a matter of agreement rather than of technology, and it is worth stating in the order.

What Visibility Is Worth

The value of knowing the state of an order is easiest to see when it is absent. A customer who expects a delivery on a date and discovers two days beforehand that a part was never available has lost the time that could have been used to approve a substitute or to re-plan the demonstration.

The same information, delivered a week earlier, is a manageable decision. This is the whole argument: the information is identical, and its value depends entirely on when it arrives.

The second effect is on trust. Where the history of an order is visible, the estimates given for the next one are believed, because the previous ones proved reliable. Where progress is only reported at the end, every date is a hope and every delay is a surprise, and the customer compensates by padding their own plan, which costs more than the delay itself.

There is a cost to the supplier as well, though a smaller one: a customer who can see the state of the work asks fewer questions, because the answer is already available. The time saved in the factory is frequently more than the time spent reporting.

Making It Work in Practice

The arrangements that work are simple. A single technical contact on each side, with the authority to answer. An agreement about what is reported and when, expressed in terms of decisions rather than percentages. A written revision reference. And a response time expectation, so that a question has an answer within a working day rather than eventually.

None of this requires new software, and none of it costs anything to put in place. What it does require is that the supplier treats communication as part of the service rather than as an interruption to it, which is a quality that is observable before the order is placed.

The test is available to any customer: send a technical question with the enquiry and observe how long the answer takes and who sends it. The operations that follow the order are the familiar ones: SMT assembly, PCBA testing and the controls described under quality management.

One last point belongs with the same subject: the delivery itself should be visible before it arrives. A packing list sent when the boards are packed, rather than discovered when the box is opened, allows the customer to prepare for what is coming and to check the quantity and the references against their own records in advance.

FAQ

Is a tracking system necessary? No. The value comes from the information reaching the customer in time to act, which is a matter of agreement rather than of software.

What is most useful to know? Whether the material is complete, where the order is in the sequence, and any question that requires a decision.

How should changes be handled? Against a single stated revision, with any adjustment proposed to the customer before it is made rather than reported afterwards.