Built from the geography up
Outlets are organised by where they actually are, rather than by an arbitrary list inherited from whoever drew the territory last.
Turn a scattered outlet book into balanced, road-true routes. Overlap diagnostics, real road distances, leaner routes and a right-sized fleet, computed entirely in your browser, so no row of your route book ever leaves it.
Client-side route intelligence · no account, no upload
Distributors and FMCG operations whose route book was drawn by whoever held the territory last.
Two files: an outlet-level book, and a point master with anchor coordinates. Both as plain CSV.
Rebalanced routes written in landmark names, an assigned vehicle per route, and a costed impact summary.
In the browser. Not a single row of your outlet book leaves the machine it was opened on.
Most route books are inherited rather than designed. OptiRoute rebuilds one around real geography and real cost, and hands back a book that is shorter to drive, cheaper to run and ready for the field.
Outlets are organised by where they actually are, rather than by an arbitrary list inherited from whoever drew the territory last.
Route sections that compete for the same ground are flagged, so conflicting territories surface before they cost anything.
Distance and time are measured along the actual road network. What the model reports is what a vehicle really covers, not what a straight line suggests it might.
A shorter line is not always a cheaper route. OptiRoute rebalances the book toward fewer, leaner routes that still keep every outlet and all of its commission.
Each route is matched to the vehicle it actually needs, so fuel, upkeep and vehicle investment come down together rather than one at a time.
No coordinates. Routes are handed back as the bazars and markets a field force already knows, in the order they will walk them.
Upload, the workspace and its constraints, the diagnostics that justify a change, the comparison that shows it, and the exports that put it in a rider’s hands.
An outlet book and a point master, dropped in side by side, with blank templates if you need them.
What was wrong with the data and what was done about it, line by line, before anything is computed.
Diagnostics, route map, impact and exports: one dataset, four views of it.
Cascading filters down to the depot, section or route you actually want to work on.
The planning levers your team controls, each explained inline, all in one rail.
Change a constraint and the previous result is retired rather than left sitting under a new heading.
Every route/section pair competing for the same ground, with how close their outlets come.
Outlets sitting where no route should reasonably reach, flagged before they distort a route.
Original and optimized side by side, pan and zoom synchronised, satellite per pane.
Distance and time measured along the road network, not as a straight line between points.
Routes, commission and daily sales before and against after, with the difference priced.
Overlap and outlier workbooks, the optimized route book as CSV, and a branded PDF report.
Two files in. Before anything is optimised, OptiRoute checks and repairs the book in the browser, then counts what is actually in it, and breaks every conflicting route pair down to how close it really comes.
The outlet book and the point master go in together. Each zone confirms the file it received, and the run reports what it is doing rather than showing a spinner.
Outlet-level book: regions, routes, retailers, locations, sales and brand volumes.
Point master: the location of every distribution point.
A health check of the book as delivered. Headline counts over the whole book, then every overlapping route/section pair with how close its outlets come.
Before anything is optimised, the repair log says what it found in your files and what it did about it. A result built on quietly corrected data is a result nobody can defend in a meeting.
The planning levers sit together in one place, each with an inline explanation of what moving it will do.
Change a constraint and the previous optimisation is retired on the spot. What is on screen is always what the current settings produce.
The whole model runs client-side. An outlet book is commercially sensitive, and the simplest way to keep it that way is for it never to be uploaded anywhere.
Two maps, pan and zoom synchronised, so a change is seen rather than described. Then the same change priced: routes, commission and daily sales before and after, and what the difference is worth annually.
The inherited tangle against the rebalanced network, each pane with its own satellite layer and cluster overlay. Route lines follow the road network, so the distance shown is the distance driven.
What the run changed, and what it is worth. Forty-eight source routes become forty-three with every outlet and all commission kept, then the annualised value of the difference.
An outlet book is one of the most commercially sensitive files a distributor has. The simplest way to keep it safe is never to send it anywhere, so OptiRoute does the whole thing in the browser.
Bring one region's outlet file and a point master. We will show you the overlaps you are already paying for, and what the rebalanced book would be worth.