How LTL and FTL move freight
Less than truckload (LTL) freight shares a trailer with shipments from other shippers. A local driver picks it up, it crosses the dock at the origin terminal, rides a linehaul trailer to one or more break bulk or destination terminals, and goes out on a local delivery truck. Each handoff is a chance to scan the freight, and also a chance for delay, damage or misrouting.
Full truckload (FTL) freight fills a trailer, or at least pays for one, and goes directly from pickup to delivery with the same truck. There are no terminals in between, so there are no terminal scans. Visibility depends on where the truck is, and that depends on how the carrier shares location data.
What LTL tracking shows
LTL status comes from the carrier's own scans, all tied to the PRO number.
| Event | Usually available | Notes |
|---|---|---|
| Picked up | Yes | Often posted when the driver returns to the terminal, not at the dock |
| Arrived at origin terminal | Yes | First dock scan |
| Departed terminal | Yes | Freight loaded on a linehaul trailer |
| Arrived at intermediate terminal | Often | Break bulk or hub handling |
| Arrived at destination terminal | Yes | Freight is in the delivering service center |
| Out for delivery | Usually | Loaded on a local truck |
| Delivered with POD | Yes | Signature and delivery receipt, often with an image |
| Exceptions | Yes | Appointment required, refused, OS&D, reweigh, held |
The estimated delivery date usually comes from the carrier's transit time for the lane and may only change when the freight misses a linehaul.
What LTL tracking cannot show
- The freight's location while it rides on a linehaul trailer between terminals.
- Whether the freight made the planned linehaul or is still on the dock, until the next scan arrives.
- An exact delivery time before the freight is out for delivery.
- Details of damage until the delivery receipt is posted.
The practical consequence is that a day without a new event is often normal on a long lane. What matters is whether the freight is sitting at the same terminal longer than it should. If an LTL shipment shows arrived at destination terminal and nothing else for more than a business day, the usual causes are an appointment requirement, a capacity problem at the terminal or a delivery attempt that was not recorded yet. Our guide what is a PRO number explains these exceptions in more detail.
What FTL tracking shows
FTL visibility is built on location updates rather than scans. Those updates can come from several sources.
- The carrier's ELD or telematics system, shared through an integration.
- A driver app that reports the phone's location, often required by brokers.
- The carrier's own tracking page or API.
- Check calls, where a dispatcher or broker phones the driver and records the answer.
When location data flows, FTL tracking can show the truck's position on a map, the distance to the consignee, a computed ETA, and arrival and departure at pickup and delivery using geofences. That level of detail is useful for appointment management and for warning a customer receiving dock about a late truck.
What FTL tracking cannot show
- Location for carriers that do not share ELD data and drivers who do not run a tracking app.
- Reliable updates in areas with poor mobile coverage.
- Detention time at the shipper or receiver, unless arrival and departure are captured.
- Whether the trailer was actually loaded or unloaded, as opposed to the truck simply being nearby.
- A proof of delivery image until the carrier or broker uploads it.
Small carriers in particular may offer nothing beyond a phone number. In that case your visibility is as good as your last check call.
LTL vs FTL tracking side by side
| Question | LTL | FTL |
|---|---|---|
| Main reference | PRO number | Load ID, BOL or PRO from the carrier |
| Source of status | Terminal and driver scans | ELD, driver app, carrier API, check calls |
| Update rhythm | At each handling step | From every few minutes to a few times a day |
| Map position | Rarely | Yes, when location data is shared |
| Typical blind spot | Linehaul between terminals | Carriers without location sharing |
| Delivery ETA | Carrier transit standard | Computed from location and distance |
| POD | Delivery receipt from the carrier | Uploaded by carrier or broker |
| Most common exceptions | Appointment, OS&D, reweigh, refused | Late to pickup, late to delivery, detention |
Partial truckload and volume LTL
Between the two sits volume LTL and partial truckload. Some carriers move these shipments on their LTL network with terminal scans, others move them direct on a dedicated truck with location tracking. Ask how a quote will move before you book, because it decides which tracking you will get.
Getting one view across both modes
Most shippers use both modes, plus parcel for small orders and ocean or air for imports. The problem is not a lack of data but its shape: LTL arrives as scans tied to PROs, FTL as locations tied to loads, and each carrier names events differently. Teams end up with LTL in one spreadsheet, truckload status in a broker portal and email threads for everything else.
A useful setup normalizes both into the same milestones (picked up, in transit, at destination, out for delivery, delivered, exception) so the whole operation can be filtered and alerted the same way. On top of that, a predicted ETA with a confidence range gives the team one way to read arrival times across modes.
Choosing between LTL and FTL with tracking in mind
Tracking should not decide the mode on its own, but it is part of the cost of a shipment. LTL is usually cheaper for a few pallets, and you accept terminal handling, scan based status and less control over the delivery time. FTL costs more for the same freight but gives you a dedicated truck, a direct route and, with the right carrier, live location. For time sensitive deliveries to retailers with strict appointment windows, the better visibility of FTL can be worth part of the price difference.
Whichever mode you choose, agree on references before pickup. For LTL, capture the PRO at pickup. For FTL, record the carrier's load number and ask whether location sharing is available for that load. A shipment booked without a usable reference is the one nobody can find when the customer calls.
Common mistakes in truck tracking
- Treating the carrier's original delivery date as fixed, even after a missed linehaul or a late pickup.
- Ignoring LTL shipments with no new event until the customer complains.
- Relying on check calls for FTL loads when the carrier can share ELD data.
- Storing PROs and load numbers in email instead of next to the order.
- Measuring on-time delivery from a spreadsheet updated by hand rather than from carrier events.
What to alert on in each mode
- LTL: no new event for one business day, freight at destination terminal without out for delivery, appointment required, OS&D, reweigh.
- FTL: no location update for a set number of hours, late arrival at pickup, ETA past the delivery appointment, long dwell at a facility.
- Both: delivered without POD after a set time, refused deliveries, any exception on shipments for key customers.
How ShipmentVisibility handles LTL and FTL
ShipmentVisibility tracks LTL by PRO number from national and regional carriers and tracks truckload by carrier reference, with events from both shown on one list next to parcel, container and air shipments. Events are normalized into the same milestone timeline and map view, alerts go by email on every plan and by Slack and webhook from Growth up, and predicted ETAs with a confidence range are available on Growth and above. For larger teams, Pro adds lane level carrier scorecards, as described in carrier on-time performance. See freight tracking for the full picture or compare plans on pricing.