By Dan Cluderay, Founder, Dark Store Systems Ltd

What happens when a pick item is missing?

When stock is not on the pick face, operators can skip (defer), part-pick, or mark Do Not Pick (DNP). Missing confirm applies forced skip quantities, may set DNP, and rebundles affected orders. Walk exit confirms missing before totes move to consolidation or packing. Rebundle and queue rebuild handle follow-up — no separate Repick job.

What should a picker do when stock is not on the pick face?

On the handheld bundle picking station, the operator has three live exception paths — not a silent walk past the bay:

ActionWhat it doesWhen operators use it
SkipDefers the line (Picker_SkipItem) so the picker can continue the walk and return laterStock may arrive from replen; line is not yet confirmed missing
Part pickConfirms a quantity below the required amount via the part-pick dialogSome units are pickable now; remainder needs follow-up
Do Not Pick (DNP)Marks the product as Do Not Pick (Picker_MissingItem)Stock is not available and the line should not block the whole walk indefinitely

Each path is visible in the admin UI — Skip, Part pick, and Do Not Pick tabs. Status labels such as Valid, Short pick, and Not valid appear on bundle and queue views; do not rely on colour alone when briefing the floor.

Decision flowchart for missing stock during picking showing Skip, Part pick, and Do Not Pick paths, forced skip quantities, rebundle, and walk exit confirmation before consolidation or packing

How does missing item confirmation work in the WMS?

  1. Picker reaches the line — The handheld shows the product, location, and required quantity on the active bundle walk.
  2. Operator chooses an exception path — Skip defers; part-pick records a lower confirmed quantity; Do Not Pick confirms the item cannot be fulfilled from the pick face.
  3. Missing confirm writes forced skips — Confirming a missing item applies QTYForcedSkipped and may set DNP on the product. Remaining quantity calculations feed bundle status, including Short pick where applicable.
  4. Rebundle updates affected orders — Incomplete lines trigger rebundle so pick work reflects what can still be fulfilled. Supervisors rebuild the [pick queue](/platform/features/warehouse/pick_queue) when needed — there is no dedicated Repick job or repick queue in the WMS.
  5. Walk exit confirms missing — Picking_WalkExitPrepare and Picking_WalkExitFinish prompt the picker to confirm missing items before totes move to [consolidation](/guides/glossary/consolidation) or a packing lane.
  6. Follow-up from validation and fill — [Pick-face validation](/guides/glossary/pick-face-validation) and [assisted fill](/platform/features/warehouse/assisted_fill) help supervisors address empty faces before the next release, reducing repeat exceptions on the same SKU.

Why is explicit missing confirmation better than a silent short pick?

A silent short pick — walking past a bay without recording the decision — is the most expensive failure mode on the floor. Packing waits for a line nobody flagged, customer service chases a gap with no audit trail, and supervisors cannot see whether stock was empty or the picker moved on.

In our experience at Approved Food scale, forcing the decision at the station and again at walk exit keeps pickers, packers, and the queue aligned. The WMS records Short pick and forced skip states explicitly so downstream teams know what to expect before a tote reaches the bench.

What happens to the order after a missing item?

OutcomeWhat the floor seesNext step
Part-picked bundleBundle may show Short pick; remaining quantity stays visiblePark in consolidation until other bundles complete, or hand off per site rules
DNP on productProduct marked Do Not Pick; line forced-skippedRebundle and queue rebuild; order may proceed without that SKU
Skipped lineLine deferred within the walk or a later passPicker returns when replen lands or supervisor reassigns work

Orders can show a parked despatch status while part-picked totes wait on the consolidation grid. That is normal multi-bundle behaviour — not a stuck order.

Frequently asked questions

What is the difference between skip and missing item?

Skip defers the line so the picker can continue the walk and return later — stock may still be pickable. Missing item confirmation (including Do Not Pick) records that the required quantity cannot be fulfilled from the pick face, applies QTYForcedSkipped, and may set DNP on the product. Skip is a pause; missing confirm is a recorded exception that triggers rebundle and queue updates.

What does Do Not Pick do?

Do Not Pick (DNP) marks a product so the line is not repeatedly presented on the walk when stock is not available. Confirming via Picker_MissingItem writes forced skip quantities and feeds bundle status. Supervisors see the outcome on queue and order views alongside Short pick and Not valid states where applicable.

Can a part-picked order still go to packing?

Yes — when site rules allow and remaining bundles are complete. Part-picked totes often park on the consolidation grid until all pick-work units for the order are done. Walk exit prompts confirm missing quantities before handoff so packers know which lines are short before they open the tote.

Is there a Repick job for missing items?

No. Dark Store Systems does not implement a dedicated Repick job or repick queue. Follow-up work is handled by rebundle, forced skip quantities, and pick queue rebuild — the same paths supervisors use after any incomplete pick.