Backloading is the practice of filling a vehicle's spare capacity on a leg it's already running, instead of sending it out or bringing it back empty. A driver delivers a full load from A to B, then instead of returning to base with nothing on board, picks up a second order along the same route or on the way home. The truck was making the trip anyway, so backloading just makes sure it isn't making it for free.
In practice, it's a matching problem: which of the live orders in the system today actually fit this specific truck's route, timing and capacity, and is the detour to collect one worth less than the empty mile it replaces. Most fleets still solve this with phone calls, driver knowledge, and a dispatcher's memory of who usually runs that lane, which is a large part of why so many trucks still run empty.
Backloading vs. Backhaul: What's the Difference?
The two terms get used interchangeably, but they describe different scopes of the same problem, and mixing them up is a common source of confusion when comparing tools.
- Backhaul usually means a planned return leg, arranged ahead of time, often as part of a scheduled round trip between two fixed points.
- Backloading is broader and more dynamic: matching a live, unplanned order to any leg of a route with spare capacity, not just the return journey.
A backhaul is decided at the planning stage. A backload can be matched in real time, right up until it no longer makes sense for the driver to detour for it, which is what makes it hard to do well by hand and a good fit for automation.
Why Empty Legs Happen
Freight demand is directional and uneven. More goods move into some regions than out of them, seasonal demand shifts lane volumes, and delivery windows rarely line up neatly between an outbound and a return load. The result: UK government figures put HGV empty running at around 28 to 30% of total vehicle mileage (Department for Transport, 2026), a figure that's barely moved in years. Every one of those miles costs fuel, driver time and vehicle wear with no revenue and no delivered goods to show for it.
Why Manual Backloading Doesn't Scale
Matching a backload by hand means a dispatcher checking a route against a list of open orders, estimating the detour, and calling around to confirm, all before the window closes. That works for a handful of trusted lanes a dispatcher knows well. It breaks down at scale: with hundreds of routes and a constantly shifting pool of live orders, no team can manually recompute whether an order fits a truck's remaining capacity and timing fast enough to catch most of the available matches.
The orders that do get matched manually tend to be the obvious ones, on familiar, high-volume lanes. The harder matches, an odd-shaped gap in a route or a smaller order that only pays off with a short detour, get missed simply because no one had time to check.
How Automated Backloading Works
Automated backloading continuously compares a fleet's live routes against the pool of available orders. For each candidate match, it calculates the actual detour cost: extra distance, extra time, and whether the order still fits the vehicle's remaining capacity and delivery window. Only matches where the detour is smaller than the value of not running that leg empty get surfaced to the dispatcher.
This is a live matching problem, not a one-time planning problem, which is why it suits a model trained on a fleet's own routes and order patterns rather than a static rules engine. Order pools shift by the hour, so what counted as a good match this morning may not by the afternoon.
What to Look for in Backloading Software
| Question to ask | Why it matters |
|---|---|
| Does it match in real time, or only at the planning stage? | Most available backloads appear after the route is already underway |
| Does it calculate actual detour cost, or just proximity? | A nearby order isn't a good match if the timing or capacity doesn't fit |
| Is it trained on your fleet's own routes and orders? | Generic matching misses the patterns specific to your lanes and customers |
| Does your data stay yours? | Pooling your order and route data with other customers isn't a given, so check |
Frequently Asked Questions
Is backloading the same as backhaul?
Not quite. Backhaul usually means a planned return leg arranged in advance. Backloading is broader and more dynamic: matching a live, unplanned order to any leg of a route with spare capacity, not just the return journey.
Why do trucks run empty in the first place?
Freight demand is directional and uneven, and delivery windows rarely line up neatly between an outbound and a return load. UK government figures put HGV empty running at around 28 to 30% of total vehicle mileage.
Can backloading be automated?
Yes. Automated backloading continuously compares a fleet's live routes against available orders, calculating the actual detour cost in distance, time and capacity, and only surfaces matches where the detour is worth it.
Backloading, Measured
Anteam Reload™ matches live orders to a fleet's existing routes and calculates the detour automatically, cutting empty legs by 50% and CO2 by 34% per matched delivery. It's trained on the fleet's own routes and order history, not a shared general model, so the matches reflect how that fleet actually runs. Book a demo to see it against your own routes.
Related reading: dynamic route insertion solves a similar real-time matching problem for same-day deliveries, and manual freight quoting breaks down for the same underlying reason, too much to track by hand.