Order Expediting Agent
Chases late supplier deliveries and confirms new dates.
- Industry
- Procure AI
- Department
- Procurement
- Team
- Purchasing Operations
- Kind
- Assistant
- Approver
- Category Manager
- Code
- PRC-07
It finds open purchase orders that are unconfirmed or past their promised date across the client portfolio, drafts the chase to each supplier with the lines outstanding, and records the new promised dates the suppliers give. Orders far past due are escalated to the requisitioner and the Category Manager with a re-source option from the preferred supplier list.
How it works
6 steps, and a person signs off before step 6.
- 01Looks it up
Finds the record the request is about in the ERP's purchasing and accounts payable modules: the open orders, confirmations, promised dates and goods receipts for the orders named..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 05Asks a person
Hands the work to Category Manager with its reasoning before anything goes out.
- 06Acts
Once approved, it acts in the source-to-pay suite: it sends the chases to suppliers and records new promised dates on the orders. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The expediting playbook: chase cadence, escalation steps, contractual delivery terms and late-delivery remedies, and the alternative suppliers by category.
Reads from
the ERP's purchasing and accounts payable modules: the open orders, confirmations, promised dates and goods receipts for the orders named.
Acts in
the source-to-pay suite: it sends the chases to suppliers and records new promised dates on the orders.
Hands back
A list with one entry per order, each with po_number, client, supplier, lines_open, promised_date, days_late, next_action (chase, record_new_date, escalate or none) and draft_message.
Asks a person when
An order is late by more than 7 business days and cancelling it or invoking a late-delivery remedy is proposed.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| Days between chases (business days) | 2 | A late order is chased again after this many business days. |
| Days late before escalation (business days) | 7 | An order later than this is escalated with a re-source option. |
| Days without confirmation before chasing (business days) | 2 | An order not confirmed within this many business days is chased. |
| Tone of the chase | firm | How the chase is worded to the supplier. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- An order not confirmed after 2 business days is chased.
- A late order is chased the next business day and every 2 business days after.
- An order late by more than 7 business days, or a critical order late at all, is escalated with a re-source option.
- Chases list only the lines not yet goods-receipted and are written in a firm tone, citing the contractual delivery term when there is one.
- Every new promised date is recorded on the order so supplier on-time-in-full is measured against it and the original date.
See the Order Expediting Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.