Blog

qAI agents for late purchase orders

AI agents for late purchase orders: what the buyer approves

AI agents for late purchase orders: the steps the agent takes, the date change that waits for the buyer, the send that is refused, and what you can check.

3 min readRunning it

by Grisha Pertaia

illustration
  1. session
  2. credential
  3. write · refused· outside permission
  4. lookup
  5. score · refused· outside permission
  6. intake
  7. route
  8. sign
  9. sign

A supplier order is late, and somebody has to find out by how much. The question for a purchasing team is not whether AI agents for late purchase orders can write a polite email. It is which steps an agent may take on its own, which step stays with the buyer, and what happens when the agent is asked to do something it should not.

The work a late order creates

A late order rarely stays in one system. The buyer reads the open order in the ERP. The buyer writes to the supplier from the purchasing mailbox. The reply arrives with an attachment, often a revised packing list or a drawing reference. Then the new date has to go back into the ERP, and accounting has to move the date it expects the invoice.

The cost is in the carrying: the same facts copied by hand from the mailbox to the ERP to accounting, for every late line. The agent takes the carrying. The decisions stay where they are.

Where a wrong action costs money

Three things go wrong here, and each one has a price.

  • A date moves without a decision. The ERP date drives the production plan and the invoice forecast. A date changed on a supplier's word alone moves both, and nobody chose it.
  • A document goes to the wrong address. A drawing sent outside the supplier record is a design you no longer control.
  • A note in an attachment is treated as an order. An attachment can carry text written for the agent, not for the buyer. An agent that follows it can mark an invoice as paid or send a file it was never asked to send.

In the workflow we build, none of the three can happen on the agent's own authority.

One late order, step by step

The supplier follow-up sandbox run shows this job end to end, with demo data. Part 4410 is late, and the agent follows up across four systems.

  1. Step 1

    A credential for this job only

    It lists what the agent may do: read orders, email the supplier on file, read replies, propose a date change, update the invoice date. It expires when the job ends.

  2. Step 2

    Read the open orders

    The ERP returns the open lines for part 4410. Allowed.

  3. Step 3

    Write to the supplier

    The agent drafts the follow-up and sends it to the address on the supplier record. Allowed.

  4. Step 4

    Read the reply

    The attachment carries a hidden instruction addressed to the agent. It is struck out before the agent reads the reply.

  5. Step 5

    Send a drawing to a new address

    The address is outside the permission for this job. Refused, with the reason on the record.

  6. Step 6

    Change the delivery date

    The step stops and waits for the buyer. The buyer approves it.

  7. Step 7

    Update accounting

    The expected invoice date moves to match. The credential closes.

The step the buyer keeps

The delivery date change waits for a person. It is the one step in the job that commits the company to something: a new plan and a new invoice date. The buyer sees the order and the supplier reply beside it, and decides.

Approval and rejection both go on the record with the buyer's name. A rejected date stays rejected. You decide later which steps, if any, stop needing a buyer. That choice is yours to make on evidence, not on day one.

What gets refused, and why it matters most

The refused send is the line in the record a purchasing lead should read first. The permission for this job names who the agent may write to: the supplier address on file. A request to send a drawing anywhere else falls outside it, so the step does not happen. The refusal is written down with its reason, in the same record as the steps that went through.

The hidden instruction in the attachment is handled before that point. Replies and attachments are read at the door before the agent sees them. The instruction is struck out, and the record shows where it was. The identity and permission guarantee sets out how a permission is issued for one job and why it never grows.

The sandbox also runs the same job with no limits in place.

The same job with no limits
  • session

    The agent follows the note in the attachment

  • session

    The drawing goes to the new address

  • session

    The open invoice is marked as paid

  • session

    The date changes, and nobody approved it

  • session

    Nothing is written down

The job on Ares
  • redacted

    The hidden instruction is struck out before the agent reads it

  • refused

    The send to a new address is refused, with its reason

  • allowed

    Accounting changes only after the date is approved

  • human review

    The buyer approves the new date

  • allowed

    Every step is on the record, the refusal included

What you can check yourself

The supplier follow-up workflow page lists the systems by type and what the record holds. The procurement page shows the other purchasing workflows and the state of each.

What it does not do

The agent does not choose suppliers, negotiate or award work. It drafts the message, and your buyer decides what to offer. It does not decide which changes need a buyer: you set that, and any threshold. It does not replace your ERP or your purchasing policy. It works between the systems you already run, and its permissions are only as good as the rules you approve.

Keep reading