B2B and D2C Commerce Data Model
The Commerce store template is built on a pre-configured data model. The data model supports standard and customizable business objects for a multitude of business relationships and interoperability with B2B and B2C stores, Salesforce Order Management, and Service Cloud.
| Required Editions |
|---|
| Available in: Enterprise, Unlimited, and Developer Editions |
| Available in: B2B Commerce and D2C Commerce |
The Commerce data model connects the store objects. Default object relationships support a full-featured B2B or B2C store experience.
Among the object relationships in the Commerce app data model are those that you use to quickly:
- Add product catalogs to provision your stores.
- Configure product variants (product size, shape, color, and so on), categories, bundles, and more.
- Select customer search capabilities and how your store displays results.
- Differentiate buyer groups and associate them with specific products and volume-discounted prices.
- Configure tax, shipping, and payment for cart checkout.
- Create promotional campaigns for targeted products.
Here’s a list of some of the default data model objects.
| Data Model Object | Description | API Name |
|---|---|---|
| Store | A website where buyers and shoppers complete wholesale and retail transactions. Includes the fields and properties that define your store. For example, supported currencies, languages, and price books. Many fields are customizable. | WebStore |
| Cart | Represents an online shopping cart in a store built with B2B or D2C Commerce on Lightning, with total amounts for products, shipping and handling, and taxes. | WebCart |
| Catalog | A catalog is a collection of the products that you sell, organized into different categories. The Commerce Admin or Merchandiser uses data import to set up the catalog. | ProductCatalog |
| Category | Categories and subcategories organize and group products in your catalog and on your storefront. The Commerce Admin or Merchandiser uses B2C data import to fill in a default compact layout, which includes name, catalog, category, search order, and so on. Layout is customizable. | ProductCategory |
| Entitlement Policy | Entitlement policies are simple entities that bring together buyer groups and products. Filtered by BuyerGroup membership. Includes CanViewPrice and CanViewProduct fields, which are customizable. | CommerceEntitlementPolicy |
| Product | The items and services you sell. The Commerce Admin or Merchandiser uses data import to fill in a default compact layout, which includes a variety of customizable fields (name, family, and so on). | Product2 |
| Buyer Account | The buyer’s or shopper’s financial information, including credit and order limits, some of which pertain only to B2B. A B2C BuyerAccount is established when a shopper self-registers. | BuyerAccount |
| Buyer Group | A group of buyers with the same assigned entitlement policies, price books, and products. Buyer Group name and description are customizable. For D2C stores, one buyer group per store is created by default during D2C data import. | BuyerGroup |
| Buyer Group Member | An individual buyer associated with a buyer group. | BuyerGroupMember |
| Price Book | A price book contains price definitions for a group of products. Typically added during setup with your store’s data import, but you can add custom fields. | PriceBook2 |
| Price Book Entry | A product entry (an association between a Pricebook2 and Product2) in a price book. | PricebookEntry |