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.
Agentic AI for operations
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

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
Most AI tools either only answer questions, or act on their own and leave you to find out afterward what they changed.
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.
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
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.
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.
A suggestion with no numbers, sources or before-and-after view is hard to trust and slow to check.
Rejecting a proposal teaches most tools nothing, so it comes back tomorrow morning.
How it works
Fit and trust
Owners, buyers and operations leads who want AI to do the preparation work but keep the final say on orders, prices and stock.
The story page
Turn replenishment pressure into faster, better-governed procurement decisions with supplier and document context attached.
Questions
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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