Run inventory health checks
Check stale counts, low stock, open receiving variance, approval delays, and sync exceptions by workspace, location, supplier, or SKU class.
Developer proof
CLI for inventory checks, exception review, exports, and agent workflows.
Some inventory work belongs in the browser. Some belongs in scheduled checks, deployment scripts, warehouse diagnostics, or a terminal session with a technical operator.
Current state
CLI documentation is a planned technical surface. Treat this as the intended workflow shape until your team confirms access during evaluation.
Capabilities
CLI keeps the same inventory controls as the product.
Technical access is useful only when it preserves the same records, approval paths, and activity history that operators rely on.
Export evidence for finance
Pull filtered activity events, PO variance, count history, and inventory snapshots for audit, month-end, or reconciliation work.
Support agent workflows
Let technical teams run agent-prepared drafts, dry runs, and review queues through the same policy model as the web app.
Keep scripts accountable
CLI commands that create drafts, export data, or change records use named tokens, scoped permissions, and activity events.
Agent workflow
Observe, detect, explain, draft, approve, execute, audit.
The technical surface keeps the agent path inspectable. A human or policy owner stays attached to expensive or risky actions.
01
Observe
Run a focused command against a location, SKU set, supplier, approval queue, or date range.
02
Detect
Return low-stock items, stale counts, receiving variance, supplier delays, or sync exceptions.
03
Explain
Return the count, PO, supplier, location, and activity context that explains the exception.
04
Draft
Create draft work only when the token and policy allow it, then return a link to the approval queue.
05
Approve
Route the draft to the buyer, finance owner, or policy owner attached to that workspace.
06
Execute
Run approved CLI-triggered work through the same product path as the web app.
07
Audit
Export the evidence in a format finance, operations, or an internal agent can review without losing the audit trail.
Guardrails
The technical path makes unsafe shortcuts hard.
Inventory agents are only useful if teams can see what happened, who approved it, and which records changed.
Dry run first
Commands that draft or change work support dry-run output so teams can inspect the affected records first.
Scoped tokens
A warehouse export token cannot approve a PO or change supplier records.
Activity events
Every non-read command creates an activity event with the token, command, filters, affected records, and result.
Purpose
What the CLI is for
The CLI is for technical operators who need repeatable checks and exports around inventory work. That could be a nightly exception report, a finance export before month-end, a count-drift diagnostic, or a dry run before a larger integration job.
Agent role
Where it fits with agents
A CLI gives internal agents and technical teams a narrow, inspectable way to ask Order3 for inventory state and create reviewable drafts. The goal is not hidden automation. The goal is repeatable operational work with policy, approval, and activity history still attached.
Order3 CLI questions
Is the Order3 CLI available today?
Treat this page as the intended technical workflow until your team confirms access with Order3. If CLI access matters to your rollout, bring that requirement to the workflow review.
What would teams use the CLI for?
Low-stock checks, approval queue review, receiving variance exports, inventory snapshots, sync diagnostics, and dry runs for agent-prepared work.
Can the CLI change inventory?
Only through scoped permissions and policy. The safe default is read, explain, dry run, draft, and route approval. Direct writes require explicit access and an activity event.
Technical evaluation
Bring the technical workflow and the control boundary.
We will map the records, API or agent surface, approval points, execution rules, and activity history before the workflow runs under policy.