How quickly do I have to push back on a confirmed date that's wrong?

Inside 24 to 48 hours of the acknowledgment landing in your inbox. The supplier interprets longer silence as acceptance and locks the new date into their schedule. After that, the next email asking for the original date reads as a buyer who changed their mind, not a buyer rejecting the original move. Even if the reply is just a clean acceptance with a written commitment to the new date, send it inside that window so the date is settled in writing instead of drifting by default. Same window applies whether the gap is two days or two weeks.

When is it worth pushing back on a small date slip?

Match the push-back to the size of the gap and the criticality of the build. A one or two day slip on a part with flex on the production calendar usually is not worth pushing back on, since the friction cost outweighs the recovery. A slip of a week or more, or any slip on a part feeding a critical-path build, deserves a same-day push-back. The framing on small slips is goodwill capital. Suppliers who absorb three small clean acceptances tend to be more responsive on the next real escalation, while suppliers who get pushed back on every two-day move start padding their acknowledgments by a week to compensate. Pick your battles.

What if the supplier confirms the price changes too?

Treat that as a separate situation, not a routine acknowledgment. A confirmed price that does not match the PO is a unilateral price change, not a date negotiation, and it usually requires escalation. Reply same day and split the two questions: accept or push back on the date, and separately confirm whether the price change is supported by a contractual clause (raw material indexing, a previously communicated increase, an Incoterms change). If the price change is not supported, push back on it specifically and reference the PO terms. Mixing the date and price negotiations into one thread tends to produce a confused outcome where neither resolves cleanly.

Should I update the ERP with the new date before the supplier confirms it in writing?

Not until the date is settled in writing on the email thread. Updating the ERP based on a verbal or implied date creates a record that does not match the supplier's system, and if the date moves again you end up with three different numbers. Once the supplier replies with a written confirmation of the final date (whether the original or a renegotiated number), update the ERP the same day. The receipt against that date will then match the three-way match and AP processes cleanly. Keep the email thread that confirms the final date attached to the PO record so the audit trail is intact.

How do I escalate a date dispute without burning the supplier?

Three rules. Push back specifically on the date, not the supplier's effort or competence. Name the production impact and offer recovery options (overtime, expedite, partial ship) so the conversation is collaborative rather than confrontational. Copy the original contact on any escalation to the account manager so you are not bypassing them. The relationship damage on date disputes comes from buyers who treat every slip as an emergency or who escalate without giving the day-to-day contact a chance to fix it. Push back in writing, give a deadline, and only escalate after the deadline passes without a workable answer. Most date mismatches resolve at the day-to-day-contact level when the push-back is specific and prompt.

How quickly do I have to push back on a confirmed date that's wrong?

Inside 24 to 48 hours of the acknowledgment landing in your inbox. The supplier interprets longer silence as acceptance and locks the new date into their schedule. After that, the next email asking for the original date reads as a buyer who changed their mind, not a buyer rejecting the original move. Even if the reply is just a clean acceptance with a written commitment to the new date, send it inside that window so the date is settled in writing instead of drifting by default. Same window applies whether the gap is two days or two weeks.

When is it worth pushing back on a small date slip?

Match the push-back to the size of the gap and the criticality of the build. A one or two day slip on a part with flex on the production calendar usually is not worth pushing back on, since the friction cost outweighs the recovery. A slip of a week or more, or any slip on a part feeding a critical-path build, deserves a same-day push-back. The framing on small slips is goodwill capital. Suppliers who absorb three small clean acceptances tend to be more responsive on the next real escalation, while suppliers who get pushed back on every two-day move start padding their acknowledgments by a week to compensate. Pick your battles.

What if the supplier confirms the price changes too?

Treat that as a separate situation, not a routine acknowledgment. A confirmed price that does not match the PO is a unilateral price change, not a date negotiation, and it usually requires escalation. Reply same day and split the two questions: accept or push back on the date, and separately confirm whether the price change is supported by a contractual clause (raw material indexing, a previously communicated increase, an Incoterms change). If the price change is not supported, push back on it specifically and reference the PO terms. Mixing the date and price negotiations into one thread tends to produce a confused outcome where neither resolves cleanly.

Should I update the ERP with the new date before the supplier confirms it in writing?

Not until the date is settled in writing on the email thread. Updating the ERP based on a verbal or implied date creates a record that does not match the supplier's system, and if the date moves again you end up with three different numbers. Once the supplier replies with a written confirmation of the final date (whether the original or a renegotiated number), update the ERP the same day. The receipt against that date will then match the three-way match and AP processes cleanly. Keep the email thread that confirms the final date attached to the PO record so the audit trail is intact.

How do I escalate a date dispute without burning the supplier?

Three rules. Push back specifically on the date, not the supplier's effort or competence. Name the production impact and offer recovery options (overtime, expedite, partial ship) so the conversation is collaborative rather than confrontational. Copy the original contact on any escalation to the account manager so you are not bypassing them. The relationship damage on date disputes comes from buyers who treat every slip as an emergency or who escalate without giving the day-to-day contact a chance to fix it. Push back in writing, give a deadline, and only escalate after the deadline passes without a workable answer. Most date mismatches resolve at the day-to-day-contact level when the push-back is specific and prompt.

