Transportation, Freight & Distribution worked example

Backhaul Savings at 86% backhaul success rate: a worked example

What does the result look like when backhaul success rate reaches 86%? The full calculation is worked below with real intermediate numbers. Use it to justify backhaul sourcing, lane matching, or private fleet collaboration between inbound and outbound teams.

The inputs for this scenario

  • Backhaul loads booked: 38 loads (unchanged)
  • Avoided cost per backhaul: 740 $ / load (unchanged)
  • Backhaul success rate: 86 % (raised for this scenario; the documented default is 75)
  • Backhaul coordination cost: 1,200 $ (unchanged)

Working through the calculation

  • Applying the documented formula (Variable backhaul savings = backhaul loads × avoided cost per backhaul × backhaul success rate) to the inputs above produces each figure below.
  • At this operating point the engine returns 25,383 $ for total backhaul savings, the number this scenario is built around.
  • At this operating point the engine returns 668 $ / unit for savings per backhaul load.
  • At this operating point the engine returns 24,183 $ for variable backhaul savings.
  • At this operating point the engine returns 1,200 $ for fixed charges.

How this compares with the baseline

  • Against the tool's baseline example, where backhaul success rate sits at 75% and the headline result is 22,290 $, this scenario comes in 13.88% above the baseline at 25,383 $.
  • A figure at this level is achievable when backhaul success rate is genuinely sustained, not just peaked for a shift. It treats avoided cost as a flat per-load figure, but real avoided cost varies by lane, fuel surcharge and whether the alternative was a spot or contract rate.

Results at a glance

  • Total backhaul savings: 25,383 $ (headline result)
  • Savings per backhaul load: 668 $ / unit
  • Variable backhaul savings: 24,183 $
  • Fixed charges: 1,200 $

Run it with your numbers

  • Every input above is editable in the live Backhaul Savings calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.