6
Order Holds is a great idea but it doesn't go far enough. All activities relating to an order 'on hold' should be blocked immediately, including building a load, release to warehouse, wave processing, and picking. In addition, if an order is currently on a load that has not been released to warehouse, there should be some notification when putting it on hold that it's currently scheduled for pickup on a load.

As it currently functions, the order can be "in process" in the warehouse and someone can put the order on "Hold" even though it's being actively picked in the warehouse. When the truck arrives and begins to be loaded (or is already loaded and "complete work" for the last step of the work is attempted) only then does the user get stopped. This is way too late in the "process."

In practice then, the truck driver has traveled to the pickup location and is ready to be loaded but this order cannot be processed unless the hold is lifted. (What if this is one of many orders that are being loaded together on the truck? Multiple orders are now held up because one cannot be loaded) This should have been stopped long before now and the pick up rescheduled or delayed. If you are going to use advanced warehouse activities, we can't only block the legacy warehouse "Pick" step.

The functionality is described in the documentation as "While the order (is) on hold, it cannot be processed by the warehouse for shipping." This is not true as release to warehouse, picking and staging outbound orders is all part of "Processed by the warehouse".
STATUS DETAILS
Needs Votes