'Any update on our order?': the supplier delay email sequence that gets answers

"Any update on our order?" feels productive to send and gets you nothing back. It asks for status, not for a decision, so it earns the supplier's cheapest reply — "we're working on it" — and you've burned a day of lead time for the privilege. Every email that actually moves a drifting order does two things: states one specific fact (PO number, promised date) and asks one specific question (a date, a quantity, a name). Here's the three-rung chase ladder, with word-for-word templates for each rung and the triggers that tell you when to climb.

One boundary first: this ladder is for the window when the order is drifting but the promised ship date hasn't formally broken — the earlier, softer chase. The moment the date passes without shipment, you're in incident territory, and the response priorities change; the incident playbook for a supplier who missed the ship date owns that situation. And if delays keep originating from ambiguity in what you originally sent, fix the source — the PO email is where the dates and quantities get locked in the first place.

The ladder at a glance

Three rules govern the whole ladder:

• One rung at a time. Skip to rung 3 only after 48 hours of silence at rung 2. Sending all three in one day tells the supplier your deadlines are decorative.
• Every email names the PO. Order number, product, quantity, promised date. The supplier's team handles many orders; yours must be findable in five seconds.
• Ask for things a person can answer. Dates, quantities, names. Never "thoughts?"

The example running through the templates: you ordered 2,000 enamel pins on PO-204, promised ship date April 18 (illustrative scenario, invented numbers).

Rung 1 — the first nudge: specific, lightweight

Subject: PO-204 — enamel pins: confirm April 18 ship?

Hi Dana,

Quick check on PO-204 (2,000 enamel pins, promised ship April 18). Can you confirm that date is still holding?

If anything has moved, a revised date is all I need for now.

Thanks, [Name], [Store]

Why it works: named PO, named product, named date, one question, and the smallest possible reply burden. "A revised date is all I need" is doing quiet work — it tells Dana that admitting a slip now is cheap, which is exactly what you want, because a slip admitted on April 10 is a plan; a slip discovered on April 18 is a crisis. No "just checking in," no exclamation marks, no guilt.

Send this even when you expect nothing is wrong. The reply itself is data: a supplier who confirms dates on time is a supplier whose dates mean something, and one who doesn't has told you how to read their next quote.

Rung 2 — the specific chase: blocker, new date, partial ship

Trigger: Dana replies "on track!" — with no date in it — or the reply is vague in any way that lacks a number. Vague is worse than silence, because it feels like an answer. Your job now is converting status-speak into two answerable questions, and opening the door to a smaller win:

Subject: PO-204 — need a revised ship date + partial-ship option

Hi Dana,

Thanks for the update. To plan my side, I need two things:

1. What's the specific blocker — materials, production queue, or QC?
2. A revised ship date you'd put in writing.

If the full 2,000 can't make the new date, can you ship 1,000 now and the balance within the week of that date? I can work with a split if the dates are real.

If a firm date isn't possible by Friday, telling me that is better than another 'on track' — I'd rather replan than re-ask.

[Name]

Why it works: the numbered questions make "on track" impossible to repeat. The partial-ship offer is the most underused move in the ladder — a supplier drowning in one late order can often extract half of it, and half shipping on time may keep you selling while the rest finishes. And the Friday line converts the conversation from open-ended to dated, while giving honesty an easy exit: "can't commit" is an acceptable answer to a question you asked, and it's still information you can plan on.

Rung 3 — the escalated email: timeline, consequence, a named owner

Trigger: 48 hours after rung 2, nothing — or another reply without a date. You now stop asking Dana and start asking Dana's employer, in writing, calmly:

Subject: PO-204 — response requested by Thursday

Hi Sam (cc Dana),

Recap so we're working from the same facts:

• PO-204 placed March 2 — 2,000 enamel pins
• Promised ship April 18; on April 16 revised to "shortly"
• Chased April 14 and April 21; no firm date since

I need two things by Thursday: the name of the person who owns this order, and a ship date you'll stand behind.

If PO-204 can't ship by May 5, I'll source the pins elsewhere and cancel the balance. I'd rather not — the design work is good — but my store can't plan around silence.

[Name]

Why it works: the recap removes the "we never said that" escape route and takes thirty seconds to verify. The consequence is specific, dated, and proportionate — not a threat, a statement of what happens next, which makes it credible. Asking for a named owner matters more than it looks: someone's name on the order changes how it's prioritized inside a factory. And the May 5 date means that even a bad outcome arrives with a deadline attached, which is all you need to start planning either way.

What to do with the replies — the part merchants skip

Every rung generates supplier data that most merchants throw away with the thread. Log two numbers per order: response time, and promised date versus actual ship date. Over a handful of orders, a pattern names itself:

• Answers fast, ships late. Communication is fine; production isn't. The fix is buffers, not emails — your chase ladder is working, and your reorder math needs a wider reality. Measuring your real lead time from PO history is the companion move.
• Goes silent at rung 2. Communication is the problem. This is the supplier to double-source around, and the pattern of response times belongs in a supplier scorecard so it shapes the next buying season, not just this order.

One template set, two diagnoses. That's the quiet payoff of chasing in a structure instead of in a panic.

Small things that change reply rates

• Subject lines carry the PO number and the ask ("confirm," "revised date," "response requested"). Your email is findable and answerable before it's opened.
• One email, one topic. Don't bundle the delay chase with a new-order question; bundled emails get half-answered.
• Send in their morning, not your evening. A chase that arrives at the start of a factory workday gets handled; one that lands at 11 p.m. local time starts its life forty emails deep.
• Keep the thread. The history is your evidence if the escalated email becomes a dispute, and your recap material if it doesn't.

Common questions

When should I email a supplier about a delay? Before the date breaks: a light, specific nudge 5–7 days before the promised ship date, or after three business days of silence on an acknowledgment. Chasing early with a specific question surfaces slips while you still have alternatives; chasing after the fact leaves you replanning instead of deciding.

What should I write in a delay email to my supplier? One specific fact and one specific ask: the PO number and promised date, then a question requiring a decision — "can you confirm that date, or give me a revised one?" Avoid "any update?" — it invites "we're working on it." Ask for dates, quantities, and names.

How do I get a supplier to respond when they've gone quiet? Escalate: recap the order facts in bullets, state one calm, dated consequence ("if it can't ship by May 5, I'll source elsewhere and cancel"), and ask for the person who owns the order. Send it to a manager, cc your contact, give a reply-by date.

Should I ask for a partial shipment when an order is late? Usually yes, once you have a revised date: a split — 1,000 of 2,000 units now, the balance within a week — costs the supplier less than perfection and keeps you selling meanwhile. Make the offer concrete, with exact quantities and dates, so it's a yes-or-no.

What's the difference between chasing a delay and handling a missed ship date? Chasing happens while the promised date still stands — you're confirming it or surfacing a slip early, with alternatives intact. Once the date has passed without shipment, it's an incident: priorities shift to expedite options, customer commitments, and recovery decisions. Different situation, different emails, different stakes.

Next step

Save the three templates beside your PO boilerplate so rung 1 goes out on schedule rather than on anxiety — the nudge is only valuable if it's early. Then pick your two least reliable suppliers and log promised-versus-actual ship dates for their last five orders. If the pattern is "answers fast, ships late," your chase emails were never the problem; your buffers are, and ten minutes with your lead-time history will tell you by how much.