Product Navigation
Before you start learning or using Salesforce Revenue Cloud, it’s important to understand some basic building blocks of Product Catalog Management.
Catalog
- A catalog is a collection of products grouped for easier browsing.
- A product can be assigned to multiple catalogs.
- Catalogs are mainly for organizing and managing product data.
- There is no pricing or functional impact based on which catalog a product belongs to.
- In simple terms, a catalog is just a container for products.
Categories
- Categories are used to group products within a catalog.
- You can create categories and subcategories in a hierarchical structure.
- A product can belong to multiple categories.
- Categories help with easier navigation and filtering for users.
- You can define rules to show or hide categories dynamically.
- In simple terms, categories help users find products faster.
Catalogs and categories are used to organize products and support easy browsing and navigation. They do not affect pricing, configuration, or availability logic directly.
Below is a sample catalog for Atlasian Products.
Product Template
Attributes
- Attributes are the basic details that describe a product (e.g., color, size, memory).
- Also called dynamic attributes.
- You define attributes with a name, label, and data type (text, number, date, picklist, etc.).
Product Classifications
- Act as templates that hold a set of attributes.
- Used to create products that share common characteristics.
- Attributes can be added to a classification in two ways:
- Assign individual attributes.
- Assign an attribute category (all attributes in that group come along).
Attribute Categories
- Help group related attributes for easier access.
- Not required but useful, especially with many attributes.
- Example: Attributes like “8GB RAM”, “16GB RAM” can be grouped under “Memory”.
- One attribute can belong to multiple categories.
How It Works Together
- Define attributes → create details like size, memory, etc.
- Organize with categories → group similar attributes.
- Assign to classifications → build templates using individual attributes or full categories.
- Create products → products based on a classification inherit its attributes.
- Customize per product → update or override values as needed (e.g., different screen sizes for phones).
Example
- Attributes – Plan and Number of Users need to be populated for a given product.
- To group these attributes, create an Attribute Category named Licence Type.
- A Product Classification called Software has been created, which can be assigned to any set of products requiring these attributes.
- Attributes can either be directly assigned to the classification, or the Attribute Category can be assigned.
- This Product Classification (e.g., Software) can then be used for products like JIRA, where both attributes are required.
