StoreConnect and Salesforce org compatibility guide

Use these checks to confirm your existing Salesforce org can run StoreConnect, before you commit to an implementation. Work through them with your Salesforce administrator to identify any gaps and what it takes to resolve them.

Before you begin

• You need a Salesforce administrator, or access to one, since most checks are made in Setup.
• Record your findings as you go. The compatibility summary at the end lists every check in one table, along with who can resolve each type of gap.

Two of the checks are hard blockers that stop the installation itself: Salesforce edition and Lightning Web Security. Confirm those first.

Check 1: Salesforce edition

StoreConnect supports multiple Salesforce editions, each with different levels of capability and conditions.

Edition	Compatibility
Enterprise Edition and above	Fully supported. Native API access and the full platform capabilities required by StoreConnect are included with no special configuration needed.
Professional Edition (or Pro Suite)	Conditionally compatible. StoreConnect can operate using its managed integration architecture, including Heroku Connect, which enables API-based functionality without requiring general API access to be enabled across the org. Compatibility should be confirmed during evaluation.
Essentials Edition	Not compatible.
Group Edition	Not compatible.

How to find your edition: Go to Setup > Company Information. Your edition is shown in the Organization Edition field.

:::note The StoreConnect AppExchange listing also lists compatible Salesforce editions and products. :::

API access

In Enterprise Edition and above, API capability is included in the platform. The sync user must have the API Enabled permission.

In Professional Edition, API access is not generally enabled across the org. StoreConnect’s managed integration still requires the sync user to have appropriate permissions, including API access where applicable.

Check 2: Lightning Web Security

StoreConnect uses dynamic imports in its Lightning Web Components. Salesforce only permits dynamic imports when Lightning Web Security (LWS) is enabled in the org. This is a hard install blocker: if LWS is not enabled, the StoreConnect package installation fails with the error LWC1503: Dynamic imports are not allowed.

:::warning You must enable Lightning Web Security before attempting to install StoreConnect from AppExchange. :::

How to verify: Go to Setup > Session Settings and confirm Use Lightning Web Security for Lightning web components and Aura components is selected.

LWS is an org-wide setting that Salesforce recommends for all orgs. Enabling it should not affect your existing components or apps, but it can. If it does, switch LWS off, resolve the issue in your other apps, then switch it on again before retrying the installation.

How to fix: See enable Lightning Web Security for step-by-step instructions.

Check 3: Standard objects

StoreConnect extends 11 standard Salesforce objects. You need to confirm that each object is accessible in your org.

Core objects (required)

These 8 objects are required for a basic install. They power the e-commerce path, pricing, and integration:

• Account
• Contact
• Order
• OrderItem
• Pricebook2
• PricebookEntry
• Product2
• User

Feature-specific objects (optional)

These 3 objects are only required if you use specific features:

• Asset — voucher fulfillment and inventory tracking
• Lead — lead-to-contact conversion
• CampaignMember — external ID assignment

:::note All three are standard Salesforce objects present in every org. “Optional” refers to the features that use them, not to the objects themselves. If the StoreConnect features that rely on these objects are included in your package installation, the installing user must have read access to them or the install fails. Check object access in Setup > Object Manager before installing. :::

Additional objects

StoreConnect also requires access to Campaign (the parent object of CampaignMember). PushTopic is granted read-only permission in the Sync permission set.

Orders

:::warning Orders are not enabled by default in Salesforce. This is the most common compatibility gap. If Orders are not enabled in your org, enable them before installing StoreConnect: go to Setup > Order Settings and select Enable Orders. :::

Person Accounts

If your org uses Person Accounts, StoreConnect supports them through runtime detection. Person Accounts are an org feature, not a separate object. See using Person Accounts with StoreConnect for the setup this requires.

What StoreConnect adds to these objects

StoreConnect adds custom fields to each of the 11 standard objects. It does not add custom record types. The table below shows the number of fields added to each object, which you can use to assess whether any object in your org is approaching its custom field limit before installing.

Object	Custom fields added
Account	28
Asset	6
CampaignMember	1
Contact	20
Lead	3
Order	42
OrderItem	29
Pricebook2	11
PricebookEntry	35
Product2	76
User	4

