Import shipments
Addresses, time windows, priorities and available weight and volume data are imported from the system of record.
NUNAV Courier turns shipment data into executable route proposals and supports dispatch when conditions change during the day. Deliveries, pickups and operating rules feed into one plan — while people remain in control.
The baseline plan is created from available shipment and vehicle data. Dispatchers review exceptions, approve routes and respond to actual operating conditions.
Addresses, time windows, priorities and available weight and volume data are imported from the system of record.
Optimization assigns shipments to suitable vehicles and calculates sequences within the agreed operating rules.
Dispatch reviews conflicts, special cases and proposals. Routes can be adjusted before they are sent to drivers.
New pickups, delays or vehicle changes can feed into updated route proposals.

Automation should not replace experience. It should free up that experience for the situations where it matters: exceptions, customer requirements and operational decisions.
Core territories can remain in place while individual shipments are assigned to suitable neighbouring routes when needed.
Planned and short-notice pickups can be considered together with active delivery routes.
Proposals remain understandable and adjustable. Dispatchers approve, correct or reject them.
Automated dispatch depends on reliable data flows. Source and target systems, synchronization and error handling are therefore defined together before production use.
Shipments, master data and route results can be exchanged through a documented interface agreed for the specific project.
Positions, driver status and feedback can provide the basis for visibility and updated planning.
Route sequence and relevant instructions are made available to the terminal, scanner or driver view in line with the process.
Plans, actual progress and agreed metrics provide a basis for evaluating cost and quality.
The software creates route proposals from shipments, vehicles and operating rules. Dispatchers no longer need to assign every shipment individually, but retain approval and intervention options.
Yes, provided pickup orders and their requirements are available as data in time. New orders during the day can be included in updated planning proposals.
No. Core territories can remain as planning rules while defined flexibility is used to balance daily volumes between neighbouring routes.
Required input and output data, update intervals, formats and error handling are specified together. The implementation depends on the interfaces available in the TMS and telematics systems.
Demonstrable planning quality matters more than the label. NUNAV combines optimization methods and real-time data. Input rules, results and human interventions should be documented transparently in the project.
A proof of concept compares planned routes with historical or manually created results. Previously agreed measures can include vehicle use, stops, driving time, capacity, punctuality and dispatch effort.
Every industry has its own rules, time windows and data structures. These solution pages show how dispatchers plan and steer each operation with NUNAV Studio.
Together, we define rules and comparison metrics, assess available data and make the optimization quality transparent.