{"title":"How the StoreConnect data model fits together","slug":"data-model-overview","url":"https://support.storeconnect.com/articles/data-model-overview","url_markdown":"https://support.storeconnect.com/articles/data-model-overview.md","subtitle":null,"summary":"Orientation for the StoreConnect Salesforce schema: the naming conventions, which objects are hubs, how records connect through lookups and junctions, and how to find your way from any object to the ones related to it.","type":"Developer_Documentation","video_url":"","keywords":"data model, salesforce schema, object model, s_c namespace, sC_Id, external id, lookup convention, hubs, store, product2, relationships, referenced by, custom objects, standard objects","last_modified":"2026-08-21T07:12:35+0000","body_markdown":"StoreConnect installs around 200 Salesforce objects. Read individually they are\nhard to place, because the schema is wide rather than deep: a handful of objects\ncarry most of the relationships, and everything else hangs off them.\n\nUse this article to get oriented before you go looking for a specific object, and\nto learn the conventions that let you predict what an object looks like before\nyou open it.\n\n:::note\nIf you are new to Salesforce objects and fields, read\n[StoreConnect and Salesforce objects and fields](storeconnect-object-and-field-definitions)\nfirst. It covers what objects, fields, and relationships are, how StoreConnect\nextends the eleven standard objects it uses, and the custom field limits that\napply. This article assumes that and concentrates on navigating the reference.\n\nTo explore the same model visually, the StoreConnect Console has a built-in\n[Schema Explorer](schema-explorer): an interactive entity relationship diagram\ncovering every object and how they connect.\n:::\n\n## Reading any object's page\n\nEvery object reference article has the same four sections, and the last one is\nthe one people miss:\n\n| Section | Answers |\n|---------|---------|\n| **Overview** | What the object is, and its API name |\n| **Fields** | Every field, its type, and whether it is required |\n| **Relationships** | What this record **points at** |\n| **Referenced by** | What **points at** this record |\n\n**Relationships** and **Referenced by** are the two directions of the same\nquestion, and you usually need the second one. If you are asking \"what is related\nto this?\", read **Referenced by**. Its **Also links to** column names what a join\nrecord connects to on its far side, so you can follow a relationship through a\njunction without opening it.\n\n## Naming conventions\n\nEverything the package installs carries the `s_c__` namespace. Beyond that, three\nconventions make most of the schema predictable.\n\n- **A lookup field ends in `_Id__c`.** `s_c__Store_Id__c` points at the store,\n  `s_c__Product_Id__c` at a product. There are 180 of them. If you are looking\n  for the link between two objects, search for the target's name followed by\n  `_Id__c`.\n- **`s_c__sC_Id__c` is the sync key.** 148 objects carry it. It is a GUID\n  StoreConnect owns, used to match records between Salesforce and the storefront\n  database. Use it as the external ID when importing, and never edit it by hand.\n- **Junction objects are named after both sides.** `Product_Tag__c`,\n  `Zone_Country__c`, `Content_Blocks_Pages__c`. See\n  [junction objects](junction-objects).\n\n## The shape of the schema\n\nA few objects carry a disproportionate share of the relationships. Knowing which\nones tells you where to start reading.\n\n| Object | Records pointing at it | What it anchors |\n|--------|-----------------------:|-----------------|\n| [Store](store-object-reference) | 40 | Nearly all configuration. 39 objects carry a store lookup |\n| [Product2](product2-object-reference) | 39 | The catalog, and most commerce |\n| [Media](media-object-reference) | 26 | Every image, file, and document |\n| [Account](account-object-reference) | 22 | Customers, suppliers, and brands |\n| [Contact](contact-object-reference) | 18 | People, and storefront sign-in |\n| [Product Category](product-category-object-reference) | 15 | Catalog structure |\n| [Order](order-object-reference) | 14 | Everything after checkout |\n\n**Store is the one to understand first.** Almost anything configurable is either\non the store record or on an object that points at it, which is what makes a\nsingle Salesforce org able to run several storefronts with different catalogs,\nthemes, and payment providers.\n\n## Functional areas\n\nThe custom objects group into a few areas. This is a reading aid rather than\nanything the schema enforces:\n\n- **Catalog** — products, categories, variants, traits, media, pricing\n- **Orders and checkout** — carts, orders, payments, vouchers, promotions, discounts\n- **Store and design** — stores, themes, pages, content blocks, menus, style and script blocks\n- **Content** — articles, article categories, tags\n- **Customers and access** — accounts, contacts, memberships, credit, points, approvals\n- **Fulfillment and inventory** — shipments, stock levels and locations, transfers, zones\n- **Point of sale** — outlets, registers, shifts, POS layouts and actions, print templates\n- **Platform** — sync records, custom data mappings, error definitions, settings\n\n[Custom objects](custom-objects) lists all of them, and\n[how stores, themes, and design elements relate](how-stores-themes-and-design-relate)\nwalks through the store and design area in detail.\n\n## Finding your way\n\nWhen you need to know how two objects connect:\n\n1. Open the object reference for either one.\n2. Check **Relationships** for a direct lookup to the other.\n3. If it is not there, check **Referenced by** — the link is often on a third\n   record that points at both. The **Also links to** column names it.\n4. If the connecting record is a junction, [junction objects](junction-objects)\n   explains what that means for querying, importing, and deleting.\n\nMost \"there is no relationship between these\" conclusions turn out to be a\njunction one step away."}