Order pool — controlling release into picking
The order pool prioritises which orders enter the pick workflow. Releasing orders triggers bundle building and pick-queue placement — upstream of pick-face validation and route sequencing. Controlling release timing prevents pickers accepting work that cannot be fulfilled from current pick-face stock. Supervisors use the pool to hold volume on peak days.
What is the order pool in Dark Store Systems?
The order pool is the upstream control surface for fulfilment volume. Orders sit in the pool until a supervisor releases them into the pick workflow. Release is the decision point: *is the floor ready for this work?*
Released orders trigger bundle building (OrderBundles) and placement on the pick queue. Nothing reaches a picker’s handheld until pick-face validation and route sequencing run downstream. The pool is not a delete-or-hold bin — it is a timing gate for when work enters the building.
How does order release work?
- Orders accumulate in the pool — Channel and manual orders arrive into the pool awaiting release. Supervisors review volume before committing the floor.
- Supervisor releases selected orders — Release action moves orders from the pool into active fulfilment processing.
- Bundle building runs — The system splits released orders into zone-grouped pick-work units ready for queue placement.
- Pick queue receives bundles — Bundles appear on the pick queue with validity status: Valid, Short pick, Empty, or Not valid. Only ready bundles should be assigned.
- Pick-face validation gates assignment — Before pickers walk, the system checks stock on pick-face locations (types 7 and 8). See pick-face validation.
- Pick routes sequence the walk — Assigned bundles follow zone route order on the handheld station. See bundle picking.
Why does release timing matter on the warehouse floor?
Flooding the floor with orders before pick faces are stocked is the fastest way to generate incomplete picks, consolidation congestion, and packing waits. In our experience at Approved Food scale, peak-day discipline — releasing in waves matched to replen and staffing — matters more than any single optimisation algorithm.
The order pool gives supervisors that lever. Hold volume when assisted fill is catching up; release when validity checks show green across the queue. The pick queue daily summary ties released orders to cost and sell values for morning stand-up review.
How does the order pool relate to the pick queue?
| Surface | Role | Operator persona |
|---|---|---|
| Order pool | Controls *when* orders enter fulfilment | Supervisor planning release waves |
| Pick queue | Controls *what* pick work is ready and assigned | Supervisor + picker execution |
Think of the pool as the tap and the queue as the pipe. Releasing too fast overflows the pipe — pickers accept bundles that fail validation or stall in consolidation. For the full fulfilment journey from channel to despatch, see how order fulfilment works.
What should I evaluate next?
- Pick queue — supervise, rebuild, and validate pick work
- Warehouse picking hub — picking modes and evidence chain
- Bundle picking — zone pick-work units on the handheld station
- Pick-face validation — gating release before walks
Frequently asked questions
What happens when I release orders from the pool?
Release triggers bundle building and pick-queue placement. Orders move from the pool into active fulfilment processing. Bundles then pass through pick-face validation before assignment to pickers. Release does not skip validation — it starts the downstream workflow.
How does the order pool relate to the pick queue?
The order pool is upstream: it controls when orders enter fulfilment. The pick queue is downstream: it shows bundle validity, supports rebuild, and is where supervisors assign work to pickers. Release from the pool feeds the queue; the queue does not replace the pool.
Can I hold orders without deleting them?
Yes — orders can remain in the pool without release. Holding volume is standard peak-day practice: wait until pick faces are stocked and staffing is aligned before releasing the next wave. Held orders stay available for release when conditions improve.
Does releasing orders bypass pick-face validation?
No. Pick-face validation runs after bundle building and before assignment. Bundles show Valid, Short pick, Empty, or Not valid on the queue. Releasing orders starts the workflow; validation still gates what reaches pickers.