How quickly do I have to reply when a supplier asks me for something?

Same business day, even if the reply is just a holding-pattern note acknowledging the request and naming a specific deadline for the full answer. The supplier reads "I have it, will respond by Friday" as engagement on the loop. Silence past 24 hours reads as a buyer who is not tracking the request, and the supplier reasonably starts to plan around buyer-side delays in their lead time. The cost of the holding-pattern note is sixty seconds and it preserves the supplier's original commitment date. The cost of waiting for the full answer to be ready before replying at all is days of self-inflicted slip.

What if the answer has to come from engineering, quality, or AP rather than from me?

Route the request internally the same hour you read it and send the supplier a holding-pattern reply that names a specific deadline for the full answer. Do not wait for the internal answer to come back before responding to the supplier. The supplier needs the loop closure (or a specific holding pattern with a deadline) regardless of where the answer is being assembled on your side. Internal routing and supplier holding-pattern reply are the same hour's work. Most buyer-side gaps are not because the answer was hard to get internally, they are because the request sat unrouted in the buyer's inbox.

How do I send the slip notification to production when the gap was on my side?

Direct and brief. The note acknowledges the gap, names the new estimated date, and proposes any recovery options. Buyers tend to soften the message or hide the cause, both of which backfire. Production respects buyers who own a slip cleanly and surface it early. The pattern they do not respect is buyers who hide the slip until it is impossible to hide and who frame it as a supplier issue when it was actually a buyer-side bottleneck. Two sentences, sent the same day you realize the gap, is the right shape. Cosmetic recovery later does not work.

Is it worth offering air-freight to recover a slip when the cause was on my side?

Yes if the build is on critical path and the freight premium is less than the line-down cost per day saved. The fact that the cause was buyer-side does not change the math on whether to recover. Internally, owning the recovery cost is also a cleaner story than absorbing the slip and explaining the line-down later. The harder question is whether the supplier should share the cost. The honest answer on a buyer-side bottleneck is no: if the supplier was waiting on you for a drawing or an approval, the freight cost is on the buyer side. Asking the supplier to absorb half the freight premium on a buyer-caused slip damages the relationship for short-term cost relief that is not actually defensible.

How quickly do I have to reply when a supplier asks me for something?

Same business day, even if the reply is just a holding-pattern note acknowledging the request and naming a specific deadline for the full answer. The supplier reads "I have it, will respond by Friday" as engagement on the loop. Silence past 24 hours reads as a buyer who is not tracking the request, and the supplier reasonably starts to plan around buyer-side delays in their lead time. The cost of the holding-pattern note is sixty seconds and it preserves the supplier's original commitment date. The cost of waiting for the full answer to be ready before replying at all is days of self-inflicted slip.

What if the answer has to come from engineering, quality, or AP rather than from me?

Route the request internally the same hour you read it and send the supplier a holding-pattern reply that names a specific deadline for the full answer. Do not wait for the internal answer to come back before responding to the supplier. The supplier needs the loop closure (or a specific holding pattern with a deadline) regardless of where the answer is being assembled on your side. Internal routing and supplier holding-pattern reply are the same hour's work. Most buyer-side gaps are not because the answer was hard to get internally, they are because the request sat unrouted in the buyer's inbox.

How do I send the slip notification to production when the gap was on my side?

Direct and brief. The note acknowledges the gap, names the new estimated date, and proposes any recovery options. Buyers tend to soften the message or hide the cause, both of which backfire. Production respects buyers who own a slip cleanly and surface it early. The pattern they do not respect is buyers who hide the slip until it is impossible to hide and who frame it as a supplier issue when it was actually a buyer-side bottleneck. Two sentences, sent the same day you realize the gap, is the right shape. Cosmetic recovery later does not work.

Is it worth offering air-freight to recover a slip when the cause was on my side?

Yes if the build is on critical path and the freight premium is less than the line-down cost per day saved. The fact that the cause was buyer-side does not change the math on whether to recover. Internally, owning the recovery cost is also a cleaner story than absorbing the slip and explaining the line-down later. The harder question is whether the supplier should share the cost. The honest answer on a buyer-side bottleneck is no: if the supplier was waiting on you for a drawing or an approval, the freight cost is on the buyer side. Asking the supplier to absorb half the freight premium on a buyer-caused slip damages the relationship for short-term cost relief that is not actually defensible.

PLAYBOOK

Your Supplier Is Waiting on You? Here's How to Unblock Yourself

“Supplier emailed Tuesday asking for the latest revision drawing on PO 2247. It is now Thursday. Three days of lead time burned and the delay is on me.”

