Risk management and analysis

Use this topic to assess the business risk of installing or upgrading StoreConnect before you make either change in a production Salesforce org. It covers the five areas that most often need attention:

1. Installing the StoreConnect app
2. Duplicate management for accounts and contacts
3. Order creation
4. Upgrading the StoreConnect app
5. Large data and sync opt-in

Read this alongside our terms and conditions and acceptable use policy.

General rules for safeguarding your data and minimizing downtime

• Perform regular backups of your Salesforce org.
• Set up a staging org and fully test (UAT) the installation or upgrade there before pushing to production. The responsibility for user acceptance testing sits with you, not StoreConnect.
• Tailor these two checklists to your requirements to help identify and manage business impact and risk:
  • Prepare to launch your store
  • Test your live store

Installing the StoreConnect app

StoreConnect installs custom Salesforce objects and adds custom fields to these standard objects:

• Account
• Asset
• CampaignMember
• Contact
• Lead
• Order
• OrderItem
• Pricebook2
• PricebookEntry
• Product2
• User

For the full field list, see StoreConnect and Salesforce objects and fields.

Two further changes happen at install time:

• Triggers — StoreConnect adds before-update and after-update triggers to the objects above and populates some of its own custom fields during installation. These triggers can fire on any record change in those objects.
• Page layouts — StoreConnect installs extra page layouts for most of the standard objects above. It does not overwrite any of your existing page layouts.

Duplicate management for accounts and contacts

Orders created through StoreConnect are linked to an Account and a Contact. Where the email address used at checkout matches an existing Contact in Salesforce, the Order is linked to that Contact and its Account.

Other than the custom fields the StoreConnect package adds, StoreConnect never updates existing Account and Contact data. Customers can still update their own name and shipping details from their profile page when logged in to your store.

See automated lead conversion to avoid duplication for more detail.

Order creation

Orders are created with the Salesforce default Order Status of Draft. Your org must therefore have an Order Status with an API name of Draft and a status category of Draft, or order creation fails.

Upgrading the StoreConnect app

An upgrade is a two-step process: the Salesforce package is upgraded first, then the web application. These steps happen independently and there is a window between them where your configuration must be ready. See Managing StoreConnect upgrades for the full upgrade procedure, including sandbox testing, theme preparation, and post-upgrade tasks.

Key risks to be aware of:

• Theme — your theme may require changes after an upgrade. Prepare updates in a cloned theme before the upgrade window to minimize downtime.
• Page layouts — new fields and objects introduced in an upgrade do not appear on existing page layouts automatically. Deprecated fields are not removed and require manual cleanup.
• Picklist values — new picklist values are not added on upgrade. Use the Manage picklist values tool in the StoreConnect Console after upgrading.
• Payment gateways — payment gateways may become unstable and should be tested after every upgrade.

Large data and sync opt-in

By default, all records on standard Salesforce objects (such as Contact, Account, and Product2) are synced to StoreConnect. For orgs with large data volumes (hundreds of thousands or millions of records), this can result in significantly longer initial setup times and degraded performance while the sync completes.

StoreConnect provides a per-record sync opt-in to control which records are included. Adding a StoreConnect_Sync__c field to a standard object before you run StoreConnect Setup restricts the initial sync to only the records you explicitly mark for inclusion.

:::warning Configure sync opt-in before you run StoreConnect Setup. If you configure it afterward, any existing records not marked enable_sync are removed from StoreConnect. :::

Use this sequence for a new installation with large data volumes. The order matters, because step 4 is what triggers the initial sync:

1. Install the StoreConnect package.
2. Configure sync opt-in on any standard objects with large record volumes. See manage standard object sync.
3. Mark the records you want included in the sync.
4. Run StoreConnect Setup.
5. Confirm the result: check that the record counts in StoreConnect match the records you marked, and that unmarked records were not pulled in.

See manage standard object sync for full configuration instructions, including how to handle Person Accounts and how to auto-enable sync for new records created by StoreConnect.

If you are unsure how any of this applies to your org, contact StoreConnect support.