Workflow · After the PO

Every ack, checked line by line.

Supplier replies compared to open POs. Changes flagged. Silent suppliers chased.

Get demo See every step

Today

You do everything. Agents should!

  1. ManualAgent Open PO list
  2. ManualAgent Check inboxes
  3. ManualAgent Check portals
  4. ManualAgent Find the PO
  5. ManualAgent Compare lines
  6. ManualAgent Spot short lines
  7. ManualAgent Catch price changes
  8. ManualAgent Type into ERP
  9. ManualAgent Call suppliers
  10. ManualAgent Chase silence

How many hours can you get back?

What it costs

Where money is lost.

  • Hidden shortfalls 60 confirmed, 100 assumed
  • Price creep New price, nobody noticed
  • Late material Found out at the dock
  • Silent suppliers No reply, no alarm

The solution

No integrations. No babysitting.

The agent works your screens like a trained employee, by your rules.

The solution

Hand the whole cycle to an agent

1 agent
  1. Loads open POs
  2. Reads replies
  3. Compares lines
  4. Records clean acks
  5. You decide changes
  6. Chases silence
  7. Reports exceptions

Agent does itYou decide

How it works

Five steps. Zero re-typing.

  1. Step 1

    It reads every reply

    Email, PDF or portal. Matched to the right PO.

    Inbox

    V-3051 · hydraulics

    RE: PO 40622 confirmation

    Checked request

    ✓Line 1: confirmed as ordered

    ✓Line 2: 50 EA @ $14.60

    ✓No duplicate open PO

  2. Step 2

    It compares line by line

    Quantity, price, date. Against the PO, not memory.

    Ack vs PO 40622 · line 2

    ✓Quantity 50 of 50

    ✓Item as ordered

    !Price $14.60 vs PO $13.90

    ExceptionPrice up $0.70 each. Held for the buyer.

  3. Step 3

    It catches the short line

    Confirmed quantity recorded. The balance stays open.

    NOVEMBER

    SMTWTFS 12345678910111213141516171819202122232425262728293031

    Need datePromised

    V-0937 · bearings · PO 40618

    Please confirm 100 EA on PO 40618.

    60 EA ship 11/12. Remaining 40 on 12/03.

    To your buyer

    Line 1: 40 EA stay open, due 12/03. ExpediteSwitch supplier

  4. Step 4

    It records clean acks

    Only fields your ERP allows. Reopened to check.

    PO ENTRY    PO#: 40611

    VENDOR: V-1180 · MRO S

    LN PART   QTY  COST

    01 4 OF 4 L As ordered Ships 11/09

    ▌

    Green screen

    ERP · PO maintenance

    PO 40611Emailed to supplier

  5. Step 5

    It chases the silent ones

    Drafted by default. Sent only where you allow.

    Draft · to V-1764 · electrical

    PO 40625 · confirmation needed

    We sent PO 40625 on 10/27 and haven't received a confirmation. Please confirm quantities, prices and ship date.

    1. PO sent
    2. No reply, 2 days
    3. Reminder sent
    4. Buyer told if still silent

The full process

PO acknowledgments: every step

What the agent does, where you decide, and the rules it checks.

  1. POs due to confirm
  2. Gather email & portal replies
  3. Reply in by due date?
    No → draft follow-up
  4. Match reply to PO
  5. Compare each line
  6. Full quantity confirmed?
    No → keep balance open
  7. Price within 2%?
    No → hold for buyer
  8. Date within 2 days?
    No → flag to planner
  9. Not already recorded?
    No → skip, log it
  10. Record in permitted fields
  11. Reopen PO to check
  12. Buyer decides exceptions
  13. Publish exception list
  14. Queue cleared

Agent does it You decide Rule check

Built for you

Built for what comes back

  1. 1Every channelEmail, PDF, portal, no-reply
  2. 2Partial confirmationsConfirmed means 60 of 100
  3. 3Quiet price changesNew price, never called out
  4. 4Moved datesShip date past need-by
  5. 5SilenceNo reply shows up nowhere

Your controls

Your rules. Exactly.

Written once in plain English. Followed every time.

  • Price up over 2%? Hold for buyer
  • Date slips 2+ days? Flag the planner
  • Ack overdue? Draft a follow-up

Never, on any run

  • Overwrite an approved PO price
  • Mark a partial ack as full
  • Receive goods from an ack
  • Send chasers you haven't enabled
  • Repeat an update it already made

When a rule says no

It stops and asks you.

Every held item lands in one queue with the documents, the values read and the rule that fired.

Approvals · 4 waiting
  • Draft follow-upReply in by due date? 2 min
  • Keep balance openFull quantity confirmed? 14 min
  • Hold for buyerPrice within 2%? 1 h
  • Flag to plannerDate within 2 days? 3 h

RUN-2291

Draft follow-up

RuleReply in by due date? No

Source PDFPO as savedRule result

I stopped here. Everything I read is attached. Your call.

ApproveSend back

The difference

Your team, before and after

Your team today and with the agent
TodayWith your agent
Finding replies Several inboxes and portals One queue
Partial acks Recorded as full Balance kept open
Price changes Found at invoice Held same day
Missing acks Buyer's memory Chased on schedule

Your existing systems

No new systems!

The agent runs where you work.

ERP

  • Prophet 21
  • Oracle Fusion
  • Epicor
  • SAP
  • NetSuite
  • Dynamics 365
  • Infor
  • Acumatica

Supplier portals

  • SAP Ariba
  • Coupa
  • Jaggaer
  • Grainger
  • Fastenal

Inbox & documents

  • Outlook
  • Gmail
  • Teams
  • Excel
  • Acrobat / PDF

Screens differ by version and setup; we confirm the exact steps on your system before a pilot. Logos and product names identify systems only and belong to their owners; they do not imply a partnership or endorsement.

Your numbers

How many hours can you get back?

Your volume, your times, your labor cost. Estimates, not results.

90staff hours per month returned to buying work
$3,780labor capacity per month
$45,360labor capacity per year

Acknowledgments × (minutes today − minutes with the agent) ÷ 60 × hourly cost

These are example assumptions, not results. Minutes per acknowledgment cover finding the reply, comparing lines, updating the PO and chasing if needed. These defaults are assumptions; replace them with your team's numbers.

Demonstration

Recordings in production

FAQ

Questions buyers ask us

Does it automatically email suppliers?

Only when you switch that on. By default it drafts follow-ups for the buyer to send. You can let it send routine chasers to set contacts on a set schedule, and it checks its log before every send so a supplier never gets the same message twice.

What happens with partial acknowledgments?

The confirmed quantity and date are recorded, the unconfirmed balance stays open on the PO, and the exact shortfall is shown. If the balance lands after the need-by date, the buyer or planner is told.

Will it overwrite approved pricing?

No. A confirmed price that differs from the PO by more than your tolerance is held for the buyer with both numbers and the difference. The PO price changes only if an authorized person decides it should.

Does it work with my ERP and supplier portals?

It works through the same screens and portal logins your buyers use, under their permissions. Acknowledgment fields differ across ERPs and versions, so we confirm on your system which fields it can update before any pilot. We don't claim every portal or ERP behaves the same way.

Clear your ack queue.

  • We build itYou show us the work once.
  • Start to finishDoes exactly what your team does.
  • No-risk trial$0 setup. See it work before you scale.

Bring a week of supplier confirmations and the open POs they answer.

Get demo