One solve.
The whole day’s
round.

Most planners stop optimising past 25 stops and chop the rest into chunks. RouteMate runs a real vehicle-routing solver: the full stop list is sequenced together over road distance, with time windows, vehicle capacity and driver shifts inside the calculation, not written beside it.

Free tier, no card · Web, iOS, Android · REST API

Fig. 01 — Single-pass sequence
142 stops
6 vans
DEPOT
Schematic — not measured dataSolving
RouteMate — operating envelope
Rev 2026.07
Sheet 01
Operating limits and capabilities, with a remark on each.
No.PropertyValueRemark
01Stops per solve500Sequenced as one list. No chunking, no seams to join.
02Constraints in the model4Time window, service time, vehicle capacity, shift length.
03Label to routed stop~2 sPhotograph a label; the address lands in the sequence.
04Intake methods5Scan, CSV, paste, manual entry, REST API.
05Dispatch to proof of delivery1One chain of custody. Photo and timestamp against the stop.

Figures are plan limits and typical measured behaviour, not guarantees. A day that cannot be met inside its constraints is reported as such.

02 · The 25-stop ceiling

Chunking is not routing

A planner built on a mapping API can re-order about 25 stops in one request. Past that it cuts the day into blocks and optimises each block alone. Every block is tidy. The joins between them are not, and nothing in the calculation is looking at them.

Blocks
3
Seam crossings
2
Sequenced against
Each block in isolation — joins left to the driver
Fig. 02 — Chunked at 25 stops
16 stops
SEAMSEAM
Schematic — not measured data
03 · Scan → dispatch → proof

One chain of custody, end to end

Every stop keeps the same identity from the moment it enters the system to the moment it is signed for. Nothing is retyped between steps, which is where records usually go missing.

Step 01

Intake

Photograph a label, paste a spreadsheet, or push from your own system over the API. The address is geocoded and enters the day as a stop.

Step 02

Dispatch

The day is solved and split across the drivers on shift, by hours and starting depot rather than by suburb. Each run lands on a phone.

Step 03

Proof

Photo, note and timestamp attach to the stop they belong to, so the record assembles itself rather than being reconstructed from a chat log.

04 · Label intake

A photograph is a data entry method

Point a phone at a consignment label. The address is read, validated against the road network and inserted into the day at the position the solver puts it, not appended to the end of the list.

Capture
AUSPOST eParcel
LODGEMENT 4821-11
SENDER: NORTHSIDE SUPPLY CO

K. AHMADI
3/216 BRUNSWICK ST
FITZROY VIC 3065
ExtractedIdle

Awaiting capture.