Hundreds of drops,
sequenced in
seconds.
Routes, shipments & warehouses, optimised. LogisPro weighs traffic, delivery windows, vehicle capacity and driver hours, then builds the lowest-cost route for every vehicle in the fleet. Once they are moving it tracks each shipment live, flags the ones that will miss their window before they miss it, and runs the warehouse behind them from putaway to dispatch.
Route optimisationLive trackingWarehouse WMS
One shipment on one corridor. Position, hub dwell and the trailing performance of this lane resolve into an arrival estimate that updates as conditions do. The amber leg is not a report of a late delivery — it is the estimate crossing the delivery window while the vehicle is still short of the border.
Route optimisation
The same twelve drops,
sequenced twice.
On the left, the order the work arrived in — three vans loaded as orders were taken, which is how a round gets planned by hand under time pressure. On the right, the identical twelve drops sequenced against traffic, delivery windows, vehicle capacity and driver hours. Nothing has been added and nothing has been dropped. Only the order has changed.
Planned by hand
As orders arrivedSequenced by LogisPro
OptimisedA worked example on one depot’s twelve drops, so that the two sequences can be read side by side. The 22 per cent distance reduction shown is the published figure for optimised routing; a live plan runs to hundreds of drops and produces its own numbers against your own windows, capacities and driver hours.
Published figures
Delay detection
Late is a prediction,
not a report.
Every active shipment is scored continuously against its own delivery window. Position, hub and border dwell and the trailing performance of the lane resolve into an arrival estimate, and the exception is raised when the estimate crosses the window — not when the consignee telephones.
| Shipment | Route | Stops | Window | ETA | Predicted delay | Status |
|---|---|---|---|---|---|---|
| SH-40912 | Jebel Ali → Riyadh | 1 | 14:00–18:00 | 20:10 | +2 h 10 | Predicted late |
| SH-40913 | Sohar → Dubai | 3 | 09:00–13:00 | 11:25 | — | In transit |
| SH-40915 | Dammam → Kuwait City | 2 | 08:00–12:00 | 12:40 | +40 min | Predicted late |
| SH-40918 | Abu Dhabi → Doha | 1 | 06:00–10:00 | 07:50 | — | In transit |
| SH-40921 | Dubai → Al Ain | 9 | 12:00–16:00 | 15:35 | — | On route |
| SH-40924 | Jeddah → Medina | 6 | 07:00–11:00 | 10:05 | — | Delivered |
Neither flagged shipment is late yet. SH-40912 is still short of Al Batha and its border dwell is running over the trailing average for the crossing, which is enough to move the estimate past the window while there is time to act on it.
The consignee hears it from you
Tracking links and estimated arrival times are issued automatically on dispatch and follow the estimate as it moves. The customer is told the window has slipped before they notice it themselves.
Rerouting is a re-optimisation
Taking a stop off one vehicle is not a phone call. The remaining stops are re-sequenced from the vehicle’s current position against the windows that are still open, and the driver’s mobile route updates.
Dispatch by exception
A planner should be looking at the shipments that need a decision rather than refreshing the ones that do not. Only a material change in the estimate raises the shipment to the top of the board.
One picture, not one per carrier
Own vehicles, courier partners and last-mile subcontractors report onto the same map and the same board, so the network is read in one place rather than in four portals.
Warehouse WMS
Putaway to dispatch,
with the keyboard
taken out.
Four hops behind the fleet. At each one the movement is confirmed by scanning a barcode or a QR code rather than by typing it, which is what removes the manual entry and the picking error that follows from it.
Any camera is a scanner
Barcode and QR both resolve to the same records, on handheld terminals or on a driver’s phone. Nothing on the floor depends on proprietary hardware being in the right hands.
One stock position
The bin, the pick and the carton move the same stock record the ledger values, so the warehouse and the books do not need reconciling to each other at the end of the month.
Drivers, vehicles, carriers
Who is on shift,
who is nearest,
who is legal to go
A route is only as good as the assignment behind it. Driver hours, shift availability, vehicle type and document validity are all attributes of the same records the optimiser plans against, so an assignment that cannot legally be made is not offered.
Hours, performance and compliance
Driver hours accrue from the trips actually run. Licence, permit and medical expiry sit on the same record, and an expired document blocks assignment rather than surfacing in an audit.
Assigned dynamically
A job is offered against proximity to the pickup, shift availability and vehicle type — so the nearest van that is on shift and the right size takes it, without a dispatcher holding the map in their head.
Multi-carrier, rate-shopped
Couriers, freight brokers and last-mile partners connect to the platform. Rate-shop across them for a given movement and book the winner without leaving the system or opening a portal.
Customers get a link
Automated tracking links and estimated arrival times go out on dispatch. Support time falls because the question most customers ring to ask has already been answered.
How it works
Three steps to a
planned morning.
Import your network
Depots, vehicles, drivers and customer addresses. Connect the order system you already run, or push orders in through the open API.
Optimise and dispatch
Each morning LogisPro builds optimised routes for the whole fleet. Review them, adjust what you want to adjust, dispatch in one click — drivers get their routes on mobile.
Track, measure, improve
Monitor deliveries live and measure on-time rate, fuel and cost per delivery. Weekly AI reports keep taking waste out of the plan.
“We were spending enormous time manually planning routes and still missing delivery windows. FlowZa LogisPro automated the entire process, cut our fuel costs by a quarter, and our customer satisfaction scores have never been higher.”
Questions operators ask
What is the difference between LogisPro and Fleetza?
LogisPro plans and tracks the work — routes, shipments and the warehouse behind them. Fleetza watches the vehicle and the driver — condition, behaviour and cost per kilometre. They share the vehicle and driver records, so a driver’s hours in LogisPro and their safety score in Fleetza belong to the same person. Operators who only need the day planned run LogisPro; operators who also want to know which vehicle is about to fail run both.
Can we keep our existing telematics?
Yes. LogisPro consumes position and hours-of-service events from a provider you already have and uses them to drive estimates and compliance. FlowZa Fleetza is one such provider — a separate application on a separate subscription, connected to LogisPro over its API like any other telematics feed.
How many drops can it sequence at once?
A depot’s full day, in seconds rather than in a morning. The optimiser weighs traffic, time windows, vehicle capacity and driver hours together, which is why the result is a plan you can dispatch rather than a shortest-path suggestion a planner then has to make legal.
Does the warehouse module need dedicated hardware?
No. Barcode and QR scanning work from any device with a camera, including a driver’s phone at the dispatch door. Ruggedised terminals are supported where the environment demands them, but nothing in the workflow depends on them.
Where does the delivery cost actually come from?
From posted figures rather than an assumed rate per kilometre. Fuel, driver pay, tolls and subcontractor settlement reach the same ledger that produces the customer invoice, so cost per delivery and margin per lane are read from accounting records instead of being estimated alongside them.