Skip to main content

Routes built in the driver app

Coming

This flow is in review and not yet in the released driver app. This page describes how it will work so you can plan for it. Nothing in your integration needs to change for it.

Some shops do not plan routes in advance. The driver collects what is ready, and the route is whatever is in the van. The driver app will support that directly:

  1. At the shop, the driver opens Create route and scans the label on each order that is ready. A scan matches the consignment barcode or tracking number, or your own order number (reference_id), so labels printed by your system work as they are.
  2. The driver reviews the list, picks a vehicle and optimises. Zoopit puts the stops in the best order for the time windows.
  3. The driver saves. The route is assigned to the driver and opens, ready to drive.

Orders that are already on a route, delivered or canceled are refused at the scan, with a message to the driver.

What your system sees​

The same as for any other route: the orders become ROUTED, then ONGOING and COMPLETED or FAILED as the driver works through them. Poll or use webhooks as described in Status updates.

A text to each recipient when the route is created is live (orders.routed) — see Recipient SMS.

What to prepare​

  • Print your order number, or a barcode of it, on the label.
  • The drivers who will build routes need permission to create routes; we set that up with you.