For more detail on which fields StoreConnect adds, including field-level definitions, see StoreConnect and Salesforce objects and fields.

Custom field limits

Salesforce limits the number of custom fields on each object, and the StoreConnect fields count toward that limit. Check the objects above for remaining capacity before you install.

The limit that most often causes a problem is the hard limit of 50 custom fields on PricebookEntry. For most other objects the limit is generally between 500 and 900 depending on your edition. See the Salesforce custom field allocation documentation and this related article for current figures.

To check an object’s custom field usage:

1. Go to Setup > Object Manager.
2. Select the object you want to check.
3. Select Limits.
4. Compare the value on the Custom Fields row against the limit, and confirm there is room for the number of StoreConnect fields listed in the table above.

:::note If you plan to use per-record sync opt-in to control which records sync, allow for one more custom field on each object you enable it on. Opt-in works by you adding a StoreConnect_Sync__c field to the object, and that field counts toward the limits above. See manage standard object sync. :::

Security

Access to StoreConnect objects and fields is controlled by five permission sets:

Permission set	Role
StoreConnect Administrator	Full admin access
StoreConnect Sync	Sync user access
StoreConnect Order Manager	Order management
StoreConnect Content Manager	Content management
StoreConnect Theme Manager	Theme management

The Administrator, Sync, and Order Manager permission sets are each paired with a corresponding standard permission set that configures field-level security on standard object fields.

POS users are managed separately from these permission sets. Access at the point of sale is controlled through Outlet User records and Outlet User Types in Salesforce. Each Outlet User Type defines the permissions available to that class of employee, including the maximum discount percentage they can apply. For instructions on setting up POS users and user types, see Add a POS user.

How to verify object access: Go to Setup > Object Manager and confirm that each required object is visible and accessible under your current license and edition.

Check 4: Streaming API

StoreConnect uses the Streaming API to receive real-time updates from Salesforce, through PushTopic records.

Streaming API is a soft requirement. StoreConnect will install and function without it, but sync behavior changes:

• With Streaming API: Changes are processed immediately as they occur in Salesforce.
• Without Streaming API: StoreConnect falls back to polling-based sync, typically checking for changes every 2–10 minutes.

Streaming API is generally available in Enterprise Edition and above. It may be limited or unavailable in Professional Edition.

How to verify: Confirm with your Salesforce administrator whether Streaming API is enabled in your org.

Check 5: Sync user

StoreConnect requires a dedicated sync user to connect your Salesforce org to your storefront. This check covers the org-level requirements that could block that user from working, not the full setup steps. For the setup procedure, see set up a StoreConnect sync user.

Login and authentication requirements

The sync user must be able to authenticate via Heroku Connect. The following org-level configurations can block this:

Requirement	Detail
Standard Salesforce domain login	The sync user must be able to log in via the standard Salesforce domain.
My Domain login access	My Domain must allow login access for the sync user.
Lightning Login	Not supported for the sync user.
Salesforce Authenticator	Not supported for the sync user.
IP restrictions	Must allow outbound access from Heroku. Heroku publishes its current outbound IP addresses in its developer documentation — add these to your org’s Network Access settings in Setup. If your org uses IP allowlisting, confirm that the Heroku IPs are included before configuring the sync user.
SSO-only login policies	Must allow direct or API login — SSO-only orgs block Heroku Connect authentication.
Login hours	The sync user’s profile must not restrict login access during the hours your storefront is expected to operate. Because sync can be triggered at any time by customer activity, the safest configuration is unrestricted login hours (24/7). If your security policy requires login hour restrictions, ensure the permitted window covers your full trading hours.

User license

The sync user must have a license that supports API access and the required object access.

License	Compatibility
Salesforce (standard full license)	Supported
Salesforce Integration User	Recommended. Included in Enterprise, Unlimited, Performance, and Developer editions. Not included by default in Professional Edition.
Salesforce Platform	Conditionally supported — only if all required objects are available under that license.

:::note If using the Salesforce Integration User license, the Salesforce API Integration Permission Set License is required to grant object and API permissions. :::

