Most logistics software is written for a forwarder. That is not a criticism — it is simply the larger market, and a forwarder’s needs are well understood. But if you own trucks, a system built for forwarding will feel almost right and stay wrong in the same place for years.
The difference is one sentence. A forwarder sells space on somebody else’s vehicle. A transport company owns the vehicle.
A forwarder’s cost arrives as an invoice from a carrier: one number, one supplier, finished. Your cost is diesel, tyres, a gearbox, a visa, a permit, a border fee and a driver’s wages, spread across months and shared by every job that truck will ever do. Those are not the same problem, and software that treats them the same lets you run profitably by accident, or unprofitably without knowing.
The five things it has to hold
1. What a trip cost. Not what you quoted — what it cost. Fuel, tolls, the border crossing, the driver’s allowance, a night’s parking, the repair on the road. In most systems each of those lands in a different expense account on a different date, and reassembling them for one journey is a manual exercise nobody has time for. A transport system has to make the trip itself the thing costs attach to, or you will never know which work is worth doing.
2. What a truck earns. The same question one level up, over a year instead of a week. Two vehicles doing identical work can differ substantially on fuel and on workshop spend, and that difference is invisible while both are expensed to the same account. A transport business that cannot produce a profit figure per vehicle is buying its next truck on instinct.
3. Fuel, as a measurement rather than a receipt. Fuel is usually the largest cost you have and the one most exposed to loss. Ordinary software records that money was spent at a filling station. It cannot tell you whether that fuel reached the tank, whether it stayed there, or how far it took you. Those are different facts from the receipt, and across a fleet they are worth more than the receipt is.
4. The workshop, as money. A job card is an operational record: what was wrong, who fixed it, which parts went in. That is half the story. The other half is the supplier’s invoice, its tax, and the cost landing against that vehicle’s lifetime running total — which is the number that eventually tells you a truck has stopped being worth keeping. Fleet software tends to stop at the job card; accounting software never learns which truck the bill was for.
5. A running account with each driver. Advances paid before a long run, expenses claimed on return, a float carried for weeks, deductions, sometimes money recovered. This is a real account with a person, it moves every week, and in most transport businesses it is reconstructed at month end from a notebook and a disagreement. It belongs in the system, with a balance you can turn a screen around and show somebody.
The things only a vehicle has
Beyond the money, ownership brings paperwork with dates on it, and those dates have consequences. Registration, insurance, permits, inspections, licences and visas all expire, and any one of them can stop a truck at a border or a checkpoint. A forwarding system has no reason to model a single one of them.
The test is not whether the software can store a document. It is whether it knows the document expires and tells somebody in time to act — and whether a truck can be stopped from being dispatched on an expired one. Storage is a filing cabinet. The warning is the feature.
The question most buyers forget: hired trucks
Almost every transport company runs somebody else’s vehicle sometimes. A peak week, a lane you do not cover, a breakdown. This is where split arrangements come apart, because a hired truck is a forwarding-shaped job — one supplier, one invoice — sitting inside a business that is otherwise asset-shaped.
If your own fleet lives in one system and subcontracted work in another, you can never answer the question that actually matters: is it cheaper to run this lane ourselves or to hire it out? That comparison needs both costs on the same basis, in the same place. Ask a vendor how their system holds a subcontracted trip beside an own-fleet one, and whether the two can be compared per kilometre. The answer is revealing.
Five questions before you buy
Take these to a demonstration. They are deliberately specific, because general questions get general answers.
Show me what one completed trip cost, broken down. Not expenses by category for a month — one journey, with every cost that attached to it.
Show me a profit figure for one vehicle over a year. If it needs an export and a spreadsheet, it does not exist.
How does fuel get into the system, and what happens when the paperwork and the tank disagree? The second half of that question is the half worth listening to.
When the workshop finishes a job, how does the supplier’s bill reach both the accounts and the vehicle’s history? If those are two separate acts of typing, they will drift.
What does a driver’s balance look like today? If the answer is a conversation rather than a screen, that account is not in the system.
Where it has to join the books
One last thing, and it is the one discovered latest. Every cost above eventually has to become an accounting entry — with the right tax treatment, in the right period, against the right supplier. A fleet system that ends at the operational record leaves somebody re-entering all of it into accounting software afterwards, which is both the largest hidden cost of running two systems and the reason the two never quite agree.
The fleet record and the accounting entry should be the same act. If they are not, you have bought a very good notebook.