How to tell customers about a delay without losing them

Most suppliers handle delays backwards. They wait until the delay is certain, work out the new date, prepare an explanation, and send a carefully composed message — by which point the customer already knows, because they checked the tracking.

The composition was never the problem. The timing was.

Why early beats complete

A customer told on the day the risk appears can still act. They can re-plan a production run, tell their own customer, or ask you to expedite part of the order. A customer told when the delay is confirmed has lost every one of those options, and the only thing left is to be annoyed.

This is why "we wanted to have all the facts first" reads as an excuse rather than diligence. From the customer's side, waiting for certainty means withholding information they could have used.

Send the first message when you know the risk is material, not when you know the outcome. It is entirely reasonable for that message to say you do not yet know the new date.

What the first message needs

Four things, and no more:

1. Which order. Their reference, not yours.
2. What has happened, in one sentence, with no detail they did not ask for.
3. What it means for their date — a revised date, or an honest range with a date by which you will confirm.
4. What you are doing about it, and what you need from them if anything.

What it does not need: an apology paragraph, an explanation of the geopolitics, or reassurance about how seriously you take this. Those read as padding around bad news, and they make the message longer without making it more useful.

Three things that reliably make it worse

Hedging the date. "We anticipate potential impact to the delivery schedule" tells the reader nothing and signals that you are managing your exposure rather than their problem. Give a date or a range.

Explaining at length. The cause matters to you far more than it matters to them. One sentence.

Going quiet after the first message. The first message creates an expectation of updates. If the next thing they hear is silence, the goodwill you bought by telling them early is spent.

A template for the first message

Subject: Update on order [REF] — revised ETA

Hello [Name],

A heads-up on order [REF]. [One sentence: what happened and which lane it affects.]

Your revised ETA is [date], from [original date]. [If uncertain: I expect to confirm the date by [date].]

[What you are doing — expediting, holding buffer stock, offering partial shipment.]

[If relevant: nothing else on your account is affected.]

[Your name]

Adapt the tone, keep the order. The structure works because it front-loads what the reader needs and leaves out what they do not.

The part that is hard to fake

None of this works if you find out late. A process for writing good delay emails is worth very little if the trigger is a missed ETA, because by then the customer has had the same information for several days.

The message is the easy half. Knowing early enough to send it is the half worth building.