Most Bangladesh logistics operators run mixed fleets — company-owned units for core lanes, vendor trucks for peak season, specialised equipment, or trial routes before capital commitment. The mix adds flexibility but destroys margin when owned and hired trips follow different control rules. Vendor movements tracked on WhatsApp while owned fleet uses formal trip desk guarantee billing disputes, fuel leakage, and owner settlement delays that shrink capacity exactly when you need it.
Cost control in mixed fleets is not choosing own versus hire philosophically — it is applying identical trip proof, fuel documentation, assignment audit trail, and settlement schedule regardless of asset ownership. Economic choice between own and hire follows volume stability, SLA intensity, and capital availability — not dispatcher convenience.
The framework below helps transport managers decide when to expand owned fleet, when to contract hire, and how to govern both without doubling administrative load.
Tax and regulatory treatment of hired versus owned units affects true cost comparison — involve finance and external advisor when scaling either direction. Some operators maintain “anchor” owned fleet for SLA clients and flex hired capacity for variable volume; the ratio should be reviewed quarterly against achieved cost per km and SLA hit rate, not set once in a strategy deck. Document why each major lane is owned or hired so new transport managers inherit reasoning, not folklore.
During negotiation with vehicle owners, share your proof and settlement standards upfront — owners who refuse trip record discipline will cost more in disputes than their quoted rate saves.
When hiring beats owning
Short peak demand — Ramadan FMCG surge, harvest windows, construction season spikes — reduces capital risk through hire. New lanes under commercial trial where volume is uncertain favour vendor capacity until route profitability proves out. Specialised equipment needed occasionally (reefer, low-bed) may cost less per trip hired than owned idle months.
Hire also transfers maintenance downtime risk when contract terms are clear — but only if vendor SLA and proof standards match owned fleet.
- Peak factor above 130% of baseline for fewer than eight weeks
- New client lane with unproven volume twelve-month forecast
- Equipment utilisation below 50% if owned
When owning beats hiring
Core lanes with stable volume, strict SLA clients, and need for driver training and brand consistency favour owned fleet. Long-term cost per km often favours owned units above utilisation threshold — model including finance cost, not diesel alone. Clients requiring dedicated branded vehicles or integrated GPS reporting rarely accept vendor variability.
One trip record and dispatch path for both
Vendor trips enter same requisition, approval, assignment, live follow-up, and close process. Parallel informal dispatch guarantees duplicate billing, missed stops on invoice, and impossible dispute resolution. Vendor master includes rate table, fuel rules, settlement cycle, and document requirements — not only phone contact.
Separate fuel rules documented per ownership type
Vendor may receive fuel cash, fuel card, or all-in rate including fuel — each model needs explicit logging duty. Who pays, who logs litres, how km is verified, and variance threshold before hold payment must be contract-visible. Applying owned-fleet pump rules to all-in vendor rate double-counts or misses leakage.
Owner settlement on schedule tied to closed trips
Delayed vendor payment loses capacity in peak weeks — owners prioritise operators who settle predictably. Automate settlement from closed trip, agreed rate, and documented deductions. Dispute window short and evidence-based; endless open queries push owners to competitors.
Compare true cost per km including admin and leakage
Hired rate quoted per trip may exclude idle waiting charges, fuel surcharges, toll surprises, and ops time managing informal vendors. Owned cost includes depreciation, insurance, workshop, and supervisor attention — full comparison prevents false economy.
Governance rhythm for mixed fleet
Monthly mixed-fleet review compares owned versus hired cost per km on overlapping lanes — shift volume when hire consistently beats own on stable lane or own beats hire on SLA-critical account. Vendor scorecard: on-time proof, fuel compliance, settlement timeliness — drop chronic poor performers before peak season when alternatives scarce.
Legal and finance sign off on vendor contract template annually — informal verbal hire terms explode in dispute when accident or fuel disagreement occurs mid-season.
Track percentage of trips on hired fleet weekly during non-peak — creeping hire dependency without SLA review may signal under-investment in owned core lanes.
Common mistakes to avoid
Treating vendor trips as “outside system” because owners resist software — choose vendors who accept proof standards or accept dispute cost. Another mistake is peak hiring without pre-booked capacity; spot market rates spike and SLAs break. Do not mix all-in and fuel-reimburse models without driver-level clarity — reimbursement fraud concentrates where rules blur.
Avoid owning vehicles for lanes you are about to lose commercially — utilisation cliff follows contract exit.
During contract renewal with vehicle owners, revalidate proof standards and settlement cycle — relationship familiarity should not erode documented controls that protect both parties when dispute arises.
Quick action checklist
- Model own vs hire cost per km with full cost stack quarterly
- Route all vendor trips through same dispatch and close workflow
- Document fuel and toll rules per vendor contract type
- Set settlement cycle and dispute window in vendor master
- Pre-book vendor capacity six weeks before known peaks
- Compare branch mix of owned vs hired against SLA performance
- Review vendor concentration risk — too few owners equals bargaining weakness
See rental and owner billing capabilities in Autonemo solutions, logistics-specific workflows on logistics transport, or book a demo for mixed-fleet control room setup.