The fulfilment document is the warehouse's work order for outbound stock. Released from a sales order (or a service order), it carries the lines to fulfil and hosts the warehouse actions in sequence: allocate reserves specific stock, pick turns allocations into picking lines that say what to take from where, confirm records that the pick physically happened, and picked delivery creates the delivery order from what was picked. Every step has a selective variant, so partial progress is normal — each line tracks its pending allocation, picking and delivery quantities throughout.
Prerequisites
- A fulfilment document with lines carrying pending quantity — released from the sales order, as described in Picking and fulfilment.
- On-hand stock of the items at the branch; allocation reserves real stock, not intentions.
- Permission to run the fulfilment actions, granted through security profiles.
Procedure
- 1
Header actions in procedure order — Allocation, Selective Allocation, Picking, Selective Picking; the arrow holds Confirm Picking, Picked Delivery, Allocation Delivery and the cancel actions.
- 2
Header: customer account, branch that will pick, and the Order or Service Order the demand came from (a service order here).
- 3
Inventory Fulfillment Order Line — one row per item to fulfil, released from the source document.
- 4
Quantity 1, Pending Allocation 1, Allocated 0: nothing is reserved yet, so Perform Allocation is the next step.
- 5
Allocation Line fills when allocation reserves specific stock (item, lot, storage location, quantity).
- 6
Picking Line (what to take from where) and Delivery Order (created by Picked or Allocation Delivery) fill in the later steps.
The saved detail page is the operational record. The header actions run the steps below in order — Allocation, Selective Allocation, Picking, Selective Picking, and behind the arrow Confirm Picking, Picked Delivery, Allocation Delivery and the cancel actions — and the four grids beneath the header are the evidence each step leaves behind: Inventory Fulfillment Order Line (the demand, with Quantity, Pending Allocation and Allocated quantities), Allocation Line, Inventory Fulfillment Picking Line (item, lot, storage location, picked and pending quantities) and Delivery Order. The capture shows a fulfilment nobody has started: the order line still carries its full quantity as pending allocation and the three lower grids are empty. Verify the header and pending quantities here before moving to the next action; do not use a manually created header to stand in for missing source demand.
Step 1 — Open the fulfilment document
Fulfilments live in the Warehouse app under Fulfilment Orders (default view All Fulfillments; the list's Status and Allocated columns show which documents are untouched). The document shows one order line per item to fulfil, each with its pending allocation quantity; if the order was released with automatic allocation, Step 2 is already done.
Step 2 — Allocate stock
Run Perform Allocation (or Selective Allocation for chosen lines and quantities). Allocation creates allocation lines that reserve specific stock — item, lot for lot-tracked items, storage location, quantity — and posts to the inventory ledger, so the reserved stock stays in hand but stops counting as available. Allocation works the same way as allocating from the order.
Step 3 — Perform picking
Run Perform Picking (or Selective Picking). Picking lines are created from the allocation lines: each one tells the picker which item, lot and storage location to take from, and how much. Picking requires allocation — with nothing allocated the action refuses with No pending picking quantities found in fulfillment allocation lines to create picking.
Step 4 — Confirm the pick
After the goods are physically taken from their locations, run Confirm Picking to mark the unconfirmed picking lines as confirmed, or Selective Confirm Picking for a subset. Confirmation is the gate to delivery: unconfirmed picking lines block the delivery release.
Step 5 — Release the delivery order
Run Picked Delivery (or Selective Picked Delivery) to create the delivery order from the confirmed picked lines — the delivery lines carry the items, lots and quantities straight from the pick, with nothing repackaged in between. Warehouses that skip the picking step can instead run Allocation Delivery to build the delivery order directly from allocated lines; once a line's allocation has moved into picking, though, delivery must go through the picked path — the engine refuses allocation delivery with Perform Picked Delivery as Picking lines are present.
Step 6 — Undo if needed
Cancel Picking (and its selective variant) removes picked quantities and returns them to the allocation; note it operates on confirmed picks — an unconfirmed line blocks it with Cannot cancel picking for lines that are not confirmed. Cancel Allocation then releases the reservation itself. Undo in reverse order: picking before allocation, since picking lines are built on allocation lines.
Expected result
Each fulfilment line shows a consistent quantity trail from the originating order through reserved, picked, confirmed and delivered quantities, with only the remainder left pending at each stage. Allocation lines identify the exact stock position or lot and reduce availability without pretending the goods left the warehouse; picking lines identify what the operator physically takes and from where; confirmation makes those picks eligible for delivery. Picked Delivery then creates a delivery order only from confirmed quantities, while Allocation Delivery is used only on the direct path that has no picking lines. For partial fulfilment, the completed portion has its own delivery evidence and the remaining pending quantities stay visible for a later run. If reversing work, cancel in dependency order so stock returns from pick to allocation and only then to available inventory.
Common problems
- No pending allocated quantities found in fulfillment order lines to create allocation. Every line is already fully allocated — there is nothing left for the action to do.
- No pending picking quantities found in fulfillment allocation lines to create picking. Nothing is allocated yet, or everything allocated is already picked. Allocate first (Step 2).
- No picking lines available to confirm. Nothing has been picked, or every picking line is already confirmed.
- Cannot create delivery for Picking Lines that are not confirmed. Run Confirm Picking (Step 4) before Picked Delivery.
- No pending delivery quantities found… Everything picked (or allocated, for allocation delivery) has already been delivered.
Common questions
Can I move part of a fulfilment forward while the rest waits?
Yes — every action from allocation to delivery has a selective variant that takes chosen lines and quantities, and each line carries its own pending quantities. A fulfilment where half the stock is picked, confirmed and delivered while the other half is still awaiting allocation is a normal state, not an error.
Do I have to pick before delivering?
No. Allocation Delivery builds the delivery order straight from allocated lines, for operations where a recorded physical pick adds no value. But the two paths don't mix per line: once allocation has been turned into picking lines, that stock delivers through Picked Delivery.
What do allocation and picking do to my stock figures?
Both post entries to the inventory ledger. Allocated stock remains in hand but is no longer available to promise elsewhere; picked stock is tracked in its own bucket until the delivery posts. That is why a location can show in-hand stock that a new order cannot touch — read the buckets, not just the total.
Related topics
- Picking and fulfilment — the order-side view of the same document
- Allocating stock to orders
- Delivery orders and dispatch
- Troubleshooting warehouse operations