Catalog Management16% of the exam
Product types, bundle structure and cardinality
Pick the right product type, build static and configurable bundles with groups, and control what reps can change through local cardinality, quantity scaling, group cardinality, exclusions, component attribute overrides and quote visibility.
Given a scenario, implement a solution using the appropriate out-of-the-box Catalog Management functionality.
~8 min read · 18 practice questions ·
What the exam expects
- Set Product Type and Configure During Sale to produce a static simple, configurable simple, static bundle or configurable bundle product.
- Apply static-bundle and configurable-bundle structure rules, including product groups and where classifications may sit.
- Configure local cardinality (required, included by default, quantity changes, min/max, Price Includes Component) and the Quantity Scaling Method, including amendment behaviour.
- Use group cardinality, nested groups, exclusions and cardinality overrides to control selection at run time.
- Convert simple products to bundles and static bundles to configurable bundles, override component attributes, validate the definition and set Quote Visibility.
Key terms: root product (the first product in a bundle hierarchy); product group (a container for components inside a bundle); local cardinality (rules on one component); group cardinality (min/max distinct components chosen from a group); Quantity Scaling Method (how a child quantity follows the parent quantity).
Key facts
Static bundle children
- Detail
- Static simple or static bundle only
Configurable bundle groups
- Detail
- Mandatory; two levels; classification once per group
Simple to bundle
- Detail
- Can't be undone; affects related quotes, orders and assets
Required component
- Detail
- Must also be included by default
Min/Max Quantity
- Detail
- Only with Allow quantity changes selected
Price Includes Component
- Detail
- Quantity can't change; deselect Allow quantity changes
Constant scaling
- Detail
- Child quantity fixed at design time; deselect Allow Quantity Changes
Proportional in amendments
- Detail
- Child quantity read-only; change the parent
Nested groups
- Detail
- Only lowest-level group cardinality is enforced
Exclusion scope
- Detail
- Root bundle only; second level and beyond
Attribute override
- Detail
- Applies to every instance of the product in the bundle
Sources for this section (7)
- Products and Bundleshelp.salesforce.com (opens in a new tab)
- Convert to Bundlehelp.salesforce.com (opens in a new tab)
- Local Cardinalityhelp.salesforce.com (opens in a new tab)
- Product Relationshipshelp.salesforce.com (opens in a new tab)
- Group Cardinalityhelp.salesforce.com (opens in a new tab)
- Exclude Componentshelp.salesforce.com (opens in a new tab)
- Override Component Attributeshelp.salesforce.com (opens in a new tab)
- Why must a required component also be included by default?
- When can you edit the cardinality of an excluded component?
- Why can't a first-level component of a bundle be excluded?
- What does a blank Quote Visibility value do for a child product?
The questions are free to read. Answers with their sources and self-grading are included with the pack.
Keep reading with the Revenue Management Consultant pack
- Core concepts
- Exam traps
- Worked scenario
The pack includes:
- All 25 lessons of the Revenue Management Consultant guide, with reading progress
- Interactive decision walks and step-by-step sequence steppers
- Practice exams purchase adds inline bank questions and topic practice (18 questions for this lesson)
- An official source cited for every claim
- An AI tutor that answers from the guide
- Choose guide-only, practice-only, or save $4 with both