Choose a TMS by how your trucks work: on long cross-border routes, with driving time limits, a return leg and telematics data. Test each criterion on one of your own orders, not on the vendor’s demo. Decide after a trial on one group of routes, once you have compared the plan in the system with what happened on the road.
How to choose a TMS for a trucking company that runs its own trucks across Europe? Put the feature lists aside first, because almost every system has a plan, a map and orders.
This guide takes you through eight criteria. For each one you get three things: why it matters on a long route, what to ask the vendor and what to check during the trial.
We test every criterion on one order: a full truckload from Gdańsk in Poland to a warehouse near Milan, with the return leg through Germany. If you want the basics first, read what a TMS is and how it works. Regulations are stated as of November 2026.
Start with how you work: carrier, forwarder or shipper
A carrier TMS plans your own vehicles, drivers and return legs, while a forwarder TMS manages orders and subcontracted carriers. This guide is written for carriers with their own trucks on mid and long-haul international routes, and the differences between the three kinds of system are covered in a TMS for carriers vs a TMS for shippers.
You can spot transport management software for carriers in the first call with a vendor. Ask them to show the Gdańsk to Milan order assigned to a specific tractor unit and driver, together with the plan for the way home.
If the demo opens with choosing a carrier and the margin on the order, the system was built with forwarders in mind. You can cross that vendor off before you start a trial.
If you run your own fleet and a forwarding desk at the same time, start with the part that brings in most of your revenue. The other one can wait for the next stage of the rollout.
8 criteria that set carrier systems apart on long routes
Choosing a TMS as a carrier comes down to eight criteria that you can check on one real trip. Here is the full list, each criterion with its test:
- Fleet plan with driving time: the same trip for two drivers gives different ETAs.
- The telematics you already have: your trucks show on the map next to their orders from the first days.
- Profit per trip and per vehicle: you see one truck’s result for the week without a spreadsheet.
- Orders, statuses and documents from the road: statuses and the CMR photo arrive without a call to the driver.
- Time windows, plan changes and the return: after you change the unloading time, the plan recalculates itself.
- Your data and leaving the system: exporting the trial orders gives you a complete file.
- Implementation and support in your language: a question asked after hours gets a specific answer.
- Pricing model: you can work out the annual cost for your fleet from a written offer.
The order is deliberate. The first five criteria cover daily dispatch work, and the last three decide what it costs to get into the system and to get out of it.
The criteria do not tell you which modules a system should have. They tell you which carrier need it must meet, and how to check that before you sign a contract.
1. Fleet plan with driving time and cross-border routes
Why it matters on a long route. A trip from Gdańsk to Milan takes more than one day of driving, and the arrival time is set by the limits in Regulation (EC) No 561/2006: daily driving time of 9 hours as a rule, a break of at least 45 minutes after 4.5 hours of driving, and no more than 56 hours of driving in a week. This route also runs into weekend and public holiday truck bans, which we keep in our guide to truck driving bans in Europe.
What to ask the vendor. Does the system build the plan around each driver’s remaining driving time? Where does that data come from: from the tachograph through telematics, or from manual entry?
What to check in the trial. Plan the Milan trip for two drivers: one at the start of the week and one with little left of the weekly driving limit. The plans and ETAs should differ, and the system should show where the rest period falls.
A plan that ignores driving time only looks good on the map. How such a plan can be built automatically is covered in our article on automatic planning of transport orders.
2. The telematics you already have in your trucks
Why it matters on a long route. On a trip through three countries, the dispatcher does not call the driver for every position update, so position and driving time must flow into the plan on their own.
Many companies already have one provider’s devices in their trucks and do not want to replace them along with the TMS. In sales offers, telematics integration is often a single word, while in practice it may cover only some brands.
What to ask the vendor. Which telematics systems does the TMS read, and what exactly does it take from them: position, driving time, statuses? Does the integration with your system already work, or does it still have to be built?
What to check in the trial. Connect your telematics in the first days and check that the truck heading to Milan shows up on the map next to its order. If position or driving time arrives late, the ETA will be late too.
If you are still choosing telematics, we collected the questions for that vendor in our guide to telematics for small transport companies. A device from the same provider as the TMS is described on the ONYX Telematics page.
3. Profit per trip and per vehicle, not just the invoice
Why it matters on a long route. A well-paid trip to Italy can still make a weak week if the truck comes back empty across half of Europe, so the vehicle’s result matters, not only the rate on the invoice.
What to ask the vendor. Does the system calculate the result for each order and for each vehicle over a chosen period? Which trip costs, such as tolls and fuel, does it assign on its own, and which do you have to enter by hand?
What to check in the trial. After the Milan trip and the return through Germany, open that truck’s result for the week. Check that revenue, costs and empty kilometres sit in one place, without an export to a spreadsheet.
Also note when the vehicle’s result becomes available. Profit you only see at month end helps the accountant, but not the decision about the next order.
4. Orders, statuses and documents from the road
Why it matters on a long route. The driver is away from base for several days, and you can only invoice the Italy run once a photo of the signed CMR consignment note reaches the office.
What to ask the vendor. How does the driver send statuses and documents: in a phone app, through the telematics terminal or some other way? Does the driver app work in the driver’s language and with a weak signal in the Alps?
What to check in the trial. Give the app to one driver for a full trip. Count how many statuses arrived without a call from the office, and check whether the documents were attached to the order straight away, ready for invoicing.
Ask the drivers themselves as well. They will use the app every day, so their verdict after one trip tells you more than a demo.
5. Time windows, plan changes and the truck’s return
Why it matters on a long route. The warehouse near Milan will take the truck within a set time window. A queue before the Brenner Pass or a longer loading in Gdańsk shifts the ETA and can push unloading to the next day.
Working with windows is covered in our article on dynamic loading and unloading time windows, and planning the way home in the one on backhaul loads and empty running.
What to ask the vendor. Does the system store a window for every stop on the route and warn you when the ETA falls outside it? Does it show where and when the truck will be free after unloading?
What to check in the trial. Change the unloading time during a trip, or move the order to another truck. The plan should recalculate itself, and the dispatcher should see the effect on the following orders at once.
Also check whether you can see the free truck in Italy before the driver calls after unloading. For a return through Germany, every hour of notice counts.
6. Your data: export, API and leaving the system
Why it matters on a long route. Trip history, customers, rates and unloading times on your lanes are company knowledge. If you ever switch systems, that data has to move with you in a readable form.
In the EU, switching between providers of data processing services is governed by the Data Act, Regulation (EU) 2023/2854. Its recital 81 counts software as a service (SaaS) among those services.
Under Article 25, the contract must describe switching clearly, including the data you can export and a notice period of no more than two months. Under Article 29, from 12 January 2027 providers may not charge customers for the switching process itself.
The rules have exceptions. Article 31 lifts some obligations for services custom-built for a single customer, and that chapter does not cover trial versions offered for a limited time. So check the exit terms in your own contract instead of assuming they follow from the law.
What to ask the vendor. Which data can you export, and in what format? Does the system have an API to exchange orders and statuses with your ERP or a customer’s system? What does the contract say about ending the agreement?
What to check in the trial. Export the orders from the trial period and open the file in a spreadsheet. If dates, rates or statuses are missing, record that as a risk.
7. Implementation, training and support in your language
Why it matters on a long route. Problems come up while the trucks are on the road, for example on a Friday evening before a weekend driving ban. The dispatcher then needs an answer in their own language, from someone who understands transport.
Implementation also takes your team’s time. At the start, most of the work goes into entering vehicles, drivers, customers and regular routes.
What to ask the vendor. Who runs the TMS implementation, and how much work stays on your side? Which hours and channels does the vendor’s support cover, and does it answer in your dispatchers’ language?
What to check in the trial. Ask support two real questions during the trial, one of them on a Friday outside office hours. Write down when and in what form you got the answer.
Also count how many people in your company need training to work in the system. Short training for the dispatcher and the drivers is a good sign that the system fits daily work.
8. Pricing model: per vehicle, per user or per module
Why it matters on a long route. The same system can cost different amounts in two companies of similar size. A per-vehicle fee grows with the fleet, and a per-user fee grows with the office.
On top of the base price come extra modules, implementation, integrations and the driver app. Compare the total cost for your fleet, not the lowest figure on the price list.
What to ask the vendor. What is in the system’s base price, and what costs extra? How does the price change when you add trucks or another dispatcher? How long is the contract term?
What to check in the trial. Work out the annual cost for your fleet from a written offer. Add the team time that the implementation needs.
If the offer does not let you work out the cost without several calls to a salesperson, that tells you something too. Pricing should be as clear as the fleet plan.
TMS for small trucking companies: what matters when you run a few trucks
In a small fleet on long routes, simplicity, one dispatcher and a fast start matter more than the number of modules. Whether a TMS makes sense with only a few trucks is covered in how many trucks you need for a TMS.
Transport management software for a small carrier should give the dispatcher one screen with the plan and the truck positions. Every extra step, such as retyping an order into a second program, takes time that a small office does not have.
With a few trucks, look at four things:
- Start without a server. A cloud system that runs in the browser needs no installation and no hardware of your own.
- Work for one dispatcher. The plan, the map and the orders should be a few clicks away, without switching between programs.
- Telematics without new devices. If your trucks already have devices, check criterion 2 before any other.
- A price that is easy to work out. With a per-vehicle fee, you know straight away what you will pay after buying the next truck.
In a small fleet, the trial in the following sections usually covers two or three trucks on one regular lane, for example to Italy. The owner is often the dispatcher too, so the decision and the test sit in the same hands.
The best TMS for a carrier? Why there is no ranking
The right TMS for a small carrier is the one that passes a test on your lanes, with your drivers and your telematics. There is no universal winner, because a fleet running to Italy and a fleet doing short domestic trips need different things.
Read online TMS rankings with care. Check who wrote them and whether the author sells one of the systems listed. Also check whether the criteria are meant for a carrier, or for a forwarder or a shipper.
Instead of a ranking, use the eight criteria from this guide. Pick two or three systems that meet criteria 1 and 2 on paper, and test them with the plan in the next section.
If you want to include ONYX TMS, here are the facts from our price list. The TMS plan costs 99 zł per month excl. VAT per vehicle, and the TMS + Telematics plan 199 zł per month excl. VAT per vehicle.
You can try the TMS plan free for 30 days. The system runs in the browser with no installation, and shows data from ONYX telematics, Trimble Transics, DBK, Fleethand, frameLOGIC and GBox.
Test before you decide: 14 days on your own routes
The surest way to check a TMS is a two-week trial on one group of routes, run from order to invoice by one dispatcher. The 14 days are our suggestion, because they cover several full international trips with a return leg. A vendor’s trial period may be longer.
The setup, that is choosing the routes, entering trucks and drivers and connecting telematics, is covered in how to start with a TMS. Below, we spread the eight criteria across the days of a trial on the Italy lane:
- Days 1-2: data and telematics. Enter only the trucks and drivers from the chosen group of routes. Check criterion 2: do the trucks show on the map next to their orders?
- Days 3-5: the first full trip. Plan the Gdańsk to Milan trip for two drivers with different driving time left (criterion 1). Give the app to the driver who goes (criterion 4), and ask support your first question (criterion 7).
- Days 6-10: changes on the road and the return. While the truck is on the road, change the unloading time or move the order to another truck (criterion 5). After unloading, plan the return through Germany and note when you saw that the truck was free.
- Days 11-12: results and data. Open the truck’s result for the week (criterion 3) and export the trial orders to a spreadsheet (criterion 6). Ask support the second question outside office hours.
- Days 13-14: cost and scoring. Work out the annual cost from a written offer (criterion 8). Score the eight criteria from 1 to 5 together with the dispatcher and the drivers.
Throughout the trial, after each trip, set the planned ETA against the real arrival time and note the reason for any gap. The spreadsheet stays only as a backup, not as a second plan.
| Criterion | Test | Sign the system passed |
|---|---|---|
| 1. Plan with drive time | Same trip for two drivers | Different ETAs and a visible rest period |
| 2. Telematics | Connecting your own devices | Trucks on the map next to orders from day one |
| 3. Profit | One truck’s result for a week | Revenue and costs without a spreadsheet |
| 4. Orders from the road | A full trip with the driver app | Statuses and CMR with no call to the driver |
| 5. Windows and return | Changing the unloading time mid-trip | The plan recalculates itself |
| 6. Data | Exporting orders from the trial period | A complete file with dates, rates and statuses |
| 7. Support | Two questions, one outside office hours | A specific answer in your language |
| 8. Pricing | Annual cost from a written offer | No line item you have to ask about |
A system that scores below 3 on criterion 1 or 2 is out, even if the rest went well. Without a plan based on driving time and telematics data, the other criteria have nothing to work with.
Mistakes when choosing a TMS
These four mistakes most often lead to a system that looked good at purchase and works poorly on the road:
- Choosing from a forwarder’s criteria list. Such lists skip driving time and the truck’s return, which decide a carrier’s result.
- Judging by the demo alone. In a demo, the vendor shows prepared data. Your route across two borders with a changed unloading time will show more.
- Ignoring the exit. Ask about data export and termination terms before you sign, not when you switch vendors.
- Buying modules in advance. Buy what you will use in the first quarter. Add the rest once your team has the basics down.
How to choose a TMS: summary
- How to choose a TMS: start from how you work, and judge the system by how your trucks run, not by the feature list.
- Check the eight criteria on one cross-border trip, with a question for the vendor and a concrete test.
- Decide after a trial on one group of routes, with a score for every criterion.
The basics of how the system works are in what a TMS is and how it works. If you want to start a trial on your own routes, see how ONYX TMS works.
