StoreConnect and Salesforce objects and fields

StoreConnect enhances Salesforce functionality by adding custom fields to several standard objects and also introduces numerous custom objects and fields to support a wide range of features, from order management and product categorization to tax calculation, content management and a whole bunch more.

Understanding Salesforce objects

In Salesforce, an object is a database table that stores a specific type of information. Each object contains fields (the columns in that table) and records (the individual rows of data). Objects can be related to one another through lookup and master-detail relationships, which allow records across different objects to be linked together.

There are two categories of objects in Salesforce:

• Standard objects — built into the Salesforce platform (for example, Account, Contact, Order, and Product2). These exist in every Salesforce org and have well-known field sets and behaviors.
• Custom objects — created by a managed package or by your org’s own configuration. StoreConnect installs a large number of custom objects as part of its managed package to support storefront and commerce functionality that standard Salesforce does not provide out of the box.

How StoreConnect uses objects

StoreConnect works with Salesforce objects in two ways:

Extending standard objects — StoreConnect adds custom fields (prefixed s_c__) to existing standard objects. For example, the standard Order object gains checkout step tracking, cart reference data, and delivery fields. The standard Product2 object gains fields for barcodes, stock management, subscriptions, and bookings. These extensions allow StoreConnect to integrate tightly with core Salesforce features like reporting, flows, and Apex.

Creating custom objects — StoreConnect introduces its own custom objects for functionality that has no native Salesforce equivalent. These include objects for stores, themes, content blocks, pages, menus, tax configuration, promotions, stock management, point of sale, and more. All StoreConnect custom objects use the s_c__ namespace prefix (for example, s_c__Store__c, s_c__Product_Category__c).

Key object relationships

Objects in StoreConnect are connected through a network of relationships. Understanding a few core relationships helps you navigate the data model:

• Store → Products — a Store__c record controls which products are available for purchase. Products (Product2) are associated with stores via product categories and pricing configurations.
• Order → Contact and Account — when a customer places an order, the Order record links to the customer’s Contact and Account records, preserving the standard Salesforce CRM relationship.
• Order → Order Items → Products — each Order has related OrderItem records, each linked to a Product2 and PricebookEntry. StoreConnect adds further detail through related objects like s_c__Fulfillment_Item__c and s_c__Payment__c.
• Product2 → Product Categories — products are organised into hierarchical categories through s_c__Product_Category__c and the s_c__Products_Product_Categories__c junction object.
• Store → Themes and Content — a store references a s_c__Theme__c for its design, and s_c__Content_Block__c records for reusable content areas.
• Store → Tax and Shipping — tax behaviour is governed by s_c__Tax__c, s_c__Tax_Group__c, and s_c__Tax_Provider__c records. Shipping is managed through s_c__Shipping_Provider__c and s_c__Shipping_Rate__c.

Many relationships use junction objects (objects with two parent lookups) to create many-to-many relationships. For example, s_c__Products_Product_Categories__c connects products to multiple categories, and s_c__Content_Blocks_Pages__c connects content blocks to multiple pages.

Working with StoreConnect objects in Salesforce

Object Manager — you can inspect all StoreConnect objects in Salesforce Setup under Object Manager. Custom objects are listed by their label and show their API name, fields, relationships, and page layouts.

Field API names — when writing Salesforce flows, validation rules, SOQL queries, or integrating with the StoreConnect API, you use the field’s API name rather than its label. StoreConnect custom fields on standard objects use the s_c__ prefix (for example, s_c__Checkout_Step__c on Order). Fields on custom objects also use this prefix (for example, s_c__Store__c.s_c__Currency_ISO_Code__c).

Relationship queries — because StoreConnect data is stored in standard Salesforce objects and relationships, you can query it using SOQL like any other Salesforce data. Lookup fields are traversable using dot notation (for example, Order.s_c__Store__c.Name), and child relationships can be queried using nested SELECT statements.

Flows and automation — StoreConnect objects are fully compatible with Salesforce Flow, and Apex triggers. This means you can build custom automations that respond to StoreConnect events, such as sending a notification when an order reaches a specific checkout step, or updating a custom field when a subscription is activated.

:::note StoreConnect custom fields and objects are delivered through a managed package. This means field API names include the s_c__ namespace and cannot be modified or deleted by your org’s administrators. You can, however, add your own custom fields to StoreConnect’s custom objects if you need to capture additional data. :::

Limitations on custom fields for Salesforce objects

Salesforce imposes limits on the number of custom fields allowed on each object. These limits apply to the combined total of all custom fields in the org — including those added by managed packages such as StoreConnect. Depending on your edition, the general limit is between 500 and 900 custom fields per object. Review the latest Salesforce information and this topic for full details.

If your org already has custom fields on any of the standard objects StoreConnect extends, it is worth confirming that enough capacity remains before installing. The table below shows how many custom fields StoreConnect adds to each standard object:

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

:::warning PricebookEntry has a Salesforce-imposed hard limit of 50 custom fields. StoreConnect adds 35. If your org already has custom fields on PricebookEntry, ensure the combined total does not exceed 50 before installing. :::

Checking an object’s available capacity

To see how many custom fields an object can still accommodate:

1. Go to Setup.
2. In the Quick Find box, search for the object name (for example, Order).
3. Select the object from the results.
4. Click Limits.
5. Check the Custom Fields row — this shows the number in use and the maximum allowed.

Compare the number in use against the available limit, then subtract the StoreConnect field count from the table above to confirm there is enough headroom.

Object reference documentation

Full field-level reference documentation for every StoreConnect object is available in the developer documentation:

• Standard objects extended by StoreConnect — all standard Salesforce objects that StoreConnect adds custom fields to, with full field definitions.
• Custom objects created by StoreConnect — the complete list of custom objects introduced by the StoreConnect managed package, with links to each object’s field reference.

For a full index of all object reference articles, see Object References.