An AI agent can send a supplier email before the planning team agrees what that email is allowed to promise. A request for an updated delivery date sounds harmless. Add permission to accept a revised quantity or acknowledge a surcharge, and an administrative task becomes a commercial decision. The boundary can move inside a single conversation.
Before giving an agent access to planning transactions, write down the rules that a competent colleague would need. The useful starting point is one bounded workflow, such as chasing an overdue purchase order. Test the information behind it, define exactly what the agent may change, and rehearse the cases that must return to a person. A pilot can begin before every data problem is fixed, provided its authority reflects those problems.

Make the evidence inspectable
For that overdue order, the agent needs more than a purchase order number. It needs the current promised date, the receiving location, the unit of measure, and the record of what has already arrived. A supplier email may contain a newer commitment than the ERP. Two systems may describe the same material differently. Decide which record governs each field and how a disputed value gets resolved.
Use the first pilot to expose these disagreements. Ask the agent to identify missing dates, contradictory quantities and assumptions that affect its recommendation. Require it to point back to the relevant record. A list of suspected errors is a useful output even while the agent remains unable to amend a purchase order. The data owner should confirm corrections rather than letting the agent quietly choose whichever value makes its answer look consistent.
Write a freshness rule for each decision input. A stock balance refreshed overnight may support tomorrow’s review but be unsuitable for reallocating material that the warehouse is picking now. Define the maximum acceptable age for that use, the treatment of missing timestamps, and the action when the limit is exceeded. Some decisions should stop; others can continue as explicitly provisional recommendations.
During the pilot, keep the planner’s existing checks available. Compare a sample of recommendations with source transactions and an independent calculation or planning view. Check both the answer and the assumptions. An explanation that sounds reasonable does not establish that the underlying stock, demand or capacity was correct.
Separate access from permission
An agent that can read several ERPs does not automatically have a reconciled planning picture. Test the whole order trail across systems, including supplier correspondence and receipts. Specify how item identifiers, sites and units connect. Where agents from different platforms participate, identify which one owns the task and how conflicting instructions reach a human reviewer.

Then assign permissions by action. Reading an order, drafting a reminder, sending it and changing its delivery date are separate permissions. The pilot charter should name the business owner for each. IT can enforce access, but the planning or procurement owner must define which commitments the business is prepared to make.
A workable initial boundary might allow the agent to request confirmation of an existing promise while prohibiting price acceptance, quantity changes and customer commitments. Those are proposed limits, not universal ones. Your contract terms and operating model determine the right boundary. Put the limits in the execution controls as well as the instructions, so a persuasive supplier reply cannot expand the agent’s authority.
Keep a decision record that connects the input snapshot to the recommendation, approval and executed action. Record the policy version too. When somebody later asks why the supplier received a message, the team should be able to reconstruct the decision without searching through a planner’s inbox. Successful transmission also needs confirmation; a drafted email is not a completed follow-up.
Rehearse the stop conditions
Consider an illustrative pilot, not a reported company case. A supplier replies that an overdue component can ship earlier if the buyer accepts an extra charge. The agent has permission to chase dates, but not to approve charges. It should preserve the offer, flag the commercial change and route it to the named buyer. A faster reply would be a poor result if it accidentally committed the business.

Define escalation triggers before running that test. Conflicting records, an unapproved supplier, a changed commercial term or a request outside the permitted action should have an explicit destination. Name a backup owner and a response deadline. If nobody responds, specify whether the agent holds the transaction, sends an approved acknowledgment or hands the case to the next duty owner. Silence must not become permission.
Test the awkward cases deliberately: a repeated supplier reply, a cancelled order, an unavailable approver and an ERP update that fails after approval. Confirm that retries cannot create duplicate messages or transactions. Check who can pause the workflow and what happens to work already in progress. These tests belong beside the happy-path demonstration, before anyone broadens access.
Expand authority only after reviewing the cases, including rejected suggestions and missed escalations. Track correction effort and unresolved exceptions alongside elapsed time. For the next pilot meeting, bring one overdue order and its actual records. Leave with an agreed source for each decision input, an enforceable permission boundary and a tested escalation route. If those remain disputed, keep the agent auditing and recommending while people settle the rules.