Every routing engine is an optimizer. Feed it two points and it minimizes a cost function: distance, time, road class weights, turn penalties. The function is sophisticated, tuned on millions of trips, and it is not yours.
It does not know that your company holds negotiated rates on Travemünde–Trelleborg and has no account with the line at Rødby. It does not know that one of your customers reimburses kilometres on national roads and refuses péage line items. It does not know that after one bad experience your operations manual keeps certain loads out of tunnels that ADR categories would technically permit. And it certainly does not know that at 09:40 you are not planning a trip at all, you are pricing one, and the entire input is "DE-68 to FR-69" from a freight board.
None of these are edge cases. They are Tuesday. The gap between the router's optimum and your operation's optimum is where dispatchers spend a surprising share of their day, and most planning tools make you close that gap by trickery: fake via points planted on approach roads, addresses typed for places you never intend to stop, routes accepted as "close enough" and corrected verbally with the driver.
We think the honest design is different: overriding the router should be a first-class control, not a workaround. Three controls in Transport Nomad now cover the three overrides dispatchers actually perform.
Deciding what the route may use
The Avoid grid in Route Settings holds six switches: turns, tolls, highways, ferries, car-shuttle trains, tunnels. Each flips between Allow and Avoid, and each flip redraws the route and recomputes its cost for the roads actually driven.
The point is not that avoiding tolls is clever. Sometimes it is, sometimes it is a slower route that burns the saving in hours. The point is that the question "do we pay the péage or drive the N-road" stops being a matter of feel. Flip the switch and both variants exist as full calculations: kilometres, hours, fuel priced per country, toll for what remains. The delta between the two totals is the price of the policy, and you decide with the number in front of you.
Two design details are worth defending in print. First, the toll figure always reflects the roads the route actually uses, so an avoid-tolls route shows the tolls that genuinely remain (there are corridors where escaping tolling is simply not possible, and pretending otherwise would be lying to your quote). Second, the switches deliberately reset between sessions. A forgotten "avoid ferries" from yesterday's what-if would silently reprice everything you quote today, and that failure mode is worse than spending two clicks to re-enable a preference. Controls that change what a route costs should not have memory you can forget about.
There is a longer walk-through of all six switches in the avoid options guide.
Deciding which ferry, not whether
Road choice is geometry, but ferry choice is commerce. Rates are negotiated per line; the departure has to match the driver's rest; deck space this week is a fact, not a parameter. Between Germany, Poland and Scandinavia there are six meaningful lines, and the one the router picks on generic cost is, with respectable probability, not the one you booked.
In Transport Nomad you now correct that the way you correct a road: grab the route, drag it onto the ferry line you want (they are drawn as dashed lines across the water), release. The route recalculates through that crossing. The drop is forgiving, a rough placement near the line is enough, and the pinned crossing behaves like a pass-through point, not a stop.
Then the cost logic does what it should: the crossing is detected, priced at the rate you entered for that specific line (once, remembered thereafter), the sea kilometres are excluded from fuel and toll, and the total reflects the trip your truck will actually make. Share the route link and the colleague opens the same crossing, not the router's second opinion. The mechanics are in the ferry crossing guide.
Deciding where the route actually ends
The third override is quieter, and it happens before there is a route at all. A route is only as precise as its endpoints, and dispatchers set endpoints in two very different situations: when they know exactly where the truck is going, and when they know almost nothing beyond a postcode zone from a board offer.
These pull the search engine in opposite directions, so Transport Nomad runs two and gives you a switch. Advanced search covers addresses, postcodes, place names and company names, with typo tolerance: type the consignee's name, pick the right match, and the route ends at their gate, not "somewhere in Mannheim". Simple search deliberately drops companies and is tuned to resolve partial postcodes cleanly: DE-68 in, zone on the map, floor price out, quote sent while the offer still exists.
A search box sounds like a small thing next to routing algorithms. It is not. The last kilometres decide the approach side, the urban crawl, sometimes a toll bridge, and every downstream figure inherits the endpoint's quality. Details and the mode comparison are in the search modes guide.
The common thread
Notice what none of these controls do. They do not predict your backloads, score your corridors, or claim to know the market rate for Friday. We remain skeptical of software that pretends to hold knowledge that actually lives in your contracts, your customer relationships and your dispatcher's head.
What they do instead is make your knowledge cheap to express. You know the customer's toll policy: one switch. You know which ferry you booked: one drag. You know the consignee, or only the zone: one search mode each. After each of these, the part software genuinely should own takes over, counting the consequences precisely: fuel per country traversed, toll for the roads actually used, the crossing at your rate, time at your fleet's cost per hour.
The router proposes. You decide. The calculator never argues.
If you want to see what your own corridors look like with the overrides in your hands, you can try Transport Nomad free for 14 days.