Solution · Operations

Delivery route planning and dispatch software

We build a system that takes the orders ready to ship, accounts for each vehicle’s capacity, delivery zones and your customers’ receiving hours, and proposes the day’s routes. Your dispatcher reviews and adjusts them, drivers follow them on their phones and you see how every delivery is going.

Company size Mid-sized Large

The problem: routes live in one person’s head

At many companies, dispatch planning depends on one person who knows the city, the customers and the drivers. Every afternoon or early morning they go through the orders in the system or a spreadsheet, group them by area from experience, eyeball whether everything fits on the truck and hand out the route sheets. It works as long as that person is around, the order count stays low and nothing changes at the last minute.

As volume grows, the symptoms show up: some trucks leave half empty while others cannot fit everything, drivers cross town twice, customers with receiving windows get their deliveries late, and loads come back because nobody was there to sign. And while the trucks are out, nobody in the office knows for sure what was delivered, what is still pending and what is coming back until the driver returns with the signed paperwork.

01

Routes built by hand every day

Planning depends on one person’s experience and eats up much of their day. If they are out sick or leave, that knowledge walks out the door with them.

02

Poorly used vehicles

Without matching weight, volume and zones, some trucks leave with empty space, others are overloaded and you pay for miles you could have avoided.

03

No visibility on the road

When a customer asks about their order, someone has to call the driver. Failed deliveries and the reasons behind them are learned late or never recorded.

How route planning works

  1. 1

    It pulls the orders ready to ship

    The system brings in from your ERP or order system everything that needs to go out, with address, weight or volume, priority and each customer’s constraints, such as receiving hours or which vehicle types can access the site.

  2. 2

    It proposes the day’s routes

    It groups orders by zone and builds routes that respect each vehicle’s capacity, delivery windows and starting point, aiming to drive less and arrive on time.

  3. 3

    Your team reviews and adjusts

    The dispatcher sees the routes on a map, moves orders between vehicles, changes the stop order or adds a rush order. The proposal is a starting point; the decision belongs to your team.

  4. 4

    Drivers follow the route on their phone

    Each driver gets their stop list in order, with turn-by-turn navigation to the next stop, contact details and customer notes.

  5. 5

    Proof of delivery and tracking

    At each stop the driver records whether the order was delivered, partially delivered or not delivered and why, with a photo or signature. The office follows progress on a dashboard and can keep the customer informed.

What it looks like in practice

Here is an illustrative example: the day’s orders grouped into routes by vehicle on a map, with each delivery’s progress updating as drivers record it.

Illustration of a route map with stops and assigned vehicles. Not based on client data.

Who it is for

By company size

Small

Not the first solution we recommend at this size.

Mid-sized

For a mid-sized company with its own or contracted fleet of several vehicles and a single shipping warehouse, the system replaces the hand-built route sheet with proposed routes the dispatcher adjusts, and gives you visibility into what happens on the road for the first time.

Large

For a large company with several distribution centers, mixed fleets, third-party carriers and customers with different terms, the system integrates with the ERP and the vehicle trackers, handles multiple shifts and provides on-time performance metrics by route, driver and customer.

Industries where it is common

It is common among logistics providers, distributors that supply stores and chains, agribusinesses that pick up from farms and deliver in town, manufacturers with their own fleet and energy or utility companies that schedule field service visits.

What's included

  • Order import from your ERP, order system or spreadsheet, with geocoded addresses.
  • Setup of vehicles, capacities, zones, starting points and customer constraints.
  • Route proposal engine and map view so your team can adjust before dispatch.
  • Mobile app for drivers with stop order, navigation and proof of delivery by photo or signature.
  • Daily tracking dashboard with completed, pending and failed deliveries and the reason for each.
  • Reports on on-time performance, vehicle utilization and exceptions by route, driver and customer.

Systems it connects to

We name categories and well-known products so you can place your case. This implies no partnership or certification with their vendors: how we connect depends on what each system allows and is defined during the assessment.

Maps and geolocation

Google Maps, Mapbox or OpenStreetMap to geocode addresses, calculate routes and navigate.

ERP and orders

SAP Business One, Microsoft Dynamics, NetSuite, Odoo or your in-house system, depending on what each one allows.

Vehicle tracking

The GPS platform your fleet already uses, if it lets you query locations, or the location from the driver’s phone.

Analytics and reporting

Power BI, SQL Server or Excel for on-time performance, transportation costs and exception reports.

What drives cost and time

We do not publish fixed prices because planning deliveries for a small fleet in one city is very different from coordinating several distribution centers with owned and contracted fleets. These are the factors that most affect cost and rollout time:

1 Constraints to account for

Weight and volume capacity, time windows, refrigerated vehicles, access or traffic restrictions by zone and customer priorities are rules the routing engine has to respect, and each one needs testing.

2 Address quality

In many cities addresses are written a dozen different ways, or they are rural. If they have to be standardized and placed on the map one by one, the initial work grows.

3 Integrations

Pulling orders from the ERP, sending delivery status back and connecting to the fleet’s GPS platform is more or less direct depending on what each system allows.

4 Driver app features

Offline mode, signature and photo capture, cash on delivery or returns recorded on the road all add functionality to the mobile app.

5 Pay-per-use map services

Mapping and routing services charge based on how many requests you make. We estimate that recurring cost with you so there are no surprises.

That is why we do not publish fixed prices or timelines: after a short assessment we give you a concrete proposal with scope, cost and stages.

When we do not recommend it

We would rather tell you before we start. There are cases where this solution is not the best investment:

If your routes are fixed

If you visit the same customers in the same order every day, there is little to optimize. A stop list and a simple delivery log will do.

If you make few deliveries

With one or two vehicles and only a handful of stops, a good spreadsheet and the map app on your phone are usually enough.

If you outsource all transportation

If a carrier plans and runs your deliveries, what helps is connecting to their tracking data, not building your own planner.

Route and dispatch planning FAQ

Does the system decide the routes on its own?

It proposes routes based on your rules, but the final call belongs to your dispatcher. They can move orders, change the sequence or pull a vehicle before publishing the routes. That review is part of the design, because some things only the people who know the operation can see.

What about badly written or rural addresses?

Addresses the system cannot place with confidence are flagged so someone can fix them or drop a pin on the map. That correction is saved to the customer record, so next time the location is already known.

Does it work if I use contracted carriers?

Yes, as long as the driver can use the app or the carrier shares delivery status. We define with you how routes are assigned to owned and contracted vehicles and what information each one has to provide.

Can I add a rush order after the trucks have left?

Yes. The dispatcher can see which vehicle is closest or has room and add the order to its route. The driver gets the change on their phone and the stop order updates.

Do drivers need a special phone?

No. The app runs on ordinary Android phones or iPhones. If coverage is spotty in your area, it can be designed to store deliveries offline and sync them when the signal returns.

Does it use artificial intelligence?

At its core is a route optimization engine. Your delivery history can also be used to better estimate time per stop or anticipate demand by zone, always as support for your team’s decisions, not a replacement for them.

Are your routes built by hand every day?

Tell us how many vehicles you dispatch, from how many warehouses and how you plan today. We will tell you honestly whether a route planner makes sense for your operation and what to tackle first.

Tell us about your case

Shall we talk about your case?

Book an assessment