Reduce empty miles without accepting an unprofitable backhaul

A truck has finished a delivery and needs to return for tomorrow's committed pickup. A low-rate backhaul would reduce empty kilometres, but it takes the vehicle away from the return route and adds an uncertain unloading wait.

Decide whether the backhaul improves the full feasible plan. The right comparison is incremental revenue against incremental cost and displaced contribution, subject to service and operating constraints. Empty kilometres alone do not measure the quality of the decision.

Define the alternative before calculating a margin

Specify where the truck must be next, by when, and what it would do without the return load. Include the empty repositioning distance, expected time, applicable driver schedule and next assignment.

Use costs that change between the alternatives. Existing lease or salaried costs may matter to overall fleet profitability but should not be added twice as if accepting one backhaul creates them anew. Conversely, an extra day can create real additional expense or use capacity that could earn contribution elsewhere.

Record the proposed pickup, delivery, vehicle suitability, service times, payment terms and additional fees. A load that is not operationally feasible should not be rescued by a positive spreadsheet margin.

Oracle Transportation Management supports service-time calculations using calendars and other inputs. A backhaul comparison needs a compatible time model, especially when the return affects the next journey. Oracle Transportation Management 26C — Rate Service Details

A return load with positive incremental contribution

This illustrative comparison uses one vehicle and a stated decision horizon ending when it is ready for its next assignment. Taxes and fixed overhead allocations are excluded. The fictional cost inputs are not market benchmarks.

Without a backhaul, the vehicle travels 200 kilometres empty at a variable cost of ₹25 per kilometre, costing ₹5,000.

With the proposed backhaul, the return movement totals 260 kilometres. Revenue is ₹8,000. Variable travel cost is ₹6,500, and the extra handling and waiting expense is ₹2,000.

The backhaul improves the leg's contribution by ₹4,500: ₹8,000 revenue minus ₹1,500 extra travel and ₹2,000 extra service expense.

The negative ₹500 leg contribution does not mean the backhaul is worse than the empty return. The vehicle had to reposition anyway. The comparison must retain that baseline.

Include the job that would be displaced

Now suppose the backhaul delays the vehicle enough to miss a committed next pickup. The approved alternative is to cover that pickup with another vehicle, adding ₹6,000 beyond the original plan.

The net improvement becomes ₹4,500 − ₹6,000 = −₹1,500. The load reduces empty movement but makes the combined plan worse by ₹1,500 on these assumptions.

Use either the actual incremental cover cost or the contribution genuinely lost from an unserved opportunity, as appropriate. Do not subtract both for the same consequence. If the cover vehicle would itself displace another job, model the relevant chain rather than hiding it in an unexplained contingency.

A revenue target for the return leg should therefore sit beside a readiness deadline for the next assignment. Operations and commercial teams need to agree which commitments may change and which require explicit customer approval.

Find the uncertainty that changes the decision

In the first scenario, the ₹4,500 advantage is the maximum additional unmodelled cost the backhaul can absorb before it becomes equal to the empty return. If expected extra delay expense rises by ₹3,000, the advantage falls to ₹1,500.

That is a sensitivity calculation, not a guarantee. Check which waiting costs are recoverable under the accepted terms and how likely collection is. A disputed charge is not the same as cash available to pay the trip's expenses.

An optimistic service-time estimate can dominate the financial result. Preserve an adverse but plausible scenario and show whether it breaches the next commitment before accepting the work.

Make the approval specific to the plan

The proposal should show the baseline, accepted load price, changed costs, timing, next-job effect and evidence still pending. Name the person authorised to accept the rate and any change to the existing commitment.

If the price or appointment changes, re-evaluate the same proposal version. A carrier message that confirms the load but changes unloading to the following day is a new decision, not a minor note.

A controlled worksheet can handle occasional backhauls. A TMS can help when it links available vehicles, compatible loads and subsequent assignments. An automated marketplace feed should nominate opportunities only after serviceability and suitability checks; it should not accept loads solely because they fill an empty leg.

Measure the result over the chosen horizon

After execution, compare planned and actual distance, time, incremental expense and next-job readiness. Record outstanding revenue and deductions separately from invoiced revenue. Keep the original baseline so the team can explain why the load was accepted.

Track incremental contribution, late next assignments and additional cover costs alongside empty kilometres. A falling empty-mile percentage can accompany worse service or lower contribution.

When repeated waiting makes an apparently useful lane unattractive, the response may be a different appointment, price or customer term. Rejecting every backhaul is not the only option; the evidence identifies which condition must change.

Accept the return load that improves the complete plan

A sound decision gives the truck productive work without concealing the cost of its next obligation. The comparison remains useful because both alternatives share the same endpoint and accounting boundary.

Next actions

1. Define the empty-repositioning route and next required assignment.
2. Calculate the backhaul's incremental revenue and costs.
3. Add the cost of any displaced commitment once.
4. Test the waiting-time downside and approve the specific plan version.