Fuel is the one input in freight pricing that changes constantly while most costing models stay fixed. For a transport management system (TMS) for freight carriers, that mismatch is where margin quietly disappears - and in New Zealand's freight market, where fuel price swings hit small and mid-size carriers hardest, the gap between what a job was quoted at and what it actually cost has become expensive to ignore.

The fixed-margin problem

Most carriers set fuel surcharges on a schedule - weekly, sometimes monthly. The surcharge is applied to a rate card that was built on an average, not on the actual cost of running that specific vehicle, on that specific lane, on that specific day.

That's fine when fuel is stable. It's not fine when it isn't.

A run costed on Monday's diesel price and delivered on Thursday can carry a materially different real cost than what was quoted. Multiply that across a fleet doing dozens of jobs a day, and the variance compounds. Nobody sees it as one big loss. It shows up as a slow, steady erosion of margin that's hard to trace back to a cause.

Junk in, junk out, as they say. If the costing input is stale, the margin output will be wrong - consistently, not occasionally.

A worked example

Consider a mid-size carrier running a regular route out of an East Auckland depot, five vehicles, twice-daily cut-offs before 10am and 2pm.

Fuel is quoted monthly. Diesel moves 8% over three weeks - not unusual in recent New Zealand conditions. The rate card doesn't move with it.

By the time the next surcharge review happens, the carrier has run several hundred jobs at a cost basis that no longer reflects reality. The invoice looks fine. The margin doesn't.

Now put fuel cost inside the operating system itself - a live variable tied to the job, not a static line reviewed monthly. Every dispatch recalculates against current cost. The exception isn't the fuel price moving. The exception is a job that falls outside expected margin, flagged at the point of dispatch rather than discovered in a P&L three weeks later.

That's the shift our customer made structurally, and it's a meaningful part of how the business reduced operating expenses by 45%. Not a fuel hedge. Not a rate renegotiation. A system built to treat cost as current, not historical.

What this means for carriers evaluating a TMS

Architecture enables the data capture.

Data enables the recalculation.

Recalculation enables margin control at the point of dispatch, not the point of invoicing.

When evaluating a transport management system, the question worth asking isn't whether it can report fuel costs. Most systems can, eventually, after the fact.

The better question is whether fuel cost is encoded as a live operational variable - one that recalculates job-level margin as conditions change, not one that waits for a monthly review cycle to catch up.

That distinction determines whether cost visibility is a management report you read after the damage is done, or an operating control that prevents the damage from accumulating in the first place.

If your current system can't answer what a job actually cost the day it ran, it's worth asking what number your pricing decisions are really built on.