Initial sync when setting up the sync user

When you configure a StoreConnect sync user for the first time, StoreConnect’s sync infrastructure performs an initial bulk pull of all records from every Salesforce object it monitors. This is expected behavior — it is how StoreConnect builds its local working copy of your Salesforce data.

What gets pulled in the initial sync

The initial bulk pull includes all records from every object in StoreConnect’s sync schema, including:

• All StoreConnect custom objects (Products, Stores, Outlets, Price Books, and so on) — these sync immediately and become available to your website.
• Standard Salesforce objects that StoreConnect monitors: Account, Contact, Order, Order Item, Campaign Member, Asset, and Lead.

The row counts you see in Sync Summaries after the initial sync reflect this full pull.

Why the record count is large

If your Salesforce org has a large volume of existing Accounts, Contacts, or other standard objects, the SF Row Count shown in Sync Summaries will include all of them — not just records that were created through StoreConnect. This is normal.

The large count does not mean those records are active on your website.

Pre-existing records are not website-active without a StoreConnect ID

Standard objects like Account and Contact only become active on the website once they have a StoreConnect ID (SCID) — a unique identifier stored in the s_c__SC_Id__c field on the record.

Records created through StoreConnect (via checkout, registration, or invitation) are assigned an SCID automatically. Pre-existing Salesforce records that were created before StoreConnect was installed do not have an SCID and will not:

• Appear as matching customers during guest checkout
• Be available for customer login
• Have any website data created against them

The sync infrastructure holds these records in its local database, but the StoreConnect application does not surface them until an SCID is present.

Adding SCIDs to pre-existing records

If you want pre-existing Accounts or Contacts to participate in StoreConnect — for example, so that customers with existing Salesforce records can log in or be matched at checkout — you need to add SCIDs to those records.

See Syncing records with StoreConnect IDs for the available methods, including inviting contacts, triggering password resets, using the Sync to SC quick action, or bulk importing via Dataloader.

For organizations with very large volumes where only a subset of records should participate in StoreConnect, per-record sync opt-in lets you control which individual records are included.

Summary