For delivery drivers
Plan a full delivery list in one route
Typical route setup
- Route size
- From a short gig batch to a manifest of up to 100 stops
- What drives the order
- Raw drive time and how tightly the drops cluster. Appointment windows are rare; volume is the problem.
- Where the list comes from
- A platform app, a manifest, a spreadsheet from dispatch, or scanned labels typed in by hand.
Why the stop limit matters
Free limits differ substantially. Google Maps supports ten locations total without automatic ordering, Geo2 allows fifteen stops, RouteXL and Spoke allow twenty per route, and MapQuest allows twenty-six locations. Shipday and SortMyStops.com each publish a 100-stop free browser tool.
Splitting the day into three routes of twenty means each group is optimized separately. You still decide which stops belong together before the planner sees them, so the full route may continue to cross the same area more than once.
Optimizing the whole block at once is the difference. That is why the free limit here is 100.
Import the manifest
If your stops arrive as a list
Copy the column and paste it. A single column of complete addresses is the most common format and needs no cleanup. Separate street / city / state / ZIP columns work too, and the importer recognizes the usual header names without configuration.
If you are reading them off labels
If the addresses exist in an email, a selectable PDF or a platform screen you can copy, paste that text instead of retyping it. The parser accepts several layouts and flags anything it cannot place confidently.
Review flagged addresses
One address placed at a city center becomes a real destination to the optimizer, which can distort the entire order. Review flagged matches before departure and place a pin when the address data is incomplete.
What it will not do for you
It does not collect photos, signatures or delivery statuses. It does not organize packages by load order or connect to a gig platform. Optimization also excludes live traffic, so treat the drive-time estimates as planning numbers and let your navigation app handle current conditions.
If you need proof of delivery, use a driver app built for that job. This planner handles the earlier step: turning an address list into an order you can review and drive.
Frequently asked questions
Does this work with Amazon Flex, DoorDash, Uber Eats or Instacart?
For the planning half, yes. Copy the addresses from your block or batch into the planner, optimize, then drive. There is no integration with those platforms, so you move the addresses across yourself and keep using their app for scans, photos and support.
Is it worth it if the platform already gives me a route?
Sometimes. Compare the platform order with the planner rather than assuming either is better. The clearest use case is a batch of stops handed to you as a plain list with no order at all.
How long does 60 stops take to optimize?
Processing time varies with route size, the selected routing provider and network conditions. Keep the page open until the result appears; if a provider is unavailable, the planner may use a configured fallback.
Can I put the route on my phone?
Yes. Scan the QR code at the depot while you still have signal, or open mobile route mode and work through the stops one at a time, opening each in your navigation app as you reach it.
What if an apartment number is missing?
The pin will usually land on the building, but the unit number is still needed at the door. Put it in the notes column when you import so it appears in the printout and on your phone.
Does it handle pickups and returns?
Yes. A pickup is just a stop. Add a note so you know which is which, and set your end point to wherever the returns have to go back to.
Try it on tomorrow's list
Paste the addresses you already have and compare the order against the one you would have driven.
Open the planner