User Manual
Help Center/User Manual/Putaway: locations, moves, and exceptions

Putaway: locations, moves, and exceptions

Last updated 2026-10-13

How Docklify merges putaway into receiving, and how to move inventory afterwards — by pallet or by product — plus exception rules.

Putaway is merged into receiving#

There is no standalone “putaway task” execution in the current version — putaway is folded into the Receive step. In palletized receiving you pick a storage location per pallet; confirming Receive writes inventory to each pallet’s storage location in one shot, and putaway is done. In direct receiving the goods land on a picking location, so putaway is complete the moment they are received.

Moving inventory afterwards (mobile)#

  1. Open the mobile “Move inventory” scan page (big single-screen buttons) and pick one of the two modes: whole-pallet move or by-product move.
  2. Whole-pallet: scan the pallet LPN. By-product: scan the source location + product + quantity (>0; source-location available qty is validated).
  3. Scan the destination location and confirm. Source and destination must differ; the destination must be active and in the same warehouse.
  4. The system writes a move double-leg ledger entry (source −qty / destination +qty, reference_type=move); a whole-pallet move also updates the pallet’s location.
  • Mixed pallets (empty item) are not supported for whole-pallet moves yet.
  • Pallets in shipped/loaded status cannot be moved; pallets with no source location (not yet put away) must be put away first.
  • Moving does not change inventory status — both legs are recorded as available.
  • Locations covered by an unfinished count task (pending/assigned/in_progress/paused) are locked — moves are rejected with LOCATION_LOCKED until the count task completes or is cancelled.

Replenishment putaway (drop step)

Replenishment tasks run in two steps on the phone. Step 1 picks from the storage location (scan source location / item / source pallet LPN, enter qty ≤ qty_to_move; the line goes pending → in_progress and records qty_picked — nothing is written to the ledger yet). Step 2: walk to the destination pick location, scan its code to confirm the drop → the system writes the move double-leg (storage −qty / pick +qty) and the line goes to done.

Location master data carries put_away_suggestion_weight (putaway suggestion weight), pick_strategy_weight (pick strategy weight) and sequence (travel order for pick paths). Maintain them in master-data → locations so future directed-putaway and routing rules have clean inputs.
Damaged goods: receiving with Condition=Damaged records damaged inventory status and it is excluded from pick allocation. Move it to a designated damaged/quarantine location as soon as possible.