Warehouse operations
Run a real warehouse from one screen.
Pick lists with state machines, not spreadsheet rows. Cycle counts with variance thresholds, not honor-system tallies. Transfer orders with partial-receipt support, because shipments don't arrive complete. The workflows that hold up when volume scales.
The problem in 30 seconds
Spreadsheet warehouses break at the worst possible time.
- A pick list lives in someone's pocket on a printed sheet. They mark "done" by crossing things out. Half-finished picks aren't trackable.
- Cycle counts happen "when there's time." When variance shows up, nobody knows whether to trust the count or the system.
- A transfer ships 50 units. 48 arrive. The Slack thread to reconcile takes longer than the receiving itself.
How it works
State machines for the things that actually matter.
Pick lists
Pick lists with a state machine, not a status field.
Every pick list moves through assigned → picking → packed → shipped, with worker assignment captured at each transition. Crashes recover; reassignment is one click. Audit log per pick list shows who did what and when.
- Worker-assignment audit at every transition
- Batch picking — group orders by location, pick once, sort after
- Mobile-friendly screens for scanner workflows
- Recoverable mid-pick state (the worker's iPad died — pick resumes where they left off)
Cycle counts
Cycle counts with variance thresholds and forced recounts.
Random counts, scheduled counts, or operator-triggered counts. If the variance against system stock exceeds your configured threshold, the count moves to recount required — automatically. A second pair of eyes reconciles; the system trusts the recount, not the first attempt.
- Tenant-configurable variance threshold (% or absolute)
- Auto-recount loop on variance exceedance
- Scheduled or random cycle (avoid count gaming)
- Adjustment record auto-created for variances over threshold
Transfer orders
Transfers with partial-receipt support — because shipments arrive incomplete.
Transfer orders move through draft → approved → in-transit → received → reconciled. The 50-shipped-48-arrived case is first-class: receive what arrived, the rest stays "in transit" until reconciled, and inventory at both locations updates as units actually move.
- Partial-receipt as a first-class status
- Damage / shortage reporting with photo evidence
- In-transit stock shows as committed, not available, in inventory sync
- Approval workflow for high-value transfers
Under the hood
What warehouse ops actually does.
Who it's for
Built for the team on the floor.
For warehouse managers
Daily ops in one dashboard. Audit log for the conversations you don't want to have twice. Variance thresholds for the conversations you want to have only when needed.
For pickers + packers
Mobile screens that survive a dropped tablet. Scan-to-pick. Pick lists that resume where you left off.
For ops finance
Reconciliation reports that match your books. Shrinkage tracked. Adjustments audit-trailed.
Pairs with
What warehouse ops talks to.
Inventory sync
Pick + cycle-count + transfer events write back to inventory in real time. No double-bookkeeping.
Learn moreOrder management
Orders route into pick queues per warehouse rules. Bulk fulfillment closes the loop.
Learn moreAutomation
Rules trigger off warehouse events: variance over X → notify manager. Damage reported → flag SKU for QA.
Learn moreThe variance-threshold cycle count loop is what sold us. We were rolling our own version with Google Sheets and a weekly Slack meeting. This replaces both.
Warehouse manager, Early access program
Warehouse operations — common questions
Stop running your warehouse on spreadsheets.
14-day free trial. No credit card. Let us walk through the variance-threshold cycle count loop with you live.