If your buyers spend their mornings writing “just following up on PO 2210” emails, the AI that can write those for them is probably already in their inbox. Gemini in Gmail and Copilot in Outlook can draft a clear vendor follow-up in under a minute and pull the ship date out of the reply when it comes back. Most purchasing teams just haven’t been shown how to use it this way.

In the manufacturing and distribution offices I work with, the open PO list is where trouble starts. A PO goes out, the vendor never acknowledges it, nobody notices for two weeks, and then a customer order is late because a part is late. Nobody did anything wrong. The follow-up just didn’t happen, because writing it was one more small task on a full day.

This guide shows how to put vendor follow-up on a steady rhythm using the tools you already pay for, with your buyer still in charge of every date.

Why unconfirmed POs turn into late customer orders

Every purchasing team knows the pattern. Sending a PO feels like the job is done. It isn’t done until the vendor confirms the quantity, the price and the ship date.

When confirmations slip, three things happen. The buyer finds out about a delay late, when there’s no time to find another source. The order desk promises a customer a date based on a ship date nobody confirmed. And the “where’s my order?” emails pile up, which I covered in How to Answer “Where’s My Order?” Emails With Gemini or Copilot.

The fix isn’t more effort. It’s a rhythm, so every open PO gets the same follow-up at the same points, whether the buyer is having a calm week or a terrible one.

The life of a vendor PO with three follow-up points: acknowledgment two days after sending, a ship-date check a week before the need date, and an escalation if the date slips
Three follow-up points cover most POs
Key takeaway Late parts usually aren’t a vendor problem first. They’re a follow-up problem. The AI makes the follow-up cheap enough to do every time.

The rule that keeps it accurate: your list, the AI’s words

Here’s the mistake I see most often. Someone asks the AI, “Which of my POs are late?” It can’t answer that. Gemini and Copilot don’t see your ERP or purchasing system, and a confident guess about a ship date is worse than no answer.

So split the job:

That split is what makes this safe. The AI never invents a date, because the only dates it touches came from your list or from the vendor’s own email.

Step by step: the weekly vendor follow-up

The weekly vendor follow-up workflow in five steps: pull the open PO list, sort into three groups, draft follow-ups with a prompt, review and send, then summarize replies and update the system
The whole routine fits in one block of time a week

Step 1: Pull your open PO list

Export or copy the open POs from your system. You only need a few columns: PO number, vendor, part numbers, quantity, need date, and last status. A spreadsheet is fine.

Step 2: Sort into three groups

Go down the list once and mark each PO:

Everything else can wait until next week. If you’re on Google Workspace, Gemini in Sheets can help with this sort. Ask it to flag rows with no acknowledgment date and rows whose need date is within 10 days. Check the result before you trust it.

Step 3: Draft the follow-ups with a prompt

Open the last email thread with each vendor and reply in that thread so the history stays together. Use Help me write in Gmail or the Copilot draft option in Outlook, with a prompt like this:

“Write a short follow-up to this vendor. PO [number], [part numbers and quantities]. We need it shipped by [date]. We have not received an acknowledgment. Ask them to confirm the quantity, price and ship date by [day]. Friendly and direct, under 80 words.”

The facts keep it accurate. The specific ask and the deadline are what get a reply. “Just checking in” emails get ignored. “Please confirm the ship date by Thursday” emails get answered.

Step 4: Review and send

Read every draft. Check the PO number, the part numbers and the date. Add anything only you know, like “your rep mentioned a backlog on the 304 stainless” or “we can take a partial shipment.” This is the part that takes judgment, and it’s quick because the writing is already done.

Step 5: Summarize the replies and update the system

When vendors write back, open the reply and ask the AI to pull out what matters:

“Summarize this vendor reply. List: confirmed ship date, any change to quantity or price, and any open questions. If something is unclear, say so.”

Check the summary against the email, then update the PO. That last instruction matters. You want the AI to tell you when the vendor was vague, not paper over it.

A vendor follow-up prompt with PO facts filled in turning into a first-draft email, plus the details a buyer still checks before sending
Facts in, follow-up out, and what the buyer still checks

Get your free AI Quick Win Kit

We'll build one AI agent for your most annoying office task and train your team on the AI you already have. Limited to 4 companies a month.

Get your free Kit

Three prompts to save for your team

