Zero-Emission Zone Routing in the Netherlands: Planning Dutch Delivery Routes Around Zone Rules in 2026

Zero-emission zone routing is the planning of delivery routes so that every stop in a Dutch city-centre zone is served by a vehicle that is allowed to enter it on that date. It treats vehicle class, zone and date as constraints inside the route plan, not as a compliance check after the plan is made. Since 1 January 2025 Dutch municipalities have been introducing zero-emission zones for city logistics, and which vehicle may enter which zone changes with the vehicle’s emission class and the calendar. For heads of transport and logistics at Dutch retailers, parcel operators and 3PLs, this guide sets out a six-step method, a worked example on illustrative numbers and what to demand from route planning software. Locus, the world’s first Decision-Intelligent, Agentic TMS, plans routes against 250+ real-world constraints.

Why Zone Rules Matter for Route Planning: The Business Case

The rules are in force and expanding. The Dutch government said on 14 March 2025 that the first 14 municipalities had introduced a zero-emission zone on 1 January 2025 and that about 15 more would follow, with a fine-free period of at least six months in each. RDW reported on 2 March 2026 that 20 municipalities and Schiphol had introduced a zone, and that over time only zero-emission delivery and freight vehicles will be allowed in them.

Transitional rights are narrow and dated. According to a trade summary of the national transition rules, Euro 5 vans may enter until 1 January 2027 and Euro 6 vans until 1 January 2028, and vehicles registered after 1 January 2025 must be zero-emission. The government’s March 2025 agreement also provides for one further year for Euro 6 vans through a planned change of the rules, which it said would benefit about 46% of company vans. Confirm each vehicle against RDW’s plate check before relying on a date.

Exemptions run through one door. RDW states that it is the only official body that grants exemptions for vehicles without access to a zone, and that applications are made only through the national Centraal Loket Zero Emissie. The Dutch government’s March 2025 agreement says that exemptions for grid congestion and business-economic reasons are to be arranged nationally, so that one granted exemption applies in all zones.

Delivery volume keeps zones busy. Dutch consumers made 347 million online purchases in 2025, worth €35.7 billion, according to the Thuiswinkel Markt Monitor reported by the Dutch Payments Association.

What Is Different About Zone-Constrained Routing

Eligibility changes by vehicle, not by fleet. Two vans of the same size can have different access to the same street because their emission class or registration date differs.

Rules vary by municipality and date. Each municipality sets its own start date and boundary, and transitional rights end on set dates, so the answer for a stop depends on where and when.

The cheapest vehicle may be ineligible. A routing engine that optimises cost first and checks access later can build routes that no allowed vehicle can serve.

Electric vehicles bring their own limits. Range, payload and charging windows decide how many in-zone stops an eligible vehicle can take.

Fallbacks are administrative. An exemption is applied for, granted by one body and time-limited, so it has to be planned as a dated option.

How to Plan Routes Around Zone Rules in Six Steps

1. Build the eligibility matrix

List every vehicle by plate, emission class, registration date and payload, and every zone by municipality, boundary and start date. For each pair, record whether the vehicle may enter and until when. Use the national plate check as the source of truth and refresh the matrix when the fleet or the rules change.

2. Make eligibility a hard constraint

Load the matrix into the route planner, so that a stop inside a zone can only be assigned to a vehicle with access on that date. Treat it as a constraint like payload, not as a preference, so that no plan contains a stop that cannot be legally served.

3. Assign eligible vehicles by range and charging window

Give each eligible vehicle the in-zone stops that fit its payload and usable range, and schedule charging between shifts. Fill remaining capacity with out-of-zone stops, and keep a margin for traffic and for stops added during the day.

4. Plan the exemption path as a dated fallback

For vehicles that lose access before they are replaced, record the exemption route through RDW’s national desk, the likely decision time and the date by which a plan B is needed. Do not build routes that depend on an exemption you have not received.

5. Run a what-if on the fleet calendar

For each future date on which a vehicle class loses access, re-plan the next peak week with that class removed. The result shows how many eligible vehicles you need, which zones become hard to serve and when a purchase or lease has to land.

6. Track compliance and cost together

Report the share of in-zone stops served by eligible vehicles, the cost per in-zone stop and the number of stops moved to another vehicle at planning time. A plan that is compliant but doubles cost per stop needs a different fleet mix.

A Worked Example on Illustrative Numbers

The numbers below are illustrative, not benchmarks. Replace them with your own fleet and zone data.

A depot runs 20 vans: 8 electric, 8 Euro 6 and 4 Euro 5. On a typical day it serves 400 stops, of which 160, or 40%, are inside zones. Each van can serve about 20 stops a day.

In the last row the gap of 16 stops is almost one extra electric van’s day of work. The what-if shows that the constraint binds when the last transitional vans lose access, not when the first ones do, and that the purchase date is set by the demand forecast and not by the rule date alone.

Static Depot Routes vs Class-Aware Routing vs Fleet-Transition Planning: Key Differences

What to Look for in Zone-Aware Route Planning Software

