User Manual
Help Center/User Manual/LastMile Zones: Delivery Zones

LastMile Zones: Delivery Zones

Last updated 2026-10-22

Draw delivery zones on the map (or import them as GeoJSON), let orders fall into their zone, then run one-click routing per zone and confirm to create the routes.

A zone is an area you draw on the map: "everything inside this outline is one delivery area." Once zones exist, orders belong to the zone their address falls in, and routing can be planned zone by zone instead of for the whole city at once. The Zones page (LastMile → Zones, /lastmile/zones) is where you draw and import zones, see how many orders are still waiting to fall into a zone, and run one-click routing for one zone at a time.

Step 1: Draw a zone on the map#

  1. Open LastMile → Zones and click "Draw zone".
  2. Type the zone name first and pick a color — the page asks for the name before it saves anything, and the color is how you tell zones apart on the map.
  3. Click on the map to drop one corner point after another; double-click to close the shape. The zone is saved as soon as the shape closes.
  4. The new zone appears in the list on the left with its color chip and how many drivers are linked to it. Click a zone in the list (or on the map) to select it.

Drawing zones on the Zones page (LastMile → Zones) is the one place where delivery areas are defined. Give each zone a name the drivers recognize — a neighborhood or a landmark works better than a code — because the same name follows the zone into routing and the route list.

Or import zones from a GeoJSON file#

  1. Click "Import GeoJSON" on the Zones page.
  2. Paste the GeoJSON text — a FeatureCollection whose features are the zone shapes — into the box.
  3. Import. The page reports how many zones were created, and they appear in the same zone list as hand-drawn ones.

Check the unassigned pool#

Under the zone list, the "Unassigned pool" counter shows how many orders are not inside any zone yet. Those orders cannot be routed by zone until they belong to one: drag them onto a zone on the dispatch map, or assign them to a zone in a batch. A growing unassigned count usually means a new neighborhood started ordering and no zone covers it yet — draw the missing zone first, then route.

Step 2: Run one-click routing for a zone#

  1. Select the zone in the list — routing always runs for the selected zone.
  2. Set the route date (today by default) under the zone list.
  3. Click "Optimize route" and wait — the button shows progress in percent while the job runs.
  4. When it finishes, the map shows the preview: one colored line per route and the stops numbered in visit order. The message above the map tells you how many routes came out and how many stops stayed unassigned.
The preview is not saved yet. Look at it first: routes that cross the whole map or stops left unassigned are cheaper to fix now — adjust the zone or the date and run it again — than after drivers have started.

Step 3: Confirm and assign#

  1. If the preview looks right, click "Confirm & assign".
  2. The planned routes are created for the route date and the drivers can take them. The page reports how many routes were created, clears the preview, and refreshes the unassigned pool.
Zones first, routing second: an order can only be routed by zone once its address falls inside one.

Docklify features used in this article#

  • LastMile → Zones (/lastmile/zones) — draw zones on the map with a name and a color
  • Import GeoJSON (LastMile → Zones) — create several zones at once from a FeatureCollection
  • Unassigned pool (LastMile → Zones) — count of orders not yet inside any zone
  • Optimize route (LastMile → Zones) — one-click routing for the selected zone, with a map preview
  • Confirm & assign (LastMile → Zones) — turn the preview into real routes drivers can take