{"title":"Manage POS data sync","slug":"manage-pos-data-sync","url":"https://support.storeconnect.com/articles/manage-pos-data-sync","url_markdown":"https://support.storeconnect.com/articles/manage-pos-data-sync.md","subtitle":null,"summary":"Monitor and update the data sync for your POS. Monitor local sync status, view server and local record counts, pause and resume syncing per object, and clear or resync records to resolve data drift or incomplete syncs.","type":"Help_Documentation","video_url":"","keywords":"pos manage data, pos sync, pos data management, resync pos, clear pos data, local record count, server record count, unsaved records, pause sync, resume sync, data drift, pos settings, pos troubleshooting","last_modified":"2026-07-30T00:28:16+0000","body_markdown":"You can view the sync status of every data object on your device for POS, in the POS terminal. Identify incomplete syncs, view local and server record counts, pause or resume syncing for specific objects, and clear and re-download data when records drift out of alignment.\n\nFor businesses with exceptionally large data sets that take time to sync, you may need to pause and resume syncs in order to free up a device for use.\n\n## Open data management screen\n\nFrom within the POS:\n\n1. Go to **Settings**.\n2. Select **Manage data**.\n\nThe screen lists all sync objects available on your device.\n\n## The data list\n\nEach row represents one sync object (for example, `contact`, `s_c__product__c`, `s_c__order__c`). The row shows:\n\n- **Object name** — the internal object identifier\n- **Record count** — the number of records synced locally, shown alongside the server count. For example: `Synced 1,234 of 2,000`\n- **Status icon** — a visual indicator of the current sync state\n\nTap any row to open the object detail page for that object.\n\n### Row status indicators\n\n| Status | Description |\n|--------|-------------|\n| Syncing | The object is actively downloading records |\n| Paused | Syncing has been paused for this object |\n| Fully synced | Local count matches the server count |\n| Subset synced | The object is scoped to a subset of server records (this is expected for outlet-scoped objects) |\n| Incomplete | Local count is lower than the expected server count and syncing is not in progress |\n\n## Object detail page\n\nTapping a row opens the detail page for that object. This page shows:\n\n| Field | Description |\n|-------|-------------|\n| Object | The object's internal API name |\n| Status | Current sync state: Syncing, Paused, Subset synced, Fully synced, or Incomplete |\n| Local records | Number of records currently stored on this device |\n| Server records | The server-side record count in scope for this device. For scoped objects (such as outlet-specific data), this shows the in-scope subset |\n| Server records (all) | For scoped objects only — the total server-side count regardless of scope. Helps identify whether a mismatch is due to scoping or a genuine sync gap |\n| Unsaved records | Records created or modified on this device that have not yet uploaded to Salesforce |\n\n:::note\nUnsaved records are preserved during any clear or resync operation. They are not deleted.\n:::\n\n## POS data sync actions\n\n### Pause and resume syncing\n\nThe primary action on both the main list and each object detail page lets you pause or resume syncing:\n\n- **Pause all syncing** — stops the sync engine from downloading new changes across all objects. Only available while a sync is in progress.\n- **Resume all syncing** — restarts syncing for all objects where it was paused.\n- **Pause syncing** (per object) — pauses syncing for a single object.\n- **Resume syncing** (per object) — resumes syncing for a single object.\n\nUse pause when you need to prevent sync activity during a bulk data operation or while investigating an issue.\n\n### Resync existing records\n\nAvailable from the **More actions** menu on both the main list and the object detail page:\n\n- **Resync all existing records** — triggers a fresh download of all records across every object without removing any local data first. Use this when records may be stale or out of date.\n- **Resync existing records** (per object) — re-downloads all records for a single object without deleting them first.\n\n### Clear and resync records\n\nAlso available from the **More actions** menu:\n\n- **Clear \u0026 resync all records** — deletes all locally stored records across every object, then triggers a full sync from the server. Use this when data drift has affected multiple objects and a resync alone is not sufficient.\n- **Clear \u0026 resync records** (per object) — deletes all local records for a single object, then re-downloads them.\n\n:::warning\nClear \u0026 resync removes all locally stored records for the affected object(s). Records currently in use (such as your active outlet and shift) and any unsaved records are preserved. All other local records are deleted and must re-download before they are available again.\n:::\n\n## When a data sync action is needed\n\n| Situation | Recommended action |\n|-----------|--------------------|\n| Records appear stale or out of date | Resync existing records |\n| Local count is lower than the server count and not recovering | Clear \u0026 resync records for the affected object |\n| Multiple objects are out of sync | Clear \u0026 resync all records |\n| Sync is running but you need to stop it temporarily | Pause all syncing |\n| A banner message says syncing is paused | Resume all syncing |\n| An object shows Incomplete status | Check for sync errors first, then use Clear \u0026 resync |"}