The Logistics Tech Stack a Baltic SME Needs in 2026

Q: Do I need telematics if I don't own trucks?

No. Telematics is GPS and engine data inside the vehicle, so it belongs to whoever owns the truck. As an asset-light shipper you ask the carrier for a status or a tracking link instead of buying telematics yourself.

For a small Baltic shipper, logistics technology is just the set of tools that move a load from "I need a price" to "the invoice is paid" without you retyping the same details five times. You do not need a big platform. You need four jobs covered — quoting, planning, tracking, settlement — and most teams running 20-60 loads a month can do the rest with a spreadsheet and a shared inbox.

This guide is for the person who books the trucks: the dispatcher, the office manager, the owner who picks up the carrier's call. We'll map the four layers of a stack, show what you can safely skip until you grow, explain the difference between a TMS, an RFQ tool and telematics, and give you a worked example of a minimal stack for a 40-load-a-month operation — in euros, so you can see what's worth paying for.

The four layers: quoting, planning, tracking, settlement

Every shipment, however small the company, passes through the same four stages. Good logistics software is just software that makes each stage a record instead of a message. Here is what each layer does and what breaks when you skip it.

Quoting

Quoting is finding a fair price before you commit. For a Baltic SME this almost always means sending the lane to a handful of carriers you already trust and comparing what comes back. When you send the same lane to five carriers you usually see a 15-30% spread — and the only way to capture that spread is to ask more than one. Done by email, this takes 20-40 minutes per lane and the replies arrive in five different formats.

Planning

Planning turns the chosen quote into an order: pickup window, delivery window, references, special needs (ADR, tail-lift, temperature). For small volumes this is light — you're not optimising routes across a fleet, you're making sure the right truck shows up at the right dock on the right day.

Tracking

Tracking answers one question your customer keeps asking: "where is it?" You don't need a live map for 40 loads a month. You need a status — assigned, loaded, in transit, delivered — and a way to know when something slips before the consignee calls you.

Settlement

Settlement matches the carrier's invoice to the agreed price and the proof of delivery, then flags anything that doesn't line up. This is where money quietly leaks: a quoted €620 lane invoiced at €680 with a "waiting time" surcharge nobody agreed to. If you can't compare the invoice to the original quote in seconds, you pay the difference.

The quoting layer is the one that pays for itself fastest, because price spread is real money on every single load. The first thing to fix is quoting — run an RFQ to your carriers in 60 seconds with UMERA instead of writing five separate emails.

What you can skip until you're bigger

Most "logistics technology" sold to SMEs solves problems you don't have yet. Skipping the wrong tool costs you time; buying the wrong tool costs you a subscription and the time to maintain it. Here's what's safe to ignore at 20-60 loads a month.

Route optimisation engines — these earn their keep when you run your own fleet of 10+ vehicles. If carriers run the trucks, the optimisation is their problem, not yours.
A full marketplace / freight exchange — load boards like the big exchanges are built for finding anonymous capacity at scale. If you have 8-15 carriers you actually trust, you don't need to fish in an open pool; you need a faster way to quote the carriers you already have.
Predictive ETA / AI tracking — nice for a 5,000-load operation. For 40 loads, a carrier status update plus a phone number does the job.
Customs / duty automation — unless you clear a lot of non-EU freight yourself, your forwarder or broker handles this. Don't buy software to replicate what you already outsource.
A data warehouse / BI dashboard — you can answer "what did we spend per lane this quarter?" from a tidy spreadsheet long before it justifies a reporting tool.

The rule: buy the layer where you currently lose the most time or money, and only that layer. For most Baltic SMEs that's quoting and settlement, not planning and tracking.

TMS vs RFQ tool vs telematics — who needs which

This is the tms vs rfq tool question that trips up most buyers, and telematics gets mixed in too. They solve different problems. Here's the plain version.

A TMS (Transport Management System) is the all-in-one: it captures the load, gets a price, tenders it, books it, tracks it and helps settle the invoice. Powerful, but heavier to set up and priced for teams that live in it all day. Worth it once you're past ~80-100 loads a month or you have several people booking. (See our full guide to what a TMS is.)
An RFQ tool does one job extremely well: send a lane to multiple carriers and collect comparable quotes fast. It's the quoting layer on its own. For a small team, this is often the only software you need to buy, because it fixes the layer that leaks the most money.
Telematics is the GPS and engine-data hardware/software inside the truck. Here's the key point about telematics for shippers: telematics belongs to whoever owns the vehicle. If carriers run your loads, you don't buy telematics — you ask the carrier for a status, or get a tracking link. You only need telematics if you run your own fleet.

