quote → cash
EN/FR Contact

Architecture

Product and catalog architecture

Why the catalog has two axes — what a product is, and where a seller finds it — and why confusing them is expensive.

Salesforce docs documented by SalesforceField experience observed on a real orgRecommended pattern what we recommendTo verify unverified
Product and catalog architecture two axes, one product
CATALOG DEFINITION SELLING browse shape required ProductCatalog the container ProductCategory the shelf Classification what it is AttributeDefinition what it carries Product2 the product SellingModel how it is sold RelatedComponent the bundle PricebookEntry the list price

Scroll the diagram sideways

Attributes hang off the classification, not off the product. The category is only what the seller browses. Modelling them as one thing works until the first product needs to appear on two shelves, or two products of the same type need different attributes.

The objects involved

Select one to open its detail.

Salesforce resources