The #1 App for North American Truckers — Trusted by 1M+ drivers for parking, stops, fuel & weigh stations.
Learn More
Trucker Path for Fleets + PCS
Keep PCS for the Load. Route the Truck Here.
PCS holds the load, the invoice and the settlement, and none of that has to move. What is missing is a route built on the truck's own height and weight, and there are two ways to add one without a connector: the fleet API, or a dispatcher planning the stop here. The load, the invoice and the settlement never leave PCS.
Via the fleet API · No prebuilt connector
- No connector
- Nothing prebuilt between PCS and Trucker Path today
- Two ways
- The fleet API, or dispatch from Trucker Path
- Nothing moves
- Billing and settlement stay in PCS; only the route changes hands
Your situation
Keep Billing Where It Is
Fleets pick PCS for dispatch, billing and settlement in one place, and nothing here asks you to move any of that. The route is the only thing that changes hands: the stop stays in PCS, and the driver gets a truck-safe path to it in the app already on the phone.
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.
Billing is the thing nobody wants to touch
Fleets choose PCS to keep dispatch, invoicing and settlement in one place, and moving any of that is a project. Nothing here asks you to. The stop stays in PCS and the driver gets a truck-safe path to it.
The miles can come back
If you want them, planned miles, actual miles and out-of-route miles per driver are readable over the fleet API and can land back in PCS beside the load they belong to, rather than living in a second dashboard nobody opens.
Other TMS platforms
Fleets Running Something Else
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.
Running Trimble instead?The same two ways in, written for a fleet on Trimble.
Running Alvys instead?The same two ways in, written for a fleet on Alvys.
McLeod connects directlyThe one TMS with an announced navigation connection, rather than the API or dispatching by hand.- Not sure which way inThe TMS hub lays out both routes side by side before you commit anyone to building something.
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
Questions From PCS Fleets
Is there a PCS integration with Trucker Path?
Not a prebuilt one. PCS is not among the TMS platforms Trucker Path has announced a connection with. Fleets running PCS use the Trucker Path for Fleets API, or plan the stop in Trucker Path and keep PCS for the load and the billing.
Do we have to move our billing?
No. PCS keeps the load, the invoice and the settlement. Trucker Path holds the route and the driver's app, and returns planned miles, actual miles and out-of-route miles if you want them back in PCS.
What do our drivers install?
Nothing new. Drivers use the Trucker Path app they already open for truck parking, fuel prices and weigh station status. The stop arrives in that app.
How do truck dimensions get applied?
You set height, width, length, weight and axle count once per truck in Trucker Path. Every trip for that truck routes against the profile, including trips your own software creates over the API.
Still have questions?navpro@truckerpath.com
Send One Stop From PCS to a Driver
Plan it in Trucker Path, dispatch it by hand, and leave the invoice where it is. Nothing to connect, seven days, no charge.
Start Free Trial