A supplier agent needs a purchase order it can identify, a channel it is authorized to read, and a person accountable for accepting changes. If those foundations are missing, adding AI to an inbox will not make purchasing reliable.
Microsoft's Procurement Agent illustrates the foundation inside an ERP: its documented Dynamics 365 workflow proposes PO changes from vendor email for purchaser review, supports outbound supplier communications, and includes impact analysis. The documentation identified it as a production-ready preview when checked September 4, 2026. Microsoft's overview
A small team can use the same operational principles without assuming it needs the same software architecture. Start by making one supplier cycle legible to the team.
Give every order an identity
Choose a PO reference and keep it with the supplier message, original item lines, approved changes and receipt. Include supplier identity and ship-to location. Supplier item codes can differ from your own; record the relationship rather than assuming a name match is enough.
Suppose two locations both order “large cups” on the same day. A reply saying “we can only send six” does not identify the location, PO, pack size or delivery date. The system should leave that ambiguity visible until a person or supplier resolves it.
A living purchase order keeps the original request and subsequent events connected. Updating the current view must not erase what was originally requested or imply that every supplier proposal was approved.
Define what a reply is allowed to change
Use different decisions for different fields: