Transportation Manager does not provide any mechanism to override the number of primary stops for a load, either directly or by modifying the default value for primary shipping location assigned to individual stops. As is the case for any rating unit, tariffs can be configured to supersede a charge with another based on manual input units only when input units are non-zero. This technique could be used to apply overrides for the number of primary stops.
Consecutive stops with a common primary shipping location will be treated as a single location in the count of primary stops, even if the address for one or both stops represents an override from the location master.
When determining if a lane itinerary is compatible with the itinerary for the load, routing will only consider the actual itinerary for the load. Even if several consecutive stops will be made at locations with identical primary shipping locations, each of these stops must be individually defined on the lane itinerary.
Optimization does not employ a strategy to exploit rating units based on primary stops. However, rating performed during optimization will use number of primary stops, when applicable.
Rate calculator / rate quotation does not allow user to override the number of primary stops when an itinerary has not been defined, even though module will allow user to specify the number of stops when intermediate stops have not been specified. In this case, routing/rating will be performed using the number of stops as the value for primary stops.
The number of primary stops for a trip will be computed as the sum of the values for all member loads. However, if the stops built flag is false for any member load, the value for the trip will be zero. The trip value will be established once stops are built for all member loads.
Shipping location is optional in some cases for non-operational freight and rate quotations. If shipping location is not assigned, Transportation Manager will assume that a primary shipping location has not been defined for this location. Therefore, it will be considered to be a primary stop.
Primary stops will have no impact on scheduling. Scheduling will allocate time at each stop regardless of whether the stop is associated with a primary stop. Specifically, none of the following "stop" functionality will be impacted: