The Open PO Tracking Tool Buyers Actually Use
TL;DR
PO-Relay is an open PO tracking tool that updates itself from your supplier email. Every open line sits on one live dashboard with the latest status, the ERP fields, and the most recent supplier signal. Read-only Gmail and ERP, no writes back.
What an open PO tracking tool means for a production buyer
Tracking, for a production buyer, is not a column in a database. It is the live answer to "what did the supplier last say on this PO line, on which date, and is the part still on track for the build?" That answer changes every day. The dates the supplier confirmed last week are not the dates that hold today. The schedule shifts when one critical line slips, and the buyer is the only person who knows because the freshest data is in the inbox.
Most "tracking tools" in the SERP are dashboards built on top of an ERP. They display the static fields the ERP already knows: the PO number, the part, the quantity, the original promise date. They do not read your supplier email, so the moment the supplier changes a date or sends a partial confirmation, the dashboard goes stale. A real open PO tracking tool listens to the email side and updates the row before the schedule meeting catches it.
What is broken about how buyers track open POs today
The ERP shows what was ordered, not what the supplier said yesterday
A clean ERP report tells you that PO 12345 has 200 pieces due March 30. It does not tell you that the supplier emailed last Thursday saying it slipped to April 12, that 60 pieces are coming partial next Tuesday, or that they need a part-number change to ship on time. The tracking that the buyer actually needs lives in the inbox, and the dashboard built on the ERP cannot see it.
A spreadsheet tracker is always a day behind
The buyer who lives by a tracking spreadsheet pays for it with their morning. Every email update has to be retyped into the sheet, every confirmed date logged, every partial recorded. By Friday the sheet has 12 rows that need a status check and three are already out of date. The reconciliation costs more than the tool saves, and on a sick day the sheet goes stale entirely.
Mental tracking works until two things slip at once
Buyers default to memory for the parts they care most about, because memory is fast. It works on a normal day. The day three lines slip, a quality issue opens, and a colleague pulls you into a two-hour meeting, the mental tracker drops a line. A part goes down on the floor and the only person who knew was the buyer who got pulled away. The system fails exactly when it matters.
How PO-Relay solves it
PO-Relay reads your Gmail and your ERP, both read-only, and builds one live view of every open PO line. The Parts Dashboard lists each line with the ERP fields you expect, PO number, part, quantity, original promise date, plus the most recent signal from your supplier email. When the supplier confirms a new date, the row updates. When a thread goes silent past your acknowledgment window, the row flags. When a partial shipment notice lands, the quantity remaining is recalculated. Tracking stops being a column in a sheet and becomes a board that maintains itself.
Email Intelligence does the matching work in the background. Each supplier reply that lands in your Gmail is parsed, matched back to the right PO line based on PO numbers, part numbers, and thread context, and the row is updated. Email Intelligence cites the source: every status change on the dashboard links back to the specific email it came from, so you can always see why the row says what it says. Open Loop Tracking sits next to the dashboard and lists the lines that need a chase today, the loops that have been silent the longest, and the lines that are at risk against your build schedule.
When a line needs a follow-up, Auto Follow-Ups drafts the chase with the prior thread and PO context attached. The draft sits next to the loop, you review and edit, and you send from your own Gmail. PO-Relay does not write back to the ERP, ever. The system of record stays where your finance team and your auditors expect it. The operational tracking layer, the live answer to "what did the supplier last say," lives in PO-Relay.
What you get
One live view of every open PO line
ERP fields and the latest supplier signal on the same row, refreshed as replies land.
Status changes cited back to the source email
Every update on the dashboard links to the specific supplier message it came from.
Silent threads flagged before they hit the schedule
When a PO has gone past your acknowledgment window, the line is flagged and a draft is queued.
Partial receipts handled correctly
Quantity remaining recalculates when a partial notice lands, so the dashboard stays accurate.
A handoff path for sick days
The state lives in PO-Relay, not in your head, so a coverage buyer can pick up where you left off.
No writes back to your ERP
Tracking happens on the operational layer, the system of record stays exactly as it is.
A morning view of what is at risk today
You walk in already knowing which lines need attention, instead of digging for them.
What PO-Relay does not do
PO-Relay does not write back to your ERP, ever. Tracking signals come from supplier email parsing only; PO-Relay does not pull live carrier API data, does not read shipment trackers, and does not classify Incoterms or track RFQs as first-class objects.
It is not an autonomous agent. It does not send email on your behalf. The dashboard is a live operational view, not a replacement for your system of record. The boundary is the point. You stay in control of every PO change that hits the ERP and every message that goes to a supplier.
How it fits with your existing tools
PO-Relay connects to your Gmail through OAuth with read-only scope and reads your ERP read-only as well. Your ERP stays as the system of record. Your Gmail stays where every supplier message arrives. There is no migration, no rip-and-replace, and no supplier onboarding. Setup typically takes about 5 minutes once your Gmail and ERP credentials are connected. Each buyer connects their own email and gets their own dashboard, so a team of buyers runs as separate per-buyer instances. If your ERP has fields PO-Relay does not surface, you still have the ERP for them; the dashboard does not try to replace the underlying data, only the live tracking layer on top.