Supplier missed the ship date: the incident playbook

18 days. That's how long the hiking socks last at 21 pairs a day — and the supplier just confirmed that the shipment due today needs 25 more days. A missed ship date is an incident, and incidents go better with a sequence than with adrenaline: get the miss confirmed in writing, quantify your actual runway, escalate in levels instead of one furious email, make only the customer promises you can keep, and log the fix so the same supplier fails the same way less often. Here's the whole sequence, starting with the arithmetic that decides everything else.

Hour zero: make the miss a fact in writing

Until it's in writing, a missed date is a rumor with good posture. The supplier may be hoping you won't notice, or hoping the delay compresses on its own; silence and 'it's on the way' are both non-dates. The hour-zero email does three things in one short message: names the missed date, asks for a new committed date, asks what changed. Keep the tone operational — you need these people cooperative for every step after this one.

One branch to check immediately: is this actually a date miss, or a quantity miss in disguise? A PO that ships complete but three weeks late and a PO that ships on time but 200 units short are sibling incidents with different playbooks — the short-ship version is covered in supplier short shipments. Confirm which one you have before the ladder starts climbing.

Step one, before any response: quantify your exposure

The instinct is to fire back at the supplier. The order of operations is the reverse: first work out what this actually costs, per SKU, because that arithmetic decides which responses you can afford.

For every SKU on the delayed PO:

Days of cover = on-hand units ÷ daily velocity

The misses that hurt are the ones where cover runs out before the replacement arrives — where you run out of stock before the new ship date lands. Worked example, all figures illustrative:

The 7-day gap on the maroon line means roughly 7 × 21 ≈ 150 units of demand (estimated) with nowhere to go — at an illustrative $19 retail, about $2,800 in estimated lost revenue if nothing changes. The charcoal line needs nothing but a calendar note: same supplier, same missed PO, two completely different incidents. The gap column is the whole triage — SKUs with zero gap get patience, SKUs with a positive gap get a plan, worked in gap-size order.

Building that table by hand per incident works. The standing version is the point, though: InventoryX computes per-SKU risk alerts from lead times and velocities you enter, so a cover figure about to break surfaces in the weekly digest — the miss becomes visible before the shelves are. It won't run the escalation for you, though; the ladder is yours.

The escalation ladder, mapped to the four-level model

Supplier escalation has a documented structure in procurement practice. Tacto's procurement glossary (March 30, 2026) defines it as 'a systematic procedure for resolving problems with suppliers through the step-by-step involvement of higher management levels,' and Qstrat's procurement guidance describes the same standard sequence: (1) operational problem-solving between the buyer and their supplier contact, (2) middle management on both sides, (3) executive management, (4) legal action or supplier replacement. Both are procurement-software vendors writing practice guides for larger buying teams — the apparatus they recommend alongside it (an escalation matrix, a communication protocol with defined channels and timelines, solution monitoring with milestones, documentation of every step) is enterprise formality, but the ladder maps cleanly onto a one-person operation. Both sources agree on the timing rule too: escalate after operational attempts fail. Premature escalation damages the relationship you're about to need.

Here's the merchant-sized version:

Level 1 (days 1–3). The hour-zero email already asked for the new date; now the operational follow-up: what's finished and packed today? A partial ship of the highest-gap SKUs narrows the exposure table while the rest finishes, at the cost of one extra freight conversation.

Level 2 (days 4–10). If the operational answers stall or the date slips again, move up a level on both sides — and bring numbers. The exposure table turns 'we're upset' into 'a 7-day gap costs roughly 150 units (estimated), so air-freighting 400 units for an illustrative $900 premium is the cheap option.' That sentence is why you did the arithmetic first, and the premium gets agreed in writing before anything ships.

Level 3 (day 10+). Owner-to-owner is a different conversation — not the shipment anymore but the pattern. This is where you ask for priority on the next run, remedies for this one, and, if the misses repeat, begin reallocating your volume.

Level 4. Legal action or supplier replacement is the model's final level, and for a small merchant the realistic version of 'replacement' is the strategic kind — a second source for the SKUs that keep failing. That's not a this-week project; it's the one waiting in the triage below.

The customer-facing decision: promise nothing you can't confirm