Permission sets and profile

• The sync user must be assigned the StoreConnect Administrator and StoreConnect Sync permission sets.
• When using a standard Salesforce license, the System Administrator profile (or equivalent permissions) is recommended.

How to verify: Confirm that your org can support the creation of a user meeting the above requirements, and that your authentication and IP policies allow external API access from Heroku.

---

Compatibility summary

Use this table to record your findings for each check.

Check	Where to verify in Setup	Type	Admin can fix?
Salesforce edition is Enterprise or above (or Professional confirmed compatible)	Setup > Company Information	Hard blocker (install)	No — requires edition upgrade or evaluation
Lightning Web Security is activated	Setup > Lightning Web Security	Hard blocker (install)	Yes
Orders are enabled	Setup > Order Settings	Hard blocker (sync)	Yes
All 8 core standard objects are accessible	Setup > Object Manager	Hard blocker (sync)	Depends on license
Sync user can be created with API-enabled license	Setup > Users	Hard blocker (sync)	May require license change
Sync user can authenticate via Heroku Connect (no SSO-only, no MFA-only, no blocking login policy)	Setup > Session Settings, Login Policies	Hard blocker (sync)	Sometimes — depends on org policy
StoreConnect permission sets can be assigned to sync user	Setup > Permission Sets	Hard blocker (sync)	Yes
IP restrictions allow Heroku access	Setup > Network Access	Hard blocker (sync)	Sometimes — depends on security policy
Streaming API is available	Setup > Remote Site Settings / Salesforce edition	Soft — polling fallback	Depends on edition
All required fields are accessible to sync user	Setup > Object Manager > Fields	Soft — data gaps possible	Yes
Sync user has View All / Modify All where needed	Setup > Profiles / Permission Sets	Soft — records may be missed	Yes
Login hours do not restrict sync user access	Setup > Profiles > Login Hours	Soft — intermittent failures	Yes

Issues that require a license, edition, or contract change

The following gaps cannot be resolved by a Salesforce administrator and require engagement with your Salesforce account team or partner:

• No available license that supports API access for the sync user
• Missing Salesforce Integration User license (where required)
• Required objects not included in your available licenses
• Unsupported Salesforce edition

Borderline situations to watch for

Even if your org passes all the checks above, the following configurations may lead to performance or reliability issues:

• Platform license with limited object access — some required objects may be unavailable, causing partial sync
• No View All / Modify All — sync may miss records due to sharing restrictions
• Restricted field-level access — required fields may not sync, causing data gaps or errors
• Fragile login or IP restrictions — sync may intermittently fail if access conditions change
• High data volume — sync performance may degrade or lag; this should be validated during implementation
• OEM Embedded License — if your org was provisioned through an OEM partner (for example, an org purchased directly from an ISV such as AccountingSeed), the standard Salesforce objects available to you may be defined or restricted by the OEM contract. In this case, the objects required by StoreConnect — including the combined set needed for all installed solutions — must be explicitly included in the OEM agreement. Confirm with your OEM vendor that the required objects are accessible before attempting to install StoreConnect.

---

Next steps

If all checks pass, you are ready to install StoreConnect. See explore StoreConnect in a Salesforce trial org to evaluate it first, or the quick start to install into your own org.

If you identified gaps, use the guidance below to determine who can help resolve them.

Contact your Salesforce administrator (internal): - Permission, profile, or configuration gaps that can be adjusted in Setup - Login, IP, or MFA settings that can be changed within your existing security policies

Contact StoreConnect support: - Questions about StoreConnect requirements or expected behavior - Uncertainty about which objects, permissions, or settings are needed - Sync issues after installation

Contact a Salesforce Partner: - SSO, MFA, or IP restrictions that cannot be adjusted to allow integration access - Security models that prevent granting the required permissions (for example, strict session security levels or least-privilege governance constraints) - Data model conflicts with StoreConnect requirements (for example, customizations affecting standard objects) - Multi-org or complex implementations

Contact Salesforce (your Account Executive or Support): - License or edition limitations that need to be resolved - Enabling API access or obtaining the required licenses for the sync user