How to Handle a Supplier Delay Notification
“Supplier just emailed: "Heads-up, PO 4108 is slipping a week, raw material issue." At least they told me. Now what?”
The supplier emailed you proactively. They flagged that an in-flight order is going to be late, gave you some kind of reason (raw material, capacity, weather, a process issue on their floor), and offered a new estimated date. This is the easy version of a late delivery, because the supplier is still being responsive and you have runway to plan around the slip rather than discovering it on the day the parts were supposed to land. The opportunity in this situation is the response. A clean reply that confirms the new date, asks the right follow-up questions, and locks the supplier into the new commitment turns a notification into a manageable plan. A vague "ok, thanks" lets the slip drift, hides the new date from production planning until it is too late to act, and trains the supplier that you absorb late notices without pushing back, which makes the next slip larger.
What this looks like
It is 2:14 Tuesday afternoon. An email lands from your contact at the supplier on PO 4108, 480 powder-coated brackets for the next assembly cycle, originally promised for the 17th. The body of the email reads: "Heads-up, we are running short on the raw material for this run and the earliest we can ship is the 24th. Will confirm a firm ship date by Friday. Apologies for the slip." That is a real notification, sent five business days before the original promise date, with a stated reason and a window for the next confirmation. The supplier is doing the right thing on their side. Your move is what determines whether the slip stays at one week or grows.
A supplier delay notification can come in three different shapes and the response is different for each. The cleanest case is a specific notification with a stated reason, a proposed new date, and a proactive timeline (like the email above). The supplier is on the front foot, they have a recovery plan, and your job is to confirm and plan around it. The middle case is a vague heads-up: "We may be running a bit late on PO 4108, will let you know." This is a partial notification that needs you to push for specifics before it can be planned around. The third case is a notification that arrives the day of or after the original promise date, which is technically a notification but functionally a missed delivery, and it should be handled with the late-delivery playbook rather than the proactive-notification one.
Before you reply, run the diagnostic. Pull the original PO acknowledgment and confirm the original promise date. Check the production schedule for the build that consumes the brackets and confirm whether a one-week slip is absorbable or whether it puts a customer-facing delivery at risk. Check whether the supplier has notified on the same part before (a pattern of delay notifications is a sourcing conversation, not a routine response). Look at the supplier's reason and decide whether you believe it. A raw-material reason is verifiable on industry indices and on the supplier's purchase records if they will share. A capacity reason is harder to verify but usually more honest because the supplier is conceding a planning miss. The reason shapes the conversation about how to recover.
Why it matters
A delay notification handled cleanly is the cheapest version of a delivery problem to manage. The supplier is being responsive, you have runway, and the cost picture is mostly the production cascade rather than the relationship cost. On a $10,000-per-hour assembly line, a one-week slip absorbed cleanly with internal communication 24 hours after the notification lands costs you the planning time only. The same one-week slip that the buyer fails to confirm and propagate internally costs the line-down hours when production discovers the slip the day before the build, plus the air-freight expedite premium of $3,000 to $40,000 to recover what could have been recovered for free with a phone call.
The supplier-relationship math runs the other direction from the late-delivery situation. A buyer who responds to a delay notification with a clean confirmation, a single specific question, and a written acknowledgment of the new date trains the supplier that proactive notifications are rewarded and not punished. A buyer who responds to every delay notification with frustration trains the supplier to delay the notification next time, which means you discover the slip later, with less runway, and at higher cost. The supplier behavior you are reinforcing in this conversation is exactly the one you want repeated on the next slip.
There is also an internal communication cost that buyers regularly miss. The delay notification is news that production planning, the line lead, and possibly your manager all need within the same business day. If the news sits in your inbox until the morning of the original promise date, you have spent the runway the supplier gave you on inbox triage. Forward the notification (with the new date and your read on the recovery plan) to the planner the same day it lands, even if the conversation with the supplier is still open on the specifics.
What to do, step by step
Step 1: Reply to the supplier the same business day with a confirmation, a specific question, and a written acknowledgment of the new date. The reply should be short and steady. Not warm, not angry. Confirm receipt, lock in the new date as the working commitment, and ask the one specific question that turns the rough notification into a planning-grade one.
Initial reply template: "[SUPPLIER NAME], thanks for the heads-up on PO [NUMBER] for [PART DESCRIPTION]. Confirming the new ship date is [PROPOSED DATE], shifted from the original [ORIGINAL DATE] due to [REASON]. Three asks to firm this up: (1) please confirm a firm ship date by [PROPOSED CONFIRMATION DATE] as you indicated, (2) please confirm whether the freight terms remain as PO'd or whether the new ship requires a freight change, and (3) if the slip is a single-event issue versus a pattern on this part, that helps us plan future buys. We can absorb the [X] day shift on the current build but please flag immediately if the date moves further. [YOUR NAME]"
Step 2: If the impact is workable, communicate internally the same day with the new date. The planner needs to know the slip exists, the new date is locked (pending firm confirmation), and the production schedule needs to absorb the change. Two sentences is enough.
Internal update template: "[PLANNER NAME], delay notification on PO [NUMBER] for [PART DESCRIPTION]. Supplier flagged a slip from [ORIGINAL DATE] to [PROPOSED DATE] (raw-material issue on their side). Working a firm confirmation by [PROPOSED CONFIRMATION DATE]. The current build can absorb the shift; the [DOWNSTREAM BUILD] runs on the original cycle and needs the parts by [DATE]. I will flag if the date moves further. [YOUR NAME]"
Step 3: If the impact is not workable, push back the same day. The supplier flagging a slip does not obligate you to absorb it, especially when the slip lands on a critical-path build. Your push-back should be specific (the build affected, the date you actually need) and should offer the supplier real recovery options.
Push-back template: "[SUPPLIER NAME], thanks for the heads-up on PO [NUMBER]. The proposed [PROPOSED DATE] slip puts the [BUILD/CUSTOMER] at risk and we cannot absorb it without a recovery plan. Two options to discuss: (1) air-freight upgrade against your current ship plan, (2) partial ship of any quantity ready by the original [ORIGINAL DATE] with the balance on the proposed [PROPOSED DATE]. Please confirm which is workable and the freight cost difference by [TIME, DAY]. [YOUR NAME]"
Step 4: When the supplier confirms the firm date (after their stated confirmation window), update the ERP, notify the planner of the final number, and close the loop. If the firm date shifts further from the original notification, treat the new date as a second slip and run the diagnostic again. The pattern of a notified slip that grows is a real signal about the supplier's control of the order.
Confirmation acknowledgment template: "[SUPPLIER NAME], confirming receipt of the firm ship date of [FIRM DATE] on PO [NUMBER]. Updating our ERP today. Please send the advance ship notice the day the parts leave your facility. Thanks for staying ahead of this. [YOUR NAME]"
Step 5: If the same supplier sends multiple delay notifications across consecutive POs (three notifications in a quarter is a useful threshold), escalate the conversation to a sourcing review rather than a per-PO complaint. The pattern matters more than any single instance, and the right move is a structured conversation about lead time, raw material reliability, and whether the supplier is a viable single source on this part going forward.
How PO-Relay handles this
When a supplier email lands flagging a delay, PO-Relay's Email Intelligence reads the message, classifies it as a delay notification, extracts the proposed new date and the stated reason, and tags the email against the right PO. The task on the Parts Dashboard updates from the original promise date to the proposed new date with the slip flagged for confirmation. You see the slip the moment you open PO-Relay rather than discovering it when the planner walks over Friday morning.
Auto Follow-Ups drafts the reply pre-loaded with the PO number, the part description, the original date, the proposed new date, the stated reason, and structured asks (firm confirmation deadline, freight terms, pattern check). The draft also generates the internal update for the planner with the same data structured for the production conversation. You review every draft and send from your own inbox. PO-Relay never sends email and never writes to your ERP.
The Parts Dashboard shows the slip propagating to the downstream tasks if the affected PO has dependencies, so you see whether the new date puts a customer-facing build at risk before you reply. The chat assistant can pull the supplier's notification history on demand if you want to ask "how many delay notifications has [SUPPLIER NAME] sent in the last quarter?" before deciding whether to escalate the conversation to a sourcing review.
The Morning Report resurfaces the delay notification the next day if the firm confirmation has not landed inside the supplier's stated window. The afternoon recap captures the firm-date confirmation when it arrives so the audit trail of the slip (when notified, when proposed, when confirmed firm) stays intact for the supplier-quality review later.
See it in action
Common mistakes to avoid
- Replying with "ok, thanks" and nothing else. The vague acknowledgment lets the slip drift, gives the supplier no signal that you are tracking the new commitment, and trains them that proactive notifications get absorbed without scrutiny. The right reply confirms the new date in writing, asks one specific question that turns the notification into a planning-grade commitment, and sets the deadline for the firm confirmation. Two paragraphs of work is enough.
- Punishing the supplier for the proactive notification. A buyer who responds to a delay notification with frustration teaches the supplier to delay the next notification until it is too late to act. The supplier behavior you are reinforcing on this slip is the one you want repeated on the next slip. Save the frustration for the supplier who goes silent, not the one who flagged the issue with runway.
- Sitting on the notification without forwarding to production. The slip is news that the planner needs the same day, even before the firm date is confirmed. If the notification sits in your inbox until the morning of the original promise date, you have spent the runway the supplier gave you on triage. A two-sentence forward to the planner the same day costs nothing and prevents the line-down conversation later.
- Treating the third notification from the same supplier as a routine fourth response. If a supplier has notified on the same part or in the same quarter multiple times, the pattern matters more than any single instance. The right move is a structured sourcing conversation about lead time and raw-material reliability, not another clean confirmation that resets the cycle. Pull the notification history before replying to the third one.