Multimodal Fleet Optimization: Assigning Cargo Bikes, Vans, and Trucks in Real-Time Logistics Networks
Your fleet operates three vehicle types, each with different cost structures, capacity limits, and access restrictions. A cargo bike can slip through pedestrian zones. A van handles suburban routes efficiently but gets stuck in downtown traffic. A truck delivers bulk orders profitably on highways but burns fuel idling at red lights in dense neighborhoods. Deciding which vehicle takes which order, in real time, across shifting demand and traffic, is the core challenge of multimodal fleet optimization.
Traditional route planning assigns vehicles once per shift based on static forecasts. That worked when delivery windows were loose and fuel was cheap. Today, cities restrict diesel access. Static plans break the moment an order comes in late, a bike gets a flat tire, or a road closes for construction.
Multimodal fleet optimization treats vehicle type as a variable, not a constraint.
Each incoming order goes to the vehicle that minimizes total cost while meeting the delivery promise.
Live telemetry and orders, constraints for each vehicle class, a cost function, and a solver.
Map your actual cost structure and constraints, then pressure-test vendor demos with real order data.
Why Real-Time Assignment Matters More Than Route Efficiency Alone
Most logistics software optimizes routes for a fixed fleet. You tell the system you have five vans, and it draws the best paths. But the real question is whether you should have sent four vans and two bikes, or swapped a van for a truck on the highway leg. Agentic AI for autonomous route recalculation in logistics can replan routes when conditions change, but it still assumes the vehicle mix is correct.
Multimodal fleet optimization solves a different problem: it treats vehicle type as a variable, not a constraint. The algorithm evaluates every incoming order against the current state of the entire fleet (location, load, remaining capacity, cost per mile, access permissions) and assigns the vehicle that minimizes total cost while meeting the delivery promise. When a new high-priority order arrives, the system may pull a nearby cargo bike off a low-margin route, reassign that delivery to a van finishing another job, and send the bike to the urgent stop.
The savings come from three sources: better vehicle utilization (fewer empty miles), mode-appropriate assignments (bikes for dense urban, trucks for bulk suburban), and fewer missed delivery windows (which trigger costly re-attempts).
The Core Components of a Multimodal Optimization Engine
Building or buying a system that assigns cargo bikes, vans, and trucks in real time requires four technical layers working together.
Figure 1. The four layers behind each real-time assignment
Restates this article: telemetry and orders, the constraints of each vehicle class and a cost function feed a solver, which assigns each order to the vehicle that minimizes total cost while meeting the delivery promise, and re-optimizes when conditions change. Structure only; no values are drawn.
1. Live Fleet Telemetry and Order Ingestion
You need GPS coordinates, remaining capacity, battery or fuel level, and driver status for every vehicle. Orders flow in from your order management system, each tagged with pickup location, destination, weight, dimensions, time window, and priority. API integration between your OMS, telematics provider, and routing engine is the plumbing that makes real-time possible. If data arrives stale or incomplete, the optimizer makes bad calls.
2. Constraint Modeling for Each Vehicle Class
Cargo bikes, vans, and trucks have different constraints:
- Cargo bikes: weight limit, volume limit, restricted to bike lanes and pedestrian zones in some cities, lower speed, zero emissions access to low-emission zones.
- Vans: higher capacity, faster on open roads, diesel or electric variants with different range and refueling logistics, restricted in some downtown cores.
- Trucks: bulk capacity, highway-optimized, high cost per mile, often banned from narrow streets and residential zones during certain hours.
The optimization engine must encode these as hard constraints and soft penalties (a van in a pedestrian zone incurs a time penalty and possible fine).
3. Cost Function That Reflects Real Operating Economics
Your objective function should minimize total cost, not just distance. Include:
- Fuel or electricity cost per mile, differentiated by vehicle type and current energy prices.
- Driver or rider hourly wage, including overtime thresholds.
- Depreciation and maintenance per mile.
- Penalty for missed delivery windows (customer refunds, brand damage).
- Penalty for exceeding vehicle capacity or violating access rules.
Many off-the-shelf routing tools optimize for shortest path or earliest arrival. That works for pizza delivery but breaks down. Custom software development lets you bake your actual P&L into the solver.
4. Solver That Scales to Hundreds of Vehicles and Thousands of Orders
Multimodal vehicle routing with time windows is NP-hard. Exact solutions are impossible beyond toy problems. Production systems use heuristics: genetic algorithms, simulated annealing, or constraint programming with branch-and-bound. Google OR-Tools and VROOM are open-source options. Commercial solvers like Gurobi carry licensing costs.
You also need to decide how often to re-optimize. Every new order? Every five minutes? Continuous re-planning gives the best assignments but burns CPU and creates driver chaos (routes change mid-shift). Settle on a hybrid: re-optimize for the next window, and use a fast greedy heuristic for urgent inserts between cycles.
When to Build Versus Buy
Off-the-shelf platforms like Routific, OptimoRoute, and Bringg offer multimodal routing. They work well if your fleet mix is stable, your cost structure fits their defaults, and you operate in regions their map data covers well.
You should consider building (or heavily customizing) if:
- You operate in markets with unusual vehicle types (electric trikes, autonomous pods, river ferries) or regulatory constraints (hyperlocal emission rules, dynamic congestion pricing).
- Your cost model is complex (tiered driver pay, vehicle leasing with mileage caps, customer-specific SLAs that affect penalty calculations).
- You need tight integration with proprietary systems (a custom order management system, warehouse automation, or dynamic pricing engine).
- You plan to embed predictive models (demand forecasting, traffic prediction, vehicle failure risk) that feed the optimizer.
Buy off the shelf
Works well if- Your fleet mix is stable
- Your cost structure fits their defaults
- You operate in regions their map data covers well
Build or heavily customize
Consider it if- Unusual vehicle types or regulatory constraints
- A complex cost model
- Tight integration with proprietary systems
- Predictive models that feed the optimizer
Building in-house gives you control but requires a team that understands operations research, real-time data pipelines, and logistics domain knowledge. Expect ongoing iteration as your fleet and business model evolve. Partnering with a firm experienced in logistics software can compress that timeline and reduce the risk of costly missteps.
Measuring Success: Metrics That Matter
Track these KPIs weekly to know if your multimodal optimization is delivering value:
- Cost per delivery: total operating cost divided by completed deliveries, segmented by vehicle type.
- On-time delivery rate: percentage of orders delivered within the promised window.
- Vehicle utilization: revenue-generating miles divided by total miles driven, plus average load factor (actual weight or volume carried versus capacity).
- Mode split: percentage of deliveries by cargo bike, van, and truck. A healthy mix means you are using each vehicle where it is most efficient.
- Re-optimization churn: how often driver routes change mid-shift. High churn signals the algorithm is too aggressive or your order flow is too volatile.
Making the Decision
Multimodal fleet optimization is not a nice-to-have when you operate more than one vehicle type. It is the difference between guessing which van should take which order and making that decision with math, data, and speed. The right system pays for itself in fuel savings and higher delivery density.
If you are evaluating whether to build, buy, or customize, start by mapping your actual cost structure and constraints. Then pressure-test vendor demos with real order data and edge cases (a bike breaks down, a truck hits traffic, a high-priority order drops in). The gap between what the demo shows and what your operation needs will tell you how much custom work you face.
Sthenos Technologies builds AI-driven logistics platforms for fleets that need more than off-the-shelf routing. If you are weighing the build-versus-buy decision for multimodal optimization, we can help you scope the solution, estimate the ROI, and de-risk the engineering path.
Related services: AI and machine learning development.
Related reading
- Guide: Multimodal Fleet Optimization: Routing Trucks, Vans, and Cargo Bikes as a Single Optimization Problem
- Guide: Multi-Constraint Route Optimization in Real-Time Logistics
- Term: What Is Route Optimization?
- Term: What Is Last Mile Delivery?
- Industry: Logistics & Supply Chain
