Agentic AI for operations

Agents that draft the work. People who approve it.

Every night Zerqano’s agents draft restock, price and purchase order proposals from your planning data, and every hour they check open orders and receipts. Each proposal shows its evidence. By default, nothing that moves money, stock or a supplier commitment changes until a person approves it.

Real screen · sample data

System health page with an alert drawer open for "Forecast input drift on unit_price", marked Critical. The Evidence table lists source, as of 3 hours ago, feature unit price, PSI 0.31 (threshold 0.25), KS statistic 0.214, p-value under 0.001 and 3 of 6 features drifted. Under Fixes, a note says a retrain approval request already exists and nothing runs until it is approved; Remediation history shows Retrain, Waiting for approval.

Sample data. An agent spotted price drift (PSI 0.31 against a 0.25 threshold) and drafted a retrain. Nothing runs until a person approves it.

In plain words

The decision, the evidence, the outcome.

Most AI tools either only answer questions, or act on their own and leave you to find out afterward what they changed.

01

The decision

Each morning a buyer or owner decides which agent proposals to approve, edit or reject: a restock pack, a price change, a receipt, a model retrain.

02

The evidence

  • The proof on each proposal: line items, the proposed change, cited sources and the fields the agent used.
  • The rules that matched it, such as a Flag on a supplier, shown before you approve.
  • For monitoring alerts, the numbers behind the alert. In the sample screen: unit price drift with PSI 0.31 against a 0.25 threshold, KS 0.214, 3 of 6 features drifted.
  • Missing values shown as “—” with the reason, so a gap is never read as zero.
03

The outcome

A reviewed queue: approved changes applied (purchase orders as drafts), rejections recorded with a reason and, if you chose, a rule, and a trace of who decided what.

The problem

Where it goes wrong today.

A useful agent prepares the decision, shows why, and waits. You need to see what it read, what it wants to change, and be able to say no once so it stops asking.

Agents that act without asking

An agent that can place an order or change a price on its own is a risk no buyer can accept for money and stock.

Proposals with no evidence

A suggestion with no numbers, sources or before-and-after view is hard to trust and slow to check.

The same wrong suggestion every day

Rejecting a proposal teaches most tools nothing, so it comes back tomorrow morning.

How it works

From your data to a decision you can check.

What it does

  • Draft restock, price and purchase order proposals every night at 04:30 UTC from your latest planning data.
  • Check every hour for open purchase orders and documents that should become receipt proposals, and update each supplier’s fill rate from past deliveries.
  • Show each proposal’s evidence: the lines, the proposed change, the sources it cited and the fields it used. A missing value shows as “—” with the reason, never as zero.
  • Hold every order, price, receipt and pipeline run for a person to approve, alone or in batches of up to 50.
  • Turn a rejection into a rule (Block, Flag or Note) so agents stop proposing the same thing.
  • Undo an approved change while it is still safe to reverse, and keep a trace of every decision.
  1. Overnight, agents read your planning data and file proposals in Opportunities. Tonight’s pack replaces yesterday’s undecided one instead of stacking a duplicate.
  2. Open a proposal and check its proof: the lines, the before-and-after change, the sources and any rule that matched.
  3. Approve, edit or reject. A rejection needs a short reason and can be saved as a rule.
  4. An approved purchase order becomes a draft purchase order. Your team sends it to the supplier when ready.
  5. If you change your mind, undo the approved change, as long as nothing downstream has moved on.

Fit and trust

Who it is for, and what you can rely on.

Who it is for

Owners, buyers and operations leads who want AI to do the preparation work but keep the final say on orders, prices and stock.

What you can rely on

  • Agents never send a purchase order to a supplier. A person sends it from Purchase orders.
  • Orders, prices, receipts and pipeline runs are never approved by an agent. Automatic confirmation exists only for some operations items, and it is off until an admin turns it on.
  • Undo is refused once a drafted purchase order has moved past draft; cancel it in Purchase orders instead.
  • A proposal is only as good as the data behind it. Where data is missing, the proposal says so rather than guessing.

The story page

