Before your dispatcher sends tomorrow’s routes, Fleetkeur runs every stop, kenteken, Euro class, registration date, and exemption status against the live Dutch LEZ/ZE ruleset — then flags illegal assignments before your vans hit the city centre.
Run a 14-day Amsterdam pilot → See how it works// 14-day pilot · cancel any time · no card upfront · billed in EUR
If you run a mixed fleet of EVs and Euro-5/6 diesels in an EU city, every delivery stop is a compliance check. Most routing APIs think about traffic and distance. None of them model the specific street, time window, and vehicle-class combinations that trigger a municipal fine.
Generic route optimisers don’t check kenteken status, Euro-class registration date, ZE-zone transition rules, or exemption status before dispatch. Fleetkeur runs every stop through Dutch compliance data first — published fines are €130 (vans/cars/coaches) and €320 (lorries) per illegal entry.
Most small-fleet dispatchers are cross-referencing three PDFs, a WhatsApp from the city council, and a memory of which intersection got enforced last month. That’s not a process. That’s a liability.
TMS systems that model this cost six figures and ship with a dedicated implementation consultant. Great if you’re DHL. Useless for a 15-van fleet with a three-person ops team.
You upload (or POST via API) your stops for the day and your fleet’s vehicle-class roster. We return a route assignment that legally enters the zones you’re authorised for and legally avoids the zones you’re not.
Building a pan-EU LEZ-routing API on day one is a trap. Every city has different rules, different classes, different exemptions, different enforcement schedules. We pick one dense, high-risk market and make it airtight before expanding.
Amsterdam has some of the EU’s most aggressive LEZ enforcement: published per-entry fines are €130 for vans/cars/coaches and €320 for lorries (Gemeente Amsterdam, 2026). Repeat exposure across a fleet stacks fast.
One set of zone rules means one scraping + normalisation pipeline we can maintain daily. That’s the difference between a product and a never-finished research project.
10–50 vehicle fleets serving Amsterdam last-mile. 300+ of them in the registry. Direct-email reachable. We can talk to 20% of them in 60 days.
Generic routing engines have started bolting on LEZ avoidance — Route4Me added it in v5.3.2, and similar overlays exist in larger global TMS platforms. They handle the geometry. They don't handle the Dutch reality: RDW kenteken history, Dutch-language ops UI, the central exemption portal, the 30.6% of NL commercial vehicles that fail Amsterdam Centrum on day one. Here's the honest comparison.
| Capability | Fleetkeur | Generic LEZ overlay |
|---|---|---|
| NL RDW kenteken-snapshot baked in (every NL operator's pre-2014 baseline pre-computed) | ✓ | – |
| Dutch-language ops UI at /nl/ — your dispatcher works in their first language | ✓ | – |
| Per-city exemption portal automation (Centraal Loket Milieuzones) | ✓ | – |
| Pre-flagged 30.6% pre-2014 NL fleet exposure on every onboarded operator | ✓ | – |
| EU-wide rerouting (DE, BE, FR, IT, ES, etc.) | – | ✓ |
| Pricing | €815/mo Fleet Pro | varies — typically per-stop or per-vehicle |
The Dutch national ZE-zone programme expands from the current 5 enforced LEZ cities to 16+ municipalities by Q3 2026. We're scaffolding city-by-city with verified data from RDW, the Centraal Loket Milieuzones (CLM), and individual gemeente ordinances. Where provincial data hasn't been published yet, we mark it pending rather than guess.
// Sources: RDW Open Data SODA (m9d7-ebf2), Centraal Loket Milieuzones (CLM), individual gemeente ZE-zone ordinances. "TBD" = zone-km² pending RDW provincial data; ZE-zone year is the gemeente's published plan, subject to council confirmation. Zaanstad excluded — no ZE-zone ordinance filed as of 2026-05.
One paid tier built for the fleets we actually serve — Amsterdam ops teams running 10–30 mixed-vehicle fleets. A narrow 14-day pilot proves the LEZ math; then it's a single subscription.
Tight pilot — 1 vehicle, 1 zone (Centrum), 5 route plans/day. Enough to see the LEZ math; not enough to operate on. No card.
The actual operating tier — up to 30 vehicles · unlimited API · priority support.
// One paid tier kept on purpose. Per-vehicle pricing creates billing friction the ops team doesn't want; we sized Fleet Pro for the typical 10–30 vehicle Amsterdam fleet. Larger fleet? Email us.
We’re onboarding 20 Amsterdam-area fleets into a free 14-day pilot. Submit your next-week stop list and vehicle roster; we’ll return the LEZ-compliant route the same day and track avoided fines.