delivery route sequencing software in Kenya answers a narrower question than most vendors admit. It does not decide which lorry carries what. It decides the order in which the driver knocks on doors.
Get that order wrong and a mathematically short route still arrives at a closed shop in Industrial Area at half past five.
A delivery route sequencing software in Kenya setup is judged at the third stop, when the driver realises the fourth customer left for school pickup twenty minutes ago.
Sequencing Is Not Route Planning
Planning decides which stops belong to a vehicle, a day, and a shift. Sequencing decides what happens first, second, and last inside that list.
Most systems sell planning, because planning looks impressive in a demo. The dispatcher’s daily pain is the order.
A van with eighteen drops in Embakasi can be planned correctly and sequenced badly, and the day still fails.
delivery route sequencing software in Kenya should be judged on the second job, not the first, because that is where the arguments start.
The two tasks also have different inputs. Planning needs capacity, weight, and zone. Sequencing needs windows, service times, traffic, and the driver’s knowledge of a gate.
Confusing them produces a beautiful map and an angry customer at four o’clock.
The dispatcher usually does sequencing by hand, on a printout, with a biro. That is the process the software has to beat.
Beating it means being faster than a biro, not cleverer than a university.
The dispatcher’s version of the question is simpler: which of these eighteen parcels goes first when the school gate closes at four? delivery route sequencing software in Kenya should answer that on one screen, not after three clicks.
Time Windows Beat Shortest Distance
The shortest route between twelve stops is a maths answer. The best route is the one that keeps the most promises.
A shop that opens at nine and closes at four cannot be served at eight, however close it sits to the depot.
delivery route sequencing software in Kenya should sort by the tightest window first, then by distance among stops that share a window.
That single rule prevents most of the disasters. The customer with a two-hour window gets served inside it, and the customer with all day absorbs the variance.
Pure distance optimisation tends to serve the easy stops first and leave the difficult window for last, which is exactly backwards.
The cost of a missed window is not the fuel saved. It is the redelivery, the phone call, and the review that follows.
A sequence that travels four extra kilometres and keeps every window is cheaper than a perfect loop with two failures.
Distance still matters, but as a tie-breaker, not as the objective.
A window of nine to eleven is tighter than one of nine to five, and delivery route sequencing software in Kenya should weight it that way even when the addresses are neighbours.
Weighting by minutes promised rather than kilometres travelled keeps the morning honest. A route that looks long but hits every window is the better route.
Two stops in the same building should never be separated by a trip across town. delivery route sequencing software in Kenya should keep them adjacent even when their windows differ by an hour.
Thika Road Before Seven
Thika Road inbound after half past six is a car park with ambitions. A van joining at Kasarani at seven will lose an hour before Garden City.
Outbound traffic behaves differently, which is why the direction of the peak matters more than the name of the road.
delivery route sequencing software in Kenya should know that a stop in Roysambu costs twenty minutes in the morning and eight in the afternoon.
The practical answer is to serve the northern corridor first if the van starts south of it, or to hold those stops until after nine.
Kahawa, Zimmerman, and Githurai sit behind the same bottleneck, so grouping them into one run is better than threading them through a CBD route.
A sequence that puts one Roysambu stop between two Westlands stops is a sequence written by someone who has never driven it.
Historical travel times beat posted speed limits, and the software should learn from the depot’s own trips.
The first month of data usually shows the morning peak is worse than anyone estimated.
Test the sequence on a Thursday, not a Sunday, because delivery route sequencing software in Kenya should be tuned to the road that actually exists at seven in the morning.
A depot that plans from a Sunday drive will always be surprised on Monday. Real trips, recorded by hour, are the only honest input.
delivery route sequencing software in Kenya should treat the peak direction as something that flips at ten, or it will be right in the morning and wrong at six.
Mombasa Road and the Southern Bypass
Mombasa Road punishes optimism. Nyayo Stadium, the Cabanas stretch, and the Mlolongo crawl can add ninety minutes to a run that looked reasonable at six.
The Southern Bypass changed the geometry for anyone heading west, but it also moved the congestion to the interchange.
delivery route sequencing software in Kenya should treat the airport corridor and the Athi River corridor as separate sequences, not one long line.
A van delivering to Mlolongo, Syokimau, and Athi River should finish the loop before returning, because the return leg is the expensive part.
Crossing to Karen or Ngong through the bypass only pays if the load justifies the distance. Otherwise the depot is buying scenery.
Evening peaks reverse the pattern. What was slow inbound at eight is slow outbound at six.
The sequence should be built for the hour it will be driven, not for the hour it was planned.
Static maps cannot do that. A library of observed times by hour can.
delivery route sequencing software in Kenya should hold a fallback route for the interchange, because one stalled lorry on the bypass can add forty minutes.
Mlolongo and Athi River should sit at the end of the corridor, not the middle, so the return leg is short and the afternoon is free.
delivery route sequencing software in Kenya should measure the corridor in minutes, because a South B stop can be closer to Industrial Area than to the next address on the map.
Rider Routes and Van Routes
A boda rider and a three-tonne lorry do not share a sequence, even when they share a postcode.
A rider can use a footpath, cut through a market, and park on a pavement for two minutes. A van needs a gate wide enough, a place to turn, and a guard willing to lift a barrier.
delivery route sequencing software in Kenya should keep separate speed profiles for each vehicle class, because the same street takes four minutes on a boda and fifteen in a lorry.
Riders also carry less, so a rider sequence can afford more stops per hour and tighter windows.
The van sequence has to account for loading bays in the CBD, where a delivery to a shop on Moi Avenue may need a handcart and a porter.
Mixing the two profiles produces impossible estimates. A dispatcher who sends a van on a rider’s route will hear about it at the first cul-de-sac.
Vehicle class belongs in the sequence engine, not in a note on the order.
delivery route sequencing software in Kenya should not pretend a van can serve twenty small parcels in a five-kilometre radius, because it will manage six.
Vehicle class also changes the parking time. A boda parks anywhere, while a lorry circles the block looking for a gap wide enough.
delivery route sequencing software in Kenya should keep refuelling out of the eight o’clock peak, because a lorry queuing for diesel is a stop that delivers nothing.
Priority Parcels and the Paid Promise
Every depot has parcels that must go first: the medical sample, the spare part for a stalled machine, the contract customer who pays for a morning slot.
Priority is not the same as urgency. Urgency is what the customer feels. Priority is what the depot has agreed to sell.
delivery route sequencing software in Kenya should let a stop carry a rank that survives re-sequencing, so a premium parcel does not drift to stop fourteen.
The rank should also carry a price. If a customer pays extra for the first hour, the sequence has to protect that revenue.
Blind prioritisation fails too. Twenty “urgent” parcels in one morning is a queue, and the sequence should say so rather than pretend.
The dispatcher needs a view of how many priority stops fit before ten o’clock, and a rule for what happens when the number is exceeded.
That conversation belongs at the counter, before the parcel is accepted, not at noon when the promise is already broken.
A priority flag without a capacity check is a promise with no owner.
delivery route sequencing software in Kenya should print the paid morning slot at the top of the run sheet with a time beside it, not behind a colour code.
When two priority parcels conflict, the one with the tighter window goes first. The other gets a call and a new estimate.
delivery route sequencing software in Kenya should count remaining minutes, not remaining parcels, when an express booking lands at nine for noon.
Re-Sequencing at Midday
The morning plan rarely survives until lunch. A breakdown, a road closure, or a customer who suddenly needs the delivery today forces a new order.
Re-sequencing is not replanning. The completed stops stay completed, the load in the van stays loaded, and only the remaining stops move.
delivery route sequencing software in Kenya should recalculate from the driver’s current position, using the parcels actually on board, not the parcels that were planned.
That distinction matters when a stop was skipped. The parcel is still in the van, and the new sequence has to place it somewhere sensible.
The customers whose windows move should be told immediately, with a new range rather than an apology.
A dispatcher who re-sequences silently creates five complaints at five o’clock.
The software should also show the cost of the change: extra kilometres, extra minutes, and which later windows are now at risk.
That cost is the argument the dispatcher needs when a customer demands to jump the queue.
delivery route sequencing software in Kenya should re-sequence at noon from the actual position and the actual load, because that is when the plan meets the day.
The change should reach the driver’s phone before the next stop, not after it, or the recalculation is only a report.
delivery route sequencing software in Kenya should recalculate every time a stop is marked complete, not only when the dispatcher remembers to press a button.
Failed Drops and the Return Leg
A failed drop is not the end of a stop. It is a parcel that stays in the van, taking up space and attention for the rest of the day.
The sequence should include a wait time, because a driver who waits four minutes and leaves is cheaper than one who waits fifteen and misses the next window.
delivery route sequencing software in Kenya should record the attempt, the reason, and whether the parcel returns to the depot or moves to tomorrow’s run.
The return leg is where sequences quietly fall apart. The last stop is often forty kilometres from the depot, and the driver is already past the legal driving hours.
Building the return leg into the sequence, rather than treating it as free, changes the shape of the afternoon.
A depot in Ruiru serving Limuru should not plan a final stop in Limuru at seven in the evening.
Failed drops also cluster. Three failures in one estate usually mean a gate policy or an address error, not three unlucky customers.
The daily sequence review should read those three together.
delivery route sequencing software in Kenya should carry a failed attempt into the next day’s sequence, so the same stop is not tried again at the same useless hour.
Fuel Cost Per Stop
Fuel is spent between stops, not at them. A route with twelve stops spread across five estates burns more than fifteen stops inside three.
The difference shows up as a cost per stop, and that number is the honest measure of a sequence.
delivery route sequencing software in Kenya should report litres per stop and shillings per stop beside the stop count, or the improvement stays invisible.
Idling is the hidden cost. A van waiting twenty minutes at a loading bay with the engine running burns fuel and delivers nothing.
Sequence the heavy, slow stops into the middle of the day, when the driver is fresh and the traffic is lighter, and the idle time falls.
Grouping by estate also reduces the number of turns, which is where small vans lose most of their fuel.
A sequence that looks tidy on a map can still cost an extra KES 900 a day in wasted movement.
Over a month, that is a salary.
delivery route sequencing software in Kenya should report fuel per stop rather than fuel per kilometre, because the idling and the reversing belong in the number.
A depot that cuts two stops from a route but adds six kilometres has probably saved nothing. The report should say so plainly.
delivery route sequencing software in Kenya should move that stop to the front of the run, because twenty minutes at the same gate every Tuesday is a sequencing problem.
Dispatcher Override and the Reason Field
Every dispatcher overrides the sequence, and that is not a failure of the software. Local knowledge lives in people, and people should be able to use it.
What matters is whether the override is recorded. An unrecorded override teaches the system nothing and hides the reason from the next shift.
delivery route sequencing software in Kenya should ask for a reason from a short list: customer request, access, traffic, load, or driver knowledge.
After a month, the override log becomes a map of the places the algorithm gets wrong.
Ten overrides on the same street is a data problem. Ten overrides by the same dispatcher may be a training problem.
Neither is visible without the reason field.
The dispatcher should also be able to lock a stop in place, so a recalculation does not undo a deliberate decision.
A lock without an expiry becomes permanent, so review the locks monthly.
delivery route sequencing software in Kenya should make the reason field mandatory on an override, or the next dispatcher inherits the change without the thinking.
Learning From Actual Times
The planned time for a stop is a guess until the depot has driven it. After three months, it is a measurement.
Arrival time, departure time, and the gap between them are the three numbers that turn a sequence engine from generic to local.
delivery route sequencing software in Kenya should compare planned against actual for every stop and publish the error by estate.
A stop in Kasarani that is planned at eight minutes and takes twenty-two is not an anomaly. It is a fact the next plan should use.
Service time libraries should be built by category: a pharmacy counter, a school office, a construction site with no gate.
Waiting at the gate is usually the largest error, and it is almost never in the original estimate.
The engine should also learn the difference between a Tuesday and a Saturday, because Kenyan delivery days are not identical.
Rainy seasons deserve their own profile. April and November are not the same road as January.
delivery route sequencing software in Kenya should learn from three months of arrival times, which will beat any vendor’s standard speed table for Nairobi.
Publish the error by estate each month. The places with the biggest gap between plan and reality are where the next improvement lives.
delivery route sequencing software in Kenya should record the arrival time at the gate, not at the estate, because the gate is where the minutes disappear.
Driver Trust in an Unfamiliar Order
A new driver follows the app because he has no choice. An experienced driver ignores it the moment it sends him somewhere silly.
That moment decides whether the software survives in the depot.
delivery route sequencing software in Kenya earns trust by being right early, on the stops the driver already knows, before it asks him to trust it on the ones he does not.
The first week should pair the sequence with the driver’s own route and show the difference, rather than demand compliance.
A skip button with a reason is better than a silent deviation. The reason becomes data, and the driver keeps his dignity.
Supervisors should resist the urge to treat every deviation as indiscipline. Sometimes the driver is right and the map is wrong.
The good depots ask the driver to explain the deviation at the end of the shift, in two minutes, and write it down.
A sequence that never learns from the people driving it will be overridden forever.
delivery route sequencing software in Kenya should let that driver record the knowledge, or it leaves with him when he changes employer.
Trust is built in the first week, on routes he already knows. If the order is right there, he will follow it on the routes he does not.
delivery route sequencing software in Kenya should offer one tap for why a stop was skipped, because that reason is worth more than the compliance percentage.
Estates, One-Way Streets and Service Roads
Nairobi’s estates have their own logic. Kilimani runs on one-way loops, Kileleshwa has service lanes behind the main blocks, and South B has roads that end at a wall.
A sequence built on a generic map will route a van the wrong way up a one-way street and call it an optimisation.
delivery route sequencing software in Kenya should accept a depot-specific map layer: no-go turns, loading bays, and the service road that saves six minutes.
Drivers know these details and rarely write them down. The software should give them a way to record them at the point of discovery.
A single note about a broken barrier can save a failed drop every week.
Estate security also changes the sequence. A gated community that closes its gates at eight in the evening moves every stop after it.
Map data ages quickly in a city that builds. A sequence engine that cannot be corrected locally will be wrong within a season.
delivery route sequencing software in Kenya should let the dispatcher draw a service road once, because it saves ten minutes and appears on almost no map.
Load Order Inside the Van
A perfect sequence is undone by a badly packed van. If the first delivery is at the back of the load, the driver spends twenty minutes unloading the street.
The sequence should generate a loading order in reverse: last stop first, first stop last, heavy items on the floor.
delivery route sequencing software in Kenya should print that load order beside the run sheet, not hide it in a separate screen.
Drivers and loaders need the same list, in the same order, or the van gets packed by habit.
Fragile items belong on top regardless of sequence, which is a constraint the engine should accept rather than fight.
Multi-drop vans with cages work differently: the cage number matters more than the stacking order.
A sequence that ignores the physical van is only a list of addresses.
The test is simple: can the loader pack the van from the printout without asking a question?
delivery route sequencing software in Kenya should print the loading order backwards from the sequence, so the last stop sits at the back doors.
A van repacked at the roadside is a van that has already lost twenty minutes, and the afternoon estimate should show that loss.
delivery route sequencing software in Kenya should put the weight constraint on the same sheet as the sequence, or a generator ends up on top of a carton of eggs.
School Runs, Market Days and Rain
The school run at seven in the morning closes estate roads for forty minutes. No algorithm fixes that, but a sequence can avoid it.
Gikomba market days change the traffic around whole streets, and a delivery to a shop inside the market needs a handcart and a different hour.
delivery route sequencing software in Kenya should carry a calendar of local events: school terms, market days, and the county fairs that block a road.
Rain deserves its own rule. The underpass at Enterprise Road floods, the murram section in Kahawa West turns to soup, and a two-wheel drive van stops.
Building a wet-weather sequence for April and November is not over-engineering. It is the difference between a late day and no day.
The driver should be able to trigger the wet profile from the cab, and the remaining stops should recalculate.
Customers on the flooded side of the route should hear about the delay before they start calling.
delivery route sequencing software in Kenya should hold a wet-weather order that avoids the known flood points, because a two-hour storm can wipe out an afternoon.
Market days move the traffic, not the customers. The shop is still open; the street in front of it is not.
Sequencing Across Counties
A route from Nairobi to Machakos, Kajiado, and Kiambu is not one sequence. It is three corridors that happen to share a depot.
Sixty kilometres between stops makes the order almost irrelevant. What matters is which corridor runs first and whether the van returns loaded.
delivery route sequencing software in Kenya should break long routes into corridors and sequence within each one, not across the whole map.
The return load is the other half of the economics. A van that goes to Nyeri empty and returns empty pays twice for the same diesel.
Sequencing should consider the pickup stops on the way back, even when they belong to a different department.
Overnight runs need a different rule set: driver rest, security at the destination, and a receiver who is awake at six.
A county route planned like a Nairobi route will always look inefficient, because the assumptions are wrong.
Long-distance sequencing is really a schedule of corridors, with slack built in for the weighbridge.
delivery route sequencing software in Kenya should name the weighbridge, the fuel stop, and the overnight point, because those three facts decide the schedule.
Return loads should be sequenced too, or the van drives back empty past three shops that were waiting for a collection.
Measuring Adherence Without Punishing Sense
Adherence is easy to measure and easy to misuse. A driver who leaves the sequence to avoid a jam is not failing; he is doing the job.
The number that matters is the window hit rate, followed by cost per stop and failed attempts.
delivery route sequencing software in Kenya should report all three together, because any one alone tells a misleading story.
A depot can hit every window by refusing difficult addresses, and it can cut cost per stop by abandoning service.
Adherence still has a place as a diagnostic. A sudden drop in one driver’s adherence usually means a road change or a broken app.
Review it weekly, with the driver present, and treat the deviation as information rather than a charge.
The best depots reward the driver who calls in a problem early, because that call saves three later failures.
delivery route sequencing software in Kenya should report the window hit rate by route, because a structural problem will make every driver look careless.
Reward the early call. A driver who reports a blocked road at ten saves the depot three failed drops and two angry calls by four.
delivery route sequencing software in Kenya should fix the route before the conversation about discipline begins, because one bad route makes five good drivers look slow.
The Order the Customer Sees
The customer never sees the sequence. They see an estimated arrival, a driver’s name, and sometimes a dot moving on a map.
That estimate is only as good as the order behind it. A sequence that ignores service times will produce an ETA that drifts all afternoon.
delivery route sequencing software in Kenya should publish the estimate from the same calculation the driver is following, not from a separate promise made at the counter.
When the sequence changes, the estimate should change with it, and the customer should be told.
A dot on a map without a believable time is entertainment, not information.
The final operational point is uncomfortable for vendors: the sequence is a promise expressed in minutes, and it has to be rebuilt every morning from real times, real roads, and the driver’s own knowledge.
delivery route sequencing software in Kenya should publish the ETA from the same calculation the driver follows, or the two will disagree by lunchtime.
delivery route sequencing software in Kenya should move the promise by minutes when the lorry is stuck, not by a vague message about soon.
A depot that reviews that promise daily will beat one that bought the biggest map.
