How do I chase vendors who have not confirmed their delivery
Flag orders where the vendor has not stated a date and quantity, send a first reminder after a threshold you choose, then a second in a later window.
Smalt AI team ·
Count an order as unconfirmed until the vendor has given you a delivery date and a quantity. That definition is ours, based on how Microsoft and SAP flag orders. Flag unconfirmed orders after a threshold you choose, send one reminder per order to the address on the purchase order, and send a second in a later window.
How to do it
The steps below come from procurement and ERP documentation. Those sources show what the systems check and how they sequence reminders. None of them sets a standard time limit, so the thresholds are yours to choose.
1. Define what “confirmed” means
A vendor receiving your order is not the same as a vendor committing to it. Splunk’s PO monitoring guide makes the distinction in EDI terms. EDI is electronic data interchange, the standard format for swapping order documents between companies. Three messages matter:
- 850: the purchase order itself
- 997: a message saying the file arrived, which shows only technical receipt
- 855: the vendor’s business-level acknowledgment of the order
Its search flags 850s that have no matching acknowledgment, or whose acknowledgment carries an E or R status.
Without EDI, the same idea works in a spreadsheet. Count an order as confirmed only when the vendor has given you a date and a quantity. A reply that says “got it, thanks” leaves the order unconfirmed.
SAP’s older Order Acknowledgment Expediters documentation (the 4.70 release) applies a similar test. Urging only covers purchase order items that carry an “Acknowledgment requirement” indicator, and the reminder program urges when there is no acknowledgment number or when the acknowledged quantity is below the order quantity.
2. Flag lines past a threshold you choose
The Procurement Agent follow-up page from Microsoft (a preview feature, dated August 2026) flags a line when three things are true:
- the confirmed receipt date is blank
- the remaining quantity is not zero
- the requested receipt date has passed
Its example filter is orders created more than 3 days ago with no confirmation. Oracle’s JD Edwards 9.2 alert for purchase orders awaiting acknowledgement takes a different route: you set a number of days past a chosen date (“Days Thru”), and it lists the orders still unacknowledged. It works for both buyer and supplier roles.
In a sheet, that means three columns (vendor-stated date, vendor-stated quantity, order date) and a filter on blanks. Choose the cutoff by judgment. Longer lead times and strategic vendors may justify a longer wait.
| System | What flags an order | Reminder behaviour | Timing given |
|---|---|---|---|
| Microsoft Procurement Agent | Blank receipt date, open quantity, date passed | One drafted email per order | Example: over 3 days |
| SAP Order Acknowledgment Expediters | No acknowledgment number, or short quantity | Reminder program urges vendor | None stated |
| Oracle JD Edwards 9.2 | Orders still unacknowledged | Alert lists them | You set “Days Thru” |
| Splunk PO monitoring | 850 without acknowledgment, or E/R status | Search flags them | None stated |
3. Send the first reminder to the right address
In Microsoft’s setup, the email goes to the email field on the purchase order first, and to the vendor contact after that. It sends one email per purchase order, unless the order changes. Emails are drafted for human review, and automatic sending is optional and off by default. That draft, review, send pattern is worth copying by hand.
Ask for the two things you are missing, in plain words: the date the vendor will ship or deliver, and the quantity. Quote the purchase order number and your requested receipt date. A template you can adapt:
Subject: PO [number] - please confirm delivery date and quantity
Hello [name], we have not yet received a confirmed delivery date and quantity for PO [number], which we requested for [date]. Could you reply with the date you will ship or deliver and the quantity you will supply? Thank you, [your name]
4. Send the second reminder in a later window
Microsoft handles a second chase as a second task whose date range does not overlap the first. Its example is one task for orders 7 days overdue, then another for orders more than 8 days overdue. Those figures only illustrate two ranges that do not overlap; they are not a rule. That separation stops the same order from matching both tasks and being chased twice at once.
Beyond the second reminder, the sources say nothing. Who gets copied, when a buyer phones, and when you look for another supplier are internal policy. Write those rules down before you need them.
5. Route the chasing through one owner
North Carolina A&T’s procurement policy on inquiries is one example. The vendor is asked to acknowledge the order and give a ship schedule. If it does not, Procurement sends an expediter inquiry. Departments go through Procurement and do not contact vendors directly. The page sets no timing rules.
One person or team sends the reminders, so a vendor does not get conflicting messages from three colleagues.
6. Keep two queues
In Microsoft’s model, unconfirmed orders and late deliveries are separate follow-up queues. They are different conversations. One asks “when will you deliver?” The other asks “you said Thursday, where is it?” Mixing them makes both reminders vague.
Doing it with an AI coworker
If your tracker lives in a spreadsheet, you can hand the routine part to Smalt. It can read a tracker or sheet and draft emails in Gmail or Outlook, and emails wait for your approval before anything is sent.
An example ask: “Chase the five vendors with unconfirmed orders.” Tell it what counts as confirmed (a date and a quantity), your threshold, and which column holds the vendor’s email. You then review and send, edit, or discard each draft.
What to check before you rely on it
The sources here are software documentation and one university policy. They describe how particular systems behave, and they set no standard timing for a first or second reminder. Escalation beyond a second reminder is internal policy and is not sourced here. The SAP, Oracle and North Carolina A&T pages are undated, and documentation pages were checked on 2026-11-04.
Check these against your own setup:
- Product status. The Procurement Agent is in preview, and the SAP page documents an older release. Your version may behave differently.
- Your own threshold. The 3-day, 7-day and 8-day figures are examples from Microsoft’s page. Pick numbers that fit your vendors’ lead times.
- Blank versus wrong. A filter on blank fields misses a vendor who confirmed a quantity short of what you ordered. SAP’s check on acknowledged quantity below order quantity covers that case, so add it.
- Changed orders. If you change an order, the earlier reminder may no longer apply. The agent sends a new email when the purchase order changes.
- Wrong contact. The purchase order email field can be stale. If a reminder bounces or draws no reply, try the vendor contact.
- Draft review. Read each draft before it goes out. Check the order number, the dates and the vendor name.
Smalt is an AI coworker that takes jobs like this end to end and hands back the finished file.