Pick lists
Overview
A pick list is a document in its own right, ahead of the delivery note. It bundles several orders into one walk — which a delivery note cannot do, because it always belongs to exactly one order.
As soon as orders are on a list, their stock is reserved; removing an order releases the reservation again. Without that, two lists would reach for the same goods and the second person would end up at an empty bin.
A list moves through: created → picking → picked → packing → completed, plus cancelled. Only on completion are delivery notes created and stock actually booked.
Core tasks
Create a list. Two ways: via a pick template — then the template selects the orders — or via an explicit selection of orders. An order already on an open list is rejected.
Choose a template. A template is the stored answer to "which orders belong on one list". Six shapes exist: one list per order, single-item run, multi-order list with consolidated quantities, two-stage with boxes, rolling "pick-to-box", and identical orders bundled. Templates are maintained through the API; there is no dedicated screen for them yet.
Walk the route. The order of tasks is the walking order, not the document order: it follows the warehouse layout — bin pick priority first, then bin code. The aisle is walked once, in one direction.
Item condition. An item in B-stock or any condition other than new is picked from a bin that holds exactly that condition; the task then carries a condition badge. New goods and B-stock of the same product are never consolidated, not even on a multi-order list, and alternative bins come only from the same condition.
Pick. Each task records the quantity actually taken. In rolling picking the box code is mandatory and must match the order's box. No stock is booked here — the goods are on the cart, not with the customer.
Report a shortage. With a reason: too little there, nothing found, damaged, expired, or deliberately skipped. What was already picked stays; the remainder becomes a clarification case.
Change the bin instead of reporting a shortage. If the bin is empty but the goods are elsewhere, the task is moved to that other bin. The system suggests candidates itself: bins holding located stock, picking bins before reserve, then in walking order. No stock moves — the task merely states where to pick.
Remove an order. It returns to the pool — as long as nothing has been picked for it yet.
Fields in detail
The What it does column answers what changes in the system — not what the field is called. The grey name behind the label is the API field: the same thing runs under that name through automation, import and AI tools.
Creating a pick list
| Field | Required | Values / format | What it does |
|---|---|---|---|
Warehouse warehouseId | yes | an existing warehouse | Which warehouse is picked from. Only orders served from there qualify. |
Orders orderUlids | yes | several orders | What is picked together. Several orders in one list are the real gain: the aisle is walked once instead of three times. |
Template templateUlid | no | an existing template | How the list is built — route strategy, split by zone, order of items. Empty means the warehouse's default. |
On creation the stock is reserved, not yet booked. It leaves the available stock but stays physically present — booking happens on withdrawal.
Settings & permissions
- Module
module.wms. wms.pick.view— see lists and clarification cases.wms.pick.execute— pick and report shortages.wms.pick.manage— create, rebuild and cancel lists. Cancelling a list releases orders someone
else may be walking right now, which is why it is a separate right.
wms.config.manage— maintain pick templates. A template decides what the warehouse does all
day; that is configuration, not daily work.
- Picking and building lists are granted to no role by default — who may do it is an operational
decision.
- The walking order comes from bin pick priority, see Multi-warehouse.
FAQ & troubleshooting
No list is created. If too few orders match the template, no list is created on purpose — an empty list would be work without content.
An order cannot be added. It is already on another open list. Two lists on the same goods would leave the second person at an empty bin.
Stock does not change when picking. Correct. Booking happens at the pack station on completion — until then the goods are on the cart.
An order can no longer be removed. Something has already been picked for it. The goods are on the cart; that is resolved through the clarification case or by putting them back.
The bin is empty although stock is on record. Try the bin change first. If it stays empty, it is a shortage with reason "nothing found" — and thus a stock discrepancy someone has to decide on.