How is a date-change request different from a delay notification?

A delay notification is the supplier informing you that an in-flight order is going to be late. The slip is happening regardless of your response, and your job is to confirm the new date and plan around it. A date-change request is the supplier asking permission to move the date on a PO they have already acknowledged. The slip has not happened yet, and you have leverage to refuse, push back, or negotiate. The response window and tone are different. Treating a date-change request as a notification (and absorbing the change reflexively) gives away the leverage. Treating a notification as a request (and trying to refuse a slip that is already operational) wastes goodwill on a fight you cannot win.

How long should I take to respond to a date-change request?

One business day is the right window. The supplier's request format creates pressure to reply quickly, but a reflexive same-day approval gives away the leverage the request format is designed to hand you. Take the 24 hours to pull the production schedule, check the criticality of the affected build, and review the supplier's history of similar requests. Then draft the reply with a clear position. Replying inside one business day signals engagement on the request. Sitting on it past two days reads as a buyer who is not engaged, and the supplier may treat the silence as a tacit approval and start producing against the new date.

When should I refuse a date-change request outright?

When the proposed shift puts a critical-path build or a customer-facing delivery at risk and the supplier has not offered a recovery path. The refusal should be specific (the build affected, the date you actually need) and should give the supplier two real options to get back to the original date: air-freight upgrade with the freight cost on a defensible split, or partial ship of any ready quantity by the original date with the balance on the proposed date. Outright refusal without offering recovery options usually escalates to the account manager and resolves there, but the conversation is harder. Offering options keeps the conversation collaborative and usually surfaces a workable path.

Should I treat all date-change requests as equally serious?

No. The criticality of the affected build and the supplier's history are the two variables that matter. A two-day shift on a non-critical part from a supplier with a clean record is a routine approval with a clean confirmation reply. A two-week shift on a critical part from a supplier on their third request in a quarter is a sourcing-review-level conversation that needs structural action, not just a per-PO answer. The triage is most of the work. Once you know which shape the request takes, the reply almost writes itself.

How do I document the date change for the audit trail?

Keep the original PO acknowledgment, the supplier's change-request email, your reply (with the final outcome), and the ERP update timestamp all attached to the PO record. The thread should show the original date, the requested date, the final date, and the rationale for the outcome. Update the ERP the same day the change settles, since a date change that lives only on email and never propagates to the ERP creates a planning gap and a three-way-match issue on the eventual receipt. The audit trail matters when finance asks why a build slipped a week later, when the supplier asks for a price adjustment that references the date change, and when the next sourcing review on the supplier needs a count of date-change requests across the quarter.

How is a date-change request different from a delay notification?

A delay notification is the supplier informing you that an in-flight order is going to be late. The slip is happening regardless of your response, and your job is to confirm the new date and plan around it. A date-change request is the supplier asking permission to move the date on a PO they have already acknowledged. The slip has not happened yet, and you have leverage to refuse, push back, or negotiate. The response window and tone are different. Treating a date-change request as a notification (and absorbing the change reflexively) gives away the leverage. Treating a notification as a request (and trying to refuse a slip that is already operational) wastes goodwill on a fight you cannot win.

How long should I take to respond to a date-change request?

One business day is the right window. The supplier's request format creates pressure to reply quickly, but a reflexive same-day approval gives away the leverage the request format is designed to hand you. Take the 24 hours to pull the production schedule, check the criticality of the affected build, and review the supplier's history of similar requests. Then draft the reply with a clear position. Replying inside one business day signals engagement on the request. Sitting on it past two days reads as a buyer who is not engaged, and the supplier may treat the silence as a tacit approval and start producing against the new date.

When should I refuse a date-change request outright?

