Skip to content
Home » PC*Miler

PC*Miler

PC*Miler Integration

Turn Truck-Specific Mileage Into Transportation Decisions

PC*Miler provides commercial routing, practical mileage, estimated route time, and state-mileage intelligence. FTM connects that information to quoting, dispatch, customer pricing, carrier cost, billing, and transportation reporting inside Salesforce.

Book Executive Demo Explore The Platform
Pickup
Delivery
Vehicle And Route Settings
PC*Miler
Commercial vehicle routing
Practical Miles
Route Time
State Mileage
Route Report
FTM on Salesforce
Transportation execution
Quote
Dispatch
Billing
Reporting
Salesforce-Native
Transportation platform
46+
Integrations
14-Day
Core go-live
24
Countries
Transportation-specific routing

Commercial Mileage Is More Than A Line Between Two Addresses

General mapping tools can show where a shipment needs to go. Transportation teams also need a consistent way to evaluate practical truck mileage, route duration, state mileage, operational requirements, carrier cost, customer pricing, and expected margin.

PC*Miler supplies transportation-specific route intelligence. FTM connects that information to the load and the workflows that depend on it.

General Route Context
Standard mapping
  • Origin and destination points
  • Map display and route visualization
  • Standard route distance
  • General travel context
PC*Miler Inside FTM
Commercial routing and mileage
  • Practical truck mileage
  • Commercial vehicle route settings
  • Route-time context
  • State-by-state mileage
  • Quote and rate context in FTM
  • Billing and margin reporting
  • Transportation record history
Automatic mileage

Calculate Route Mileage When The Load Changes

Once the integration is configured, FTM can request PC*Miler route information when a load is created or when configured pickup and delivery information changes. This reduces repeated mileage lookups and helps operations teams use the same route reference throughout the load lifecycle.

Load Created
Transportation record opened in FTM
Pickup And Delivery Added
Addresses entered on the load
FTM Requests PC*Miler Route Report
Configured route type and vehicle settings used
Route Data Returned
Mileage and configured fields received
Mileage Added To Load
Practical miles stored on the record
Quote, Dispatch, Billing, And Reporting Updated
Mileage available across the load lifecycle
The exact trigger behavior and returned fields depend on the configured FTM implementation and licensed PC*Miler services.
One mileage standard

Use The Same Mileage Context Across The Load Lifecycle

When quoting, dispatch, carrier pay, customer billing, and reporting use different mileage sources, teams can create avoidable disputes and inconsistent margins. FTM connects PC*Miler route information to the transportation record so each department can work from shared operational context.

Quote
Mileage as pricing input
Carrier Rate Review
Same miles, carrier context
Shared
Dispatch
Route context in the load
Customer Billing
Mileage tied to invoice
Carrier Cost
Same reference, carrier pay
Margin Reporting
Miles beside revenue and cost
PC*Miler practical mileage as shared reference across the load lifecycle
PC*Miler mileage should support the transportation decision. It does not independently determine the final customer or carrier rate.
Truck-specific route context

Plan With Commercial Vehicle Requirements In Mind

PC*Miler route reports can be configured using commercial vehicle and route settings, helping transportation teams evaluate routes using context designed for trucking operations.

Practical Routing
Use practical commercial route mileage as a transportation planning reference. Practical mileage is specific to trucking workflows and differs from standard consumer mapping distances.
Truck Route Context
Request routes using configured commercial vehicle settings. The available route profile depends on the selected PC*Miler settings and the configured FTM implementation.
Route-Time Planning
Use returned route duration or estimated-time information when enabled and supported by the licensed PC*Miler services in the implementation.
Directions And Route Path
Support directions or route-path visibility when included in the licensed and configured implementation. Availability depends on the selected PC*Miler report type and add-on licensing.
State mileage

Connect State-By-State Mileage To Reporting Workflows

State mileage can support fuel-tax analysis, jurisdiction reporting, cost review, and transportation reporting. FTM can store returned state-mileage information on the load and make it available for configured reporting, formulas, or downstream workflows.

