The source
What comes in
- Current PO and revision history
- Supplier change request or revised quote
- Buyer acceptance and tolerance rules
PO change management agent The supplier changed a line.
The supplier changed a line.
Keep the whole revision.
LaunchAI compares the proposed change with the current PO, shows its impact and prepares the revision your rules allow.
The job in one minute
What the agent takes off your desk.
A purchase order change request asks to amend an existing order before the revised commitment is accepted. It identifies the current PO and line, the proposed values, the reason and the required decision. LaunchAI can compare a supplier proposal with the effective order, prepare the request and apply an authorized revision while retaining the earlier evidence.
The finish
What comes out
An approved revision or a documented rejection, with affected lines identified.
Your rules
Who owns the decision
The buyer and the responsible team keep commercial, qualification and financial authority. The agent does the permitted work and brings exceptions to their owner.
See it run
Watch the agent work through it.
In this conceptual walkthrough, an AI agent picks up Vectra Castings' order confirmation OC-VC-55871 for PO 4500018832 from the purchasing inbox and opens the PO in Manage Purchase Orders, filtered by PO, supplier 300417 and plant 1100. It compares the three items and writes each delta to a variance sheet: item 10 is up 1.41% (+240.00 USD), item 20 is up 9.62% (+700.00 USD) and moves from 11/20 to 12/04, and item 30 matches. Under tolerance policy PRC-TOL-05 and the PO change workflow rules, it confirms items 10 and 30, changes item 10's net price to 43.10 (released by rule WF-CHG-01 with no approver), and verifies the saved values by reopening the PO. Item 20 is left unchanged and sent to buyer01 as review request RV-2207; the buyer replies to keep it on hold. The agent emails the planner a late-delivery alert for production order 1004417, reads the approval history and change log, and writes a before-and-after audit sheet.
Conceptual walkthrough with sample data. Screens are generic stand-ins modeled on the named system, not its own interface; workflow and screens vary by ERP.
- S06 · short · 1:18Audit trail from source document to ERP record
At the buyer’s desk
The work is spread across several windows.
The unit price is unchanged, but the minimum buy is higher. A new confirmation arrives while the old one is still open on the buyer’s screen. The next update needs the current revision and an actual decision about the extra quantity.
A date change can be buried inside a new confirmation PDF while the buyer is working from an older email. Updating the ERP from the wrong revision creates a false commitment. Change handling needs a current baseline, a change request and an explicit decision before the accepted version is distributed.
How the agent does it
Same screens. Your rules. A checked result.
LaunchAI follows the purchasing task through your existing applications. Each step has a source to read, a rule to apply or an outcome to check.
-
Establish the baseline
Read the latest effective order and identify pending amendments before processing another request.
-
Calculate the difference
Compare line quantity, price, specification, ship-to and schedule. Highlight downstream demand affected by the change.
-
Route the decision
Prepare evidence for the buyer or approver. Separate permitted administrative corrections from changes to the commercial commitment.
-
Synchronize the accepted version
Apply the authorized revision and confirm the supplier communication refers to the same version. Retain the earlier values.
The detail that changes the job
What gets caught before the next step.
A supplier changes 500 units to a minimum order of 600 and offers the same unit price.
Move the divider to see how the starting information becomes a checked outcome. The complete fields are in the table below.
| Field | Starting information | Checked outcome |
|---|---|---|
| Unit price | Unchanged | No price variance |
| Commitment | 500 units ordered | 100 additional units proposed |
| Decision | Looks like a matching price | Quantity and total value need review |
Worked example, not a customer result. Values and documents illustrate what to test.
Exact rules. Context. A person where needed.
The exception has somewhere to go.
The agent needs to recognize the point where the next action depends on missing information or another person’s authority.
- Two change requests overlap on the same line.
- The proposed quantity exceeds approved demand or agreement limits.
Define the allowed fields and actions in your software. A draft, an external commitment and an approved payment are different steps.
Show the working
Measure the work that actually gets done.
Agree on the baseline and the finish before the pilot. Count review and exception work as well as completed transactions.
Measure 01
Changes with complete before-and-after evidence
Measure 02
Unresolved change-request age
Measure 03
Updates applied from an obsolete revision
A format your team can use
What goes in a PO change request?
A change request is a decision record. Keep it separate from the current effective PO until the authorized owner accepts it. This suggested record can sit in your ERP workflow, request form or existing spreadsheet.
| Field | What to record | Why it matters |
|---|---|---|
| Order identity | Company, PO number, line and current revision | Avoid changing a similarly named order |
| Before and after | Current and proposed quantity, price, date or specification | Make the actual amendment visible |
| Reason and source | Supplier proposal, internal request and supporting document | Explain why the change is being requested |
| Impact | Extended value, affected demand and relevant delivery consequences | An unchanged unit price can still increase the commitment |
| Decision | Approver, outcome, decision date and accepted limits | A request is not authority to amend the order |
| Effective revision | Saved version and authorized supplier communication | Ensure the ERP and supplier refer to the same accepted order |
The practical questions
What buyers ask.
Can a promised-date update change the purchase commitment?
It may affect production or customer demand even when price stays the same. Define which date changes require buyer acceptance.
Should the old order values be deleted?
Keep the revision trail so the buyer can establish what was requested, proposed and finally accepted.
Is a change request the same as a revised purchase order?
No. The request proposes an amendment. A revised PO records the accepted change after the required decision. Retain the request, approval and effective revision so the buyer can reconstruct the sequence.
Your applications. Your purchasing rules.
See the work happen on your screens.
We’ll scope the input, the saved output and the exception that needs your team.