Routes that replan themselves when orders land.

A route a driver is already running does not get rewritten underneath them. Planning can add work to the end of it, and that arrives as an offer the driver can decline. Stops already closed stay closed.

Yes. Dispatch sees the proposal before it goes out and can revise stops, split a route, adjust timing, or take manual control of the plan and keep it.

Yes. A trip can be frozen, and planning will stop proposing changes to it. Use it for the routes you have already promised to a driver or a client while the rest of the day keeps replanning.

Two ways. Dispatch assigns a route to a driver directly, or the trip goes out as a timed offer. Offers go to the nearest available driver first and move down the list from there.

The offer has a clock on it. If the driver declines or the time runs out, it moves to the next available driver. If nobody takes it, the trip goes back to dispatch and shows up in the list of trips needing manual dispatch rather than sitting unassigned.

It does not get quietly forced onto a route. Work that will not fit your windows, capacities, and driver rules is held for the next planning run or flagged for dispatch to place by hand.

The console opens on the exceptions rather than a wall of averages: stops at risk, stops already overdue, trips that need manual dispatch, and drafts still missing details. The idea is that dispatch sees the alert on the screen before the customer calls.

A photo and the completion status before the stop closes. If a stop is skipped or fails, the driver records the reason. It lands on the trip record with the rest of the delivery history.

Dispatch creates the work in the console, or your business clients submit their own shipments through their portal and follow the status there. There is also an API with access tokens if you want another system to push orders in. If your orders live somewhere else today, tell us and we will confirm the practical way to connect it.

Yes. Each client organization gets its own portal: submit a shipment with pickup, drop-off, and window, watch the status change, and copy the tracking link. Dispatch sees that work in the same pipeline without typing it in again.

A tracking page with live status, the ETA window, the driver on the map when location is available, a progress timeline, and proof of delivery once the stop closes.

Yours. The console, the driver app, the client portal, and every tracking link a customer opens carry your company identity, not ours.

No, and it is worth being clear about it. Route Optima is built for last-mile delivery: planning, dispatch, driver execution, client intake, and customer visibility. It does not do freight forwarding, container tracking, or carrier rate procurement.

The 15–40% range is from busy days delivery companies sent us, on distance and drive time against the plan they were running. It is not a guarantee. It moves with your geography, how dense your orders are, and how good the current plan already is. That is the point of sending one day.

About 2,000 orders a day for a single fleet. How far that goes in practice depends on how complex your rules are and how often you replan, which we check on your own day.

We go through the comparison with you. If it holds up, we configure your rules, run real days with dispatch, and train the team, then start a free 14-day live trial on your real operation. You pick a paid plan after the trial, not before.

It is used only to build your comparison, shared with no one, and deleted on request. We need addresses and timings. If some columns are sensitive, strip them and we will tell you if anything essential is missing.