The workshop is behind schedule. A material shipment didn't arrive when it was supposed to. Whatever the reason, you now have to send a message to a customer who paid a deposit weeks ago and is expecting their piece on a date you're not going to hit. Most sellers put this message off longer than they should, because it feels like admitting a failure — but the delay itself rarely costs the sale. How and when you communicate it usually decides whether the customer stays patient or starts asking for a refund.
The short version
Customers are far more forgiving of a delay they hear about early, in plain language, with a real new date, than one they discover by asking first. The message that keeps trust intact has four parts: what happened, what it means for their timeline, what you're doing about it, and when they'll hear from you next. Silence — not the delay itself — is what usually turns a patient customer into a frustrated one.
Why the delay itself isn't the real problem
Made-to-order customers already understand, at least in principle, that they're waiting for something to be built rather than pulled off a shelf. What erodes their patience isn't the wait — it's uncertainty about the wait. A customer who knows their piece will be two weeks later than expected, and why, can plan around that. A customer who doesn't hear anything and starts wondering whether their order has been forgotten, or worse, whether the money is gone, reacts very differently — even if the actual delay ends up being identical in both cases.
This is why the instinct to delay the delay message — waiting until you're certain of the new date, or hoping the gap closes before anyone notices — usually backfires. The version of the message sent proactively, even with some uncertainty, lands better than the same information delivered defensively after the customer asks first.
The four things a delay message needs
1. What happened
A brief, honest reason — not a lengthy justification, just enough that the customer understands this wasn't negligence. “The specialty fabric I ordered was delayed by the supplier” or “the workshop had an equipment issue this week” both work. Vague non-answers (“there's been a delay”) read as evasive even when the actual reason is perfectly reasonable.
2. What it means for their timeline
The specific, updated estimate — not “soon” or “not much longer,” but an actual date or date range. If you genuinely don't know yet, say that plainly and commit to a date by which you will know, rather than leaving the timeline open-ended.
3. What you're doing about it
A sentence showing the situation is being actively managed, not just waited out — “I've sourced the material from a backup supplier” or “I've moved your order up in the workshop queue to make up the time.” This doesn't need to be dramatic; it just needs to show the delay is being handled, not ignored.
4. When they'll hear from you next
A committed next check-in point, even if there's nothing new to report yet. “I'll update you again by Friday either way” removes the customer's need to wonder when they'll know more, which is often the actual source of anxiety more than the delay itself.
How late is late, in practice
Not every slip needs the same message, and treating a three-day adjustment like a crisis trains customers to panic at the word “update.” A rough calibration most made-to-order sellers land on:
- Under a week on a multi-week build. Usually absorbed inside the original estimate if you gave a range rather than a fixed date. Worth a brief note, not a formal delay message.
- One to three weeks. This is the four-part message above, sent as soon as the slip looks likely rather than once it's certain.
- Past a date the customer named — a birthday, a move-in, a wedding. Treat this as a different category regardless of how many days it is, because the deadline, not the duration, is what the customer actually bought.
- A month or more. The message needs a fifth part: what you're offering to make it right, and an explicit acknowledgment that they can decide the order no longer works for them.
The point of deciding these tiers in advance is the same as with a cancellation policy: it stops the response being improvised while you're already stressed about the delay itself.
What this looks like in practice
“Hi [name] — wanted to give you an update on your order. The finish I sourced for your piece was delayed in transit and won't arrive until early next week, which pushes your completion date to [new date] instead of [original date]. I've already followed up with the supplier to confirm the new arrival, and I'll check in again by [date] with a confirmed timeline either way. Sorry for the added wait — I want to make sure it's right before it comes to you.”
Notice what this message doesn't do: it doesn't over-apologize, doesn't bury the actual information in reassurance, and doesn't ask the customer how they feel about it. It states the fact, the impact, the action, and the next check-in, and lets the customer respond however they want to.
Timing matters as much as wording
Sending the message the moment a delay becomes likely — not once it's certain — consistently produces better outcomes than waiting for full clarity. A customer who hears “this might push your date back a few days, I'll confirm by Thursday” reacts far better than one who hears nothing and then gets a firm delay notice after their expected delivery date has already quietly passed. Early and slightly uncertain beats late and fully confirmed, almost every time, because the early version signals the seller is paying attention, while the late version signals the opposite — even if neither seller actually was negligent.
What erodes a customer's patience isn't the wait — it's uncertainty about the wait. A customer who knows their piece is two weeks late, and why, can plan around that. A customer who hears nothing starts wondering if the order — and the money already paid — has simply been forgotten.
Phrases that quietly make it worse
A few common habits undermine an otherwise well-intentioned delay message:
- “It should be ready soon” — “soon” means nothing specific and forces the customer to guess whether that's days or weeks, which usually produces a follow-up question rather than reassurance.
- “These things happen” — true, but it minimizes the customer's inconvenience rather than acknowledging it, and can read as dismissive even when that's not the intent.
- Blaming a third party in detail (“the supplier really dropped the ball, I've been trying to reach them for days”) — this can come across as deflecting responsibility rather than owning the update, even when the supplier genuinely is the cause. A brief, factual mention of the cause is enough; an extended complaint shifts the tone from informative to defensive.
- No timeline at all — even “I don't know yet, but I'll confirm by Thursday” is better than an open-ended “I'll let you know when I know,” which leaves the customer with nothing concrete to hold onto.
The common thread across all four is specificity. Vague reassurance feels good to write but does little for the person reading it; a concrete, if imperfect, timeline does more to preserve trust than a warmer-sounding but emptier message.
Every order carries its own status and balance, so the update writes itself.
See how it worksWhen a delay turns into a bigger conversation
Sometimes a delay is significant enough that it changes the terms of the order — a multi-month push, or a delay that runs past an event the piece was meant for. In those cases, the four-part message above still applies, but it's worth adding a fifth element: acknowledging the customer's options. Offering a partial refund of the deposit, a discount on the balance, or simply asking directly what would make the situation feel fair shows the seller isn't assuming the customer will just absorb the inconvenience quietly. This doesn't need to be offered defensively — a straightforward “given how significant this delay is, I want to make it right; would a [specific gesture] help?” usually resolves more goodwill than it costs.
If the conversation goes further than a gesture and the customer wants out entirely, that's a different decision with its own norms — what sellers typically retain, refund or credit is set out in what happens if a customer cancels after paying a deposit.
Why this is easier when you actually know the status
A lot of delayed-order anxiety, on both sides, comes from not having a clear, current answer to “where does this order actually stand right now.” If checking an order's status means scrolling back through a chat thread trying to remember the last update, it's genuinely harder to communicate delays promptly and consistently — because the seller themselves has to reconstruct the situation before they can explain it to the customer.
An order page that updates as production moves forward reduces this friction from both directions: the customer can check for themselves without needing to ask, and when a real delay does happen, the seller isn't starting the conversation from scratch trying to remember what was last said. What such a page needs to contain — and how to have one without building it — is covered in how to give custom order customers an order page.
Give customers a live page showing where their order actually stands.
See how it worksThe bottom line
A delay doesn't have to cost a made-to-order seller a customer's trust — what costs the trust is silence, vagueness, or a customer discovering the delay by having to ask first. A short message that states what happened, what it means for the timeline, what's being done, and when they'll hear next covers almost every situation, and sending it early — even with some uncertainty still attached — consistently beats waiting for full clarity.
Frequently asked questions
How soon should I tell a customer their order is going to be late?
As soon as a delay becomes likely, even before it's fully confirmed. A message that says “this might push your date back, I'll confirm by [date]” sent early lands better than a fully certain delay notice sent late.
Should I offer compensation every time an order is delayed?
Not necessarily for minor delays of a few days, which most customers absorb without issue if communicated clearly. For significant delays — weeks, or past an important date — offering a gesture like a partial discount or deposit adjustment is worth considering.
What if I genuinely don't know the new completion date yet?
Say that plainly rather than guessing or staying silent — “I don't have a confirmed new date yet, but I'll update you by [specific date] either way” is honest and still gives the customer a concrete point to expect information.
How often should I proactively update a customer once a delay is in progress?
Committing to a specific next check-in date, even without new information, is usually more reassuring than frequent but vague updates. Weekly check-ins are a reasonable default for delays measured in weeks.
Does apologizing too much in a delay message make it worse?
It can — over-apologizing tends to bury the actual useful information (what happened, the new timeline, the next update) under reassurance the customer doesn't need. A brief, sincere acknowledgment followed by clear facts works better than an extended apology.
Should the delay explanation be detailed or brief?
Brief and honest is usually best — enough detail that the customer understands it wasn't negligence, without turning the message into a lengthy justification that can read as defensive.
Is it better to call a customer about a delay or send a message?
For minor delays, a written message is usually sufficient and lets the customer process it on their own time. For significant delays or when a bigger conversation about options is needed, a call can convey more care and allow for real-time back-and-forth.
Note
The communication practices described reflect general customer-service principles commonly recommended for service and made-to-order businesses, rather than findings from a specific formal study. Individual customer reactions to delays vary, and these are general guidelines rather than guaranteed outcomes.