Know what to buy, when, and why.

Turn replenishment pressure into faster, better-governed procurement decisions with supplier and document context attached.

Read the story

Questions

What people ask about agents and approvals.

What do Zerqano’s agents actually do?

They prepare decisions. Every night at 04:30 UTC they read your latest planning data and draft restock, price and purchase order proposals. Every hour they look for open purchase orders and documents that should become receipt proposals, and update each supplier’s fill rate from past deliveries. The proposals wait in Opportunities and Operations for a person to decide.

Which parts run without a person?

The scheduled checks run on their own: the 04:30 UTC draft run, the hourly operations check, a sweep every 15 minutes that expires proposals nobody decided, and a daily digest notification. Those steps only read data, file proposals and update supplier fill rates. Changing an order, a price, stock or a model needs a person, unless your admin has switched on automatic confirmation for the narrow cases described below.

Can an agent place an order or email a supplier?

No. Approving a purchase order proposal creates a draft purchase order in Zerqano. Sending it to the supplier, by email or by copying the text into WhatsApp or SMS, is a separate action a signed-in person takes from Purchase orders. Agents have no tool to send it.

What always needs a person to approve?

Anything that moves money, stock or a supplier commitment: drafting purchase orders, reorder and expedite proposals, applying prices and price rules, posting receipts, committing sales orders, approving documents into records, re-running the data pipeline and promoting a model. These are on a fixed list in the code, and earned autonomy can never auto-approve anything on it.

Can I let Zerqano approve some things automatically?

Only in narrow cases, and only if an admin switches it on; it is off by default. Automatic confirmation covers some operations items: receipt proposals (which also require a person’s dock count, so today they still go to a person) and, with a second switch, sales order proposals under a value cap. Every automatic confirmation is written to the audit log and shown in the "Handled automatically" lane for 24 hours.

How does a proposal show its evidence?

Each proposal has a Proof panel. It lists the line items, the proposed change, the sources the agent cited, the fields it used, any rule that matched, and the IDs that link it to the run that produced it. After approval it also shows the before-and-after of what was actually written. A value that is missing, such as savings without a unit cost, shows as "—" with the reason.

What happens when I reject a proposal?

You give a reason of at least 3 characters, either typed or picked (Not now, Wrong data, Too aggressive, Supplier issue, Duplicate, Other). You can tick "Remember as a rule" and choose Block, Flag or Note for a supplier, SKU, category or kind, with optional start and end dates. A Block rule makes agents leave matching lines out of new proposals; a Flag keeps matches out of batch approvals unless you include them; a Note changes nothing.

Who can override a rule?

Any member can create Flag and Note rules. Block rules are created and overridden by owners, admins and data stewards. Approving a proposal that a Block rule matches needs a single item and a note of at least 10 characters, so the override is on record.

Can I undo an approval?

Yes, for changes that can be reversed, such as drafted purchase orders. Zerqano checks first that nothing has moved on: if a drafted order has already moved past draft, it may be with the supplier, so undo refuses and asks you to cancel it in Purchase orders. If a reversal fails, the change stays marked as done rather than pretending it was undone.

Can I require two people to approve?

Yes. An organization can require a second person for high-impact actions. The person whose agent made the proposal then cannot approve it themselves, and automatic confirmation of operations items stops. It is off by default so a solo owner can keep working. If Zerqano cannot read the setting, it refuses self-approval rather than allowing it.

Will I see the same proposal every morning?

Not as a pile-up. Tonight’s pack for the same subject replaces yesterday’s undecided one instead of adding a duplicate. A rejection saved as a Block rule stops the agent proposing those lines again. Agent proposals nobody decides expire after 48 hours.

Does Zerqano retrain or swap its own models?

No. When monitoring finds drift, the agent can draft a retrain request; nothing runs until a person approves it. Automatic drafting of retrains is off by default, and promoting a new model version is limited to platform administrators and also needs approval.

Try it on your own data.

Free for up to 150 SKUs · 14 days of full access · No card required

Sample data · a fictional outdoor-gear store · not a customer’s results