GPS Trackers for Trucks: How to Track a Truck and How to Choose the Hardware
A rigid on regional delivery, a tractor unit on international haulage and a 3.5t van doing last-mile work are three different tracking problems. The device that suits one will usually disappoint on the others.
Discuss your truck projectStart with the decision
Key decisions for truck tracking hardware
Start with the route and vehicle class
Delivery, regional and long-haul vehicles create different reporting, power and interface decisions.
Key point: A rigid on regional delivery, a tractor unit on international haulage and a 3.5t van doing last-mile work are three different tracking problems.
Make installation part of the specification
Confirm voltage, mounting and time off the road before selecting wired, OBD or battery hardware.
Key point: Whether the fleet is 12V, 24V or mixed, and whether trailers or unpowered assets are in scope, belongs in the specification before selection.
Check every market the trucks enter
Supported cellular generation, bands and roaming need checking by destination market.
Key point: Cellular generation and bands in every country the trucks enter, plus each market's shutdown roadmap, must be established before the order.
Decide which fields the platform can use
Vehicle state only helps when each field is mapped correctly in the intended platform.
Key point: Raw position and state become arrival times, geofence alerts and driver reports only once each field is mapped correctly in the platform.
Validate on the real vehicle
Use the same vehicle class, power tap, mounting position and operating route as the wider order.
Key point: A sample that powers on has proved almost nothing about how it behaves after a week on the road.
Most truck tracking projects are specified around the wrong question. "Which tracker is best" has no answer until you know what the vehicle exposes, where it runs, and what the office actually needs to see.
This guide covers how truck GPS tracking works, why delivery fleets and long-haul fleets need different hardware, the checks that decide whether a unit survives its first year, and the commercial terms worth settling before an order.
How to track a truck with GPS
A truck tracker is four things in one housing: a positioning receiver, a cellular modem, a power circuit, and — on some models — an interface that reads the vehicle itself.
- Position is acquired. The unit fixes its position from satellite constellations. Accuracy drops in tunnels, urban canyons and covered depots, which is why antenna placement is part of the specification, not an installation afterthought.
- Vehicle state is read. An ignition sense or digital input tells the device whether the truck is running. Where the vehicle exposes a bus, a CAN/J1939 or FMS connection can add odometer, fuel, engine hours and fault codes.
- Data is packaged and sent. The device batches readings and transmits over cellular on an interval, on an event, or both. Those rules — not the hardware — determine data volume and SIM cost.
- The platform interprets it. Raw position and state become arrival times, geofence alerts and driver reports only once each field is mapped correctly in the platform. This mapping step is where most integration problems surface.
If the office only needs to answer "where is the truck and when will it arrive", a location-only device does the job. Buying a CAN-capable unit for that requirement adds cost, installation time and a dependency on an interface the vehicle may not expose.
Delivery fleets and long-haul fleets need different hardware
This is the distinction most buyers skip, and it drives more of the specification than the vehicle badge does.
| Check | Delivery | Long-haul |
|---|---|---|
| Reporting interval | Frequent under motion — a 5-minute gap is a whole street in a city. | Longer intervals are acceptable; events matter more than density. |
| Power & installation | Van or 3.5t rigid; often leased, so a non-invasive install matters. | Tractor unit or heavy rigid; usually owned, so a wired install is acceptable. |
| Vehicle interface | Low. The van may expose little, and the office rarely uses engine data. | High. Fuel and engine hours change how the fleet is run. |
| Data volume | Higher per vehicle. Worth modelling before choosing a SIM plan. | Lower per vehicle, but roaming across markets has to be checked. |
| Typical vehicle | Van or 3.5t rigid; often leased. | Tractor unit or heavy rigid; usually owned. |
The practical consequence: a mixed operation running both usually needs two device classes, not one. See mixed fleet telematics for how that is handled without ending up with two platforms.
What to confirm before buying truck tracking hardware
Six checks decide whether the device survives and returns what the project needs.
Voltage range
What to establish: Whether the fleet is 12V, 24V or mixed, and whether trailers or unpowered assets are in scope.
If you get it wrong: A unit specified for vans fails on 24V trucks; a wired unit is useless on a drop trailer.
Network & roaming
What to establish: Cellular generation and bands in every country the trucks enter, plus each market's shutdown roadmap.
If you get it wrong: Vehicles report at home and go dark across a border — exactly where visibility mattered.
Vehicle interface
What to establish: Whether the truck exposes CAN/J1939 or an FMS connector, model by model rather than brand by brand.
If you get it wrong: You pay for engine data capability that has nothing to connect to.
Installation impact
What to establish: Wired, OBD or battery; how long the vehicle is off the road; whether a lease forbids permanent wiring.
If you get it wrong: Downtime costs more than the hardware, and lease breaches cost more again.
Enclosure & placement
What to establish: Ingress rating, temperature range, and a mounting position with sky view that is not the first place a thief looks.
If you get it wrong: Intermittent fixes that look like hardware faults but are installation faults.
Reporting strategy
What to establish: Interval under motion, at rest and on event, decided per vehicle class rather than left at factory default.
If you get it wrong: An unexpected data bill, or gaps precisely when the office needs live position.
Match the vehicle and data requirement to a documented starting point
| Vehicle or data need | Starting model path | Existing product page and PDF | Confirm before order |
|---|---|---|---|
| Road fleet with external inputs | C003F-CAT1 for 1-Wire and optional serial or accessory paths. | Product page · C003F PDF | Vehicle power, selected interface, accessories, firmware and platform field mapping. |
| Truck or asset where machine data is required | A300 as an industrial gateway starting point for CAN/J1939 and serial interfaces. | Product page · A300 PDF | Reachable vehicle interface, actual protocol and fields, hardware version, firmware and receiving platform. |
| Drop trailer or unpowered asset | GT76-CAT1 as a battery asset-tracking path. | Product page · GT76 PDF | Battery/module option, reporting profile, mounting, maintenance and route coverage. Wake timing, fresh-position acquisition after sleep and later upload remain separate exact-model tests. |
These are documented starting points, not a promise that every truck exposes the required data. The installation environment, protocol, selected firmware and the actual data source still need project confirmation. OBD is a general category discussed for comparison; it is not in LEXUNYU's current nine-model catalogue and requires a separately verified model and vehicle fit before it can be offered. Record the vehicle, power, data need, model/firmware, source material and platform decoding conditions in the truck hardware selection record (CSV).
Compliance and market fit
Compliance is a market question, not a hardware preference
Two regulatory currents affect truck hardware bought today. The first is the retirement of older cellular generations, which happens market by market and can leave a device obsolete before its warranty expires. The second is tachograph scope in Europe, where the range of vehicles covered on international work has been widening to include lighter commercial vehicles.
Neither is something a supplier can settle for you in the abstract — both depend on which countries the trucks actually enter. We wrote up the current position in EU smart tachograph expansion and the 2G shutdown, and confirm both points against the destination markets before an order rather than assuming catalogue-wide coverage.
Ordinary GPS/CAN data is separate from a verified remote DDD file path; see the DDD project guide.
Vehicle sample validation
Test on the vehicle, not on a desk
A sample that powers on has proved almost nothing about how it behaves after a week on the road. Four things to check:
- Install where it will really go — same vehicle class, same power tap, same mounting position the installer will use in production.
- Confirm the fields, not the connection — check that ignition, odometer, fuel and any sensor values arrive with correct units, not just that the device shows online.
- Point it at your own server — where the model supports it, confirm the data reaches the platform you intend to run, in a shape you can use.
- Run it for days across a real route — reconnection after tunnels and coverage gaps, and behaviour on a border crossing, only show up over time.
The full method is described in sample validation.
Commercial terms worth settling first
| Specification | Value |
|---|---|
| Minimum order | Custom orders start from 100 units. Samples and small validation batches are handled separately. |
| Lead time | Confirmed by model, configuration and order quantity. A configured order and a stock item are not the same lead time. |
| Warranty | 12-month limited warranty from the shipment date shown on the commercial invoice. DOA within 30 days is handled under the existing order terms. |
| Certification | Documents available for selected models; applicable marks confirmed for the specific model and destination market. |
| Platform choice | No requirement to use a particular platform. Devices can be pointed at your own server where the model supports it. |
| Contract term | No multi-year lock-in and no automatic renewal as a condition of buying hardware. |
| Reply time (written) | We reply within one working day. |
Before you contact anyone
The tracker selection check walks through the six checks above, the data usage calculator estimates cellular volume from reporting interval — useful before committing to a SIM plan for a delivery fleet — and the blank field confirmation sheet records what each vehicle class needs. All three are free and usable with any supplier, including ours. Related fleet paths: delivery vehicles, trucks and vans, and China GPS tracker sourcing.
Truck, lorry, HGV: the same vehicle, different words
This page uses truck throughout, because that is what most of our buyers say. It is worth being explicit about the alternatives, because quotes and specifications cross borders and the words do not.
Lorry
the standard word in the UK and Ireland for what North America calls a truck. A "lorry GPS tracker" and a "truck GPS tracker" are the same product.
HGV
(heavy goods vehicle) — the UK regulatory category above 3.5 tonnes. If a specification says HGV, expect 24 V and expect tachograph and driver-hours questions to follow.
LCV
(light commercial vehicle) — the European term for vans and light trucks below 3.5 tonnes. Supply and interface depend on the exact vehicle: use OBD-II only where a suitable accessible port is confirmed, or verify a hardwire route. The wider LCV rollout is covered in more depth on GPS tracking for company vehicles.
Rigid vs articulated
a rigid carries its own body; an articulated unit pulls a separate trailer that needs its own tracker, because it will not stay attached to this tractor.
The hardware questions are identical in every case. What changes with the word is the voltage you should assume and the compliance regime you are buying into — which is why we ask for the category, not the noun.
Carrying temperature-controlled loads changes the specification more than any of the above; that is covered separately on cold chain vehicle tracking.
Frequently asked questions
Choosing the hardware
How do you track a truck with GPS?
A tracker fitted to the vehicle fixes its position from satellite signals, reads vehicle state from an ignition input or a CAN/J1939 connection, and transmits over cellular on an interval or on an event. The platform turns those readings into live position, arrival estimates and alerts once each field is mapped correctly.
What is the difference between a delivery truck tracker and a long-haul one?
Mainly reporting frequency, installation method and whether engine data is worth having. Delivery work needs frequent position updates and often a non-invasive install on leased vehicles; long-haul benefits more from fuel, hours and route records and usually tolerates a wired install.
Do I need a device that reads the truck's engine data?
Only if the office will use it. If the requirement is location and arrival times, a location-only device is cheaper, faster to fit and does not depend on the vehicle exposing a bus.
Will one model cover trucks, vans and trailers?
Rarely. Voltage differences and unpowered trailers usually mean two or three device classes. Trying to standardise on one model is the most common reason a rollout stalls halfway.
What about trucks crossing borders?
Roaming behaviour and the cellular generations supported in each destination country have to be checked before the order. A device that works at home can go quiet across a border.
Can the tracker report to our existing platform?
Where the model supports it, yes. We confirm that capability per model before you commit, so the platform choice stays open after the hardware is bought.
Ordering and support
What is the minimum order quantity?
Custom orders start from 100 units. Samples and small validation batches are handled separately, so testing does not require a production commitment.
How long is the lead time?
Confirmed by model, configuration and order quantity. We do not publish a single figure because a configured order and a stock item behave differently.
What warranty applies?
A 12-month limited warranty from the shipment date shown on the commercial invoice — a date both sides can verify from the same document.
Do you supply certification documents?
Certification documents are available for selected models. Which marks apply is confirmed for the specific model and destination market at order time.