Operations Covered
What an operator can scan today, as of WarehouseQ v2.0.77.0 (dated 2026-07-20). This list has changed release over release and will keep changing as the product grows — treat this page as version-dated, not evergreen, and check it again after any update.
Core flow
Receive — post inbound stock against an open purchase order or transfer order.
Put away — move received stock from a receiving area into its storage bin.
Pick — pull stock from storage to fulfill an outbound order.
Ship — post the outbound shipment.
Move — relocate stock between bins within a location.
Accuracy
Count — physical inventory counts, reconciled against the ledger.
Adjust — correct a known discrepancy directly.
Advanced per-lot counting — counts scoped to an individual lot rather than a whole bin, for operations where a bin can legitimately hold several lots of the same item at once.
Cross-location and manufacturing
Transfer — move stock between locations, including lines carrying lot, serial, or package tracking.
Production output — report finished output from a production order.
Consumption — report the components consumed to produce that output.
Assembly — report a kit assembled from component items, distinct from a full production order.
Logistics
License plates — handle stock identified and moved by a license plate — a single identifier for a pallet or tote — rather than tracking every item on it line by line.
Replenishment — move stock from bulk storage into active pick locations, so picking bins don’t run dry mid-shift.
Pick generation — generate pick work directly from open outbound demand.
What this page deliberately doesn’t publish
Which specific operations are actually available at which specific Business Central warehouse configuration (see warehouse topology, explained) is a genuinely fast-moving detail — it has changed release over release, and a snapshot table here would go stale the moment it was published. What’s stable across releases is the mechanism, not a fixed matrix: WarehouseQ reads a location’s actual current setup and only ever offers an operator the operations that location genuinely supports. A location running basic warehousing won’t be offered directed-pick-specific behavior it has no way to fulfill; a location that hasn’t turned on transfer processing at all won’t be offered the transfer operation. If an operation isn’t offered on a given floor, that’s the app declining loudly and by design, not a bug or a missing feature.
The same discipline applies to item tracking: an operation is only ever asked to handle lot, serial, or package numbers where the underlying item and location setup actually calls for it — see item tracking & FEFO for what that looks like from an operator’s side.
Related reading
Item tracking & FEFO — how tracked operations work in practice. Offline & connectivity — what happens to any of these operations when a signal drops mid-scan. Your first scan — a walkthrough of the receive operation from install to a posted, ledger-confirmed result.