Illustrative Route Breakdown
California
142 mi
Arizona
368 mi
New Mexico
295 mi
Texas
141 mi
Miles shown are illustrative only. Customers remain responsible for validating configuration and reports against applicable IFTA, fuel-tax, accounting, and regulatory requirements.
StateMiles% RouteStatus
California
142
15.1%
Arizona
368
39.1%
New Mexico
295
31.4%
Texas
141
15.0%
Total
946
100%
State mileage available for configured reporting workflows
Quote to margin

Connect Planned Mileage To Transportation Economics

Mileage influences more than dispatch. It can affect customer quotes, carrier negotiations, fuel expectations, accessorial planning, delivery commitments, invoice review, and load profitability. FTM keeps route intelligence connected to the financial record rather than leaving it in a separate mileage tool.

PC*Miler Practical Miles
Commercial route returned
Quote Context
Mileage as pricing reference
Customer Revenue + Carrier Cost + Accessorials
Financial record in FTM
Expected Margin
Planned margin before execution
Actual Margin Reporting
Planned versus actual in Salesforce
Pricing Consistency
Use one route reference during pricing conversations. Consistent mileage supports cleaner discussions with both customers and carriers.
Cost Review
Compare carrier cost with expected route requirements. Route intelligence connected to the carrier pay item supports more informed cost review.
Margin Analysis
Review mileage beside revenue, cost, and operational performance in Salesforce reporting. Mileage supports the decision but does not determine final profitability on its own.
Dispatch planning

Give Dispatchers Commercial Route Context Inside The Load

Dispatchers should not need to manually transfer mileage from a separate routing tool into the TMS. FTM connects route information to the load where assignment, communication, documents, exceptions, and status updates are managed.

Load Record | FTM
Load Number
FTM-20491
Pickup
Dallas, TX
Delivery
Atlanta, GA
Equipment
53′ Dry Van
Practical Miles
782 mi
Est Route Time
~11.5 hrs
State Mileage
Available
Carrier
Apex Transport Inc.
Load Status
Dispatched
Customer Rate
$2,150
Carrier Cost
$1,640
Expected Margin
$510

FTM runs natively on Salesforce, keeping load, customer, carrier, route, financial, and reporting data in one operational environment.

Practical mileage, state mileage, estimated route time, and directions returned from PC*Miler connect to the same load where the carrier is assigned, the customer is billed, and the margin is tracked.

Commercial route intelligence and operational execution become the same record.

Salesforce-Native Does Not Mean Salesforce Required
Organizations do not need existing Salesforce licenses before implementing FTM. Salesforce Enterprise platform can be included as part of the FTM implementation at no additional platform cost.
Planned versus actual

Keep Route Planning Connected To The Final Load Outcome

A planned route is most useful when teams can compare it with what happened during execution. FTM can connect planned mileage with load status, tracking information, documents, customer charges, carrier costs, and reporting.

PC*Miler Planned
Route planning context
  • Practical miles from PC*Miler
  • Planned route time
  • Expected carrier cost
  • Expected margin
FTM Execution Data
Outcome from the load record
  • Completed load status
  • Final documents and POD
  • Customer invoice
  • Actual carrier cost
  • Final margin reporting
PC*Miler provides planned route information before and during load execution. Actual driven mileage, final delivery time, and execution outcomes come from FTM, carrier communications, telematics, documents, or other configured sources.
Operational outcomes

What Changes When Mileage Becomes Part Of The Workflow

Faster Mileage Retrieval
Reduce repeated manual route lookups. PC*Miler mileage is requested and stored on the load automatically, based on the configured trigger.
More Consistent Quotes
Use a common mileage reference during pricing. Practical truck mileage supports more consistent conversations with customers and carriers.
Stronger Dispatch Context
Review practical miles and route time inside the load record where dispatch decisions are made, without switching to a separate mileage tool.
Better State Reporting
Store state mileage for configured reporting workflows. State-by-state mileage can support fuel-tax analysis and jurisdiction review when configured.
Clearer Billing Review
Compare route context with customer and carrier charges. Practical mileage connected to the invoice record supports more consistent billing review.
Improved Margin Visibility
Analyze route mileage beside load revenue and cost in Salesforce reporting. Route intelligence connected to financial data supports better operational analysis.
Built for transportation teams