When the proposed shift puts a critical-path build or a customer-facing delivery at risk and the supplier has not offered a recovery path. The refusal should be specific (the build affected, the date you actually need) and should give the supplier two real options to get back to the original date: air-freight upgrade with the freight cost on a defensible split, or partial ship of any ready quantity by the original date with the balance on the proposed date. Outright refusal without offering recovery options usually escalates to the account manager and resolves there, but the conversation is harder. Offering options keeps the conversation collaborative and usually surfaces a workable path.

Should I treat all date-change requests as equally serious?

No. The criticality of the affected build and the supplier's history are the two variables that matter. A two-day shift on a non-critical part from a supplier with a clean record is a routine approval with a clean confirmation reply. A two-week shift on a critical part from a supplier on their third request in a quarter is a sourcing-review-level conversation that needs structural action, not just a per-PO answer. The triage is most of the work. Once you know which shape the request takes, the reply almost writes itself.

How do I document the date change for the audit trail?

Keep the original PO acknowledgment, the supplier's change-request email, your reply (with the final outcome), and the ERP update timestamp all attached to the PO record. The thread should show the original date, the requested date, the final date, and the rationale for the outcome. Update the ERP the same day the change settles, since a date change that lives only on email and never propagates to the ERP creates a planning gap and a three-way-match issue on the eventual receipt. The audit trail matters when finance asks why a build slipped a week later, when the supplier asks for a price adjustment that references the date change, and when the next sourcing review on the supplier needs a count of date-change requests across the quarter.

PLAYBOOK

Supplier Requesting a Date Change on a Confirmed PO? Here's What to Do

“Email from the supplier just landed: "Requesting to push PO 5817 from May 12 to May 26." They acknowledged the original two weeks ago. Approve, push back, or negotiate?”

A supplier just asked you to move the date on a PO they already acknowledged. The original commitment is in writing, the date is in your ERP, and production planning is built around the original. The new request is not a delay notification (which says the slip is happening regardless) and it is not a date mismatch on the original acknowledgment (which would have been resolved when the PO was first confirmed). It is the supplier asking permission to change a date they already committed to. The right response is more deliberate than either of those situations because you still have leverage: refuse, push back, negotiate. The wrong response (a quick "ok" because the new date looks workable) gives away that leverage permanently and trains the supplier that confirmed dates are negotiable on demand. Most date-change requests resolve cleanly when the buyer takes the request seriously, runs the diagnostic, and replies with a real position rather than a default approval.

What this looks like

It is 11:48 Monday morning. An email from your contact at Coastal Casting just landed. The body reads: "Hi, requesting to push the ship date on PO 5817 from May 12 to May 26. We are working through a foundry capacity issue and the two-week shift would let us complete the lot without expediting another customer's order. Please confirm if this works on your side." PO 5817 is for 180 cast iron housings, originally acknowledged on the 8th of last month with the May 12 ship date. The two-week shift puts the parts at your dock the first week of June instead of the third week of May. The supplier is asking, not telling.

A date-change request can take three different shapes and the response differs sharply for each. The clean case is a request like the one above: a specific reason, a specific new date, a polite acknowledgment that the original is on their commitment and they are asking permission to move it. The middle case is a vague request: "We may need to push the date a couple of weeks, please advise." This is a half-formed request that should not be acted on until the supplier names a specific new date. The third case is a request that is technically a notification dressed in request language: "We will be shipping on May 26 instead of May 12, please update your ERP." That phrasing is the supplier reframing a unilateral move as a buyer-side update, and it deserves the response of a delay notification, not a request.

Before you reply, run the diagnostic. Pull the original PO acknowledgment and confirm the exact original date. Check the production schedule for the build that consumes the housings and confirm whether the two-week shift is absorbable, painful but workable, or unacceptable. Check the supplier's history of date-change requests on similar parts (a pattern of requests is a sourcing conversation, not a per-PO answer). Look at the stated reason and decide whether you believe it. Most date-change requests rooted in capacity are honest because the supplier is admitting a planning miss. Requests rooted in commercial reasons (better-paying customer, faster-paying customer) are usually framed differently and deserve harder push-back.

Why it matters

A confirmed PO with an acknowledged date is one of the few hard commitments in the supplier-buyer relationship. Treating the change request as a routine approval erodes that commitment for every future PO with the same supplier. Buyers who approve the third date-change request from the same supplier without push-back have signaled that confirmed dates are negotiable on demand, which means the supplier's internal planning will treat your dates as flexible by default. The next time you need a hard date (a customer-facing build, a critical-path part, an exit from a problem situation), the supplier's behavior is set against you rather than for you.

On the production side, the math depends on the criticality of the build. A two-week shift on a part feeding a $10,000-per-hour assembly line is real exposure: $80,000 per day of line-down cost if the new date forces the build to slip and there is no recovery option, plus $3,000 to $40,000 in air-freight expedite cost if you have to recover the original date by upgrading the freight. Even on non-critical parts, two weeks of unplanned slack pulls inventory dollars out of the working capital cycle and shifts your backlog of open POs further out, which makes the next planning cycle harder.

The audit trail consequence is the one buyers most often miss. A confirmed PO with two different dates (the original on the PO and the new one negotiated by email) has to be reconciled in the ERP, the supplier's system, and your team's shared status views. If the date changes via a "yes please go ahead" reply that nobody propagates to the ERP, production planning works against the original date, AP's three-way match runs against the original promise, and the receipt that lands two weeks later looks late on paper even though the supplier delivered to the renegotiated commitment. Push the new date into the ERP the same day you accept the change, and keep the email thread that confirms the change attached to the PO record.

What to do, step by step

Step 1: Take 24 hours to run the diagnostic. The supplier's request creates pressure to reply quickly, but a reflexive approval gives away the leverage that the request format is designed to hand you. Pull the production schedule, confirm the criticality of the affected build, check the supplier's history of date-change requests on similar parts, and decide whether the request is workable, painful but absorbable, or unacceptable. Then draft the reply.

Step 2: If the request is workable and the supplier has a clean record, reply with a clear approval and the conditions that protect you on the next request. The approval should also confirm any commercial implications (freight terms, payment terms) so the change does not silently include other concessions.

Approval template: "[SUPPLIER NAME], approving the date change on PO [NUMBER] from [ORIGINAL DATE] to [PROPOSED DATE]. Confirming the [REASON] is a one-time situation, not a forward indicator on this part. Original PO terms (price, freight, payment) remain unchanged and are not renegotiated by the date change. Updating our ERP today and treating [PROPOSED DATE] as the new firm commitment. Please send the advance ship notice the day the parts leave your facility. [YOUR NAME]"

Step 3: If the request is workable but the supplier has a pattern (third request in a quarter, repeated requests on similar parts), reply with a conditional approval and a structural ask. The structural ask names the pattern and proposes a sourcing or commercial response (lead time review, dual-sourcing conversation, price discussion).

Conditional approval template: "[SUPPLIER NAME], approving the date change on PO [NUMBER] from [ORIGINAL DATE] to [PROPOSED DATE]. Flagging that this is the [Nth] date-change request from your team in the last quarter on similar parts. Recommend we put time on the calendar this week to discuss lead time on the [PART CATEGORY] family and whether the current commitment cycle is the right one going forward. Original PO terms remain unchanged. Please send the advance ship notice the day the parts leave your facility. [YOUR NAME]"

Step 4: If the request is not workable, push back with a specific refusal and offer recovery options that get the supplier to the original date. The push-back is direct but not confrontational. Name the production impact, refuse the proposed date, and give the supplier two real paths back to the original.

Push-back template: "[SUPPLIER NAME], thanks for flagging the foundry situation on PO [NUMBER]. The proposed shift from [ORIGINAL DATE] to [PROPOSED DATE] is not workable on our side because [BUILD/CUSTOMER] is on the original cycle. Two options to discuss: (1) air-freight upgrade against the original date with the freight cost shared on a basis we can defend, (2) partial ship of any quantity ready by the original date with the balance on the proposed [PROPOSED DATE]. Please confirm which is workable by [TIME, DAY]. If neither is workable, escalating to the account manager because the original date is a hard commitment on our side. [YOUR NAME]"