A supplier email landed in your inbox earlier this week asking for something. A drawing. A spec clarification. An approval on a deviation request. A confirmation of an Incoterms detail. You scanned the email, meant to come back to it, and got pulled into the next fire. Three days later the supplier sends a polite second follow-up and you realize the delivery on PO 2247 has been sitting still since Tuesday because you have not sent the drawing they need to start production. The hardest open loop in production buying is the one where you are the bottleneck. The supplier is doing their job, the order is technically active, and the only thing preventing the parts from moving forward is an answer that is on your plate. The recovery is not difficult, but the diagnostic is uncomfortable: you have to admit that the delay is not the supplier's fault, get the answer to them today, and prevent the same gap from forming on the next request.

What this looks like

It is 9:14 Thursday morning. You are scanning your inbox during the morning report when you spot the second email from your contact at Henderson Tooling on PO 2247. The first email landed Tuesday at 11:08, asking for the latest revision of the drawing for the housing they are about to start machining. The second email landed this morning at 7:52, with a polite "following up on the drawing request, please send when convenient." Two business days have passed. The supplier has not started production on the lot because they do not have the drawing. The original promise date was the 19th. You are now three days into a runway you did not realize you were burning.

The "supplier waiting on you" situation can take five different shapes and each one calls for the same recovery move (get them what they need today) but a different prevention move (stop the same gap from happening again next time). The supplier may need a current revision of a drawing because the file they have is from a prior PO and engineering has issued a change since. They may need a clarification on an Incoterms detail or a freight-routing question. They may be asking for an approval on a deviation request (a process change, a material substitution, a tolerance relief) that requires sign-off from quality or engineering on your side. They may need a confirmation of a packaging or labeling spec. Or they may need a payment or commercial answer (an open invoice, a credit hold, a contract addendum) that lives on the AP or commercial side of your team.

Before you respond, run the diagnostic. Pull the supplier's email and confirm exactly what they are asking for (some requests are framed loosely and answering the wrong question wastes another cycle). Check whether the answer is in your court or whether it has to come from engineering, quality, AP, or commercial. Check whether the request has been sitting in your inbox longer than 24 hours and confirm the current promise date on the PO. The amount of lead time you have already burned determines whether this is a same-day fix or whether you also have to send a slip notification to production planning. Then check whether you have answered this same supplier's same kind of question before. If you have, the prevention move is process, not memory.

Why it matters

The cost picture on a buyer-side bottleneck is uncomfortable because the supplier is going to ship on the date they get the answer plus the production cycle, not on the original promise date. If your answer takes three days and the production cycle is six weeks, the new promise date is the original promise date plus three days, and the slip is on you. On a $10,000-per-hour assembly line that depends on the affected build, three days of self-inflicted slip is $240,000 of line-down exposure that did not need to exist. The slip also tends to compound because the buyer who absorbs three days of delay on the answer side often also waits to send the internal slip notification, which means production discovers the new date late and any expedite recovery happens at premium freight cost.

The supplier-relationship cost is real and runs the opposite direction from a late-supplier situation. A buyer who consistently leaves the supplier waiting on info trains the supplier to plan around buyer-side delays in their lead time quotes, which means the next quote you ask for builds in a few days of buyer-response buffer. The supplier's account manager also notices the pattern. Buyers who answer fast tend to get faster supplier responses on the next request, since the supplier knows the loop will close cleanly. Buyers who stall on info requests get treated as low-priority on the supplier's morning queue, which compounds the next time you need a fast answer.

The internal communication cost is the one buyers find hardest to send. The slip is your fault, not the supplier's, and the proactive note to the planner has to admit that. Buyers who avoid the note tend to wait until the slip is impossible to hide, which is the worst time to surface it. A two-sentence note the day you realize you have been the bottleneck (with the new estimated date and a clean acknowledgment that the gap was on the buyer side) costs nothing in goodwill and prevents the discovery from landing on production by surprise.

What to do, step by step

Step 1: Get the supplier what they need today. Whatever the question is, route it to the answer (engineering for drawings, quality for deviation approvals, AP for commercial answers) the same hour you read the second follow-up. If you are waiting on internal sign-off for the answer, send the supplier a partial response that confirms you have the request and gives a specific deadline for the full answer.

Holding-pattern reply template: "[SUPPLIER NAME], confirming receipt of your request on PO [NUMBER] for [SPECIFIC ASK]. Routing to [INTERNAL FUNCTION] now and will have the full answer to you by [TIME, DAY]. If you can run any of the prep work that does not depend on this answer in the meantime, please do so to protect the original ship date of [DATE]. [YOUR NAME]"

Step 2: Send the actual answer with the requested file or detail attached. The reply should restate what was asked (so the supplier can match it cleanly to their internal request), provide the answer or attached file, and confirm any downstream impact on the PO.

Answer reply template: "[SUPPLIER NAME], here is the [DRAWING/SPEC/APPROVAL] you requested for PO [NUMBER]. [ATTACHED FILE NAME, REVISION, DATE]. Confirming the original promise date of [DATE] still stands; if the answer changes anything on your production plan please flag it back to me today so we can plan around any shift. Apologies for the delay on getting this to you. [YOUR NAME]"

Step 3: If you have burned enough lead time that the original promise date is no longer realistic, send the supplier a request for a revised promise date and a clean note to the planner the same day. Owning the slip in writing is uncomfortable but the alternative (letting the supplier come back later with the slip framed as their date move) is worse for the audit trail.

Slip-acknowledgment template (to supplier): "[SUPPLIER NAME], the [REQUEST] is attached. Acknowledging the request was open on our side from [REQUEST DATE] to today, [X] business days. Please confirm what the revised firm ship date is given the gap. If air-freight upgrade is needed to recover the original [ORIGINAL DATE] please send the cost difference and I will work the approval. [YOUR NAME]"

Step 4: Send the planner a clean internal note acknowledging the slip and the cause. Two sentences is enough. The note has to land before the supplier confirms the new date, so production planning is not surprised by a slip notification that comes from the supplier rather than from you.

Internal update template: "[PLANNER NAME], heads-up on PO [NUMBER] for [PART DESCRIPTION]. The supplier was waiting on a [DRAWING/SPEC/APPROVAL] from our side and the request was open in my queue from [REQUEST DATE] to today. Working a revised firm ship date with [SUPPLIER NAME], best estimate is [NEW DATE], [X] days past the original [ORIGINAL DATE]. If the [BUILD] needs the original date, working an air-freight option. Will confirm by [TIME, DAY]. The gap was on our side and I am tightening the queue process to prevent a repeat. [YOUR NAME]"

Step 5: Set up the prevention move. If the request type is one you have answered before for the same supplier, the right answer is process, not memory. Standing requests that come up repeatedly (revision drawings, deviation approvals, packaging confirmations) should have a queue or a checklist on your side so the next request lands on a process rather than a hope you will see it in time.

How PO-Relay handles this

When a supplier email lands asking for something from the buyer side, PO-Relay's Email Intelligence reads the message, classifies it as a buyer-side info request, extracts the specific ask (drawing, spec, deviation approval, commercial detail), and tags the email against the right PO. The task on the board flips from "waiting on supplier" to "waiting on buyer" with the request and the deadline (if the supplier provided one) attached. The flip is the difference between an email that gets buried and a task that surfaces in your morning report until it is closed.

The Parts Dashboard sorts "waiting on buyer" tasks to the top with a clear visual cue, so you cannot miss that the open loop is on your plate rather than the supplier's. The chat assistant can pull a list of all currently open buyer-side tasks on demand if you want to ask "what am I blocking right now?" before the morning planning meeting. The pattern of which suppliers are most often waiting on you is also visible across time so the prevention conversation has data behind it.

Auto Follow-Ups drafts the holding-pattern reply, the answer reply, and the slip-acknowledgment to the planner pre-loaded with the PO number, the specific ask, the request date, and the estimated answer time. The drafts assume the buyer is going to reply from their own inbox with the actual file attached (drawing, spec, approval), so the structure is set up for you to drop the attachment in and send. PO-Relay never sends email and never writes to your ERP.

The Morning Report resurfaces every "waiting on buyer" task daily until it is closed, ranked by how long the request has been open and the criticality of the affected PO. The afternoon recap captures the answer when it ships so the audit trail of when the request landed, when you replied, and what the resulting ship date became stays intact for the supplier-quality and the AP review later.

See it in action

Get started Learn more

Common mistakes to avoid

Treating a buyer-side info request as low-priority because the supplier is being polite. The polite second follow-up is not the supplier giving you more time. It is the supplier flagging that the lead time is being burned on your side and they are about to start producing the slip into their own promise. Same-day reply, even if the reply is just a holding-pattern note with a deadline, prevents the slip from compounding.
Sending an "I will get back to you" reply with no specific deadline. "As soon as possible" is not a date and the supplier will count it as a non-response. The reply that turns the situation into a tracked one names a specific time you will have the answer back to them ("by end of business Friday") and routes the actual question to whoever has to answer it on your side. Without the deadline the loop stays open in the supplier's inbox and the lead time keeps draining.
Hiding the slip from production planning. The slip is your fault and the proactive note has to admit that. Buyers who avoid the note tend to wait until the slip is impossible to hide, which is the worst possible time to surface it. A two-sentence note the day you realize the gap costs nothing in goodwill and prevents the discovery from landing on production from the supplier rather than from you.
Solving each request as a one-off without setting up the prevention. If the same supplier has asked for the same kind of answer before (revision drawings, deviation approvals, packaging confirmations), the right move is a queue or a checklist that catches the next request on a process rather than a hope you will see it in time. Memory does not scale past a few suppliers and a few request types.

Keep reading

GlossaryLead Time GlossaryPO Acknowledgment FeatureEmail Intelligence FeatureAuto Follow-Ups FeatureTask Management FeatureMorning Report