Skip to content

Analyze retail territories and store coverage

Use TerritoryKit for retail territory analysis when you need to map stores, branches, outlets, partners, or candidate locations against custom zones.

Who this is for

This workflow is for retail operators, franchise teams, store-network analysts, and real-estate teams comparing coverage areas or market zones.

TerritoryKit map builder showing store locations, retail territory zones, analysis counts, and export controls.
Retail teams can compare store coverage zones and export the analysis from the browser.

Step-by-step workflow

  1. Import store or branch locations

    Upload a CSV or Excel file with one row per store, outlet, partner, branch, or candidate location.

  2. Draw or import retail territories

    Draw polygon or circle zones, or import existing market boundaries from KML or KMZ files.

  3. Count records by zone

    Use analytics to see how many locations fall inside each zone and which locations are not assigned.

  4. Review overlaps or gaps

    Look for locations covered by more than one territory and locations outside all selected territories.

  5. Export the analysis

    Export metrics, point membership, territory geometry, or a project backup from the browser.

Supported inputs

  • CSV, XLSX, or XLS files with store, branch, outlet, or candidate location coordinates.
  • KML or KMZ files for existing retail or franchise territory boundaries.
  • Optional fields such as format, status, market, category, partner type, or opening stage.
  • Try the synthetic retail sample CSV.

Tips and common mistakes

  • Confirm every spreadsheet point has valid latitude and longitude values.
  • Remove empty rows before importing CSV or Excel files.
  • Use readable headers so layer styling and group-by options are easier to understand.
  • Check for points outside every zone before exporting results.
  • If imported KML/KMZ boundaries do not appear, confirm the file contains supported geometry.

Export and results

Export metrics as CSV or Excel, point membership as CSV or Excel, zone geometry as GeoJSON or KML, and a portable project backup for later editing.

Current limitations

TerritoryKit does not include demographic modeling, drive-time trade areas, revenue forecasting, catchment modeling, or automated site selection.

FAQ

Can I map store locations from a spreadsheet?

Yes, if the spreadsheet includes latitude and longitude columns.

Can I compare store coverage zones?

Yes. Draw or import zones and compare them with your store point layer.

Can I find stores outside a territory?

Yes. Analytics reports unassigned records.

Can I export retail territory analysis?

Yes. Export metrics and point membership as CSV or Excel, plus geometry as KML or GeoJSON.

Does TerritoryKit forecast store revenue?

No. It helps map and analyze territory coverage; it does not forecast revenue.

Related guides

Build your first territory map

Bring your coordinates, draw the zones you need, and see the results as the map changes.

Open Map Builder
No account required