Your warehouse says 40.The marketplace says 0.
The agent reads the stock page in your seller account, joins it with your warehouse export in a terminal card you can watch and turns each mismatch into a task on the board — a supply that never shipped, a shortage at receiving, a best seller about to run out. The most expensive one it prepares itself.
Five SKUs, three problems, one supply file. Allow the script when it asks.
The agent compares the marketplace’s stock page with your warehouse export in a terminal card, puts every mismatch on the board and prepares the supply file for the one costing you sales.
Both sides of the story
The marketplace’s numbers from the browser card, yours from the export — joined with DuckDB in a terminal card.
Mismatches become tasks
Each one lands on the kanban board with the SKU and what needs doing.
Before it runs out
Days of stock left from last week’s sales, so a restock is planned rather than rushed.
You keep the account
The supply file is prepared for you; uploading it and booking a slot stay yours.
From two tables to a plan
A browser, a terminal and a board.
Works in the seller accounts you already use
More for marketplace sellers
The same cards, a different chore.
Work that starts on its own
Any agent card can send itself a prompt every day at a set time — card menu → Schedule. Here is what that prompt can run.
Stop losing sales to empty shelves
The agent does the counting.
macOS and Linux are coming later.
The first-run wizard installs an agent CLI, Git and the dictation model for you — or skips each step.