# Zones

<p class="doc-lead">Zones group districts for sales territory planning and reporting. The list is hierarchical: create zones and attach districts from your location master.</p>

<div class="doc-toc">
<p class="doc-toc-title">On this page</p>
<div class="doc-toc-section">
<div class="doc-toc-links">
<a href="#/settings/zones?id=overview">Overview &amp; List View</a>
<a href="#/settings/zones?id=quick-start">Quick Start</a>
<a href="#/settings/zones?id=fields">Fields</a>
<a href="#/settings/zones?id=actions">Actions</a>
<a href="#/settings/zones?id=related">Related</a>
</div>
</div>
</div>

<hr class="doc-section-divider">

<h2 id="overview">Overview &amp; List View</h2>

Go to <b>Settings → Others → Zones</b>.

Tree-style list with scroll pagination (similar to Locations).

<!-- screenshot pending -->

<b>List columns</b>

| **Column** | **Description** |
|------------|-----------------|
| Name | Zone name. |
| Districts | Districts assigned to this zone. |

<b>List actions</b>: New, View, Edit, Delete (multi), contextual New for child nodes.

<hr class="doc-section-divider">

<h2 id="quick-start">Quick Start</h2>

<h3>1. Set up districts</h3>
Ensure districts exist under <a href="#/settings/locations">Locations</a>.

<h3>2. Create zones</h3>
Click <b>New</b>, name the zone, and select districts.

<h3>3. Use on customers and routes</h3>
Assign zones on customers or route planning for field sales reports.

<hr class="doc-section-divider">

<h2 id="fields">Fields</h2>

| **Field** | **Description** |
|-----------|-----------------|
| Name * | Zone label. |
| Districts | One or more districts included in the territory. |

<hr class="doc-section-divider">

<h2 id="actions">Actions</h2>

New, View, Edit, Delete — hierarchical New at each level.

<hr class="doc-section-divider">

<h2 id="faq">FAQ</h2>

<p><b>Must districts exist before creating zones?</b></p>
<p>Yes. Create districts under <a href="#/settings/locations">Locations</a>, then assign them to zones on the zone form.</p>

<p><b>Can a district belong to multiple zones?</b></p>
<p>Typically one district maps to one zone — duplicate assignment depends on your data entry; avoid overlap for clean territory reports.</p>

<p><b>How do zones affect Field Sale App?</b></p>
<p>Customer and route filters on user settings may use zone data — pair with <a href="#/settings/routes">Routes</a> for beat planning.</p>

<p><b>Zones vs Locations hierarchy?</b></p>
<p>Locations structure addresses. Zones group districts for sales territory — complementary masters.</p>

<p><b>Can I delete a zone with customers?</b></p>
<p>Reassign customer zone fields first — deletion may be blocked when references exist.</p>

<p><b>Is the zone list hierarchical?</b></p>
<p>Tree-style list supports parent-child zone nodes for regional rollups — use contextual New for child zones.</p>

<hr class="doc-section-divider">

<h2 id="related">Related Topics</h2>

<ul>
<li><a href="#/settings/locations">Locations</a></li>
<li><a href="#/settings/routes">Routes</a></li>
<li><a href="#/sales/customers">Customers</a></li>
</ul>