Fuel surcharge triggers: Why most freight contracts get them wrong
Fuel surcharge clauses are a common feature of freight contracts. The vast majority of such clauses were included with the best of intentions. Rather than having to reopen base rates with shippers from time to time in response to rises in diesel prices, carriers and shippers can agree a formula by which a fuel surcharge is calculated.
While the formula is typically fine, the trigger is rarely challenged until there is a material difference between the contract requirements and what the market is actually charging.
How fuel surcharges are supposed to work
Fuel surcharges are typically structured into the carrier contract in a similar fashion. First, the contract specifies a “base price” for diesel fuel. The contract then references a publicly reported fuel price index (usually on a weekly basis) such as the U.S. Department of Energy average price for on-highway diesel fuel. The contract would then specify a formula to calculate the difference between current fuel prices and the contract-specified base price for diesel fuel. The contract would then specify an “efficiency” or “reverse” factor for the carrier and multiply the above calculated amount by said factor to arrive at the amount of the fuel surcharge to be charged to the shipper. A sample contract section for calculating a fuel surcharge would include a hyperlink to the publicly reported fuel price index for said contract and include a simple example to facilitate verification of said calculated amount by both the carrier’s billing department and the shipper’s accounting department.
The way a fuel surcharge is implemented in a contract is good (i.e., instead of negotiating for a price increase, you implement a transparent way of adding a percentage to the base rate based on a formula and a number that can go up and down wildly).
Where the design actually breaks
A good fuel surcharge formula relies on a good base, which is typically established at contract time and then deteriorates until the end of the contract. There is industry guidance for carriers to negotiate fuel surcharge terms. A contract that establishes a trigger price for a fuel surcharge (e.g. diesel price of $3.50 per gallon) will not increase the fuel surcharge until the price reaches the contractually negotiated trigger price. The formula will then continue to apply after that.
This is not a mistake. It’s a structural problem with the way these agreements are negotiated. We negotiated this agreement over diesel at $3.50 per gallon. We created a simple formula that adds a fixed amount to the base rate for every increase above the agreed-upon base. And even though the base rate is far removed from current prices, the simple formula still applies. The single number negotiated by the two parties so long ago is expected to be accurate forever. It was never designed to fail. It fails because the market continues to move while a single number is expected to remain accurate.
The cost runs both directions
It's tempting to assume this only hurts carriers, since a stale baseline usually means the surcharge undercounts real fuel cost as prices climb. That's true, and it's a real problem, and industry associations representing owner-operators are explicit that a properly functioning surcharge should pass through the full increase in fuel cost, typically stepping up by a set increment for every defined rise in the diesel index above the established baseline, and a baseline that's fallen behind the market breaks that pass-through even when the formula itself is technically still running as written.
But it cuts the other way too. A shipper who locked in a low baseline during a fuel spike, expecting it to reflect an unusually high market, ends up overpaying the surcharge long after diesel prices normalize, because nobody went back to reset the reference point downward either. Both failure modes have the same root cause: a number that was accurate on the day it was signed and has been treated as permanent ever since in a contract governing a cost that moves weekly.
The operational consequence compounds beyond the invoice itself. A carrier absorbing an undercounted surcharge for months has a real incentive to deprioritize that shipper's loads when capacity gets tight, exactly the vendor-trust erosion that shows up as reduced availability during peak season, when reliable capacity matters most. A stale fuel clause isn't just a billing inaccuracy; it's a slow leak in the vendor relationship that a shipper often doesn't notice until it shows up as a capacity problem somewhere else entirely.
Why this is also a planning problem, not just a contract problem
Fuel surcharge accuracy matters beyond the invoice, because the same stale fuel assumption that breaks a contract clause also breaks the route cost modeling a planning engine relies on. A routing system asked to optimize for cost rather than distance, the correct approach, and the one serious freight operations should already be running needs an accurate current fuel cost per kilometer as an input. If that number is pulled from a contract's outdated baseline instead of the actual current index, the "cost-optimal" route the system produces is optimizing against a fuel price that no longer exists, which means it's not actually cost-optimal at all. It just looks like it is, because the model's fuel assumption never got flagged as wrong.
This is precisely why fuel index tracking can't live only in the contracting workflow. It needs to be a shared, continuously updated input feeding both the invoicing calculation and the route planning engine so that a diesel price movement updates the correct surcharge on an invoice and the correct cost assumption behind a route recommendation from the same source of truth at the same time.
What a TMS should actually be doing with this data
The fix isn't asking procurement teams to manually revisit fuel baselines more often, which is the same static-clause problem with a slightly shorter interval, and it still depends on someone remembering to act. The fix is a system that tracks the fuel index continuously and applies it automatically, both to billing and to planning.
This is the specific gap Libera's approach to freight procurement and invoicing is built to close. Rather than treating a fuel surcharge as a static clause someone keys in once, the platform's contract-based billing recalculates each invoice against current terms at the point of generation, so a fuel adjustment reflects live index data rather than a number set at signing and forgotten. That same fuel cost input feeds directly into Libera's capacity and route planning engine, which scores routes on total landed cost rather than distance, a calculation that is only as accurate as the fuel assumption underneath it, which is exactly why that assumption needs to update automatically rather than depend on someone remembering to renegotiate a baseline that's drifted out of date.
The broader principle here connects back to the same discipline behind precision contracting and freight settlement: a contract variable that isn't tracked as live, structured data will eventually drift from market reality, whether that variable is a fuel surcharge trigger, a detention rate, or an accessorial charge. The fix is the same in every case: treat the variable as data that updates continuously, not a number written into a document once and assumed to hold.
What a stale baseline actually costs, in numbers
The abstraction here is easy to underestimate until it's run through actual figures. Consider a contract signed with a baseline diesel price of $3.20 a gallon and a standard formula adding $0.05 per mile to the surcharge for every $0.50 increase in the index above that baseline. At signing, this looked reasonable; $3.20 was a fair reflection of the market at the time.
Two years later, the index sits at $5.35 a gallon, a $2.15 increase over the stale baseline. Under the contract's formula, that should trigger roughly $0.21 per mile in surcharge, which is four full increments above baseline. If nobody has touched the contract, that's exactly what gets applied, and the formula is technically doing its job correctly. The actual failure shows up when the baseline itself no longer represents anything real: a shipper who assumes $3.20 is still a sane "normal" fuel price is anchoring every cost projection, every route plan, and every margin calculation to a number that stopped being true years ago, even though the surcharge formula running on top of it is executing exactly as written.
Multiply that misalignment across a fleet running 300 loaded miles a day, 250 operating days a year, and the fuel-cost assumption embedded in planning and budgeting can run tens of thousands of dollars away from reality per vehicle annually, not because the surcharge formula failed but because the number everyone forgot to revisit was quietly doing all the damage underneath it.
What to ask when reviewing a fuel surcharge clause
If you're auditing your own freight contracts, the useful question isn't whether a fuel surcharge clause exists as nearly every contract has one. The better question is when the baseline was last checked against current market conditions, and whether that check happens automatically or depends on someone remembering to do it manually. A clause that hasn't been revisited since it was signed is not protecting either party from fuel volatility anymore; it's just quietly generating a discrepancy that will eventually surface as a dispute, a margin leak, or a capacity problem, whichever shows up first.
