Import orders
Recipients, meals, delivery dates, time windows and notes are imported via file or an agreed interface.
Industry solution · NUNAV Courier
NUNAV Courier for social meal delivery services
Route planning for meal delivery and meals on wheels
NUNAV Courier connects orders, route planning, loading order and driver guidance in one consistent workflow. Daily deliveries can be planned reliably, adjusted at short notice and evaluated transparently.
For in-house drivers, fixed time windows and recurring recipients
North morning route08:15–11:45
42Stops
3Routes
98%within window
One workflow instead of isolated tools
From order to proof of delivery
The daily route is created from your orders, operating conditions and experience — with the information the kitchen, dispatch and drivers actually need.
Plan routes
NUNAV assigns stops to vehicles and accounts for travel times, capacities, breaks and individual delivery requirements.
Prepare loading
Packing and loading lists follow the planned order. This makes assignment easier and reduces searching at the vehicle.
Deliver and evaluate
Drivers see the next task, important notes and delivery status. Dispatch keeps track of overall progress.
Predictable in daily operations
Not just the shortest route. A reliable one.
Meal delivery is not only about distance. Recurring workflows, familiar delivery times and plans that can respond to change matter just as much.
Stable delivery windows
Time windows and familiar sequences can be included as route planning constraints.
Notes at the relevant stop
Access details, key arrangements, drop-off locations or special recipient notes are available where they are needed.
Replan when the day changes
Absences, additional stops or late departures can be included in an updated plan.
Integration and reporting
Fits into your system landscape
Existing data should remain useful. Start with structured files and extend the workflow through a web API where needed.
File import
Orders and master data can be imported using agreed CSV or Excel structures.
Web API
For recurring data flows, we jointly assess a REST-based connection to the system of record.
Reports and metrics
Route progress, delivery status, travel times and other agreed metrics provide a basis for evaluation and documentation.
Roles and data protection
Access, retention and the recipient data required are configured for the use case and your policies.
Frequently asked questions
What meal delivery teams want to know
How does NUNAV Courier plan routes for a meal delivery service?
Planning combines recipients and orders with time windows, vehicles, travel times, capacities, breaks and other operating rules. The result is a set of executable routes for the driver team.
How can delivery times remain as consistent as possible?
Recurring time windows and preferred sequences can be considered as planning constraints. When conditions change, a new plan shows which route allocation remains realistic.
Can orders be imported from our specialist system?
Yes. You can start with agreed CSV or Excel files. For automated workflows, a REST-based integration can be assessed and implemented for the specific project.
What information does the driver team see?
The driver view guides the route and shows the delivery information, recipient notes and status options needed at each step. The exact information scope is defined by role.
Which evaluations are available?
Depending on the agreed setup, route status, stops, travel and delivery times, and deviations can be evaluated. Individual report layouts are specified during the project.
What happens in areas with poor or no data coverage?
Dynamic planning and updates require a data connection. Requirements for areas with weak coverage and potential operational fallback procedures therefore need to be tested explicitly during the pilot.
Industry solutions with NUNAV Studio
Route planning for different delivery operations
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.
Start with real operations
Let us model one delivery day as a pilot.
We assess data, rules, the driver workflow and desired reporting with a manageable example — before you decide on a rollout.