Sync selectivity
This content is for Spring ’26. Switch to the latest version for up-to-date documentation.
The sync engine uses context-aware selectivity so each device receives the data it is likely to need for the coming days, rather than downloading the entire org.
Default strategy (summary)
Section titled “Default strategy (summary)”- User details for the signed-in user.
- Visits and tasks for the user within a configurable window (for example up to two weeks ahead, subject to limits such as 1000 records).
- Accounts linked to those visits and accounts owned by the user.
- Historical account data (orders, invoices, attributes, etc.) within the configured scope.
- Active products, price books, commercial policies, assortments, promotions, and related records.
Exact windows and filters are defined in mobile configuration. Deeper tuning (for example user-scoped product filters) is described in Mobile configuration and Additional configuration values.
Location sync strategy
Section titled “Location sync strategy”After the default scope is applied, the engine can use visit geography from config: it derives a bounding region around planned visits and pulls accounts in that area so unplanned drop-ins remain usable offline.