The resolver
Whenever a new customer or a new site is created, PortaPro asks
"which territory does this address belong to?" The resolver runs against
every active, non-deleted territory in your org and checks:
list?
the territory's polygon boundary?
Territories are returned in this order: ZIP matches first, then
polygon matches, then alphabetical by territory name. The first candidate
becomes the tagged territory.
What triggers a resolve
Inactive territories are skipped
Territories with Active turned off are excluded from the resolver.
This is the clean way to temporarily remove a route from rotation
without losing its ZIPs, polygon, driver assignments, or schedule.
Deleted territories are skipped
Soft-deleted territories are also excluded. Their historical tags on
existing jobs are kept for reporting, but they never match new addresses.
Manual override always wins
If you set a specific territory on a site by hand, the resolver leaves
that alone. Auto-assignment only writes into an empty territory slot.