Walkthrough

From order file to delivered, in six steps

This is what your team does each day, in the order they do it. Steps one to five belong to your operator and take him minutes rather than hours; step six is the part you look at. Nothing below is a concept — every screen is running today on the ITC distributor pilot.

Step 1 · Morning

Import today’s orders

Your ERP already produces a daily sales order file. Drop it into RouteSync and it becomes structured, weighed, retailer-matched work.

Duplicate-safe by designOrder numbers already in the system are skipped, never overwritten. Re-uploading the same file twice does nothing.
Weight comes from the file, not from data entryEvery line where the base unit is kilograms is summed onto the order. That number is what the planner uses. No one types a weight, ever.
Problems surface before you commitUnknown customer codes, bad dates and unmatched SKUs are listed on a preview screen. Valid rows commit; the rest wait for a fix.
The product catalogue fills itselfNew SKUs and pack configurations are learned from the same file. There is no second master for your team to maintain.
routesync.app/wd/orders/import
Import orders · preview Commit 154 orders
Rows read
1,312
Orders
154
Duplicates skipped
12
Unknown customer
3
Detected columns · Trishul Sales Order Register
Order No. → orders.order_noMapped
Customer Code → retailer lookupMapped
Base UOM / Base UOM Qty → order weight (kg)Mapped
SKU Code · Name → SKU master (auto-created)18 new SKUs
Import preview — you see exactly what will land before you commit
Step 2 · Before planning

Know the shape of the day

Four tiles on the dashboard tell you where every order in the business stands right now — and the exception card tells you what needs a human.

Imported
Landed from the file, not yet workable
Ready
The pool the planner picks from
Dispatched
On a trip the driver hasn’t started
In trip
Driver has started; GPS is being captured
Delivered
Confirmed at the shop, with proof
Undelivered
Closed with a reason — shop closed, refused, address

Nothing changes state on its own. RouteSync detects stale trips and stuck orders and surfaces them as a button — the database only moves when a person clicks.

routesync.app/wd
Today · WD-447 Hyderabad · Tue 28 Jul
Import orders Plan trip
Imported / Ready
0 / 154
154 ready to plan
Out for delivery
59
3 trips active
Delivered
535
OFR 99.8%
Issues today
1
1 stop flagged
Live now
A TR-28Jul-0431 · Ramesh · TS09 EK 4412 12 / 19 stops
B TR-28Jul-0432 · Suresh · TS09 FA 8890 7 / 16 stops
C TR-28Jul-0433 · Naveen · TS10 CB 2201 idle 27 min
Exceptions today
VB554 · SOWMYA K/GShop closed
VB121 · SRI BHAVANIPartial
All other stops on plan
The operator dashboard — four tiles, live trips, exceptions
Step 3 · The core

Auto-route builds the day’s trips

Every ready order. Every eligible vehicle. Every retailer’s pin. The planner takes all three and proposes a full set of trips — then hands you the pen.

You set four dials

Fill % target, max stops per trip, which vehicles to use and in what priority, and which salesmen’s orders to leave out of this plan.

Clustered by geography

Orders are grouped by where the shops physically are, so a trip stays in one part of the city instead of zig-zagging across it. Same-beat shops get a nudge to stay together — but never a cross-town detour.

Capacity is a hard wall

Each cluster is capped at your fill target of the vehicle’s rated weight — a deliberate safety margin against last-minute additions. It is not overridable from the screen.

Sequenced, not just grouped

Within each trip the stop order is optimised from the warehouse outward, then polished — so the driver gets a route, not a list.

routesync.app/wd/trips/auto-route/preview
Auto-route preview · 154 ready orders · 4 vehicles
Save as drafts Re-generate
Trips
4
Stops planned
71
Weight
3,842 kg
Unplanned
6
closed pending driver
Trip 1 · TS09 EK 441274% full
1VB279 · ANNAPURNA KIRANAM38.6 kg
2VB461 · SRI VENKATESHWARA KG50.9 kg
3VB1405 · GAYTHRI KGS6.0 kg
+ 16 more stops · ETA 09:40 → 15:20
Trip 2 · TS09 FA 889071% full
1VB562 · BHARATHI K/G8.2 kg
2VB635 · SRI VENKATESHWARA5.4 kg
+ 14 more stops · ETA 09:40 → 14:05
6 orders left in the Ready pool — 4 retailers have no GPS pin, 2 exceed remaining capacity. Review
Preview — four trips, fill bars, and what didn’t fit

Nothing is committed until you say so

See it on a map firstColoured route per trip, numbered pins in delivery order. Sidebar cards show stops, estimated fill and the ETA window per vehicle.
Move a retailer between tripsDrag it across, reorder within a trip, drop a stop entirely. The plan is a starting point, not a verdict.
What didn’t fit stays visibleLeftovers sit in a clearly labelled unplanned bucket with the reason — no GPS pin, over remaining capacity — and stay in the ready pool for tomorrow or a second run.
Or plan by handThe manual builder is still there: pick retailers beat by beat, watch the capacity bar, hit Calculate & optimise. Use it when you already know what the day should look like.
routesync.app/wd/trips/build
Build a trip · manual (beat-wise) Calculate & optimise
Ready-order pool · grouped by beat
CY0000000018 · NACHARAM_Z2_Prime11 eligible
VB279 · ANNAPURNA KIRANAM2 orders · 104 pkts
VB461 · SRI VENKATESHWARA KG1 order · 99 pkts
VB282 · GANESH K/M1 order · 1 pkt
CY0000000051 · NACHARAM_Z2_2w_1a9 eligible
VB562 · BHARATHI K/G1 order · 8 pkts
Trip stopsFill 74%
1KEERTHANA KIRANA15.7 kg
2VB0143 PUSHPA KIRANAM38.6 kg
3VB121 · SRI BHAVANI50.9 kg
4VB1439 · SRI BALAJI65.3 kg
11 stops · 499 packets · 2 h 40 m est.
The manual builder — pool on the left, trip on the right, capacity live
Step 4 · One click