PLAYBOOK

Supplier Confirmed a Different Date Than Your PO? Here's What to Do

“They acknowledged PO 3380 but moved the date out two weeks. Production planning is built around the original. Do I push back or absorb?”

Your supplier acknowledged the PO. The acknowledgment landed on time and reads professional. The only problem is the date they confirmed is not the date you asked for. Maybe two days off, maybe two weeks. The PO is now technically acknowledged in the ERP, but the date on their record and the date on yours are different, and unless you reconcile this in the next 24 hours, production planning is going to build around a date that no longer exists. A date mismatch on an acknowledgment is one of the most common situations in production buying, and the easiest to misread. The supplier is not refusing the order. They are negotiating the terms by acknowledging on their own date and waiting to see whether you will push back. Most buyers do not push back, the date silently becomes the new normal, and the production schedule absorbs the slip without anyone deciding to.

What this looks like

It is 11:14 Thursday morning. The acknowledgment for PO 3380 just landed in your inbox. You placed the PO three weeks ago for 200 cast aluminum manifolds, requested delivery the 28th to feed the next pump build. The supplier's acknowledgment confirms the part number, the quantity, and the price. The promised ship date reads the 5th of next month, eight business days past your requested date. No explanation in the body of the email, no note about why the date moved. Just a clean acknowledgment with a different number on it.

A date-mismatch acknowledgment can mean four different things and the supplier rarely tells you which one in the email itself. They may have a real capacity constraint and the new date is the earliest they can actually ship, in which case pushing back will not move it. They may have padded the date by a week as standard practice, in which case asking for the original date will produce it without much friction. They may have read the PO wrong and committed against the wrong cycle, in which case a quick correction fixes it. Or they may be probing to see whether you noticed, because the new date is more comfortable for their schedule and they will hold it if nobody objects. Each one calls for a different response and the cost of getting it wrong is paid by your production schedule.

Before you draft the reply, run the diagnostic. Pull the original PO and confirm the requested date you sent (the difference may be smaller than your ERP shows, since some ERPs default to a calculated date that is not the same as the date you negotiated). Check the supplier's last lead time on the same part to see whether the new date is normal for them or a real slip. Check whether your production planner has any flex in the new date or whether the original is hard. Then look at the acknowledgment language. If the supplier wrote "shipping the 5th" with no commentary, that is a probe. If they wrote "due to material lead time, the earliest we can ship is the 5th," that is a real capacity claim. The wording shapes the response.

Why it matters

A date mismatch that goes unchallenged becomes the new agreement. If you do not push back inside 24 to 48 hours of the acknowledgment, the supplier reasonably interprets your silence as acceptance and locks the new date into their schedule. The next time their account manager reviews the relationship, your file shows a clean record of acknowledgments on dates of their choosing, and the next quote you ask for builds on the longer cycle. The window to push back is short and it does not reopen, so the cost of waiting is not just this PO. It is the next ten POs with the same supplier.

On the production side, the math depends on how tight the original date was. An eight-day slip on a part feeding a $10,000-per-hour assembly line is a real schedule conversation, and the longer you wait to reconcile the date, the fewer recovery options you have. If you push back the same day and the supplier agrees to the original date, the production planner never has to hear about it. If you wait a week and the supplier holds the new date, you are now telling production about a slip that has already cost a week of recovery time, and any expedite or air-freight upgrade gets quoted at premium because the runway is gone.

