Webfleet’s 100-orders-per-device cap: the documented ceiling on dense routes

What Webfleet documents about the driver dispatch surface

The Webfleet Work App is the driver-side mobile app in the Webfleet platform. The standard flow pushes orders, routes, messages and tasks from the WEBFLEET console to the Work App or the PRO Driver Terminal in the cab. The public product pages document the following:

• Work App capabilities. Order and task management, electronic Proof of Delivery with real-time visualization, two-way messaging, push notifications, working-hours logging, license checks, OptiDrive 360 performance scoring, secure-truck-parking booking, temperature alerts, 24+ languages, QR-code driver onboarding, TomTom GO Fleet navigation integration.
• PRO Driver Terminal. Ruggedized in-cab tablet, including the Driver Terminal PRO X launched at CV Show 2026.
• Routes over-the-air. WEBFLEET.connect documents endpoints for pushing predefined routes and orders to the driver device.

What the public documentation does not surface is a per-device order cap. Third-party integration partner documentation reports that Webfleet does not accept more than 100 orders pushed to a single device in one batch. The cap is the structural ceiling on what can be displayed to the driver in one session of the Work App or PRO Driver Terminal.

None of this means Webfleet’s telematics stack is the wrong tool above 100 stops per driver per day. GPS, OptiDrive 360, Tachograph Manager and Webfleet Video work at any density. What hits the design ceiling is the dispatch surface around pushing the full route to the driver in one batch.

What the cap looks like in practice

The 100-orders-per-device cap matters in three concrete ways:

• Split-session dispatch. A driver with 140 stops in a day cannot have the full route pushed in one batch. The planner pushes the first 100, has the driver close the session at lunchtime, then pushes the remaining 40. Mid-day re-optimization becomes harder because the next batch has to be ready exactly when the first batch closes; the operation runs to a stricter timetable than the planner controls.
• Spreadsheet overflow. An alternative workaround is to push 100 stops to the Work App and carry the overflow in a paper or spreadsheet manifest. The driver works the cap-respecting digital route, then switches to paper for the rest of the day. Stops worked on paper don’t flow back into the telematics record cleanly, and the operations team loses end-of-day insight on the paper stops.
• Capped route shape. The third workaround is to plan routes at 100 stops or fewer and accept lower density. This trims drive-time efficiency: routes that could be one driver doing 140 stops are spread across two drivers doing 70 each, with the second driver duplicating the first part of the route.

In each case, the operation pays a tax to fit the dispatch surface. The right answer is for the optimization layer to plan the full route as one unit and segment the push to the driver in cap-respecting chunks, with the next chunk streaming as the current chunk closes.

At a glance: a dense urban distribution operation on Webfleet

A dense urban distribution operation running 80 drivers across three depots in London, Birmingham and Manchester. Roughly 140 stops per driver per day on the densest urban routes (parcel and grocery), 60 to 80 stops per driver on suburban routes. Webfleet for the telematics stack: WEBFLEET console for back-office tracking, OptiDrive 360 scoring the drivers, Tachograph Manager handling EU HGV compliance, Webfleet Video on the heaviest vehicles, Webfleet Work App in the cab.

The 100-orders-per-device cap hits on the 20 densest urban routes. The planner had been splitting those routes into two 70-stop sessions (morning batch and afternoon batch), with the driver closing the morning session before lunch and signing back in for the afternoon. The split-session pattern absorbed roughly 12 minutes per driver per day on session management, plus the planner had to be at their desk at lunchtime to release the afternoon batch. On bad-traffic days the afternoon batch couldn’t accommodate mid-day re-optimization because the planner was already preparing the next driver’s batch.

Adding eLogii plans the full 140-stop route as one unit on the engine side, with all constraints (time windows, capacity, skills, depot start/end, customer SLAs) holding across the whole route. The push to the Work App streams in cap-respecting segments: the driver sees the first segment in the morning, and the next segment streams automatically when the first closes. The planner doesn’t have to be at their desk at lunchtime. Mid-day re-optimization runs against the full route in eLogii and updates the next pushed segment. Webfleet captures the in-cab GPS, OptiDrive, tachograph and Webfleet Video stream against the unified route, not against two disconnected sessions.

What eLogii adds, in one place

The constraint-based optimization decision layer that runs alongside Webfleet at dense-route scale:

