Below are Mandel's takeaways from Nick Gospodinov's conversation with host Jyothi Hartley on Art of Procurement's ProcureTech Insider series.
The work continues after the order is sent
Nick describes the follow-up around backorders, production milestones, and partial shipments. Sending the PO starts that work; it does not establish that the supplier has accepted every line or can meet the required dates.
For a buying team, the useful question is: what evidence lets us call this order confirmed? Start with the PO confirmation checklist to review quantities, specifications, prices, dates, and differences that need approval.
A message and a system record can tell different stories
The interview's central argument is that new supplier information often arrives in communication before it reaches the ERP. Nick describes connecting that information back to the system of record, rather than replacing it.
When a supplier changes a date, ask which line and quantity it covers, whether it means dispatch or receipt, and who must accept the change. The purchase order date guide explains how to keep the requirement, supplier promise, and actual event distinct.
Make the first evaluation concrete
The conversation also covers adoption and trust. A useful next step is to choose one familiar workflow and define which actions need buyer approval before evaluating any system.
Bring a completed order and its supplier messages. Ask what the system would have noticed, what it would have proposed, and what would still need a person's decision. Our procurement AI evaluation guide gives a structure for reviewing the evidence and the work left with your team.
These are Mandel's practical takeaways from the conversation, not independently verified performance results. The interview is a starting point for questions; your own order records are the basis for an evaluation.