Most purchasing teams need three follow-ups. Here are the starting points I give teams. Put them in a shared doc and adjust the wording to sound like your company.

Acknowledgment request. “Write a short email asking this vendor to acknowledge PO [number] for [parts and quantities]. Ask them to confirm quantity, price and ship date by [day]. Friendly, under 70 words.”

Ship date check. “Write a short email confirming PO [number] is still on track to ship by [date]. Ask them to reply with tracking once it ships, or let us know today if the date has changed. Under 70 words.”

Slipped date. “Write a firm, polite email about PO [number]. The ship date moved from [old date] to [new date], and we need it by [need date] for a customer order. Ask what it would take to ship by [need date], whether a partial shipment is possible, and for an answer by [day]. Under 100 words.”

The slipped-date prompt is where this pays off most. Those are the emails buyers put off because they’re uncomfortable to write. A steady, specific draft makes it easy to send the same day you learn about the slip, which is when it does the most good.

Keep the customer side in sync

A confirmed vendor date is only useful if the order desk knows about it. When a vendor date moves, the customer conversation usually needs to move too.

This is where tasks connect. The vendor summary from Step 5 gives your order desk the facts they need for a customer status reply. If customer POs arrive by email, the summary also checks the date you promised against what you can actually ship, which ties back to turning emailed purchase orders into clean order summaries.

One rule I give every office: never promise a customer a date the vendor hasn’t confirmed. If the vendor date isn’t confirmed, the customer email says when you’ll know, not a guess.

How to know it’s working

Don’t take my word for it. Measure it in your own office.

Before you start, count how many open POs have no acknowledgment and how many vendor dates you learned about late in the last month. Then run the weekly routine for three or four weeks and count again. Ask the buyers how long the follow-up block takes compared to the scattered follow-ups it replaced.

You’re looking for fewer surprises, not just faster emails. Are you finding out about slipped dates earlier? Are fewer customer orders going late because of a part? Those are the numbers that matter, and they’ll be your numbers, not an estimate from me.

Three mistakes I see

Asking the AI which POs are late. It doesn’t know. The buyer pulls the list from the system every time.

Vague follow-ups. “Just checking in on this” gives the vendor nothing to answer. Always include the PO number, the date you need and a deadline for the reply.

Keeping the prompts in one person’s head. If only one buyer knows the routine, it stops when they’re on vacation. Put the three prompts and the weekly checklist in a shared doc.

Where to start

Pick your ten oldest open POs with no acknowledgment and run Steps 3 and 4 on them this week. That’s a small, safe test, and you’ll know within a few days whether vendors answer faster when the ask is specific.

If you’d like help getting your team started, the free AI Quick Win Kit gives you a ready-made agent and a training pack built for manufacturing and distribution offices, and I check in after a week so you can measure before and after with your own numbers.

Frequently asked questions

Can Gemini or Copilot track my open purchase orders automatically?

Not on their own. Gemini in Gmail and Copilot in Outlook can draft follow-up emails and summarize vendor replies, but they don’t see your ERP or purchasing system. A buyer pulls the open PO list and the AI handles the writing. Connecting the PO list directly to an AI agent is a separate build that can come later.

What should a vendor PO follow-up email include?

The PO number, the line items or part numbers in question, the date you need, and one clear ask, usually a confirmed ship date or a signed acknowledgment by a specific day. Keep it under 100 words. Vendors answer short, specific emails faster than long ones.

How often should purchasing follow up on an unconfirmed PO?

A simple rhythm works for most offices: ask for acknowledgment within two business days of sending the PO, follow up again a week before the need date, and escalate if a date slips. The point is that the rhythm is the same every time, so nothing depends on someone remembering.

Can AI read a vendor's reply and pull out the ship date?

Yes. You can ask Gemini or Copilot to summarize a vendor’s reply into the confirmed date, any changed quantities and any open questions. A person should still check the summary against the email before updating the PO, because a misread date is exactly the mistake you’re trying to prevent.

Who can help set this up for a purchasing team?

Jackson Rose at Proverb Consulting trains manufacturing and distribution office teams to use the Gemini or Copilot they already pay for on real tasks like vendor follow-up, starting with one task and a check-in after a week.


Get your free AI Quick Win Kit

We'll build one AI agent for your most annoying office task and train your team on the AI you already have. Limited to 4 companies a month.

Get your free Kit