Creating Zones
Zones are the geographic building blocks of your service area. Each zone represents a distinct region where you offer services, with its own pricing, availability, and team assignments.
What Is a Zone?
A zone defines:
- Geographic boundary — The specific area covered, defined by postal codes
- Service availability — When services are available in this area
- Pricing rules — Zone-specific pricing adjustments
- Team assignments — Which crew members serve this zone
- Priority rating — How this zone ranks relative to others for scheduling
Creating a New Zone
- Navigate to Zones in the left sidebar
- Click Create Zone
- Fill in the zone details:
- Name — A descriptive name (e.g., "Eugene Metro", "Downtown Portland")
- Slug — Auto-generated from the name, used in URLs
- Color — Pick a color for map visualization
- Priority rating — P10 (highest) to P100 (lowest), in increments of 10
- Description — Optional notes about this zone
- Click Create to save the zone
After creation, you will be taken to the zone detail page where you can configure coverage, labor, pricing, and more.
Zone Detail Tabs
Each zone has several configuration tabs:
| Tab | Purpose |
|---|---|
| Overview | Zone summary, status, and basic info |
| Coverage | Map-based postal code selection and boundary drawing |
| Labor | Assign team members and set capacity |
| Schedule | Configure availability windows |
| Pricing | Zone-specific pricing rules and adjustments |
| Coupons | Zone-specific promotional offers |
| Industries | Which service industries are offered in this zone |
Coverage Configuration
The Coverage tab provides a map-based interface for defining your zone boundary:
- Postal code search — Search and add postal codes to the zone
- Boundary drawing — Draw custom boundaries on the map using the polygon tool
- Boundary import — Import pre-defined boundaries from Geoapify data
- Visual overlay — See other zones' boundaries to avoid overlap
The map shows postal code markers, zone boundaries, and other zones in dimmed colors for reference.
Best Practices
- Start broad, refine later — Create zones with generous boundaries, then tighten based on operational data
- No overlap — Postal codes should belong to one zone only. The system warns about overlap.
- Priority matters — Higher priority zones get preference when a postal code is disputed
- Color coding — Use distinct colors for adjacent zones for clear map visualization
On this page