Choosing Software for a Haulage Company: What to Test in the Field
A practical selection guide for fleet owners, freight forwarders and small to mid-sized transport operators: where in your daily flow software actually breaks, what to test in a demo and how, and the real cost shape of the four available approaches. Published by Logistivo, with where our own product sits set out openly in its own section. The short answer for a haulier choosing software: buy the system that holds your most-repeated chain in one single record. In road transport that chain is fixed, namely enquiry, quote, job won, vehicle and driver assigned, documents produced, border crossed, goods delivered, invoice raised, cash collected. If a product breaks somewhere in the middle of it, WhatsApp and spreadsheets will fill the gap again, and the licence you pay for has only added one more place to type the same data. Hauliers most often decide on two misleading axes: the length of the feature list and how good the vehicle tracking looks on a map. What decides the outcome in the field is different, namely whether the driver will actually use that screen, whether rates and customer names stay closed to him, how many times the same weight and package count gets rewritten in a day, and whether work handed to a subcontractor stays visible to you. This guide is published by Logistivo, so read it as candid rather than neutral: the criteria below are written around what happens in the field rather than around any one product, and where Logistivo sits in this comparison — including what it does not do — is set out in its own section. Use the workflow, criteria and four-way comparison to score your own operation, and run any demo on your hardest file rather than the vendor's tidy sample data.
Workflow steps and what software must do
An enquiry lands: from a customer, from your network, or from a tender sheet — Work arrives on three channels at once in a single morning: a call from a regular customer, a system enquiry from a company in your network, and a lane list to be filled in for an annual agreement. Which one you look at first is decided by the vehicles you have free that day and the routes you actually run. Incoming enquiries gathered into one list; filtering by route, country and equipment type; an instant notification to the team when something new lands. For multi-lane seasonal pricing, bulk quote entry from a sheet. Suitable work is spotted late on the list, the customer waits without an answer and the truck runs back empty. Crowded lane lists are too tiring to fill in by hand, so that work is never quoted at all.
The price is built and the quote goes out — The rate per vehicle, border and customs costs and the chance of a return load are added up in someone's head, and the figure is given by phone or email. When the customer negotiates, a second and sometimes a third figure appears, and which one stands becomes unclear. Rate per vehicle and total revenue visible on the same screen; the quote revisable, with the previous figure voided automatically on revision; a record of who quoted what and when, and a measured win rate. The customer cannot tell which figure is current, and the accepted price does not match what ends up on the invoice. You never learn which lane earns or what share of your quotes you win, so pricing strategy stays a matter of instinct.
The job is won: tractor, trailer and driver are matched, or the work is subcontracted — You match a free tractor, a suitable trailer and a driver allowed to run that route. When no suitable vehicle is available, all or part of the job goes to a haulier you know, and coordination goes back to the telephone. Eligibility checks at assignment: are the driver's documents valid, does he have enough days left abroad, is he already booked on another trip on those dates? On subcontracting, continued sight of progress while customer and rate information stays closed to the subcontractor. The same driver is booked on two trips; a driver with an expired visa sets off and is turned back at the border. Subcontracted work drops into 'gone, waiting to hear', and the answer you give your customer depends on the subcontractor picking up his phone.
Loading and paperwork: delivery note, CMR consignment note, packing list, export declaration — At the loading point the package count, weight and packaging are settled, and the same details are written separately onto the delivery note (irsaliye in Türkiye), the consignment note, the packing list and the invoice. In international road haulage the CMR consignment note travels with the goods; as a rule it is made out in three originals and signed by the sender and the carrier. Under the CMR Convention the sender is generally responsible for the accuracy of the particulars entered in the consignment note, including party names, package count, weight and description of the goods, while the carrier's role is to check the number of packages, the marks and the apparent condition of the goods and to enter reservations where necessary. Consignment note and other documents generated from one load record; the driver able to attach document photos from his phone at loading; automatic flagging of any difference in weight, package count or party name between documents. Because the same detail is typed onto several documents by hand, it drifts somewhere, and the drift is usually discovered either at the border or at the bank. The photo taken in the field disappears inside a group chat, and the office goes hunting for it weeks later.
Border, transit and customs waiting — The export declaration is usually lodged at the competent customs office where the goods are located, though which office is competent varies with the country, the procedure and any simplifications in place. The vehicle then travels to the frontier with those documents. At the border the exit formalities are done, the transit document (a T1 declaration or a TIR carnet) is processed where one is required, and the paperwork is checked. If an inconsistency or a missing document appears, waiting is measured in hours and demurrage and delay costs run up with nothing planned for them. A consistency check across documents before the shipment leaves; the customs broker able to join the same file as a party; the ability to check the commodity code (HS code) against destination-country duties and trade measures before departure; automatic counting of the driver's Schengen 90/180 day allowance. The missing document is discovered at the frontier; the vehicle waits, cost overruns the plan and the delivery date given to the customer slips. An unnoticed additional duty turns a trip you thought was profitable into a loss, and a driver over his day allowance is refused entry.
Tracking in transit and keeping the customer informed — The customer asks 'where is the truck' once or twice a day; you call the driver, the driver is on the road and the answer is delayed. The same information is explained three times to three people over the course of a day. Position flowing under the record of the load being carried rather than the vehicle; every status change stored with a timestamp; the customer able to see it from their own screen or a shared link; correspondence held per load and, where needed, translated automatically. The day goes on giving status updates. In a dispute you cannot evidence where the vehicle was and when; a message in a foreign language is misread and the truck goes to the wrong address.
Delivery, POD and equipment return — The goods are unloaded, the signed consignment note copy and proof of delivery are taken, and the trailer is emptied or dropped with the other party. Damage arguments usually start at exactly this point, and responsibility is left unproven. The driver able to attach proof of delivery to the load directly from his phone; delivery time and place captured automatically; a photographic handover record when a trailer changes hands, with the responsibility window tracked. The signed consignment note reaches the office weeks later, no invoice can be raised until it does, and collection is delayed. Because nobody can prove at which stage damage occurred, the deduction is usually charged unfairly to the last driver.
Settlement, invoicing, collection and closing the ledger — The trip ends and the freight invoice is raised; the subcontractor's settlement and the driver's expenses are deducted. The customer pays on terms or does not, and in most firms this whole stage runs in a completely different program. The invoice generated from the load record; account balance and receivables ageing updating by themselves when a collection is marked; support for the e-invoicing format your EU customer's system accepts; driver expenses charged to the correct side. The same figure is keyed three times into operations, invoicing and accounting, and errors compound. Overdue receivables grow unnoticed and break cash flow; a cross-border invoice rejected on format grounds stretches collection out over months.
Selection criteria
The dispatch core: checking driver and vehicle eligibility at the moment of assignment — A haulier's day is spent deciding who drives what and where. If a system merely records that assignment, it is keeping a ledger; if it checks the driver's document validity, the days he has left abroad and the vehicle's availability while you assign, it is doing dispatch. The difference between the two is a truck turned back at a border after it has already left the yard. Set up a driver whose visa expires shortly and whose allowance for days abroad is nearly used up, then try to assign him to a new trip: does the warning appear on the assignment screen itself, or must you open a separate documents page to see it? Repeat with a second trip whose dates overlap, and note exactly what the system says.
The field step a driver can complete without asking anyone — Most transport data is produced behind the wheel: loading confirmation, document photos, position, proof of delivery. If the driver cannot manage that step alone, the data reaches the office late, incomplete or never, and the operations team spends the day collecting it by phone. The driver interface is the most underrated line item in haulage software and the one that kills the most projects. Install the demo account on your own driver's phone and, without standing next to him and without talking him through it, ask him to move a load to 'loaded' and attach a photo of the CMR consignment note. Can he finish it alone on the first attempt? Note where he gets stuck, because that step will repeat on every single trip.
Commercial data kept closed to the driver and the field — The moment you give a driver an account so he can update a load, most setups also open up your freight rates, your customer list and your correspondence. Once that information leaves the building it does not come back, and it usually lands with your nearest competitor. Permission separation is not an advanced feature here; for a haulier it is the entry condition. Log into the demo with a driver account and go looking on purpose: freight rate, customer company name, account balance, office chats. If you can see a figure or a customer name on any screen, that setup is leaking your commercial directory.
Position flowing against the load record, not just against the vehicle — A haulier's customer asks 'where is my consignment', and that question can only be answered if position is attached to that load's record. When position lives on a separate map, there is no shareable answer for the customer and the moment of delivery never gets recorded either. If you already run in-cab hardware, the question becomes: can that data be tied to the trip record, and in what form? Open a load in the demo, assign a vehicle, and build the customer-facing view yourself: if there is a share link, open it on your own phone without logging in; if not, invite a second user to the demo with customer permissions and look from that window. Can you see that load's position and status but not the rate or your other customers? Also check whether the time and place of 'delivered' are captured automatically.
Quote arithmetic: rate per vehicle, revisions, and a win/loss trail — In haulage the price is usually discussed per vehicle and then moves once or twice in negotiation. If the software holds only a single total figure, the accepted price and the invoiced amount will drift apart, and you will never learn which lane earns what. A sales process with no measured win rate is a sales process run on instinct. Quote a three-vehicle enquiry with a price per vehicle, then revise the price. Check three things at once: does the total revenue update by itself, does the previous quote become void automatically, and does the other side see one single current figure?
Documents generated from one record, with a consistency check before dispatch — In international road transport the consignment note travels with the goods, and the same weight, package count and party details are also written onto the invoice, the packing list and the delivery note (irsaliye in Türkiye). Copy that information by hand and it will drift somewhere, and the drift is discovered either at the border or at the bank. Generating paperwork from one record cuts that drift off at source; how much time and how many corrections it actually saves you is something only your own document volume can tell you. Upload a real invoice and packing list from your own archive and deliberately change the package count on one of them: does the system catch the difference before you point it out? Then try producing the CMR consignment note from the same load record without keying any data again.
Visibility and an information wall when work is passed to a subcontractor — When you run out of capacity you hand work to another haulier, and at that moment two things are needed at once: continued sight of his progress, and no sight for him of your customer or your rate. Most software either never models this or sets it up as 'a second customer'. If you run your own fleet and never subcontract, lower this criterion; if you pass on a meaningful share of your work, raise it to critical. Hand part of a load to a second haulier, then look from his account. The correct outcome is this: the subcontractor should not see your customer or the rate you quoted that customer, while you should see his status updates without having to phone him.
Expiry calendar and proactive alerts for vehicle and driver documents — Insurance, roadworthiness tests, passports, visas and professional competence cards expire quietly, and the place you notice is usually a border post or a roadside check, at which point the trip is cancelled. Storing those dates is not enough; the system has to come and tell you. A warning you only see once you open the screen does not count as monitoring. Enter a driver visa and a vehicle inspection that both expire in two weeks, then log out and wait a few days. Does the alert reach you by email or notification on its own, or do you have to go looking for it?
Settlement, invoicing, collection and ledger closing running off the same record — In haulage the money is earned on collection, not on completion, and between the two sit the freight invoice, the subcontractor settlement and the driver's expenses. If operations live in one program while invoicing and ledgers live somewhere else, the same figure is keyed two or three times, errors compound and overdue receivables grow unnoticed. If you serve EU customers, issuing the invoice in the e-invoicing format their side accepts directly affects how fast you get paid. Raise an invoice from a completed load in the demo and mark it as collected. Do the account balance and the receivables ageing update in that one action, or do you end up entering the same amount again on an accounting screen?
Comparing the approaches
Manual coordination by phone, WhatsApp and spreadsheets — Small operators running a single lane, turning a handful of trips a month, who know every vehicle and driver by name; also seasonal businesses whose operation stands still for much of the year. As long as everyone still knows everyone, flexibility outweighs the overhead. The cost accumulates in people and in mistakes rather than in licences: a truck standing at a border, an invoice raised late, an overdue receivable nobody spotted, and the extra operations staff hired as you grow. None of it appears as a budget line, which is exactly why it looks free.
General-purpose software plus a spreadsheet system (bookkeeping package, ERP add-on, templates) — Companies whose accounting side is already settled and who try to squeeze transport into the same package; or businesses with an operations manager who enjoys building spreadsheets and wants to shape the process by hand. The subscription line looks cheap; the real spend is the time of whoever builds the sheets and repairs them each time they break. That labour is never invoiced, so it is never measured, and when the person leaves, the cost of rebuilding the whole arrangement arrives in one lump.
Single-purpose point tools (vehicle tracking only, document archive only, bookkeeping only) — Hauliers whose pain sits in one place: everything runs except vehicle position, say, or only the consignment note and invoice archive is falling apart. It also makes sense if you accept moving data between tools by hand, or can free up one person to do exactly that. Each tool means a separate subscription, a separate contract and a separate support line, plus the hours spent carrying data between them by hand. Do not decide on instinct: put the monthly fees, the transfer time and the renewal dates of the tools you already run into one table, then set that total beside a quote for a single end-to-end platform.
End-to-end transport management platform (TMS) — Hauliers and freight forwarders running the same lanes again and again, with their own fleet, with subcontractors or with both, doing international or multi-stop work. If you can see that the dispatch desk is held up by phone calls as trip numbers climb, this is your column. Being able to get drivers onto an app is a precondition. The visible spend is one subscription plus setup and training effort; what actually decides the answer is not the shape of the pricing model but the number that model produces at your volume. Quote the same product twice, once against last year's real volume and once against your growth case; only at the end of those two sums does it become clear whether per-user, per-vehicle, per-load or flat pricing stays cheaper.
Common buying mistakes
Leaving telematics data and the trip record disconnected — In-cab tracking units, tachographs and fuel sensors do real work in haulage: tachograph data for driving and rest compliance, a level sensor when fuel loss is suspected, and position continuity from the hardware when the driver's phone is off or out of charge. The problem is that this data is never joined to the trip record; the map sits on one screen while the load's status and paperwork sit on another, and the office spends the day merging them. Do not frame the decision as 'telematics or transport software'. Ask both candidates whether they can attach your existing device data to that load's record, and in what form.
Buying a field interface your driver will never use — Office screens are impressive in a demo, because the demo is shown by an office person to an office person. Yet most transport data is produced behind the wheel, and if the driver side is clumsy the field half of the system never fills: no position, no document photos, no delivery time, and the office collects data by phone exactly as before. Even the onboarding step matters, because a long registration and password flow can end adoption on its own. Test the decision with your most reluctant driver rather than your keenest, and try to get a trip completed without standing next to him or talking him through it.
Not recalculating the pricing model against your own volume — Four models are common and none is right or wrong on its own. Per-user pricing is cheapest in a small team, climbs as the team grows and can push firms into sharing one login. Per-vehicle pricing drops your spend automatically when the fleet shrinks and raises it as the fleet grows. Per-load pricing shifts risk to the vendor in a quiet season, takes a bigger share in a busy month, and can blur your own cost while you are quoting. A flat package does not punish growth but carries the highest unit cost at low volume. The measure is not the shape of the model but the twelve-month total: price every candidate twice, once against last year's real volume and once against your growth case, and put setup, training, data migration, extra modules and support tier into the same table.
Adopting software while keeping the old arrangement open — The most common migration error is buying the system while keeping the field and the paperwork in a group chat. Two parallel records never become two complete records; both end up half filled, nobody knows which one is right, and by month end neither is trusted. Set a cut-off date: after it, the status, photos and documents of any new trip live only in the system, and the group chat stays a communication channel rather than a record store. In firms that never announce that rule clearly, the new system usually becomes a second archive within weeks.
Finding out afterwards that you cannot get your data out — Firms study how easy it is to get in and ignore the exit door. When you want to change systems years later you need three separate things: operational history, ledger and invoice movements, and the uploaded document archive. In most systems the first two can be dumped to a table, but thousands of consignment note and invoice images cannot be downloaded in bulk, which makes leaving impossible in practice rather than in theory. Before signing, request the format, scope and price of all three in writing, and have a small export run on the demo account.
Watching the demo on the vendor's prepared data — In a prepared demo dataset everything works: addresses are clean, documents agree, the driver co-operates. Your operation is not like that. You have half-written addresses, handwritten packing lists, package counts that change after loading and a consignment note that surfaces two days later. So do not watch the demo, use it: pick last month's most troublesome file, upload its real documents, assign your real driver and run the process to the end. You only find out where a candidate breaks by feeding it your own messy data.
Frequently asked questions
Does a haulage company really need software, and at how many vehicles?
The threshold is not vehicle count but trips and handovers per unit of time. A firm running intensive trips with few vehicles can carry a heavier coordination load than one running occasional trips with many. The practical measure is how many calls it takes to organise one trip, and how many separate places the same information gets written. If a large part of your day goes on answering 'where is the truck', 'have the documents arrived', 'has it been invoiced', log that time for a week, multiply it by your staff cost and set it against a candidate's monthly fee. Fleet size on its own tells you nothing.
What is a TMS, and how does it differ from fleet tracking software?
A TMS, a transport management system, manages the commercial and operational life of a trip: enquiry, quote, job acceptance, vehicle and driver assignment, documents, status, proof of delivery, settlement and invoicing. Fleet tracking software follows the vehicle's position, speed and route history. One answers 'where is the truck', the other answers 'where is the job'. They sit in different layers and do not replace each other, and plenty of firms run both. What decides the value is whether the position data can be tied to a specific load record.
I already run vehicle tracking hardware. Do I still need transport software?
You do not need to throw the hardware away; the question is whether that data can be attached to a trip record. There are things the hardware genuinely does better: driving and rest compliance from tachograph data, fuel loss monitoring from a level sensor, and position continuity when the driver's phone is off or flat. What the device cannot know is the commercial side, namely whose goods these are, at what rate they were taken, whether the paperwork is complete and whether the invoice has been raised. Ask any candidate whether it can ingest your device data and in what form; if it cannot, the office will keep merging two screens.
My drivers are not technical. Will they really use a mobile app?
What decides adoption is not a driver's fondness for technology but how many taps the app needs to do a job. If the driver side is built around one screen, large buttons and single-tap status updates, adoption is high; if it needs menu navigation, form filling and a long registration, use collapses fast. Count the onboarding step too, because a lengthy password and verification flow can sink adoption on its own. Before you buy, pick your most reluctant driver and let him run the demo, then let his result decide.
I have no trucks of my own; I work as a freight forwarder with subcontractors. Does a TMS suit me?
It does, but the centre of gravity shifts. For a forwarder without a fleet the vehicle and driver assignment module is secondary; what matters is sourcing capacity, visibility over subcontracted work, the document chain and ledger discipline. Look at four things: when you hand work over, can you see the subcontractor's progress without phoning, does your customer's name and your sell rate stay hidden from him, and do the amount you charge and the amount you pay him sit side by side in the same record? If those work, the system suits you without a single truck on your books.
What does transport software cost, and how do the pricing models differ?
Quoting a single figure or range would mislead you, because most products do not publish list prices and quotes are built around users, vehicles, modules and service level. Compare on four models instead: per user, per vehicle, per load or transaction, and flat package. Ask every candidate for a written quote against the same scenario, namely your own vehicle count, user count and monthly trips, then line up the twelve-month totals. Ask separately about the invisible items: setup, training, data migration, extra modules, support tier, and any charge for exporting your data when the contract ends.
Do I have to drop my existing bookkeeping and e-invoicing package?
Not necessarily, but decide at the outset who carries data between the two systems. In practice there are three routes: the transport software raises the invoice and pushes it to accounting; the accounting package stays the master record and the transport side only prepares the settlement; or both are full-scope and one of them is switched off. The worst outcome is the arrangement nobody decided on, where the same invoice is keyed by hand in both places. Do not start the migration before that decision is made.
How much does moving to software stop the operation, and how do you do it?
Done properly the operation does not stop, because the migration starts from today rather than from history. The practical route is this: do not try to carry the old archive across, open new trips in the new system and finish running jobs the old way. In the first phase pick one lane or a few vehicles as a pilot, bring those drivers onto the app, then widen the scope. Set one single cut-over date for account balances and open invoices. The critical thing is not to keep both arrangements alive forever.
What should happen in the software when I subcontract a job?
Two things at once: you keep seeing, he does not. The subcontractor should see only the leg handed to him, the addresses and the rate you agreed with him; your customer's identity, the rate you gave that customer and all other correspondence must stay closed. You, meanwhile, should see his status updates, his uploaded documents and the proof of delivery without making a call. On top of that, what you charge and what you pay him should sit side by side in the same trip record, not in a separate spreadsheet at month end. Without those three, the subcontracted job has left your control.
Can I move my data to another system later?
Ask before you sign, because asking afterwards gives you no leverage. Clarify three things separately: operational data (load history, statuses, quotes), financial data (invoices, collections, ledger movements) and the uploaded file archive (consignment notes, invoice images, proofs of delivery). Request the format, the scope and any charge in writing for each one, then have a small export run on the demo account. Systems that cannot bulk-download the document archive make leaving impossible in practice rather than in theory.