Short picks, zero allocation and backorders
A short pick is actual quantity below assigned work; zero allocation decides before dispatch not to send a line. Remainder handling depends on source and release policy. App completion never ships automatically.
Reports and review
For ordered 40/allocated 30/actual 25, report SHORT with 25 and verify DG receipt. Valid short picks alone do not require review. Skipped, damaged, over-picked, or PICKED with quantity unequal to allocation produces REQUIRED and blocks release. Have a supervisor verify; the current UI has no clearing button, so contact an administrator.
Zero-allocation lines
Zero-allocation lines are not sent to the App and count as short/processed progress, not reported picked quantity. All-zero work cannot be normally dispatched or released: shipment requires at least one positive actual quantity.
Keep or drop remainder
Choose BACKORDER to retain remainder or DROP not to; omission uses the system default. Odoo backorders follow original delivery/reservation lines and must be checked in Odoo. Native DG orders do not create follow-up backorders automatically; supervisors handle remaining demand.
When retry is appropriate
After fixing input/permission issues, reload the task before acting. If a release command exists, inspect it rather than recreate it. UNKNOWN first checks receipts; CONFLICT requires source verification. Never change actual quantity to allocation to bypass an exception.
Can an all-zero batch be released just to close it?
Not as a normal shipment: at least one positive actual quantity is required. Zero allocation means no dispatch and a shortage; supervisors decide order handling.
Does DROP delete demand or history?
No. It tells Odoo not to keep the shipment remainder as a backorder. Ordered, allocated and reported quantities remain for checking; native DG does not create a remainder order either.