While the ladder climbs internally, the storefront has its own exposure. The rule: no restock promise you can't confirm. 'Back in two weeks' based on a supplier's verbal 'should be fine' is a promise you'll be apologizing for in an inbox full of order-status tickets.

• Pause ads on the affected SKUs. Spending to accelerate demand into a 7-day gap converts marketing budget into lost units — the gap column, again.
• Keep the listing honest. The product stays up. The copy says 'restocking' only once a date is confirmed in writing, and any back-in-stock notification fires when stock is received and counted, not when the supplier says it shipped.
• If the gap column is zero, change nothing. Visible churn on a SKU that self-resolves costs more than the quiet wait.

Triage: wait, partial ship, expedite, or substitute supplier

Four ways out of the gap, and the exposure table picks between them:

The wait option deserves its honest limitation: it's only free when the math says zero. For everything else, a partial ship of the top-gap SKUs is usually the cheapest move available inside two weeks, and an expedite is a purchase you make only when the numbers beat the premium.

Post-incident: the three entries that make it rarer

The incident isn't closed when the truck arrives. Three entries, same day:

1. The scorecard. However informally you track suppliers, on-time performance belongs in the record — one missed date is data, a repeating one is a pattern, and patterns are what supplier scorecards exist to catch. Log it while the dates are fresh; '22 days late in October' beats 'they were late that time.'
2. The clause. Most small merchants discover mid-incident that their PO says nothing about what happens when a date is missed: no remedy, no expedite-cost allocation, no cancel-for-cause trigger. That absence is the finding; the fix belongs in the next supplier contract.
3. The retro. Thirty minutes, once the dust settles, on one question: did your reorder point fire too late, or did the supplier fail inside a correct plan? If the planned lead time was a quote rather than a measurement, that's your half of the failure — measuring supplier lead time is the discipline that fixes it. If the plan was right and the supplier still missed, the ladder and the scorecard carry it. The half-hour review template is in the out-of-stock post-mortem.

If the supplier was also your only source, note that in the same sitting — a single-source SKU that just showed you its failure mode is the argument for qualifying a backup while things are calm, not during the next miss.

Common questions

What do I do when a supplier misses a ship date? First, make it a fact: a short email naming the missed date and asking for a new committed one. Second, quantify exposure — days of cover (on-hand ÷ velocity) for every affected SKU against the new date. Then work the ladder: operational requests in days 1–3, management involvement around days 4–10, executive only after operational attempts fail.

When should I escalate a supplier problem to management? Procurement practice guides describe a four-level sequence — operational, middle management, executive, legal or replacement — and agree escalation should follow failed operational attempts, because premature escalation damages the relationship. Practically: operational in days 1–3, management when dates slip or the channel stalls, executive when it repeats.

Should I pay to expedite a late shipment? Run the comparison first: gap days × daily velocity (your estimated lost units) against the expedite premium, agreed in writing before anything ships. If a 7-day gap costs roughly 150 units and air freight on the balance costs less than those units' margin, expedite is cheap. If every affected SKU has zero gap, expedite is theater.

How do I stop suppliers from missing ship dates? You reduce frequency and impact, not to zero: plan against measured lead times instead of quotes, track on-time performance on a scorecard, put real remedies in the contract, and keep a second source for the SKUs whose failure hurts most. Misses stay possible — the goal is that none of them find you with three days of cover.

Is a partial shipment worth accepting? Usually yes, when some lines are finished and others aren't: a partial ship of the highest-gap SKUs now narrows the exposure while the balance follows. Confirm in writing that the balance ships complete on its own committed date — otherwise you've traded one incident for two.

Next step

Close this incident, then build the standing version of the ladder while it's vivid: a one-page escalation matrix for your top supplier — named contacts, channels, and timelines for levels 1 through 3 — so the next miss starts climbing in minutes instead of in a mood. Then run the half-hour retro from the template linked above; the output is one primary cause and one process change, written down where the next reorder decision can see it. The paper trail this playbook depends on starts with the PO itself — the purchase order template shows the fields that make disputes arguable. If the delay pattern repeats, domestic vs overseas sourcing is the structural re-think worth a season. For catalogs where every order is a long-lead promise — furniture is the extreme case — furniture store inventory shows how MTO sellers absorb slippage. And plan the annual version before it happens: the Chinese New Year factory shutdown is the one delay with a published date.