PC Miler — Configurable Routing and Mileage Options
The PC Miler integration supports configurable routing and mileage parameters at the organization level. Your organization can define how PC Miler calculates mileage by choosing the routing type that best fits your operation and, optionally, controlling other calculation parameters such as vehicle type, toll road preferences, and more. These settings apply everywhere PC Miler is used in the TMS — shipment mileage lookups, rating and tariff calculations, and mileage-based reporting.
You must have your own PC Miler integration, configured as an Integration Source in the TMS. These settings are managed at the organization level by an administrator.
How it works
Parameters are added as Integration Source Settings using the following naming pattern:
MileageReport_{ParameterName} = {Value}
For example, to set the routing type to Fastest:
Setting Name: MileageReport_RouteType
Setting Value: Fastest
When PC Miler is called, the TMS automatically detects any settings that follow this pattern and passes them directly to the PC Miler API. Multiple parameters can be active at the same time — all will be included in each request.
Routing Type Options
The most commonly configured parameter is MileageReport_RouteType, which controls how PC Miler selects a route between stops.
| Setting value | What it does |
|---|---|
| Practical | Routes based on commonly used roads, balancing distance and ease of travel. This is the default if no routing type is configured. |
| Shortest | Routes based on the shortest total distance, regardless of road type or travel time. |
| Fastest | Routes based on the fastest estimated travel time. |
Additional Configurable Parameters
Beyond routing type, any parameter supported by the PC Miler Route Reports API can be configured using the same MileageReport_{ParameterName} pattern. Below are the most commonly used options:
| Setting name | Available values | What it controls |
|---|---|---|
MileageReport_RouteType |
Practical, Shortest, Fastest | How the route between stops is selected. |
MileageReport_VehicleType |
Truck, Light, Auto | The type of vehicle used for routing calculations. Affects road restrictions and route selection. |
MileageReport_TollRoads |
Always, AvoidWhenPossible, None | Whether toll roads are used, avoided where possible, or excluded entirely. |
MileageReport_HighwayOnly |
true, false | When set to true, routing is restricted to highways only. |
MileageReport_BordersOpen |
true, false | Controls whether international border crossings are included in routing. Relevant for cross-border shipments. |
The full list of supported parameters is available in the PC Miler Route Reports API documentation. Any parameter listed there can be configured using the MileageReport_{ParameterName} pattern — no additional development work is required.
Example configuration
An organization that wants to route by fastest travel time, restrict to trucks, and avoid toll roads where possible would configure the following Integration Source Settings:
| Setting name | Setting value |
|---|---|
MileageReport_RouteType |
Fastest |
MileageReport_VehicleType |
Truck |
MileageReport_TollRoads |
AvoidWhenPossible |
All three parameters would be passed to PC Miler in every mileage request for that organization.
Where these settings apply
Once configured, the parameters apply to all PC Miler mileage calculations in your TMS:
- Shipment mileage lookups
- Rating and tariff mileage calculations
- Mileage-based reporting
Default behavior
If no MileageReport_RouteType setting is configured, PC Miler uses Practical routing by default. All other PC Miler defaults also remain in effect for any parameter not explicitly set.
Mileage to Next Stop
Mileage to Next Stop stores the distance from each stop on a shipment to the stop that follows it. Your organization can choose whether that value comes from PC Miler or from the ZIP-to-ZIP fallback, without disconnecting the integration.
| Setting value | What it does |
| true (default) | Stop-to-stop mileage is calculated through your PC Miler integration, matching the routing used for shipment mileage. |
| false | Stop-to-stop mileage uses a ZIP-to-ZIP calculation instead. PC Miler still serves shipment mileage, rating and the Mileage Calculator. |
A few things to know before you set it:
EnableStopMileagehas noMileageReport_prefix. It selects which provider is used, rather than telling PC Miler how to route.- The ZIP-to-ZIP fallback does not route over roads, so values read lower than PC Miler road miles — often substantially lower on a long leg.
- Existing shipments keep their stored mileage until they are recalculated. After changing this setting, use Recalculate on a shipment's Stops panel to confirm the new provider is in use.
For how the value is displayed and used across the TMS, see Mileage to Next Stop.
- Stop-to-stop mileage is calculated through PC Miler unless
EnableStopMileageis explicitly set to false. Organizations with no PC Miler license key use the ZIP-to-ZIP fallback for stop mileage regardless of this setting. - Settings are added under LSP > Integration Sources: open your mileage (PC Miler) source and enter each one as a Name / Value pair under Source Settings.