How to choose a TMS in 2026: a working checklist for small and mid-size carriers

Most TMS comparisons are written by vendors, and it shows: every list ranks the author first. This one takes a different approach — instead of ranking products, it gives you the questions that separate them. Ask all of these and the shortlist mostly builds itself.

Start from the licence fee, then keep counting

The monthly licence is the number every vendor prints, and for legacy systems it is often the smallest number in the deal. Before comparing licences, get written answers on:

• Setup and onboarding fees. Established Nordic systems commonly quote implementation projects in the tens of thousands of kronor before the first booking is planned. Ask what is included, and what an added user, vehicle or depot costs later.
• Per-integration consultancy. If connecting your telematics, your accounting system or a customer’s EDI is a billable project each time, the integration list on the website is a price list, not a feature list.
• Telematics doubling. Some TMS products are software-only and require a separate tracking subscription per vehicle from a second supplier. That is a second monthly fee, a second contract and a second support queue.
• The exit. Ask, before signing: how do we get our data out, in what format, and at what cost? A vendor that answers this clearly on the way in is a vendor you can leave — which, paradoxically, is the vendor worth staying with.

“All features” versus feature gates

Pricing models split into two philosophies. One charges by scale — vehicles, bookings, users — with every capability available on every plan. The other gates capabilities: route optimisation on the Pro plan, the customer portal on Enterprise, the API “on request”.

Feature gating punishes growth in an unpleasant way: the moment you win a customer who needs EDI is the moment your software bill steps up, regardless of whether your volumes did. If you are a five-truck operation planning to be a twenty-truck operation, model the price at both sizes — and at the size in between, where gated plans tend to squeeze hardest.

The driver is a user too

A TMS that stops at the office door leaves your most expensive data entry to the evening: drivers photographing paper CMRs, dispatchers retyping status calls. Check that the driver app is:

• Included, not a per-device add-on that quietly doubles your per-vehicle cost.
• Usable on the phones your drivers already have — a bring-your-own-device app beats dedicated hardware on cost and on adoption.
• Actually complete: stop list, status updates, photo and signature capture, vehicle checks. If a driver still needs paper for any step, you will get paper for every step.

Compliance is a deadline, not a feature

From 9 July 2027, under the EU’s eFTI Regulation (2020/1056), enforcement authorities in every member state must accept freight transport information presented electronically. Digital consignment documentation is moving from competitive advantage to baseline expectation — and a TMS bought in 2026 will still be your system of record in 2027. Ask any candidate vendor two questions: does it produce a digital consignment note today, and can a third party verify one without calling you? (We wrote a separate guide on what eFTI means for road carriers.)

Where the data lives, and with whom

For EU carriers this is now a procurement question, not an IT preference. Ask where the system is hosted, under which jurisdiction, and whether your data sits in a database shared with other companies or in one that is yours. Per-tenant isolation matters for a concrete reason: your customer list and your pricing are the two most competitively sensitive datasets you own, and they should not share a schema with anyone else’s.

A one-page checklist

1. Total first-year cost: licence + setup + integrations + telematics + driver app, at today’s fleet size and at next year’s.
2. Are features gated by plan, or do you pay for scale only?
3. Is the driver app included, and does it cover the whole job?
4. Digital consignment notes: produced today, verifiable by a third party?
5. Hosting: EU jurisdiction, per-customer data isolation, documented export.
6. Contract: monthly, or a lock-in that outlives your patience?
7. A live demo on your workflows — your lanes, your customers, your pricing — not a rehearsed dataset.

Where navichain stands on these

We built navichain to answer this checklist plainly: every feature on every plan (you pay for scale, not capabilities), the driver app included with two seats per vehicle, digital consignment notes with independent verification, EU hosting with an isolated database per customer, and monthly billing with no lock-in. Pricing is public, from 995 kr a month — the full ladder is on the pricing page, and the platform page shows what is actually inside.