• Full-route optimization regardless of cap. The route lives in eLogii’s data model as one unit, with all its constraints intact. Stop density doesn’t fragment the optimization.
• Cap-respecting segmented push. eLogii streams the route to the Work App or PRO Driver Terminal in segments under the 100-orders-per-device cap. The next segment streams as the current segment closes.
• Two engines. Default engine for high-throughput daily planning (100 tasks in under 10 seconds). Advanced engine for multi-depot, multi-day, long-haul and constraint-heavy operations.
• Six configurable modes. Three assignment modes (Optimize Everything; Add to Routes, Keep Existing Assignments; Add to Routes, Keep Existing Assignments and ETAs). Three load-balancing modes (Most Efficient Routes; Balance the Minimum Number of Routes; Use All Vehicles / Finish as Soon as Possible).
• Mid-day re-optimization. Re-optimization runs against the full route in eLogii and updates the next pushed segment automatically. The planner doesn’t coordinate batch handoffs.
• Rule-based protection. Pin specific stops to specific segments, lock customer-confirmed slots, exclude segments from a re-run. Visible rules, not buried defaults.
• REST-callable. All six modes plus optimization triggers exposed as REST endpoints. Seven webhook events including live driver GPS and Route ETAs Update.

How the integration sits with Webfleet

Webfleet stays the system of record for GPS, OptiDrive 360, tachograph and Webfleet Video record. The operational system (FSM or ERP) stays the system of record for the work record. The connector between eLogii and the stack is custom-built; there is no published eLogii to Webfleet integration on either side. Webfleet documents WEBFLEET.connect through its developer portal with OAuth 2.0 authentication.

1. Read from the operational source. eLogii reads stops, drivers, vehicles, depots and skills from the FSM, ERP or Webfleet directly via WEBFLEET.connect.
2. Optimize the full route in eLogii. The run produces the full driver-vehicle-stop assignment respecting all constraints, regardless of stop density.
3. Push in segments. Routes are written back over WEBFLEET.connect in cap-respecting segments under 100 orders per device. The next segment streams as the current segment closes on the driver side.
4. Driver experience improved. The driver opens the Webfleet Work App or PRO Driver Terminal in the cab and sees the current segment, with the next segment arriving when needed. No mid-day session handoff with the planner. Webfleet captures the GPS, OptiDrive, tachograph and Webfleet Video stream against the unified route.

Most teams complete the connector build in 3 to 5 weeks. The most common first wave for dense-route operations is the depot where the 100-stop cap is biting hardest.

Frequently asked questions

What is the documented 100-orders-per-device cap in Webfleet?

Third-party integration partner documentation reports that Webfleet does not accept more than 100 orders pushed to a single device. The cap is documented as a structural limit of the WEBFLEET.connect job dispatch surface. For a driver running 80 stops in a day, the cap is invisible. For dense urban distribution running 120 to 180 stops per driver per day, planners have to split the route across multiple device sessions or carry the overflow in spreadsheets.

Does this mean Webfleet is the wrong tool above 100 stops per driver?

No. Webfleet’s telematics stack (GPS, OptiDrive 360, Tachograph Manager, Webfleet Video, TPMS) runs across fleets of all sizes and stop densities. The Webfleet Work App and PRO Driver Terminals are useful in-cab surfaces. The 100-orders-per-device cap is one documented place where the dispatch surface was designed around a band of typical fleet operations. Once the operation runs denser per-driver days, the optimization decision layer can plan the full route as one unit and stream it to the driver in cap-respecting segments, with the constraint model holding the whole route together on the eLogii side.

What does the cap look like in practice?

Per the documented limit: a driver with more than 100 stops in a day cannot have the full route pushed to the Work App or PRO Driver Terminal in one batch. The planner has to either split the route across two device sessions (reset and re-push at lunchtime, for example), carry the overflow in a paper or spreadsheet manifest, or trim the route below the cap and accept lower density. Each of these adds planner time and operational risk. The split-session pattern in particular makes mid-day re-optimization harder, because the next batch has to be ready when the first batch closes.

How does eLogii handle dense routes past the 100-orders-per-device cap?

eLogii plans the full route as one unit on the engine side, regardless of stop density. The route lives in eLogii’s data model with all its constraints (skills, capacity, time windows, SLAs, depot start/end, recurring cadences) intact. When the route is pushed to the driver over WEBFLEET.connect, eLogii streams it in cap-respecting segments and re-streams the next segment as the driver completes the current one. The constraint model and the routing decision are not divided by the cap; only the display to the driver is segmented. Mid-day re-optimization runs against the full route in eLogii and updates the next pushed segment automatically.

How does the integration work for dense-route fleets?

Custom integration against WEBFLEET.connect (OAuth 2.0) and the operational system of record (FSM or ERP). eLogii reads stops, drivers, vehicles, depots and skills from the operational systems; the optimization run produces the full driver-vehicle-stop assignment respecting constraints; routes are written back over WEBFLEET.connect in cap-respecting segments. The driver opens the Webfleet Work App or PRO Driver Terminal in the cab and sees the current segment, with the next segment streaming when the first closes. Webfleet captures the in-cab GPS, OptiDrive, tachograph and Webfleet Video stream. Typical connector build: 3 to 5 weeks.