Dispatch — and everyone knows

Dispatch locks the trip, pushes it to the driver’s phone, and starts the clock. Three things happen at once, and none of them need a phone call.

The driver sees his route instantlyOrdered stops, retailer details, packet counts and one-tap navigation. Stops stay locked until he taps Start, so the odometer reading is captured properly.
Each retailer gets a WhatsApp“Your delivery is on the way” the moment the driver starts. You can turn this off per distributor if retailers ask you to.
Every stop gets a delivery OTPThe driver must enter the code the retailer received before a stop can be marked delivered. A fallback code covers the phone-is-off case.
Trip 1 · 19 stops10:41 ·
Next stop · 3 of 19
VB121 · SRI BHAVANI
1.4 km · ETA 11:06 · 60 packets
Navigate Deliver
Confirm delivery
4-digit OTP sent to retailer on WhatsApp
7 3 1 _
GPS captured · ±12 m
Remaining
4VB1405 · GAYTHRI KGS
5VB1439 · SRI BALAJI
The driver app — installs to the home screen, works on any Android phone
Step 5 · On the road

Watch the day happen

The live tracking page refreshes every 60 seconds. Map on top, stop timeline below, exceptions front and centre.

Planned vs actual, per stopETA, actual arrival, the delta, time at stop and distance delta. You can see a route degrading before the day is lost.
Idle-too-long flags itselfA driver parked at one stop past the threshold gets a red pill on the trip row. That’s your cue to call — not a routine check-in.
Every exception is evidencedShop closed, refused, address mismatch, partial — each captured with GPS and a timestamp. When a retailer disputes, you have the record.
Wrong shop pin? Fixed from the fieldDrivers and field salesmen can flag a bad location with a photo and a GPS reading. It lands in a review queue; one click updates the master.
routesync.app/wd/tracking
Live tracking · refreshes every 60s
3 in progress 1 delayed
closed pending driver
TR-28Jul-0431 · Ramesh
KEERTHANA KIRANA10:14 · +2m
VB0143 PUSHPA KIRANAM10:41 · −6m
3 VB121 · SRI BHAVANIat stop 27m
4 VB1405 · GAYTHRI KGSETA 11:35
5 VB1439 · SRI BALAJIETA 11:58
Plan vs actual · Δ distance +1.8 kmOpen
Live tracking — ETA vs actual, delay flags, per-stop timeline
Step 6 · End of day · your part

Close the day with numbers, not opinions

This is the step that matters to whoever runs the business. Three headline measures on screen, and one spreadsheet when somebody needs the detail behind them.

Weight utilization
Delivered weight ÷ capacity
Time utilization
Planned ÷ actual duration
Delivery utilization
Actual stops ÷ your target
Order fill rate
Stops closed ÷ stops planned
Delivery latency
Share closed same-day / D+1

Read weight and time together: a day at 40% weight but 95% time means the routes are geographically inefficient, not under-loaded. That distinction is the whole point of measuring both.

routesync.app/wd/reports
Reports · last 30 days Download .xlsx
Delivery latency
74.7%
closed on D+1
Order fill rate
92.4%
stops closed / total
Exception rate
13.8%
undelivered / total
The three utilizations
Weight utilization72%
Time utilization88%
Delivery utilization57%
Workbook · 6 sheets
Reports · daily rollup Summary · per trip Details · per hop Invoice level · per order Delivery aging Vehicle raw
Reports — three utilizations, and a six-sheet export
And above all of it

One view across every distributor

The brand-side portal shows every distributor on the network measured the same way, in the same shape, so an outlier is obvious at a glance. Onboarding a new distributor is four steps: create it, assign the operator, add the vehicles, add the drivers.

Strict data isolationEvery record is scoped to its distributor. A super-admin can look across, but always with an explicit “acting as” banner and a full audit trail.
One shared product cataloguePack sizes and per-case weights live centrally, so every distributor’s numbers mean the same thing.
Same codebase from 3 to 50Adding distributors is an onboarding wave, not a new version. Nobody gets left on old software.
routesync.app/admin
All distributors · last 30 days Today 30 days
Total orders
14,208
Pending
312
Active
186
Delivered
13,402
Issues
308
Per distributor
WD-447 · Hyderabad96% fulfilled
WD-512 · Secunderabad91% fulfilled
WD-388 · Warangal78% fulfilled
The brand-side portal — every distributor, same shape

See this running on your data

30 minutes, screen-shared on the live system. Bring one day’s order file and your vehicle list — we’ll plan it in front of you.

Quick support