Release gates for supply chain AI agents
Your supply chain agent places replenishment orders, reschedules deliveries and updates stock in ERP and warehouse systems. One wrong order feeds the next forecast. Agentiqa is an AI Quality System for these agents: release gates run the agent's key tasks before each release and check the orders and stock movements it wrote.
Where it writes: ERP and warehouse systems: replenishment orders, delivery dates, stock movements, supplier master data.
What goes wrong with supply chain agents
These are the errors that pass a quick look at the reply and show up in the record:
| Error type | Example |
|---|---|
| Wrong unit | 50 pieces ordered when 50 boxes were meant. |
| Wrong location | The main warehouse restocked when the demand is at a regional site. |
| Wrong date | A delivery date entered as a ship date. |
| Duplicate writes | A duplicate order after a slow response. |
Behind most of them are a few named error types: wrong data, a false "done" (hallucinated success), duplicate writes, partial writes and regressions since the last release (AI agent regression testing).
What the release gate checks
Unit, location, dates, master-data changes, and that each order was saved once.
The gate judges the result in the connected system. Different wording in the agent's reply doesn't fail a task. A wrong value, an extra record or a false success message does.
How it works
- Key tasks, in plain words. You and an Agentiqa engineer pick the tasks where a mistake costs the most, for example placing a replenishment order for a regional site or moving a delivery date. Each task is described in plain words.
- Run before each release. The gate runs each task in a real browser with a test account, then checks what changed in the connected system, not only the agent's reply. That is where wrong data, a false "done", duplicate writes and partial writes show up.
- Confirmed regressions only. When you rerun the failed tasks, AI Quality Manager reports a step as a regression only if it fails again. Unconfirmed failures are listed separately.
- Evidence for the decision. Each failure comes with a trace, the recording and steps to reproduce. Your team decides whether the version ships.
AI Quality Manager compares each release with the previous one, shows regression candidates, and proposes test updates and new tests. A person on your team approves them.
Rollout
First release gates are live within 7 minutes. Then comes the 3-day enterprise rollout: an Agentiqa engineer works with your team, on-site or remote, to cover the riskiest actions in your domain, and keeps the gates current as your prompts, models and product change.
Vertical Agents Safety Review
For teams whose agents write into business systems. Free, 20 minutes.
Security
- Credentials are encrypted with AES-256-GCM. The agent types them by name, so their real values stay out of the model's context.
- SOC 2 in progress (not yet achieved). Data processing agreement (DPA) on request.
- Agentiqa is independent of the team and the tools that built the agent.
More in Security.
Read more
Vertical Agents Safety Review
For teams whose agents write into business systems. Free, 20 minutes.
FAQ
The orders and stock movements the agent wrote: unit, location, dates, master-data changes, and that each order was saved once.
Because a quantity in the wrong unit is valid data. The record saves without an error, so only a check of the saved value catches 50 pieces where 50 boxes were meant.
Yes, when the order is part of a gate task. After the task, the gate reads the orders back and checks that each one was saved once.
First release gates are live within 7 minutes. The 3-day enterprise rollout covers the riskiest actions in your domain with an Agentiqa engineer, on-site or remote.