Warehouse Ops
Move received and returned stock into bins, keep counts accurate, and top up pick faces.
Warehouse Ops is the home for the moves that keep stock in the right place: putting away what just arrived, putting back what came off a cancelled pick, counting bins to keep inventory honest, and topping up pick faces before they run dry. It's operator-only, so brand accounts never see it. Every action here (generating tasks, starting a move, counting a bin, editing a rule) is warehouse-staff only.
The section has four pages under the Warehouse Ops sub-nav:
Task Queue
Every putaway, put-back, and replenishment task, with live counts and one-click start.
Active Tasks
The scan-guided screen where a task actually gets done.
Cycle Count
Pickable bins ranked by how long since they were last counted.
Replen Rules
Per-SKU min/max thresholds that trigger replenishment.
Task Queue
Task Queue → /warehouse-ops/putaway. One list for all three kinds of
stock-movement task. The Generate Replen Tasks button (top right) asks the
system to check every replenishment rule and create tasks for any pick face
that's dipped below its minimum.
Across the top, three donut cards summarize the queue by task type, each showing how many are pending versus in progress, and a Progress bar shows how much of the queue is already being worked.
There are three task types:
| Type | What it is |
|---|---|
| Putaway | Move newly received stock from receiving into a storage or pick bin. |
| Put-Back | Return stock to its bin after a pick was cancelled or short. |
| Replenishment | Top up a pick face from reserve when it falls below its rule's minimum. |
Filter the table with the type tabs (All / Putaway / Put-Back / Replenishment) and the status dropdown, which defaults to Pending. Every task carries a status: Pending, In Progress, Completed, or Cancelled.
The table lists the task's type, SKU, source bin, destination bin, quantity (moved / total once work starts), status, and created date. For a pending or in-progress task you can edit the destination bin inline (except replenishment, which targets the rule's pick bin), and the Start button opens the Active Tasks screen with the task loaded. Cancel drops it from the queue. When there's nothing queued, the table reads "No putaway tasks found."
Active Tasks
Active Tasks → /warehouse-ops/putaway/active. The hands-on, scan-guided
screen where a move actually happens, built for a scanner or tablet. It has two
modes, and which one you get depends on how you arrive:
Two ways in
From a queued task — pressing Start on a task (or tapping it in the list) opens the guided flow: an Active Task screen with a Pick Up → Drop Off → Done stepper. Pick Up shows a big "Go to <source bin>" with the product image and a count that ticks up as you scan; Drop Off shows the item and a fixed "Bring to <bin>" (replenishment) or a searchable destination (putaway / put-back), then Confirm Drop Off; Done is a "Task Complete" screen with Back to Task Queue.
Ad-hoc — opening the page fresh and scanning a bin/tote (no task) runs the five-step flow below, which ends on a Done screen offering Put Away More from Same Bin / Scan New Source. The screenshots here show this ad-hoc path.
Scan Source. The screen opens on a list of pending tasks — each with its type (Putaway / Put-Back / Replenishment), SKU, and source → destination — plus a combined search/scan box. Scan the bin or tote you're pulling from. For a tote put-back you then choose Stage for Later or Put Back Now.
Select Item. The bin's contents appear with each SKU's available quantity. Scan the SKU barcode or tap the item. If a bin holds several lots (or a lot plus untracked stock), you pick exactly which pool to move.
Destination. Scan the destination bin, or pick one from Suggested Destinations — which flags replenishment-needed bins, notes which already hold the SKU, and shows current stock. Set the quantity (capped by what's available). Dropping onto a pallet location shows a pallet banner and warns if the pallet belongs to another client.
Confirm. A summary shows the SKU, the from-bin, the to-bin, and the quantity. Confirm to execute the move and update stock.
Cycle Count
Cycle Count → /warehouse-ops/cycle-count. Two tabs: Queue, the worklist
of bins still to count, and History, the log of counts already done.
Queue
Pickable bins sorted by how long since they were last counted, so the most stale bins float to the top. The idea is simple: count the ones at the top first.
A donut at the top breaks the bins into Never counted (red), Overdue (amber, 30 days or more), and Fresh (green). Search by bin or zone to narrow the list.
Each row shows the bin, its warehouse and zone, the number of SKUs and total units in it, which SKUs are in it, and when it was last counted, shown as a color-coded pill (Never, Today, or N days ago — green under a week, amber under a month, red beyond).
The Contents column names the SKUs rather than just counting them, heaviest first, so you know what you're walking to before you get there. Click any SKU code to open that product's detail. Bins holding more than three SKUs show the first three and a +N more hint; hover it to see the rest.
Press Count to open a count dialog already pointed at that bin, where you record what you actually find. If there's nothing to count, the list reads "No pickable bins with stock to count."
History
Every counted line, newest first: when it was counted, the bin, the SKU, the quantity Before and After, the Result, and who counted it.
The result is a Match badge when the count agreed with the system, or a
signed variance (+3, -2) when it corrected one. Counts that found nothing
wrong are recorded too, which is what makes count accuracy measurable — a bin
that was verified and correct is a different thing from a bin nobody has
touched. Search by SKU, bin, or the person who counted.
The same rows appear on a product's Activity tab, so you can read a single SKU's count history from the SKU itself.
Replenishment tasks
/warehouse-ops/replenishment. A live dashboard for replenishment work,
separate from the rules that drive it. It isn't in the sub-nav — you reach it from
the home dashboard's Low-stock bins / Pending replenishments exceptions.
Four KPIs head the page — Pending Tasks, In Progress, Low Stock Locations, and Active Rules — with a Generate Tasks button that checks every rule and creates tasks for pick faces below their minimum. The table lists each task (SKU, source bin, dest bin, requested, moved, status, created) with a Cancel action; a status filter narrows it. These are the same replenishment tasks you'll find in the Task Queue — this is just the replenishment-only view.
Replenishment Rules
Replen Rules → /warehouse-ops/replenishment/rules. The min/max thresholds
that drive replenishment. When a pick face's stock falls below a rule's minimum,
the system can generate a replenishment task to top it back up. The page has two
tabs, and a link out to the automation engine for bulk rules.
Per-SKU rules
The default tab. A table of individual SKU rules: brand, SKU, pick bin, Min, Max, Current stock, and Variance (shown red when stock is below the target, green when above). Search by SKU and filter by Active / Inactive / All. Click a rule's status badge to toggle it on or off, or Edit to change its thresholds.
Add Rule (or Edit) opens a panel where you choose the SKU and its pick bin, then set the Min Quantity (replenishment triggers when stock falls below this) and Max Quantity (replenish up to this). Max has to be greater than Min.
By SKU / Group
The same rules seen from the SKU's side, grouped by size category. Each SKU lists the per-SKU rules that apply to it (green cards showing min / max / current / variance) alongside any bulk rules from the automation engine (blue cards showing their When / Then conditions). Search by SKU, tick Hide SKUs without rules to focus, and the header totals how many SKUs, per-SKU rules, and bulk rules are in play. Bulk rules themselves are authored in Automation.
Put-Back
Put-back is the reverse of picking: returning units that were already picked back into stock. It happens whenever picked work gets undone — and it's easy to miss because there's no sidebar link for it.
A put-back task is created when you:
- cancel a picked order (its totes are flagged),
- cancel a pick list,
- clear a flagged tote and choose "Put Back",
- abandon a short pick ("Abandon & re-queue"),
- pack a tote whose order was fulfilled externally, or
- recall a lot — with one twist: recalled units go to a quarantine bin, not back to sellable stock.
Two places handle the work. The guided Active Tasks flow walks
a put-back task type just like a putaway (Pick Up from the staging bin → Drop
Off at the original bin). And a dedicated Put-Back Tasks page
(/fulfillment/put-back, reached by URL or mid-flow — not the sidebar) lists them
as a table: SKU, Qty, Staging Bin, Original Bin, Order, Tote, and Status,
with a Pending / Completed filter and a Complete confirm action that moves
the units from the staging bin back to their original location.