Useful Across Brokers, Carriers, Shippers, And Mixed Operations

Freight Brokers
Use practical mileage during quoting, carrier rate review, dispatch, customer billing, and margin analysis. One mileage reference across the brokerage workflow.
Carriers
Use commercial route context, estimated duration, state mileage, dispatch planning, and reporting designed for trucking operations.
Shippers
Use consistent mileage and route expectations during transportation planning, carrier cost review, and delivery service analysis.
Mixed Operations
Use one routing and mileage reference across brokerage, fleet, and shipper workflows inside one Salesforce-native platform.
Continue the transportation workflow

Related FTM Capabilities

Quoting System
Dispatch Console
Carrier and Driver App
Customer Portal
Billing and Reporting
Implementation

Connect PC*Miler To FTM With A Controlled Setup

Implementation is configured inside Salesforce using secure credential management and FTM’s integration settings. A sandbox-first approach is recommended before production deployment.

  • An active PC*Miler or Trimble Maps API license
  • Access to the required route-report services
  • Secure credential configuration in Salesforce
  • FTM integration activation
  • Selection of required report types and route settings
  • Sandbox testing before production
  • Production validation
Before You Begin
PC*Miler integration configuration does not require modification of FTM code. Credentials and integration settings are managed through FTM configuration in Salesforce. No sensitive credentials should be stored in unsecured configuration fields or exposed in shared environments.
Available route reports, datasets, features, and licensing requirements are controlled by Trimble Maps and may vary by PC*Miler version, account, region, and add-on license.
FAQ

Common Questions

The integration can request configured PC*Miler route reports and connect returned information such as practical mileage, estimated route time context, state mileage, directions, or route paths to the FTM load record. Available fields depend on the configured implementation and PC*Miler license.
Google Maps provides broad location and mapping context. PC*Miler is designed for commercial transportation routing and mileage workflows, including practical truck mileage, state mileage, and route settings specific to trucking operations. FTM can use either integration for different operational needs.
Once configured, FTM can request mileage when defined load events occur, such as load creation or changes to pickup and delivery information. The exact automation depends on the implementation and licensed PC*Miler services.
PC*Miler route reports can provide state or country mileage breakdowns when the required report type is enabled. FTM can store and use that information in configured reporting workflows.
State mileage can support fuel-tax and IFTA-related workflows, but each customer is responsible for validating its configuration, data, and reporting requirements against applicable regulatory obligations.
PC*Miler offers Hours of Service reporting and estimated arrival capabilities in supported versions and configurations. Availability inside FTM depends on the customer’s license and implementation.
No. Mileage can support quoting and cost review, but final rates also depend on capacity, equipment, market conditions, service requirements, accessorials, fuel, risk, and commercial agreements.
PC*Miler supports directions and route-path reports. Availability may depend on the selected report type, PC*Miler version, and add-on licensing.
Not necessarily. These capabilities may require specific services, datasets, configurations, or premium licenses from Trimble Maps. The current FTM integration can support practical mileage, estimated route time, and state mileage, depending on configuration and licensed services.
The setup generally requires an appropriate PC*Miler or Trimble Maps API license, secure Salesforce credentials, FTM configuration, selected route-report settings, testing, and production validation.
PC*Miler + FTM

Use One Mileage Reference Across Transportation Operations

See how FTM connects truck-specific routing and mileage intelligence to quoting, dispatch, billing, state reporting, and margin analysis inside Salesforce.

Book Executive Demo Explore The Platform
Salesforce-native transportation management since 2016.
Let's Talk!

Thanks for stopping by! We're here to help, please don't hesitate to reach out.

Watch 3-Min Demo
↑