Vehicle-level eligibility. Look for constraints that attach to a vehicle’s class and registration date, not only to a vehicle type.

Date-aware rules. Check that zone access can change on a date and that a plan can be run for a future date.

Range and charging in the plan. Ask whether usable range and charging windows are modelled with load and traffic.

Mixed-fleet optimisation. Look for plans that choose between electric and combustion vehicles by stop, not by fleet.

What-if planning. Check that you can remove a vehicle class from a future date and compare the plan.

Rule-Heavy Dispatch in Action: Real-World Results

Neither deployment below is in the Netherlands or concerns zero-emission zones. They show what happens when jurisdiction rules become planning constraints.

A global lottery operator running field service in 25+ US states. Each state has its own contract, labour rules and response windows, some as short as one hour with penalties of $100+ an hour, and no two technicians share the same skills. With Locus’s Dispatch, Capacity and Orchestrator agents assigning each case within each state’s terms, the operator ran 25+ states on one autonomous dispatch engine and reported 20% lower SLA penalty risk, 18% lower fuel spend and 15% less drive distance and time. Read the field service case study.

A leading Vietnamese beverage company serving thousands of small retail points a day. Distributors ran mixed fleets of vans, trucks and motorbikes, with vehicle restrictions and partial deliveries modelled as planning rules. The company saw 37% less fuel consumed, 22% more orders per delivery trip and 12% less distance. Read the beverage distributor case study.

Common Zone Routing Mistakes to Avoid

Treating the zone as a driver instruction. Telling drivers to avoid a zone moves the problem onto the road, so make access a constraint at planning time.

Assuming one date for the fleet. Vehicle classes lose access on different dates, so plan by vehicle and by date.

Counting on an exemption. An exemption is granted by RDW and not guaranteed, so plan it as a fallback and not as capacity.

Ignoring range and payload. An eligible electric vehicle that cannot carry the load or finish the route does not solve the stop.

How Locus Approaches Zone-Constrained Routing

Locus, the world’s first Decision-Intelligent, Agentic TMS, was recognised by Gartner for seven consecutive years and appears in the 2026 Hype Cycle for Supply Chain Execution and Logistics Technologies. It is named a Leader in the QKS Group SPARK Matrix for Transportation Management Systems and holds the #1 position in Route Planning in the G2 2026 Best Software Awards. In October 2025, Ingka Investments, the investment arm of Ingka Group, the world’s largest IKEA retailer, acquired Locus. Locus continues to operate independently.

Locus’s route optimisation engine plans against 250+ real-world constraints, including vehicle limits, time slots, service times and traffic rules, and recomputes routes during delays. Its EV fleet framework describes allocating routes by powertrain, with electric vehicles on routes whose range and charging fit and combustion vehicles where electric would hurt service or economics, and lists low-emission zone rules such as Amsterdam’s zero-emission zone as allocation inputs. Six governance mechanisms, including autonomy levels and human-in-the-loop approval, keep planners in control of what runs automatically. Locus has optimised 1.5B+ deliveries for 360+ enterprise customers across 30+ countries. Public sources do not show Dutch deployments or describe how Dutch zone boundaries, emission classes and transition dates are maintained, so during evaluation ask how zone rules and their dates are loaded and updated, how vehicle class and registration date are modelled, how range and charging are planned, and whether a plan can be run for a future fleet. To see how Locus would plan your Dutch routes, schedule a demo.

For heads of transport asking how to plan routes around zero-emission zones, Locus offers one planner that treats zone access, vehicle limits and service windows as constraints in the same plan, so the route that is built is a route that can be driven.

Frequently Asked Questions

What is zero-emission zone routing? It is the planning of delivery routes so that every stop in a zero-emission zone is served by a vehicle that may enter on that date. It treats emission class, zone and date as constraints in the route plan.

Which Dutch cities have zero-emission zones? Zones began on 1 January 2025 in the first 14 municipalities, and RDW reported in March 2026 that 20 municipalities and Schiphol had introduced one, including Amsterdam, Rotterdam, The Hague and Utrecht. Check the government’s overview and the plate check for the current list.

Who grants exemptions for zero-emission zones? Only RDW, through the national Centraal Loket Zero Emissie. Treat an exemption as a fallback with a decision time, not as guaranteed capacity.

How do I know when my vans lose access? Check each vehicle’s plate against RDW’s plate check, and note that vehicles registered after 1 January 2025 must be zero-emission. A trade summary puts Euro 5 vans’ transitional access at 1 January 2027 and Euro 6 vans’ at 1 January 2028, subject to a planned further year for Euro 6 vans, so confirm each date.

How should I plan my fleet for the transition? Run a what-if on the fleet calendar: remove each vehicle class on its end date and re-plan a peak week to see how many eligible vehicles you need and when.

Does Locus support zero-emission zone routing? Locus plans against 250+ constraints and describes allocating routes by powertrain with low-emission zones as inputs. Ask Locus how Dutch zone rules, emission classes and transition dates are loaded, updated and tested for a future fleet.