A "scan rejected" message is Fast WMS protecting your stock accuracy. Rather than let the wrong pallet, batch, or bin through, it blocks the scan and tells you why. The fix depends on the reason — and the reason is usually visible in the message. Here are the cases you will meet and what to do about each.
Likely causes and fixes
- "Pallet is already used" (status Closed / C). The pallet was fully picked or dispatched and is closed. Scan a different available pallet; use a stock report to find the remaining quantity.
- Pallet on Hold (H) or Damage (D). The stock exists but is blocked from picking. If the hold is no longer needed, release it from the pallet status screen; otherwise pick an available pallet.
- Fails expiry or batch eligibility. Under FIFO/FEFO rules, expiry is a hard filter — an expired or out-of-sequence batch is refused so the wrong stock physically cannot go out. Pick the pallet the system directs you to.
- Wrong bin during putaway or transfer. The pallet and the scanned bin do not match the intended move. Scan the correct bin, then the pallet.
- Wrong document or stage. Scanning a pick on an order that is not yet released, or already dispatched, is rejected. Check the order status first.
- Duplicate or unreadable barcode. A torn label or a re-used LPN number can be refused. Reprint the label.
Work through it in order
- Read the message — it usually names the reason (already used, on hold, expiry, wrong bin).
- Check the pallet's status and expiry in Stock Enquiry on the handheld.
- If it is on hold and should not be, release it; if it is closed, pick an available pallet instead.
- For expiry or FIFO rejections, follow the pallet the system directs you to rather than overriding it.
- If the label is damaged, reprint it — see Setting up a Zebra label printer.
A rejected scan is doing its jobMost rejections mean the rule worked — the wrong batch or a closed pallet was stopped before it left the building. Treat it as a prompt to check status, not as a fault to force past.
To understand the picking rules behind expiry and batch rejections, see FIFO & FEFO picking. If scans are being accepted but not reaching the server, that is a sync problem instead — see The app won't sync after reconnecting.
A scan that shouldn't be rejected?
Send us the pallet number and message and we'll pinpoint the rule that's firing.
Contact support