01Capture the short-pick event without rewriting it
Record facility, warehouse, work ID and line, wave, shipment, order or transfer, item and variant, lot or serial requirement, source and destination, license plate or handling unit, requested quantity, actual picked quantity, unit, operator or device, event time and selected reason. Retain the original work state and message. Microsoft describes a short-pick action that records actual quantity and a reason in the work-exceptions log; use that as a system example, not proof that every implementation captures the same evidence. Note whether the worker found zero, a partial quantity, damage, the wrong item, unsafe access or a container mismatch. Do not change the requested quantity to equal the result before investigation.
02Secure the location, stock and remaining work
Stop duplicate picking from the affected source while keeping unrelated work moving. Identify open tasks, reservations, replenishments and mobile sessions touching the location or license plate. Protect any physically found units from being moved without a recorded event. If a count is required, follow the approved blind, directed or supervised method and preserve who observed what. Do not zero the entire location only because one work line was short. Check whether a parent pallet was broken, a child container moved, the label became detached or the stock is present under another permitted status. Safety and access controls take precedence over an urgent search. Mark the order line and shipment state so a replacement task cannot silently coexist with the unresolved original.
03Reconstruct inventory and work events
Build a sequence from the last trusted count or receipt through putaway, transfer, replenishment, reservation, prior picks, packing returns, adjustments and the short-pick event. Compare transaction time, physical-event time and interface-posting time. Check offline scans, retries, reversed work, open movement, duplicate license plates and unit conversions. Review whether the wave reserved stock before a replenishment completed or whether another task consumed it first. A negative balance, available quantity or system license plate is evidence to investigate, not physical proof. Trace both directions: from the missing work quantity to candidate stock events and from every physically observed unit back to a valid identity and status.
04Classify the supported cause
Choose the narrowest supported cause: physical shortage, wrong system location, wrong physical location, unposted move, damaged or blocked units, mixed item, wrong lot or serial, unit-of-measure error, reserve/replenishment delay, duplicate reservation, inaccessible stock, label failure, work-template error or unknown. Separate immediate condition from root cause. For example, an empty pick face is the condition; a late replenishment trigger or misposted transfer may be the cause. Do not accuse an employee or supplier from one difference. Record contrary evidence and confidence where the cause remains open. If the issue reveals a broader count or control risk, open the appropriate inventory investigation rather than expanding one work exception indefinitely.
05Decide reallocation, partial completion or commercial action
Search only verified eligible inventory that meets ownership, status, item, variant, lot, expiry, serial, location and customer restrictions. Microsoft documents manual and automatic item-reallocation options in one system; record the actual local behavior and who may choose an alternate location. If reallocating, cancel or close the affected remainder correctly, create one replacement task and preserve its link. For partial completion, reconcile picked and remaining quantity and decide whether the shipment may split. Substitution requires product and commercial authorization, not a picker decision. If no eligible inventory exists, route the line to replenishment, backorder, customer decision or cancellation. Update the promise only through the responsible order process.
06Control inventory correction and reservation release
An inventory adjustment should identify item, location, license plate, lot or serial, quantity, unit, status, reason, supporting count and approver. Review whether removing reservations is necessary and what demand will be affected. Microsoft configuration can combine short-pick behavior with an inventory adjustment and reservation removal, but that setup is a choice, not a universal accounting rule. Prevent a single mobile action from creating an unsupported financial write-off. Link material losses to shrinkage, damage, claim, write-off or other qualified review where needed. Recalculate available quantity only after the source transactions post. Confirm that the original and replacement reservations sum to the true remaining order demand.
07Reconcile the order and prevent recurrence
Bridge requested quantity to picked, reallocated and picked elsewhere, replenishment pending, backordered, substituted, canceled and unresolved. Confirm the destination put, package contents, shipment, staging and customer status reflect the supported result. Monitor short-pick rate using released lines or units as a stable denominator and separate physical shortage from location, status, replenishment, master-data and work-design causes. Review repeat locations, items, shifts and times without turning correlation into blame. Sample closed exceptions back to physical count and sample later adjustments back to work. Improve slotting, replenishment triggers, label control, unit data, reservation timing or training through owned actions. Close only when the quantity bridge balances and any stock correction is independently traceable.