FieldFlow Delivery
FieldFlow

Dispatch and route planning

Plan the day's trips once, in the right order.

Dispatch builds waves and trips on one board, with suggestions. When a trip is approved, Google's Routes API reorders its drops for the road and every stop gets an ETA, and the new order is kept only when it is actually shorter.

  • Waves, trips and vehicles on one board
  • Road order for up to 25 drops
  • An ETA for every stop
Example · Trip TR-2318 · Dadar hubDispatch order
  1. 1Om Sai StoresETA 9:47
  2. 2Gupta KiranaETA 10:31
  3. 3Sion Super MartETA 10:55
  4. 4Balaji StoresETA 11:33
  5. 5Laxmi TradersETA 12:05
  6. 6Matunga DairyETA 12:35
Planned distance
31.2 km

On approval Google’s Routes API reorders up to 25 drops for the road. The new order is kept only when it is shorter.

What it does

Dispatch and route planning, in six parts.

Hubs, zones and pincodes
Each hub serves zones made of pincodes, and orders without a zone wait in a queue with the nearest zone suggested.
Waves
Plan the day in waves, morning and afternoon, and move each wave from plan to approval to loading to the road.
A dispatch board
Drag orders onto trips and trips onto vehicles, with suggestions to start from.
Road order, kept only when shorter
On approval, Google's Routes API reorders up to 25 drops. Dispatch's own order stays when it is already as short.
ETAs and trip cost
Every stop gets a planned arrival, and each trip a cost from the vehicle's fixed rate plus its per-km rate.
Dispatch stays in charge
Reassign, re-sequence or complete a trip from the dashboard; the driver follows the order dispatch sets.

See it on your own trips.

A 30-minute demo, then a pilot from one hub with a few vehicles, so you judge FieldFlow Delivery on your own drops.

Offline-first
Every drop saved on the phone first
Proof and cash
On every stop, reconciled every evening
One or many
Your own fleet, or several distributors