An AI Purchase Order Assistant That Drafts, Not Sends

TL;DR

PO-Relay is an AI purchase order assistant that reads alongside the buyer. It parses every supplier reply, matches it back to the right PO line, and drafts the next follow-up with full context. It does not send email, does not write to the ERP, and is not an agent.

What an AI purchase order assistant means for a production buyer

A production buyer running 100 plus open PO lines spends most of the day in two places: Gmail, where supplier replies are landing, and the ERP, where the static state of every PO lives. The work in the middle, matching the reply to the right line, deciding whether the loop is closed, drafting the next follow-up, is the work that fills the morning. An AI assistant for that desk does the watching, the matching, and the writing so the buyer can spend the day on judgment calls and exceptions.

Most named "AI procurement" tools in the SERP position as agents that take actions: send emails, place orders, escalate to suppliers on a schedule. A production buyer does not need an agent. The relationship cost of one autonomous email to the wrong supplier on the wrong day outweighs a year of saved time. The right AI for this work is an assistant: it does the prep, you make the call.

What is broken about AI for purchase orders today

Generic AI cannot see your inbox or your ERP

A general chat tool is helpful for drafting an email when you paste in the context. It cannot see the actual supplier thread, the actual PO line, or the actual date the supplier last confirmed. The buyer ends up doing the research half of the work, pasting context into a prompt, and pasting the reply back. The AI helps with the writing and adds nothing to the matching, the tracking, or the timing.

Agent tools take actions buyers cannot afford to delegate

Agent-positioned tools email suppliers, change PO records, and escalate without asking. When the supplier is on vacation, when there is a quality hold open on a different line, or when a commercial dispute is in motion, the autonomous email lands at exactly the wrong moment. Buyers spend the next week unwinding the relationship damage. The autonomy is the bug, not the feature.

Black-box AI hides the source of every claim

AI that says "the supplier is two weeks behind" without showing which email it read is hard to trust. The buyer has to verify every assertion before acting on it, which costs more time than the AI saved. An AI assistant that helps a production buyer has to cite its sources: every status change links back to the specific supplier message it came from, so the buyer can confirm at a glance.

How PO-Relay solves it

Email Intelligence is the engine. It reads every supplier reply that lands in your Gmail, parses the content, and matches it back to the right PO line based on PO numbers, part numbers, and thread context. When the supplier confirms a date, the row updates. When a partial shipment notice arrives, the quantity remaining is recalculated. Every status change cites the specific email it came from, so you can verify the source at a glance instead of trusting a black box.

Auto Follow-Ups handles the drafting side. The moment a thread should have a reply by now and does not, the assistant queues a draft with the prior thread, the PO numbers, the dates the supplier last committed to, and the current risk against your build schedule. The draft sits next to the loop, not in your sent folder. You open it, edit anything that needs your voice, and send from your own Gmail in your own name. The assistant never sends on your behalf, and the entire positioning is deliberate: a misfired chase costs more than the time it saves.

Chat Assistant sits over your dashboard so you can ask questions in plain language. "Which lines are at risk this week?" "What did Acme say about PO 12345?" "Show me every line that has gone unacknowledged for more than five business days." The answers come back with the source emails and PO lines linked. The assistant flags what it is not sure about, rather than guessing. When the question needs an action, the assistant queues a draft for your review; it does not act on its own.

What you get

  • Every supplier reply matched to the right PO line

    No more re-reading the same email three times to figure out which line it belongs to.

  • Drafts for every silent thread, with full context attached

    The thread, the PO, and the risk are loaded so review takes seconds.

  • Status changes cited back to the source email

    Every assertion on the dashboard links to the specific message it came from.

  • Plain-language questions, real answers

    Chat over your own data with the source linked on every reply.

  • Uncertainty flagged, not guessed

    The assistant tells you when it is not sure, instead of inventing a confident answer.

  • No autonomous outreach

    You are in the seat for every email that goes to a supplier.

  • No writes back to your ERP

    Read-only on both sides, so the system of record stays exactly as it is.

What PO-Relay does not do

PO-Relay is not an agent. It does not send email autonomously, does not contact suppliers through portals or phone, and does not write back to your ERP. It does not place orders, change PO records, or take actions on your behalf. It does not learn your tone as a personalization model; it follows the SOPs you supply.

The line is the entire positioning. An assistant prepares; you decide. You stay in control of every send, every PO change, and every escalation. AI that takes actions is exactly what a production buyer cannot afford to delegate.

How it fits with your existing tools

PO-Relay connects to Gmail through OAuth with read-only scope and reads your ERP read-only. Nothing in either system changes. Drafts live inside the assistant, not in your inbox, until you copy them in to send. Setup runs about 5 minutes once your Gmail and ERP credentials are connected, and there is no migration, no supplier onboarding, and no IT project to schedule. Each buyer connects their own Gmail and gets their own dashboard, so a team of buyers runs as separate per-buyer instances. See the security page for specifics on data handling, retention, and how supplier email content is treated.

Frequently asked questions