There is a documentation cost too. A PO with two different dates on it (the requested date in your ERP, the confirmed date in the supplier's acknowledgment) breaks the audit trail in subtle ways. AP's three-way match runs against whatever date is in the ERP. If receiving lands on the supplier's confirmed date and the ERP still shows the requested date, the receipt looks late on paper even though the supplier delivered to their commitment. Finance asks why on every late receipt. Reconcile the date in writing and update the ERP the same day, or you spend the next month explaining a discrepancy that should have been a five-minute correction.

What to do, step by step

Step 1: Reconcile the diagnostic before you draft the reply. Confirm the original requested date from the PO, the date in the acknowledgment, and the gap in business days. Check the supplier's last lead time on similar parts. Check production planning's flex on the new date. The answer to the next email depends on whether you have room to absorb the slip or whether you need the original date.

Step 2: If the new date is workable, accept in writing immediately and update the ERP. Do not let the date sit unconfirmed in your inbox for a week. A clean acceptance also locks the supplier in: once they have your written acceptance of the new date, the next slip is on them.

Acceptance template: "[SUPPLIER NAME], confirming receipt of acknowledgment on PO [NUMBER] for [PART DESCRIPTION]. Noting the ship date moved from [REQUESTED DATE] to [CONFIRMED DATE], an [X] business day shift. We can absorb this on the current build schedule. Please treat the [CONFIRMED DATE] as a firm commitment and send the advance ship notice the day the parts leave your facility. Updating our ERP to reflect the new date today. [YOUR NAME]"

Step 3: If the new date is not workable, push back the same day with specifics, not frustration. The push-back email names the original date, asks specifically what is driving the slip, and offers two paths: hit the original date, or expedite at the supplier's cost if the slip is on their end.

Push-back template: "[SUPPLIER NAME], thanks for the acknowledgment on PO [NUMBER]. The confirmed ship date of [CONFIRMED DATE] is [X] business days past our requested [REQUESTED DATE], which is on the production critical path for the [BUILD/CUSTOMER]. Please confirm what is driving the change. If this is a capacity constraint, we need an option to recover (overtime, raw-material expediting, or partial ship of the ready quantity by the original date). If the change is on our side, please confirm what we can do to bring the date back. Please respond by [TIME, DAY]. [YOUR NAME]"

Step 4: If the supplier holds the new date and the slip is real, escalate to the account manager once and once only. Day three with no movement on the date is the trigger most teams use. Copy your original contact. State the facts plainly. Give the account manager a finite ask (recover the original date, ship a partial early, or share the production cost of the slip via expedite) rather than a vague complaint.

Account-manager escalation template: "[ACCOUNT MANAGER NAME], following up on PO [NUMBER] for [PART DESCRIPTION]. We requested ship by [REQUESTED DATE] and the acknowledgment confirmed [CONFIRMED DATE], an [X] day slip. I asked [SUPPLIER CONTACT] on [DATE] for either the original date or a recovery option and have not received a workable path. The original date is on our production critical path for [BUILD/CUSTOMER]. Please confirm by end of business today either the original ship date, a partial ship of the ready quantity, or a shared-cost expedite that closes the gap. Copying [SUPPLIER CONTACT] for visibility. [YOUR NAME]"

Step 5: Once the date is settled (whether the original or a renegotiated number), update the ERP, notify the planner, and move on. Two sentences to the planner closes the internal loop and stops the date from drifting between inboxes.

Internal update template: "[PLANNER NAME], date confirmation on PO [NUMBER] for [PART DESCRIPTION]. Final ship date is [DATE] (originally requested [REQUESTED DATE]). Updating ERP today. Production should plan around [DATE] for the [BUILD]. I will flag the moment anything moves before then. [YOUR NAME]"

How PO-Relay handles this

When an acknowledgment lands, PO-Relay's Email Intelligence reads the message, extracts the confirmed ship date, and compares it against the requested date on the PO. If the dates match, the loop is closed and the task advances to fulfillment monitoring. If the dates differ, the loop is flagged as "date mismatch" with the gap in business days surfaced on the task and the original acknowledgment email attached for context.

The Parts Dashboard shows date-mismatch flags sorted to the top by urgency, so you see the new date the moment you open PO-Relay rather than discovering it on a Monday morning when the acknowledgment has been sitting in the inbox for four days. The downstream impact on critical-path builds is visible on the same view, so you can see whether the slip lands on a build with flex or a build without before drafting the reply.

Auto Follow-Ups drafts the reply pre-loaded with the PO number, the part description, the requested date, the confirmed date, the gap in business days, and structured options for the supplier (accept, push back, request a recovery path). The acceptance draft and the push-back draft are different templates with different escalation language. You review every draft, edit anything that needs adjusting, and send from your own inbox. PO-Relay never sends email and never writes to your ERP.

The Morning Report resurfaces unresolved date mismatches the next morning, so a busy afternoon does not bury the task. Once you settle the date with the supplier, the task advances and the loop continues under normal monitoring. The chat assistant can also pull the date-mismatch detail on demand if the planner walks up asking which POs have moved this week.

See it in action

Get started Learn more

Common mistakes to avoid

Letting the new date sit silently as acceptance. If you do not push back inside 24 to 48 hours, the supplier reasonably interprets silence as agreement and locks the date into their schedule. The window to negotiate is short and it does not reopen. Reply the same day, even if the reply is just a clean acceptance, so the supplier knows the new date is closed in writing rather than absorbed by default.
Treating every mismatch as a fight. Some date moves are routine (a one or two day shift on a part the supplier produces in batches) and pushing back hard creates friction for nothing. Match the response to the size of the gap and the criticality of the build. A two-day slip on a non-critical build accepted cleanly preserves goodwill for the next time the slip is real and on critical path.
Pushing back without specifics. "We need the original date" is not a request, it is a complaint. Push-back emails that name the original date, the production impact, and offer recovery options (overtime, expedite, partial ship) get specific responses. Vague push-back gets vague responses, and you end up at the same place a week later with less leverage.
Forgetting to update the ERP after the date settles. A verbal or email confirmation of a new date that never makes it into the ERP creates two problems: production planning works against the wrong date and AP's three-way match runs against the wrong promise. Update the same day the date settles. The five minutes of ERP work prevents an hour of cleanup later.

Keep reading

GlossaryPO Acknowledgment GlossaryLead Time FeatureEmail Intelligence FeatureAuto Follow-Ups FeatureParts Dashboard