Boundary Data Update Cycle in Territory Planning

Territory Planning doesn’t always reflect the latest boundary data for a specific country. The timing of when different regions process and validate updates or when you create alignments can affect the freshness of boundary data.

Required Editions

Available in: both Salesforce Classic (not available in all orgs) and Lightning Experience
Available for an additional cost in: Enterprise, Performance, Unlimited, and Developer Editions with Sales Planning in English only, and only if you have Web Services API enabled

Boundary data in Territory Planning, such as zips codes, are sourced from third-party vendors. These vendors work with governmental and administrative sources for each country to validate the data, so it can take several months for Territory Planning to reflect any boundary changes or additions.

For some regions of the world, such as North America and Western Europe, vendors receive monthly or quarterly boundary updates from their sources. Other regions don’t have a regular cadence and updates vary from country to country. After updated boundary data is validated, Salesforce receives the updated data, performs additional testing and validation, and finally releases the updated boundaries during the next major release.

To limit disruptions, existing alignments don’t inherit updated boundary data. For copied data alignments, use the Refresh Data Sources option on the source dataset. For live data alignments, remove the boundary dataset in an alignment and then re-add it. For information about when to expect updated boundary data, check out the Salesforce Release Notes.