Legacy Hold Reasons

When using the legacy Hold Reasons, you were able to create Hold Reasons and they were all visible to Drivers and Dispatchers when putting Orders on Hold for all Accounts. There were no filters on the Hold reasons. 

Hold Reasons are only available when an Order is put on hold and are not available to add additional exceptions that could have happened on an Order. The Hold is done by the Driver on the Driver App as well as from the Dispatch Board. 

Exception Codes

There are different types of Exception Codes:

1. Hold
2. Pickup or Delivery
3. Checkpoint
4. Items

Having different types of Exceptions allows you to add Exceptions to an Order at different point of its lifecycle and to specific parcels. The feature allows for a more flexible approach to track the different interventions in the lifecycle of an order down to the parcel level.  Different exception codes can be set to be available to the Driver or only to be added by a dispatcher. 

The Exception code of type Hold works the same way as the original Legacy Hold Reasons however, you can set in a schedule which Hold Exception code is available by account and also which Hold Exception Code can be added by a Driver or a Dispatcher. This gives you greater flexibility when setting up the Hold Exception codes. Furthermore, you can now use the other Exception types to add information on Orders.

Exception codes can be added from the Back Office Order details, the Dispatch Board as well as from the Driver App. 

Exception Codes are associated to Exception Schedules and different Exception Schedules can be associated to different Accounts unlike the Hold reasons which were associated to all accounts.

For more information about Exception codes, please review the Exception code article.

You can also review this article to review how to setup Exception codes and schedules.