Agent configuration

The configuration defines how the agent behaves. It is organised into tabs.

Agent instruction

A free text field for plain language instructions to the agent. This is the catch all for behaviour that is not covered by a structured toggle.

Summary, Emails and Policies

Expandable instruction lists. Each instruction can be scoped to Global, a single supplier, or a single material. Rules the agent learned on its own are flagged and can be accepted into the standing rule set. Every list lets you add new instructions.

Tolerances

A table of fields, each with a sign dropdown, a value, and an enable toggle. A master switch turns the whole tolerance engine on or off. You can add your own tolerance fields.

Suppliers

Per supplier rules that the agent learned or that you set yourself, for example confirms in German so parse AB as the confirmation number, splits deliveries by default, or legal name differs but it is the same supplier. Supplier names and rules are editable, rules can be removed or added per supplier, and new suppliers can be added.

Reminders

Rules that chase missing or incomplete confirmations. See the article Reminders and escalation for the full list.

Notifications

Sets, per notice type, whether surfacing the notice puts the thread into Needs review or has no status impact. By default a process note sets the thread to Needs review, while factory holidays, out of office replies, and general notes have no status impact.

Process rules

Rule	What it does
Auto sync when no deviations are detected	When the confirmation matches on every field, sync automatically.
Confirm individual line items in the ERP	When off, the whole purchase order must be confirmed at once.
Compare a revised confirmation against the last confirmed date	A revised confirmation date is compared to the previously confirmed date rather than the originally requested one.
Auto confirm when everything matches within tolerance	No manual review inside the configured tolerances.
Block the update if the purchase order changed in the ERP after comparison	Forces a fresh comparison against the current order first.
Set the delivery complete indicator when a position is cancelled	Cancelled positions close cleanly in the ERP.
Require a reason when closing without a purchase order update	The reason is logged to the audit trail.
Treat empty confirmed values as acceptable	An empty confirmed field can be accepted as is.

Choosing the right mechanism

What you want	Where to set it
Accept anything within a margin	Set a tolerance on the field and enable auto confirm within tolerance.
Never touch a field automatically	Mark it informational or key, or leave it out of the syncable set.
Chase suppliers who confirm late	Configure reminders with day thresholds and escalation to a Cc lead.
Treat a deviation as unacceptable	Reject the field. The agent drafts the supplier email and the thread waits for a corrected confirmation.
Force a human look at a remark such as a coating change	Set the process note notification to Needs review.
Confirm line by line instead of all at once	Enable Confirm individual line items in the ERP.
Compare reconfirmations against what was last agreed	Enable Compare a revised confirmation against the last confirmed date.