When a Shipment Starts Slipping: Early Signals and the First 48 Hours

Almost no supplier announces a delay in advance. What happens instead is a sequence of small changes: an answer that takes a day longer than usual, a completion date that moves by a few days, an explanation that is slightly different each time you ask. By the time a delay is stated plainly, the options have already narrowed.

This guide is about the earlier part of that curve — what the signals look like, why they are hard to read from another timezone, and what actually helps in the first two days.

Why delays are announced late

There is a structural reason, and it is not usually dishonesty. A supplier who says “we may be late” risks losing the order or triggering a penalty, and a supplier who says nothing may still make the date. So the incentive is to wait and hope — and to say something only when the date is definitively lost.

The result is that the information exists before it is communicated. The production line is behind, the component has not arrived, the sub-supplier has not delivered — these are known internally well before they are admitted externally.

The signals, in rough order of appearance

• Response time changes. The most reliable early indicator and the easiest to miss. A contact who answered in hours now takes a day, and the answers get shorter.
• The reason changes. First it was a component, then it was a test, then it was the holiday. Shifting explanations usually mean the first one was not the whole story.
• Dates become vague. “Next week” replaces a specific date. Precision disappearing from someone who was previously precise is information.
• Requests you have not seen before. An unexpected ask to change a specification, split the shipment, or adjust a document often indicates something upstream is not going to plan.
• Photographs and updates stop arriving. Progress updates that used to be volunteered now have to be asked for.
• Partial shipments are proposed. An offer to ship part of the order now is frequently a sign that the rest will not be ready when promised.

None of these individually mean a delay is coming. Two or three together, from a supplier whose normal behaviour you know, usually do.

Why this is hard to read remotely

Every signal above is a change in behaviour, and detecting a change requires knowing the baseline. A buyer who emails every few days sees snapshots and cannot easily distinguish “they are busy this week” from “something has gone wrong”.

There is also a timezone effect that costs real time. A question sent in the evening reaches China the next morning and may be answered the following day — so a buyer can lose three or four days establishing what is happening, which is often most of the window in which action was possible.

The first 48 hours

Once you suspect a slip, the objective is not to apply pressure but to establish facts while choices remain. In rough order:

1. Get a specific current state, not a new promise. Ask what is physically done — how many units are complete, tested and packed — rather than when it will finish. A completion estimate can be negotiated; a physical count cannot.
2. Identify the constraint. Is it materials, a component, a test slot, capacity, or a sub-supplier? The response differs completely depending on which, and a supplier will often say “soon” rather than naming it unless asked directly.
3. Ask what would unblock it. Sometimes the answer is a decision only you can make — approving a substitute component, accepting a partial shipment, or confirming a specification detail that is holding a test.
4. Have someone look, if that is possible. A photograph of the current state or a visit the same day settles the question faster than any exchange of messages.
5. Decide your own deadline independently. Work out the last date at which a delayed delivery still works for you — the vessel, the season, the launch — and tell the supplier that date rather than asking them for one.

What is worth doing and what is not

• Worth doing: establishing the physical state, naming the constraint, offering to make a decision that unblocks it, and stating your real deadline.
• Worth doing: agreeing a partial shipment if part of the order is genuinely ready and the rest can follow.
• Not worth doing: escalating threats before you know the cause. Pressure applied to the wrong constraint does nothing, and it makes the next conversation less honest.
• Not worth doing: accepting a new date without asking what changed. A revised promise from a supplier who has not identified the constraint is a hope, not a plan.

Preventing the next one

The durable lesson is that slips are easier to see coming on the next order than on this one. Three things help:

• Agree progress checkpoints in the order terms — what will be reported and when — so that silence is itself a signal rather than the normal state.
• Know the critical path before the order starts. Which component, test or process is most likely to slip, and what its lead time is; the mechanics are set out in what actually decides lead times.
• Have someone in the same timezone who can establish facts the same day rather than over three days.

How ApplianceChain helps

This is one of the places where being local is worth the most, because the value is entirely about time. We can go and look the same day, establish what is physically done rather than what is promised, and often identify the constraint by asking the question in person in a way that is difficult by email.

We do not guarantee dates and we cannot make a supplier faster. What we do is shorten the interval between something going wrong and you knowing about it — which is usually the difference between having options and having none.