How it works

From Geotab credential to first alert in under an hour.

  1. Enter your Geotab database, username, and password on the Odomotive setup screen.
  2. Odomotive pulls your vehicle list and starts polling fault codes every 60 seconds.
  3. Add your preferred shops, pick alert thresholds.
  4. When a vehicle throws a DTC that matches your rules, you get an SMS in seconds.
  5. Reply YES — Odo calls the shop, books the slot, and texts you the confirmation.
What we read from Geotab

Four data types. Nothing more.

Device list. We need to know which vehicles are in your fleet so we can route alerts to the right shop and pull odometer readings. We re-sync the device list every 24 hours.

Fault data (DTCs).The full DTC stream including freeze frames. This is what powers everything — the rules engine, the prioritization, the shop recommendations. We poll every 60 seconds.

Status data (odometer + engine hours). Mileage and engine-hour readings so we can trigger mileage-based PM alerts (oil change due, brake inspection due) and provide accurate context to the shop when Odo books the appointment.

Vehicle position — event-triggered only.When you’ve approved a shop appointment, we read position briefly around the drop-off time to confirm arrival and departure (so the booking auto-closes and you get an appointment-complete confirmation). We do not poll position continuously, we don’t store route history, and we ignore position outside scheduled appointment windows.

What we don’t read from Geotab

Privacy guardrails are hard-coded, not promised.

We do not request, fetch, store, or display any of the following from your Geotab database:

Continuous GPS / route history.Position reads are event-triggered only (around scheduled shop appointments). We don’t track where your trucks go, how they got there, or what route they took. Trip records are out of scope.

Driver hours / HOS. ELD log data, duty status, and trip records are out of scope.

Speeding / harsh-braking events.Driver-behavior data stays in Geotab where it belongs. We’re not in the driver-coaching business.

Fuel transactions. Fuel-card integrations and fuel-tax data are not part of the Odomotive scope.

Frequently asked

Geotab integration questions.

How long does the Geotab integration take to set up?
Five minutes. You enter your Geotab database name, username, and password. Odomotive pulls your vehicle list automatically. You then add your preferred shops and drop-off windows. Total setup including shop configuration: under 10 minutes.
What permissions does Odomotive need on Geotab?
Read-only. We pull vehicle list, fault codes (DTCs and freeze frames), odometer, engine hours, and vehicle position. Position is event-triggered — we read it only around scheduled shop appointments to confirm arrival/departure. We do not pull route history, trip records, driver behavior, harsh-event data, hours-of-service, dashcam footage, or fuel data.
Does Odomotive work with all Geotab GO devices?
Yes. Any Geotab GO device reporting DTCs over the standard Geotab API is supported — GO9, GO9+, GO RUGGED, and the older GO7. No hardware changes, no plugins.
Will Odomotive interfere with my existing Geotab workflows?
No. We connect with a read-only Geotab user. We don’t modify vehicles, users, groups, rules, exceptions, or any other Geotab configuration. Your dispatchers continue using Geotab exactly as they do today.
What happens if I disconnect Geotab from Odomotive?
The access token revokes within seconds. We stop polling immediately. Historical fault data is retained 30 days in case you reconnect, then permanently deleted.
5-minute Geotab setup

Connect Geotab. First alert within the hour.

$239 to start (founder rate, was $299). 90-day money-back guarantee. Locked for life.