To automate supplier follow-up on open purchase orders, define the PO conditions that trigger a message: no acknowledgment by the confirm-by date, a need date approaching with no confirmed ship date, a date already passed, or a supplier-proposed change. Send one structured question per PO line, match the reply to that line, write accepted dates back to the ERP, and route anything outside tolerance to a buyer.
Morsa publishes this guide and appears in it. Every vendor fact was read on the vendor’s own site on 12 October 2026.
What triggers an automated supplier follow-up?
A field in the ERP, not a calendar reminder. Automation works when each open PO line carries two dates, the date you requested and the date the supplier confirmed, and a rule compares them with today. Microsoft’s Procurement Agent for Dynamics 365 ships with two default tasks that show the pattern. “Unconfirmed purchase orders” finds lines “with a delivery date within the next 60 days” where “the confirmed delivery date is blank.” “Delayed purchase orders” finds lines whose confirmed date “is one or more days ago.” Both skip lines with nothing left to deliver.
Trigger | ERP condition | Typical first action |
|---|---|---|
No acknowledgment | Confirmed date blank after the confirm-by window | Ask for acknowledgment and a ship date |
Need date approaching | Need date inside your lead buffer, no ship confirmation or ASN | Ask the supplier to reconfirm the date |
Date passed | Confirmed date before today, quantity still open | Ask for a new date and the reason |
Supplier change | Reply proposes a new date, quantity or price | Compare to tolerance, then accept or route |
No response | N reminders sent, no reply | Escalate to the owner’s manager |
What should the follow-up message say?
One PO line, one question, one way to answer. SourceDay’s guidance is to include “the PO number, line item, requested date, current confirmed date if available, required response, and deadline,” and to “Avoid vague ‘checking in’ messages.” A template that parses cleanly:
PO 45120, line 3, 400 pcs of part 7781. We need it on site by 14 November. Please reply with your confirmed ship date by 17:00 Thursday, in the form: CONFIRM 45120-3 SHIP DD/MM/YYYY, or NEWDATE 45120-3 DD/MM/YYYY REASON.
Send it where the supplier answers. Leverage AI embeds POs “right in their inboxes.” SourceDay offers its portal, “interactive email,” EDI and API. Coupa and SAP Business Network give suppliers a free portal account. Microsoft lets buyers set the tone (“Casual or Formal, Urgent, or Non-urgent”) and makes an email footer mandatory when emails send automatically.
How do supplier replies update the ERP?
The reply has to become a field update on the right line, with a person in the loop for anything that matters. The working sequence:
Read the reply, whether it is an email body, a PDF acknowledgment, a spreadsheet, a portal entry or an EDI 855.
Match it to the PO and line. Coupa says its AI “reads supplier email replies, matches them to the right PO lines, and confirms or flags changes automatically.”
Compare the confirmed date with the need date and your tolerance.
Accept or route. SourceDay’s PO Change Agent applies “configurable business rules to automatically accept or reject low-risk proposed changes”; everything else goes to the buyer.
Write back the confirmed date to the ERP line. Leverage AI: “As you accept changes, your ERP is auto-updated.”
Log what was sent, what came back, and who accepted it.
When should follow-up escalate, and when should it stop?
Escalate on silence and on impact, and stop on proof. A useful rule escalates when the owner has had no answer by a set time, and the message says what the late line will hit: which work order, which line, which customer shipment. Leverage AI publishes one example ladder: a reminder at 24 hours past the deadline, the category lead at 48, the supplier manager at 72 and the procurement head at 96. Shorter ladders suit parts with short lead times; the point is that the ladder is written down, not improvised.
Stop when the goods receipt posts in the ERP, not when the supplier says “shipped.” A shipping confirmation moves the line to in transit; only the receipt closes it. That one rule keeps an open-PO list honest, because nothing drops off it on a promise. The process side, from PO terms to scorecards, is in how to stop chasing suppliers for delivery dates.
What can software automate?
All six steps, with different starting points. SourceDay’s Open Order Chaser “automatically sends reminder emails based on configured cadence” and writes accepted changes back through certified Epicor, Infor, NetSuite and Acumatica integrations. Leverage AI reads email, PDF and Excel replies. Coupa and SAP run follow-up inside their supplier networks. Microsoft’s Procurement Agent drafts the email inside Dynamics 365 for a buyer to send. Canals reads acknowledgments, ship notices and packing slips. Didero runs agents across procurement. Morsa chases across channels and ties the late line to the orders and customers it affects. Two questions decide between them: where will your suppliers reply, and does the tool only chase, or also tell you what each late line puts at risk? Prices, ERPs and go-live times are in the best PO expediting software for 2026.
What does it look like in a plant?
At J4S, a 120-person glass manufacturing plant, the trigger was not an ERP field but a stores message: “6 mm clear stock enough till Wednesday” at Mon 21:10. Morsa matched it to 3 open orders on Line 2 dispatching Thursday and Friday and created work for the purchasing head, due Tue 12:00. The nudge went at Tue 10:00. Silence triggered the escalation at Tue 13:00, to the Production Head, stating 1,200 pieces of Friday dispatch at risk. The supplier’s Wednesday date arrived at Tue 15:20 and updated the due date with who and why. The goods receipt at Wed 11:40 closed it. Times are illustrative per the J4S story; this is manufacturing proof. Over four weeks, J4S went from about 30% to about 75% of roughly 900 commitments done on time.
Where does Morsa fit, and when is it the wrong choice?
Morsa fits when the trigger can come from anywhere (a moved date in the ERP, a supplier email, a message in a group, a call) and the follow-up has to reach people in different channels: email, Outlook, Teams, WhatsApp, phone, Slack or whatever the team runs on. It decides within your approved rules, chases, escalates with the consequence stated, and closes on the goods receipt. It connects to systems such as SAP Business One, Dynamics 365 including Business Central, NetSuite and Odoo, and to others through an API, a database, an export or an email trail. Anil Kohli, Production Head at J4S: “Our people don’t have to learn any new software. People just message the way they always have. Morsa coordinates all the messages in the background.”
Morsa is the wrong choice if your suppliers already confirm in a portal and you only need reminders on unconfirmed lines (SourceDay, Coupa, SAP or Microsoft’s agent cover that), or if you want a self-serve tool rather than a pilot. Book a demo: https://cal.com/morsa
Sources
Microsoft Learn, Follow up on purchase orders by using the Procurement Agent (production-ready preview), read 12 October 2026, learn.microsoft.com
SourceDay, How to Automate Supplier Follow-Ups Without Losing Control (23 June 2026) and AI Agents, read 12 October 2026, sourceday.com/blog, sourceday.com/ai-agents
Leverage AI, Purchase Order Automation and 7 Tools to Automate PO Acknowledgments and Ship Dates (5 February 2026), read 12 October 2026, tryleverage.ai, tryleverage.ai/blog
Coupa, Supply Chain Collaboration, read 12 October 2026, coupa.com
SAP, SAP Business Network Supplier Account Pricing, read 12 October 2026, sap.com
Canals, homepage, read 12 October 2026, canals.ai
Didero, homepage, read 12 October 2026, didero.ai
Morsa, J4S customer story, read 12 October 2026, /customers/j4s
Changelog
12 October 2026: first published.
