Help CenterZones, hubs & SLA

Zones

Admin portalZones, hubs & SLAUpdated today

Zones are the neighbourhoods inside a city. They decide which hub handles an order and which areas you serve.

Before you start
  • Everyone with access to Areas can look at zones. Changing coverage, aliases or the Auto-detect setting needs the Edit coverage or Manage zones permission.
1

Open the Zones tab

Switch from Cities to Zones. You see every city together, or choose one.

Areas › ZonesSample screen
AreasCitiesZones1Riyadh ▾2Filters3Auto-detect zone 4Custom zone5⋯
  1. City. All cities, or one city. It is optional.
  2. Filters. Served by hub (each hub, or No hub), Type (Built-in or Custom) and Coverage (Served or Not served).
  3. Auto-detect zone. A company setting. On: each new order gets its zone automatically. Off: the zone stays empty and is picked by hand.
  4. Custom zone opens the New custom zone form.
  5. The ⋯ menu imports custom zones from a KML or GeoJSON file, and imports and exports aliases.
2

Find zones and read the table

Use the quick filters and the table to see where every zone stands.

Areas › ZonesSample screen
1
All192Built-in190Custom2Not served / no hub41
2 Zone3 Type4 Served by hub5 Coverage
Business districtOverrides Al Olaya, Al SulimaniyahCustomGroupedRiyadh North HubServed
Al OlayaCovered by Business districtBuilt-inRiyadh North HubServed
Al SahafaAlso: الصحافةBuilt-inNo hubServed
Al RawdahBuilt-inRiyadh East HubNot served
  1. Quick filters. All, Built-in, Custom, and Not served / no hub. The last one shows zones that are not served, whose city is not served, or that no hub serves.
  2. Zone. The name and its other names. A custom zone shows “Overrides” and the neighbourhoods it covers. A built-in zone inside a custom zone shows “Covered by”.
  3. Type. Built-in zones have a lock: they come from Fleetics and cannot be edited. Custom zones are your own, and show Grouped or Drawn.
  4. Served by hub. The hub that serves the zone, or “No hub” in amber. A custom zone’s hub applies to every neighbourhood it covers.
  5. Coverage. Served, Not served, or City not served.
3

Read the map

The map beside the table shows the zones of the city.

Areas › ZonesSample screen
15234
  1. Built-in zones are drawn with a light fill.
  2. Custom zones are drawn dashed.
  3. The selected zone is highlighted. Click a row in the table and its zone lights up. Click a zone on the map and its row is selected.
  4. Hubs are dots on the map.
  5. Zones that are not served are greyed out.
4

Know built-in and custom zones

Every city comes with its neighbourhoods as built-in zones. You can add your own custom zones on top.

Built-in zonesCustom zones
Who makes themFleeticsYou
Can you edit or delete them?No. You can mark them Served or Not served and edit their aliases.Yes
On the mapLight fillDashed outline
When both cover an area—The custom zone wins over the built-in zones it covers
5

Mark a zone served or not served

Open a zone’s menu. A zone that is not served shows Out of coverage on new orders.

Areas › ZonesSample screen
On a built-in zone
1 Show on map
2 Edit aliases
3 Mark as not served
On a custom zone
1 Show on map
2 Edit aliases
3 Mark as not served
4 Edit custom zone
5 Delete custom zone
  1. Show on map highlights the zone on the map.
  2. Edit aliases opens the zone’s other names.
  3. Mark as served or not served. Not served: new orders in the zone show Out of coverage.
  4. Edit custom zone. Custom zones only.
  5. Delete custom zone. Custom zones only. The built-in neighbourhoods it covered apply again. Orders already created keep their zone.
6

Let Fleetics find the zone for each order

The Auto-detect zone setting decides whether orders get their zone by themselves.

Areas › ZonesSample screen
Auto-detect zoneA company setting1
Order to Riyadh · pin on the mapDistrict text: Al Malqa2Zone: Al Malqa
Order to Riyadh · no pinDistrict text: Malqa area3Bad addressZone: none
  1. On or off. With the setting on, every new order gets its zone by itself. With it off, the zone stays empty and you pick it by hand on the order.
  2. How the zone is found. From the pin on the map first. Without a pin, from the city and district text, using zone names and aliases.
  3. No match. A domestic order in a served city whose pin and district match no zone is still accepted, but flagged Bad address, with no zone and no hub, so someone can fix it.
TipAn order keeps the zone and hub it got when it was created. Changing a zone only affects new orders.

Screens are simplified drawings with sample data. Your portal may look a little different, but the names and steps are the same.

Common questions

A neighbourhood is missing. What now?

Some cities may not have all their neighbourhoods yet. Create a custom zone for the area, or contact Fleetics.

Why does an order show Bad address?

Auto-detect zone is on, the order is in a served city, and neither its pin nor its district matched a zone. Fix the address, or add the district as an alias.

Does one zone belong to more than one hub?

No. Each zone is served by at most one hub.

What does “Overrides” mean?

A custom zone covers that neighbourhood, so the custom zone applies to it.

Related guides

Create a custom zoneAliasesHubs
Was this helpful?
On this pageOpen the Zones tabFind zones and read the tableRead the mapKnow built-in and custom zonesMark a zone served or not servedLet Fleetics find the zone for each orderCommon questions