Automation
Stop doing the same thing twice.
The boring repetitive operator work — pause listings on low stock, route orders to the closest warehouse, notify the team when a SKU goes negative — runs on rules. You build the rules; we run them every event.
The problem in 30 seconds
The same operator task, done by hand, every day.
- Every morning your operator pauses listings for SKUs below 5 units. Twenty minutes. Every morning.
- A high-priority customer orders. By the time someone notices it should ship same-day, the cutoff has passed.
- A reorder threshold gets crossed at 2am. Nobody sees it until 9am. Twelve potential sales worth of friction.
How it works
Rules fire on real events, with an audit log.
Rule builder
If/then rules for the workflows you'd otherwise do by hand.
Pick a trigger from the events library (inventory dropped below threshold, order received from priority customer, return marked damaged). Pick an action (pause channel listing, notify Slack, create transfer order, fire webhook). Add conditions if needed. Save.
- No code. Operator-friendly UI.
- Conditional logic (AND / OR clauses)
- Per-channel, per-warehouse, per-SKU scope
Triggers + actions
A growing library, not a vague promise.
Events you can listen for: stock-level threshold crossed, order received, order shipped, return requested, channel sync failed, cycle count variance exceeded, transfer received, refund issued. Actions you can fire: pause listing, resume listing, route to warehouse, notify channel (Slack, email, webhook), create transfer order, adjust stock, tag entity.
Custom webhooks let you bridge anything we don't have a first-class action for.
Audit log
Every rule fire — logged, reversible where it matters.
Every fire of every rule is logged with the trigger event, the conditions evaluated, the action taken, and the resulting state change. Reversible actions (stock adjustments, listing pauses) have an undo button. Non-reversible ones (webhooks fired, Slack messages sent) are at least traceable.
- Dry-run mode — preview what would fire without firing
- Per-rule run history with filter by outcome
- Undo for reversible actions
Under the hood
What automation actually does.
Who it's for
Built for the team that wants to stop doing busywork.
For ops leads
Build the rules. Audit the fires. Stop being the human cron job.
For founders
Codify "the way we do things" once. Onboarding a new operator stops being tribal knowledge transfer.
For developers
Custom webhooks let you bridge to anything not in our native action library. Headless when you need it.
Pairs with
What automation talks to.
Inventory sync
Inventory events are the most-used trigger. Threshold crossed → action fired.
Learn moreOrder management
Order received / shipped / returned events feed automation. Priority routing happens in milliseconds.
Learn moreReports
Scheduled rules can email reports on a cadence. The CFO sees the weekly P&L without asking.
Learn moreWe had a 20-minute morning routine of pausing listings for low-stock SKUs. The first automation rule killed it. Three more rules later, our operator has half her morning back.
Founder, Early access program
Automation — common questions
Codify the busywork. Run on rules.
14-day free trial. No credit card. Build your first rule in under five minutes.