Risk management and analysis

There are five (5) areas we have identified as most requiring Risk Management & Analysis

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

As well as our standard terms and conditions, and acceptable use policies the following will be beneficial in understanding prior to installing the StoreConnect App:

General rules for safeguarding your data and minimising downtime

• You should perform regular backups of your Salesforce Org.

• Staging orgs should be set up to fully test (UAT) the installation or upgrade prior to pushing through to Production.

• The onus is on our users/clients to thoroughly UAT (User Acceptance Testing) the installation or upgrade prior to pushing it through to their Production Org.

• The user/client can tailor the following two checklists to their requirements to assist in identifying and managing business impact and risks:

  • Prepare to launch your store

  • Test your live store

Installing the StoreConnect app

• StoreConnect installs custom Salesforce objects and makes use of some standard objects

  • StoreConnect Object Reference

  • StoreConnect adds custom fields to the following Salesforce objects.

    • Account
    • Asset
    • CampaignMember
    • Contact
    • Lead
    • Order
    • OrderItem
    • Pricebook2
    • PricebookEntry
    • Product2
    • User
• Before/After Update Triggers
  • StoreConnect will add Triggers to the above objects and populate some of our custom fields with StoreConnect data during installation. The triggers can fire on any on any record changes in those objects.
• Page Layouts
  • StoreConnect installs extra page layouts for most of the above Standard Objects and does not overwrite any of your existing Page Layouts

Duplicate management for accounts and contacts

Orders created through StoreConnect will be linked to an Account and Contact. Where the email address used at checkout matches an existing contact in Salesforce, the order will be linked to that Contact and its Account. Other than a few custom fields added by the StoreConnect Package, existing Account and Contact data is never updated by StoreConnect. Customers can however update name and shipping details from their profile page when logged into your store.

See Lead, Contact and Account Deduplication for more details around this.

Order creation

Orders are created with the Salesforce default Order Status of Draft, which means you must have an Order Status with an API Name of Draft and a Status Category of Draft.

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 minimise downtime.
• Page layouts — new fields and objects introduced in an upgrade will not appear on existing page layouts automatically. Deprecated fields will not be 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 in the sync. Adding a StoreConnect_Sync__c field to a standard object before running StoreConnect Setup restricts the initial sync to only the records you explicitly mark for inclusion.

The recommended sequence for new installations with large data volumes:

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 sync
4. Run StoreConnect Setup

Configuring sync opt-in after Setup has already run requires care — any existing records not marked enable_sync will be removed from StoreConnect. 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.

Please contact our support team for further information.