Tool	What it does	Who needs it	Typical monthly cost (SME)
RFQ tool	Quote a lane to many carriers, compare replies	Almost every shipper; the quoting layer	€0-150
TMS	Full quote → book → track → settle	80+ loads/month or multi-person teams	€200-1,000+
Telematics	Live vehicle GPS + engine data	Fleet owners only (not asset-light shippers)	€15-40 per vehicle

If you don't own trucks, telematics is not your purchase — it's your carrier's. If you book fewer than ~80 loads a month, an RFQ tool usually beats a full TMS on cost and time-to-value.

A minimal stack for a 40-load-a-month shipper (table)

Here's a concrete supply chain technology stack for a Baltic SME moving 40 loads a month — say a Vilnius distributor sending mixed pallets to Germany and Poland. The goal is to cover all four layers with the least software and the least busywork.

Layer	Tool	What it replaces	Monthly cost
Quoting	RFQ tool (e.g. UMERA)	5 separate emails per lane	€0-150
Planning	Shared calendar + order template	Sticky notes, memory	€0
Tracking	Carrier status link / WhatsApp update	"Where is my truck?" calls	€0
Settlement	Spreadsheet matching quote vs invoice	Paying unchecked surcharges	€0
Documents	Shared drive for CMR / POD scans	A drawer of paper	€0-12

Total: roughly €0-160/month — and most of that is the RFQ tool, the one layer that pays for itself.

Worked example: where the money is, Vilnius → Hamburg

Take one real-shaped lane: Vilnius → Hamburg, ~1,200 km, a part-load of 8 europallets (~3,200 kg, ~5.0 LDM), 2-day transit.

Quote by phone to one carrier: €0.62/km → about €744 for the run. You take it because you're busy.
RFQ to five carriers, 60 seconds to send: replies range €0.52-€0.68/km. You take the €0.54/km = €648 quote from a carrier you've used before.
Saving on this one load: €96. Across 40 loads a month, capturing even half that spread on the lanes where it exists is real money — often several thousand euros a year, for the cost of sending a quote properly.

Want to sanity-check a per-km or per-pallet number before you accept it? Run it through the freight-rate calculator first, so you know whether €0.54/km is a good Vilnius-Hamburg price or just the first one you were offered.

What to buy vs what a spreadsheet still handles

The honest answer for most Baltic SMEs: buy the quoting layer, keep the rest in a spreadsheet until volume forces your hand. A spreadsheet is not a failure state — it's the right tool until the cost of maintaining it (typos, version confusion, the one person who "knows the file") exceeds the cost of software.

Buy software when:

You lose price spread on every load. Quoting is where money leaks fastest, and an RFQ tool plugs it directly.
More than one person books trucks. Shared state in a spreadsheet breaks down once two people edit it; that's the moment a real system earns its price.
You're past ~80 loads a month. Above this, a full TMS starts saving more time than it costs to run.

Keep the spreadsheet when:

You're tracking 40 loads and one person books them. A clean sheet with one row per load, columns for quote / carrier / status / invoice, beats an over-spec'd platform.
Your reporting needs are "what did we spend per lane?" A pivot table answers that for free.

One thing software won't decide for you: who carries the cost and risk at each handover. That's set by your Incoterms, not your tech stack — know which term applies before you quote, because it changes who pays for the leg you're pricing. Our Incoterms guide breaks down the common terms for road freight.

General information only — not customs, tax or legal advice.

FAQ

What is logistics technology for a small shipper?

It's the set of tools that move a load from "I need a price" to "the invoice is paid" — covering four jobs: quoting, planning, tracking and settlement. For a small Baltic SME, that often means one RFQ tool plus a spreadsheet, not a big platform.

Do I need a TMS or just an RFQ tool?

If you book fewer than about 80 loads a month and one person handles them, an RFQ tool usually wins — it fixes the quoting layer (where money leaks fastest) at a fraction of a TMS's cost. Move to a full TMS when volume grows or several people start booking.

Is UMERA a load board or freight exchange?

No. A load board matches anonymous capacity in an open pool. UMERA is built for the carriers you already trust: you send a lane and they quote via a no-account magic link — no marketplace, no logins for them. It's the quoting layer, not a marketplace.

Do I need telematics if I don't own trucks?

No. Telematics is GPS and engine data inside the vehicle, so it belongs to whoever owns the truck. As an asset-light shipper you ask the carrier for a status or a tracking link instead of buying telematics yourself.

How much should a small logistics tech stack cost?

For 40 loads a month you can cover all four layers for roughly €0-160 a month — most of it the RFQ tool. Planning, tracking and settlement can stay in a free spreadsheet and shared calendar until your volume justifies more.

When should I stop using a spreadsheet?

When more than one person books trucks, when version confusion starts costing you, or when you pass ~80 loads a month. Until then, a clean one-row-per-load spreadsheet for planning, tracking and settlement is the right tool — just buy the quoting layer.