Why Routific and Onfleet Miss Local European Emission Zones

The Routing Gap Nobody Talks About

Routific and Onfleet are solid tools for what they were built to do: sequence stops, estimate drive times, and give dispatchers a clean dashboard. Neither platform, however, was designed with European low-emission zones (milieuzones) in mind. That's not a criticism of their engineering — it's simply outside their original scope. Both were built primarily for North American logistics patterns, where urban access restrictions based on vehicle emissions class are rare. For fleets operating in Dutch, German, or Belgian cities, that gap becomes a real operational risk rather than a theoretical one.

What These Platforms Actually Optimize For

Routific's strength is route efficiency: minimizing total distance and drive time while respecting time windows and vehicle capacity. Onfleet leans into real-time visibility — customer notifications, driver tracking, proof of delivery. Both are excellent at the logistics math. But neither ingests municipal zone boundaries, vehicle emission classifications (Euro norms, diesel vs. electric, vehicle weight class), or the fact that a zone's rules can differ from one Dutch city to the next. A route that looks optimal on the map can, in practice, route a Euro 4 diesel van straight through a zone where it isn't permitted to drive at all.

This matters because milieuzones aren't uniform. Rotterdam, Amsterdam, Utrecht, and smaller municipalities each set their own vehicle eligibility rules, and some zones apply only to certain vehicle types or at certain hours. A routing engine that treats all drivable roads as equally available will happily generate a route through a restricted street, leaving the driver — not the software — to discover the problem at the wheel.

Why "Fastest Route" Isn't the Same as "Compliant Route"

The core issue is architectural. Routific and Onfleet calculate the shortest or fastest path based on standard mapping data layers: road type, speed limit, traffic conditions, turn restrictions. Emission zone boundaries are a separate regulatory data layer that most commercial routing platforms simply haven't integrated, because it's a niche concern outside their primary markets. Without that layer, the software has no way to know that a given street segment is off-limits to a particular vehicle class at a particular time.

For dispatchers, this creates a false sense of security. A route plan that's been optimized and approved in the platform can still generate fines, delays, or forced detours once a driver is already en route — problems that are expensive to fix after the fact and nearly impossible to catch by manually cross-referencing municipal zone maps for every st