Transportation Manager will attempt to identify the Domicile that the carrier will use to service the load.
If the carrier is domicile based, the tractor domicile for the load or trip will be used as the domicile.
Otherwise, the address for the load's first stop will be evaluated versus the geographic area definitions for the Dispatch Zones defined for each of the carrier's domiciles. The Domicile associated with the Dispatch Zone with the most precise geographic area definition will be deemed to be the Domicile that the carrier will use to service the load. If a Division is defined for a domicile and this Division is not equal to the Division for the load, the Domicile will be excluded from consideration.
Potentially, the same Dispatch Zone could be defined for more than one qualifying Domicile. In this case, the application will select one of the Domiciles associated with the Dispatch Zone.
If multiple Dispatch Zones qualify with the same level of geographic precision, the application will select the Domicile associated with any one of these Dispatch Zones.
If Domiciles have not been defined for the carrier, this process will fail to identify a Domicile for the load. Likewise, if the load's first stop does not fall within the geographic areas associated with the Dispatch Zone for any of the carrier's domiciles, the process will again fail to identify a Domicile.
The process used to identify the most applicable Dispatch Zone will mirror the logic used to establish a G/L Region when creating a shipping location.
Domiciles assigned to loads by Transportation Planner are not recognized by the Transportation Manager process that establishes the Tender Contact for a load.
Domiciles will be eligible to be used as the source for Tender Contacts even when the Enabled for Optimization/Routing for the Domicile is not checked.