Product
What can be sold, and what shape it has
Catalog, classification, attributes, bundles, selling models
The catalog is where most Revenue Cloud implementations are won or lost, because every later stage inherits its structure. Three axes have to stay separate: what a product is (its classification, which decides the attributes it carries), where a seller finds it (its category), and what a bundle contains (its related components).
Modelling those three as one idea works until the first product has to appear on two shelves, or two products of the same type need different attributes. Unwinding it later means touching every quote line already captured.
The objects
Select any object to open its detail — purpose, the fields that matter, what it relates to, and what to watch for.
The architecture
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.
Implementation guides
Use cases
A bundle catalog that survives contact with sellers
Model bundles, options and regional variants without producing a catalog nobody can maintain.
MigrationComing from Salesforce CPQ
What transfers, what does not, and the distinction that makes most CPQ material inapplicable.