An OBD tracker can be a practical way to add a company vehicle tracker without booking a workshop installation, but suitability depends on the vehicle, operating pattern and privacy policy. This guide explains how to assess OBD trackers for company cars, pool cars and mixed-use vehicles, what to test before deployment, and which checks to repeat at handovers and fleet audits.
Overview
An OBD tracker is a small GPS device that connects to a vehicle’s diagnostic socket, commonly known as the OBD or OBD-II port. Once connected and activated, it can normally send location and journey data to fleet tracking software over a mobile network. Depending on the device and platform, the system may also provide information such as ignition status, mileage estimates, battery voltage or selected vehicle data.
For a business, the attraction is straightforward: installation is usually quick, devices can be moved between vehicles, and fleet administrators can manage journeys through a web portal or mobile app. That makes an OBD GPS tracker worth considering for pool cars, short-term vehicles, salary-sacrifice or company cars, and fleets that change vehicle assignments regularly.
However, convenience is not the same as universal suitability. An OBD socket may be difficult to reach, permanently occupied by another accessory or positioned where a connected device could be unplugged accidentally. Some vehicles may expose different data, while network coverage, subscription terms and platform settings affect the quality of the service. A company vehicle tracker should therefore be assessed as part of a wider fleet tracking software decision, not selected on the device alone.
Before collecting journey data, establish a clear business purpose, tell affected drivers how the system works and configure private-use controls where the software supports them. For UK organisations, privacy, transparency, access permissions and retention should be considered alongside vehicle security and operational needs. For practical background, see Fleet Vehicle Tracking and GDPR in the UK.
What to track
Compatibility and suitability checklist
Ask the supplier to confirm compatibility for each make, model, year and vehicle type rather than assuming that every socket behaves in the same way. Record the result in the fleet tracking software or an accompanying asset register.
| Area | What to check | Why it matters |
|---|---|---|
| OBD access | Locate the socket, check whether it is occupied and confirm that the device can remain connected without obstructing the driver. | An inaccessible or exposed port can make installation impractical or increase the risk of accidental removal. |
| Power draw | Ask for the device’s standby behaviour, power requirements and any low-voltage safeguards. | A tracker that remains powered while parked should not be assumed to be suitable for every battery condition or usage pattern. |
| Installation | Confirm whether the device is genuinely plug-and-play, needs an activation step or requires an adapter or extension lead. | A simple deployment process reduces errors when vehicles change hands. |
| Tamper detection | Check whether the platform can alert administrators when the unit is unplugged, loses power or stops communicating. | An OBD unit is physically removable, so visibility of disconnection is important. |
| Data accuracy | Test location refresh, journey start and end events, mileage fields and parking locations in normal operating conditions. | Reports should be reliable enough for the stated business purpose; do not rely on untested fields. |
| Private-use controls | Look for privacy mode, business-hours rules, journey classification or driver-controlled privacy features, and confirm exactly what remains visible. | Mixed-use vehicles require a setting that matches the organisation’s written policy and employee notice. |
| Removal between vehicles | Check whether the device can be reassigned in software and whether historical journeys remain attached to the old vehicle. | Correct handover records prevent one vehicle’s activity being attributed to another. |
Questions to ask before buying
- Which vehicle models and operating systems have been tested with the device?
- Which mobile networks does it use, and what happens when coverage is unavailable?
- How often does it send location data, and can the update interval be configured?
- Does the software show unplugged, powered-down and offline states separately?
- Can administrators restrict access by role, vehicle group or depot?
- How are devices activated, returned, replaced and cancelled when a subscription ends?
- Can journey data be exported for mileage records, fleet reviews or internal investigations?
For larger fleets, compare the OBD option with a hardwired GPS tracker. A hardwired unit may be more appropriate where tamper resistance, concealed installation or continuous vehicle integration is a priority. Conversely, an OBD tracker can be more convenient where vehicles are leased, shared or frequently replaced.
Cadence and checkpoints
A controlled deployment is more useful than simply plugging in devices and opening the app. Use the following workflow for each company car or pool car:
- Define the purpose. Document whether the system is being used for vehicle security, allocation, mileage administration, operational visibility, driver support or another specific purpose.
- Record the vehicle. Capture the registration or internal vehicle ID, make, model, driver or pool allocation, device serial number and installation date.
- Check the policy. Confirm how business and private journeys are handled, who can view the data, how long records are retained and how drivers can raise questions.
- Install and label. Connect the device securely, avoid blocking pedals or controls, and label it in a way that helps authorised users identify it without making removal easier.
- Test before release. Create a short journey, check the map position and timestamp, confirm the vehicle identity, and test an unplug or loss-of-power alert if supported.
- Assign access. Give users only the permissions needed for their role. Remove access for leavers and change permissions when responsibilities change.
- Review after handover. When a vehicle changes driver, department or depot, update both the software assignment and the physical fleet record.
- Decommission correctly. At sale, return or replacement, remove the device, close or transfer the software assignment and retain only the records required under the organisation’s policy.
Use a monthly operational check for active devices: review offline units, unplug alerts, unusual gaps in journeys and vehicles with no recent data. Complete a more formal quarterly audit covering serial numbers, vehicle assignments, user access, private-use settings and subscription status. A short checklist is often enough, provided someone owns the task and exceptions are recorded.
Where driving behaviour is also being monitored, avoid treating every alert as a performance issue. Review thresholds, context and repeat patterns before taking action. The guide to driver behaviour monitoring in the UK provides a useful framework for selecting alerts that support constructive conversations.
How to interpret changes
A sudden gap in location data does not automatically indicate deliberate interference. Check the vehicle’s battery condition, mobile coverage, device status, software outage notifications and recent servicing first. If the unit has been unplugged, compare the time with a handover, workshop visit or driver report.
Likewise, a mileage discrepancy may reflect the tracker’s data source, a change in device assignment, an odometer reset or an incomplete journey record. Treat the platform as one operational record and define which source takes precedence for each business process. Do not present an estimated field as an exact measurement without testing it against the vehicle and the supplier’s documentation.
For privacy, interpret visibility settings literally. A setting labelled “private mode” may hide map points, suppress notifications or stop journey storage, depending on the platform. Confirm the behaviour with a controlled test and explain it clearly to drivers. If private use is allowed, ensure the software’s configuration still matches the organisation’s policy after updates or user changes.
Patterns are generally more useful than isolated events. Repeated offline periods may point to a device, socket or network issue. Repeated unplug alerts may justify a different installation method. Frequent vehicle reassignment may indicate that a pool-car process needs better check-in and check-out controls rather than a new tracker.
When to revisit
Review the arrangement at every vehicle handover and as part of a quarterly device audit. At minimum, confirm that the physical device, vehicle record, driver allocation and software assignment still match. Check that leavers’ accounts have been removed, administrator access remains appropriate, and private-use controls reflect the current policy.
Revisit the supplier specification at least every six months, or sooner after a material change. Useful update triggers include a vehicle replacement programme, a new device model, a mobile-network change, an app or platform redesign, altered subscription terms, new privacy guidance, or a change in how the fleet uses company cars. Re-test compatibility rather than copying an old assumption to a new vehicle.
Keep a simple review log with the date, vehicles sampled, issues found, actions agreed and next review date. If OBD trackers repeatedly fail the tamper, power or privacy requirements for a particular group of vehicles, compare hardwired devices or another tracking approach instead of forcing an unsuitable deployment.
The practical next step is to pilot one or two representative vehicles, record the results against the compatibility table, collect driver feedback and only then expand the pool. For wider software selection, compare the required OBD features with the questions in Fleet Tracking Software UK: Features, Costs and Questions to Ask Before You Buy. That process keeps the company car tracker aligned with fleet operations, vehicle privacy and the checks needed to keep records trustworthy over time.