Gmail for Procurement, Without Leaving Gmail
TL;DR
PO-Relay reads your Gmail inbox read-only, classifies every supplier reply against the right PO line, and drafts follow-ups when threads go silent. You keep working in Gmail; the assistant works alongside. No portal to migrate to, no supplier onboarding.
What Gmail-based procurement means for a production buyer
A mid-market production buyer runs the day from Gmail. Suppliers email there. Colleagues ping there. Acknowledgments, shipment notices, partial confirmations, expedite responses, and quality questions all land in the same inbox. The buyer's actual workflow is "read the email, find the PO line in the ERP, decide what to do, write the reply." A procurement tool that asks the buyer to leave Gmail and live in a separate portal is asking them to break the workflow that already works.
Most procurement tools in the SERP do exactly that: a vendor portal, a separate workspace, a parallel inbox the supplier has to onboard onto. None of that fits a buyer at a 200-person manufacturer who runs 100 plus open POs from a Gmail inbox. The assistant has to come to where the buyer already works, read the inbox where the supplier already replies, and stay out of the way while the buyer sends from their own account.
What is broken about procurement in Gmail today
A separate portal asks suppliers to relearn how to talk to you
Vendor portals work for the largest buyers because the largest buyers can dictate terms. A mid-market buyer asking 80 suppliers to log into a new portal to confirm POs gets crickets, then a phone call, then an email back to the same Gmail account anyway. The portal becomes a parallel inbox no one updates, and the real conversation stays in Gmail.
Search alone in Gmail does not give you a live status
A clean Gmail inbox is a search tool, not a tracker. To answer "where is PO 12345" you search the PO number, scroll the thread, find the most recent supplier reply, cross-reference the ERP, and assemble the answer in your head. Multiply by 50 lines on a normal day and the search-driven workflow eats hours. Gmail is good at finding individual messages and bad at maintaining live state across many.
Manual classification of supplier email burns the morning
20 to 30 supplier emails arrive by 9 AM. Each one has to be read, matched to a PO, decided on. Some are acknowledgments, some are shipment notices, some are expedite responses, some are unrelated. Classifying them by hand is the first hour of the day on a normal morning, and longer on the day the inbox piled up overnight. The work is repetitive and the cost is real.
How PO-Relay solves it
PO-Relay connects to Gmail through OAuth with read-only scope and reads your ERP read-only as well. Email Intelligence parses every supplier reply as it arrives, classifies it against the right PO line based on PO numbers, part numbers, and thread context, and updates the parts dashboard. Acknowledgments close the loop. Shipment notices update the status. Date changes log against the line and flag the schedule risk. Partial confirmations recalculate the quantity remaining. The classification work that used to fill the first hour happens in the background while you read your morning report.
When a thread should have a reply by now and does not, Auto Follow-Ups drafts the chase with the prior thread, the PO numbers, and the current risk attached. The draft lives inside the assistant, not in your Gmail drafts folder. You open it next to the loop on the dashboard, edit anything that needs your voice, and copy it into a fresh Gmail compose to send from your own account in your own name. Suppliers see the same email address, the same signature, and the same tone they have always seen. The assistant does the prep; you do the send.
Chat Assistant sits over the dashboard so you can ask questions in plain language about the data the assistant has already pulled together. "What did Acme say about PO 12345 this week?" "Show me every line that has been silent for more than five business days." "Which lines confirmed a date change in the last week?" The answers come back with the source emails linked, so you can verify any claim at a glance. Working in Gmail stays the default; the assistant is the layer on top that turns the inbox into a tracker.
What you get
Every supplier email classified against the right PO line
Acknowledgments, shipment notices, date changes, and partials all matched automatically.
A live parts dashboard fed from your inbox
The freshest data on every PO is in your email; the dashboard reflects it within minutes.
Drafts queued for every silent thread
You review and copy each draft into Gmail to send from your own account.
No portal for your suppliers to onboard onto
They keep emailing the same address; nothing about their workflow changes.
Source citations on every status change
Each update on the dashboard links back to the specific email it came from.
Chat over your own data
Plain-language questions, real answers, with the supplier emails linked.
No migration, no rip-and-replace
Gmail and your ERP stay where they are; the assistant reads them read-only.
What PO-Relay does not do
PO-Relay does not send email through your Gmail account. Drafts live in the assistant, and you copy them into a fresh Gmail compose to send from your own account. PO-Relay does not manage calendar invites, contacts, or any Gmail surface beyond reading your supplier email. It does not write back to your ERP and is not an agent.
You stay in control of every email that goes out and every PO change that hits the system of record. The boundary is the trust hook for IT and the privacy hook for your inbox.
How it fits with your existing tools
PO-Relay connects through Gmail's standard OAuth flow with read-only scope, the same authorization model your IT team has approved many times. It reads your ERP read-only as well. Setup runs about 5 minutes once your Gmail and ERP credentials are connected. There is no migration, no rip-and-replace, no supplier onboarding, and no separate portal for anyone to log into. Each buyer connects their own Gmail and gets their own dashboard, so a team of buyers runs as separate per-buyer instances and one buyer's inbox is never visible to another. See the security page for specifics on data handling and retention.