Skip to content

Trucker Path for Fleets + Trimble

Running Trimble? Here Is How Your Drivers Get Truck-Safe Routes

Nothing is prebuilt between Trimble and Trucker Path, and this page does not pretend otherwise. There are two real ways in: your own developers post trips to the fleet API, or a dispatcher plans the stop in Trucker Path and Trimble carries on as the system of record. Trimble stays the system of record; only the route and the driver's app move.

Start Free Trial
TrimbleTrucker Path
Illustration: a trip sent through the fleet API from a dispatch computer to navigation on the driver’s phone.

Via the fleet API · No prebuilt connector

No connector
Nothing prebuilt between Trimble and Trucker Path today
Two ways
The fleet API, or dispatch from Trucker Path
Two products
Trimble sells navigation of its own, so this is a where-is-the-trip-built question

Your situation

You May Already Have Trimble Navigation

Trimble sells CoPilot, its own commercial navigation, powered by PC*Miler. If your drivers already run it, the question is not which one routes around low bridges and weight limits — both are built for trucks — but where the trip is built, what the driver opens, and what else sits on the account. We wrote that comparison out row by row.

Through the fleet API

Your system posts a trip with the stop coordinates and a driver ID, and the route opens in that driver's Trucker Path app. Planned, actual and out-of-route miles read back the same way.

Or dispatch by hand first

Plan the stop in Trucker Path and send it to a driver. Nothing has to be connected, so you can see exactly what a driver gets before committing developer time.

You may already have commercial navigation

Trimble sells CoPilot, powered by PC*Miler. If your drivers run it, the open question is not whether the route is built for a truck but where the trip is created, what the driver opens, and what else sits on the same account.

What else is on the account here

Besides the route: four load boards on one screen, fuel prices and stops along the way, truck parking and weigh station status — in the app the driver already opens. Navigation added to an existing stack does not bring those with it.

Other TMS platforms

The answer is the same shape whichever TMS holds the load: the fleet API, or dispatching from Trucker Path while the TMS stays the system of record.

Reported by fleets running Trucker Path

$84,000-some down to $40,000-someThomas E., Founder of Keller Trucking, on one month of toll bills.
Drivers up to speed quicklyChandler Klein, Sr. Business Analyst at Christenson Transportation.
2,800+ fleets, 45,000+ vehiclesRunning Trucker Path for Fleets on their own trucks today.

FAQ

Is there a Trimble integration with Trucker Path?

Not a prebuilt one. Trimble is not among the TMS platforms Trucker Path has announced a connection with. Fleets running Trimble reach the same result through the Trucker Path for Fleets API, or by planning the stop in Trucker Path and keeping Trimble as the system of record.

We already use CoPilot. Why add Trucker Path?

CoPilot is navigation you add to systems you already run. Trucker Path for Fleets is the dispatch surface itself, and fuel and freight run on the same platform. The full side-by-side comparison is on this site.

What would connecting take?

Your developers post a trip to the fleet API with the stop coordinates and a driver ID. Authentication is a Client Identifier and a JWT. The API takes coordinates rather than addresses, so your system resolves the address first.

Does Trimble stay our system of record?

Yes, if you want it to. The load, the billing and the settlement stay in Trimble. Trucker Path holds the route and the driver's app.

Still have questions?navpro@truckerpath.com

Build a trip on your own truck profile and send it by hand. Trimble does not have to change for you to look. Nothing to connect, seven days, no charge.

Start Free Trial