Fleet & Tracking

Know before
they ask.

Live positions, geofence events at pickup and delivery, and two-way driver communication — with the status flowing back into the load record automatically, so nobody has to phone a driver to update a customer.

tracking.freightronics.net
Tractor unit on the highway under GPS tracking Live position · ETAs · POD
What it does

Live position and status

Tracking that reaches the load record and the customer, rather than living in a map somebody has to watch.

Live position

Devices reporting continuously, with location history kept per device — so the question is not just where a truck is, but where it has been.

Geofences

Arrival and departure detected at pickup and delivery rather than reported, with the event written against the load and the stop it belongs to.

Driver communication

Two-way messaging with drivers, and a mobile app that carries documents and stop detail — so a proof of delivery arrives as a record, not a photograph in someone's phone.

Alerts

Alert rules with triggers and per-user subscriptions, so the people who need to know are told and everyone else is not.

TMS integration

Status that arrives on its own

Tracking is only worth the licence if the status reaches the systems and people who act on it. When it does not, someone reads a map and retypes what they see into the load — which is the job tracking was bought to remove.

Tracking events flow into the load record, and out to customers and partners, without a person in the middle. The 214 status your partners expect comes from the same events.

  • Load tracking eventsPosition and status recorded against the load and its stops.
  • TMS integrationA defined integration path rather than a nightly export.
  • Documents on the loadProof of delivery and paperwork attached to the load record.
  • System eventsPlatform-level events kept so behaviour can be explained afterwards.
  • Telematics and ELDProvider integrations feeding the same device and location model.
  • Driver appA mobile app for drivers without a telematics device on the tractor.
  • Device alertsPer-device alert state and notification preferences.
  • Location historyPosition history retained per device rather than only the latest ping.
Devices

Whatever is already in the cab

Fleets rarely get to start clean. There is an ELD provider under contract, some owner-operators on something else, and a handful of trailers with no device at all.

Devices are modelled generically, with telematics and ELD providers integrated alongside the driver app — so coverage is a question of what each truck has, not a single-vendor decision.

Coverage

What is in the box

Devices, geofences, alerts and the driver app.

Live tracking 5

  • Device position reporting
  • Location history per device
  • Load tracking events
  • Stop-level status
  • Map view

Geofencing 4

  • Geofences at pickup and delivery
  • Arrival and departure events
  • Automatic status change
  • Event history on the load

Devices 5

  • Telematics and ELD integrations
  • Driver mobile app
  • Device alerts
  • Per-device notification preferences
  • Mixed-fleet coverage

Alerting 4

  • Alert definitions
  • Alert triggers
  • Per-user subscriptions
  • Device-level alerts

Communication 4

  • Two-way driver chat
  • Info requests on the load
  • Message history
  • Documents and proof of delivery

Integration 4

  • TMS status flow
  • 214 status generation
  • System event log
  • Company and user scoping
Connected

One layer under the whole lifecycle

Tracking is only useful where decisions are made. Events land on the load in the TMS and become the status your partners are expecting.

Bring us your mixed fleet

Company trucks on one ELD, owner-operators on another, and trailers with nothing at all. That is the normal case, and it is the one worth talking through.

Request a demo See all products