Webfleet integration
Real-time vehicle tracking, driver management and route optimisation from one of the world's leading telematics platforms.
What is Webfleet?
Webfleet is Bridgestone’s fleet management platform, formerly TomTom Telematics. Vehicles carry a Webfleet tracking unit, often paired with a driver terminal on which drivers receive orders and text messages. Other software connects through WEBFLEET.connect, Webfleet’s API — the interface Transportial uses.
What syncs between Webfleet and Transportial
- To Webfleet
Confirmed trips as orders on the terminal
When you confirm a trip, Transportial sends it to Webfleet as destination orders: by default one order per load or unload, or one per stop when grouped execution is switched on. Each order carries the address and coordinates, the planned date and time, and an order text with the trip number, consignments and goods, time window, reference or PIN, TAR, seal and remarks. Pickups and deliveries are sent as their own order type.
- To Webfleet
Documents with the order
Documents on the stop travel with the order to the terminal: up to five files of 5 MB each, as PDF, image, text or Word files.
- To Webfleet
Changes and cancellations
Changes to a confirmed or in-transit trip update the orders already on the terminal, and orders the trip no longer needs are cancelled. Cancelling the trip cancels its orders in Webfleet, or deletes them if you switch that option on.
- Into Transportial
Order status from the driver
What the driver does on the terminal moves the stop along in Transportial: accepted, started, arrived, work finished, departed and finished. A rejected order marks the stop as failed so it can be replanned.
- Into Transportial
Positions and vehicle data
Position, speed, heading, odometer, address, ignition and the logged-on driver, stamped with the time the unit reported them rather than the time they were collected.
- Into Transportial
Driver logon and logoff
When a driver logs on to a vehicle’s terminal, Transportial links that driver to the vehicle; logging off unlinks them.
- Both ways
Driver messages
Messages planners write in the vehicle chat go to the terminal as plain text, and what the driver types comes back into the same chat with a push notification. File attachments are not sent to the terminal.
- Into Transportial
Vehicles and drivers
Vehicles are imported with name, licence plate, VIN, type, fuel type, dimensions and tank size; drivers with their name and tachograph card. Vehicles removed from Webfleet are switched off in Transportial.
How to connect Webfleet
Get your WEBFLEET.connect details: the account name, the username and password of a Webfleet user with API access, and an API key.
Add the Webfleet integration in Transportial and enter them. Vehicles and drivers are imported on the first sync, and Transportial creates the Webfleet message queues it reads from itself — nothing to configure for that.
Plan a trip on a Webfleet vehicle and confirm it. The orders appear on that vehicle’s terminal, and their status comes back on the stops.
Sync frequency and limits
- Order status, positions, driver logons and messages are read from Webfleet’s message queue every 30 seconds.
- Vehicles are refreshed every 3 hours, drivers every 6 hours.
- A queue message is only acknowledged once it is stored in Transportial; if a run fails, the message is picked up again on the next one.
- At most five attachments per order, 5 MB each.
- Once a driver has accepted or started an order, Webfleet no longer accepts changes to it.
Typical use case
A distribution company runs Webfleet units with driver terminals in its trucks. Planners build the day in Transportial and confirm each trip; the loads and unloads appear on the terminal with address, time window, reference and the delivery documents. As drivers arrive, finish and depart, the stops update on the plan board and in customer tracking, and a rejected order shows up straight away as a failed stop instead of a phone call at the end of the day.
Frequently asked questions
Does every stop become a separate Webfleet order?
By default every load and unload is its own order. With grouped execution switched on for your platform, all actions at one stop are sent together as one order.
Can I change a trip after it has been sent to Webfleet?
Yes, while the driver hasn’t accepted or started the order: changes to a confirmed or in-transit trip update the order on the terminal. Once the driver is working on it, Webfleet refuses changes, so cancel the trip and send it again.
What happens when a driver rejects an order?
The stop is marked as failed in Transportial, so the planner sees it immediately and can replan it.
Do orders created in Webfleet itself come into Transportial?
Only if you switch on adopting unplanned actions: they are then added to the vehicle’s current trip. Otherwise they are acknowledged and ignored.
Connect Webfleet to your TMS
Transportial’s integration framework links your operation to Webfleet and any other system you run.