Step 5: Once the date is settled (whether approved, conditionally approved, renegotiated, or refused), update the ERP the same day, notify the planner of the final number, and keep the email thread that confirms the outcome attached to the PO record. The audit trail showing original date, requested date, final date, and the rationale matters when the same conversation comes up on the next PO.

Internal update template: "[PLANNER NAME], date change settled on PO [NUMBER] for [PART DESCRIPTION]. Final ship date is [DATE] (original [ORIGINAL DATE], supplier requested [PROPOSED DATE]). [APPROVAL/CONDITIONAL/REFUSAL/RENEGOTIATION] outcome. Updating ERP today. Production should plan around [DATE] for the [BUILD]. Pattern flag on this supplier if applicable. [YOUR NAME]"

How PO-Relay handles this

When a supplier email lands requesting a date change on a confirmed PO, PO-Relay's Email Intelligence reads the message, classifies it as a date-change request (distinct from a date-mismatch acknowledgment, a delay notification, or an open question), extracts the proposed new date and the stated reason, and tags the email against the right PO. The task on the Parts Dashboard is flagged as "date change requested" with the original date, the proposed date, the gap in business days, and the supplier's prior history of similar requests visible on the same view.

The chat assistant can pull the supplier's date-change request history on demand if you want to ask "how many date-change requests has [SUPPLIER NAME] sent in the last quarter?" before drafting the reply. The pattern view is the difference between treating each request as a one-time situation and recognizing the structural conversation that needs to happen with a repeat-requester supplier.

Auto Follow-Ups drafts the approval, conditional approval, push-back, and internal-update emails pre-loaded with the PO number, original date, proposed date, and the structural context (criticality of the affected build, supplier history). The four templates cover the common outcomes so you select the one that fits the diagnostic and edit from there. You review every draft and send from your own inbox. PO-Relay never sends email and never writes to your ERP.

The Morning Report resurfaces unresolved date-change requests the next day if you have not replied within 24 hours, because the right response window for a request like this is one business day. Once the change is settled, the assistant updates the task with the final date and the loop continues under normal monitoring. The audit trail of original date, requested date, final date, and the rationale stays attached to the task for the supplier-quality and sourcing review later.

See it in action

Get started Learn more

Common mistakes to avoid

Approving the change reflexively because the new date looks workable. The supplier's request format is designed to invite a quick approval. A reflexive yes gives away leverage permanently and trains the supplier that confirmed dates are negotiable on demand. Take 24 hours to run the diagnostic, even when the answer is going to be approval. The pause itself signals that confirmed dates are taken seriously on your side.
Treating a notification dressed in request language as a real request. "We will be shipping on May 26 instead of May 12, please update your ERP" is not a request, it is a unilateral move. Respond with the delay-notification playbook, not the date-change-request one. The framing matters because the response trains the supplier on whether they can convert future date moves into buyer-side updates.
Approving the change without naming the conditions that protect you. A clean approval reply confirms the new date, locks in that the original PO terms (price, freight, payment) are unchanged by the date change, and treats the new date as a firm commitment. Approvals that do not name those conditions leave the door open for the supplier to stack additional concessions on the same change request.
Forgetting to flag the pattern when a supplier requests a third change in a quarter. Per-PO approval on the third request resets the conversation and signals that the cycle is acceptable. The right move at the threshold is a structural conversation about lead time, capacity reliability, and whether the supplier is a viable single source on this part. Document the requests so the conversation is on data rather than impressions.

Keep reading

GlossaryPO Acknowledgment GlossaryLead Time FeatureEmail Intelligence FeatureAuto Follow-Ups FeatureChat Assistant