> ## Documentation Index > Fetch the complete documentation index at: https://docs.vortexiq.ai/llms.txt > Use this file to discover all available pages before exploring further. # Master vs Variant Product Count, Salesforce Commerce Cloud > Master vs Variant Product Count, the ratio of base/master products to variants across your SFCC catalog. How to read it, why it matters, and how to act on it. **Card class:** [Non-Hero](/nerve-centre/overview#card-classes-explained) • **Category:** [Ecommerce Platform](/nerve-centre/connectors#connectors-by-type) > The Salesforce Commerce Cloud product model has master and variant relationships. This donut surfaces the ratio so you can see catalog complexity at a glance. ## At a glance > A donut showing how your Salesforce Commerce Cloud (SFCC, formerly Demandware) catalog splits between master (base) products and their variants. SFCC uses a structured product model: a master product is the conceptual item (a shirt), variation groups slice it (by colour), and variants are the individually-buyable, sellable SKUs (a specific colour and size). This card makes the master-to-variant ratio visible, which is a direct read on catalog complexity, merchandising effort, and how dense your variation matrix is. | | | | ------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **What it counts** | Two slices: the count of master / base products, and the count of variant products. Variation groups sit conceptually between the two and are not the buyable unit; the buyable, inventoried SKU is the variant. | | **Why it matters** | The ratio is a fingerprint of your catalog. A high variant-to-master ratio means deep variation matrices (lots of sizes and colours per style), which drives merchandising workload, inventory complexity, and storefront filtering needs. A near-1:1 ratio means a flat catalog of simple products. | | **Reading the value** | Read the donut as catalog shape, not catalog size. A fashion realm naturally skews heavily toward variants; a homewares or digital-goods realm skews flatter. Sudden shifts in the ratio usually mean a catalog import added or removed a whole product family. | | **SFCC product model** | Master / base product, variation groups, variants. Only variants carry their own inventory record and are individually purchasable. The master is a merchandising and grouping construct. | | **What it is not** | Not a stock or availability metric. A variant can exist and be online but be out of stock, this card counts catalog structure, not inventory. Pair with the stock cards for availability. | | **Online flag interplay** | Both masters and variants carry an online flag. A master can be offline while variants exist, or vice versa. This card counts catalog records regardless of online state unless filtered. | | **Unit** | number (count per slice) | | **Time window** | Real-time (`RT`), the current catalog state | | **Alert trigger** | none configured | | **Sentiment key** | `scc_master_vs_variant_count` | | **Roles** | owner, operations | ## Calculation Calculated automatically from your Salesforce Commerce Cloud data. See the At a glance summary above for what the metric tracks and the worked example below for a typical reading. ## Worked example A fashion retailer on a single SFCC B2C realm. Their catalog is built around styles, each available in several colours and a size run. Snapshot taken 12 Mar 26. | Product type | Count | Notes | | ------------------------------------------ | ------------------ | ------------------------------------------------- | | Master / base products (styles) | 4,200 | One per design, e.g. "Classic Oxford Shirt" | | Variation groups (e.g. by colour) | 11,800 | Grouping construct, not separately buyable | | Variants (buyable SKUs) | 58,400 | Colour x size, each with its own inventory record | | **Master vs Variant Product Count (card)** | **4,200 / 58,400** | Roughly 1 master to 14 variants | Three things to notice: 1. **The 1:14 master-to-variant ratio is a classic apparel fingerprint.** Each style spawns roughly fourteen buyable SKUs once you multiply colours by sizes. That is healthy and expected for fashion. The same ratio on a homewares realm would be surprising and worth questioning, it would suggest variation depth the category does not usually need. 2. **Variation groups (11,800) are intentionally not a slice on the donut.** They are a merchandising and navigation construct, not a buyable, inventoried unit. The card deliberately compares masters to the variants that actually carry stock and revenue, so the ratio reflects real catalog and inventory complexity rather than grouping overhead. 3. **The 58,400 variants are the inventory and merchandising workload.** Every one is a SKU that needs an inventory record, pricing, and potentially imagery. This number is the better predictor of operational effort than the master count. Pair it with [Total Products](/nerve-centre/kpi-cards/salesforce-commerce-cloud/total-products) and [Out-of-Stock Products](/nerve-centre/kpi-cards/salesforce-commerce-cloud/out-of-stock-products) to see how much of that depth is actually sellable today. 4. **A ratio that jumps overnight points to a catalog import event.** If masters stay flat but variants spike, a new size run or colourway was bulk-loaded. If both jump, a whole new category landed. The ratio is a quick sanity check after any large PIM or catalog feed run. ## Sibling cards merchants should reference together | Card | Why pair it with Master vs Variant Product Count | | ----------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------- | | [Total Products](/nerve-centre/kpi-cards/salesforce-commerce-cloud/total-products) | The total catalog size. This card explains the shape of that total, masters plus variants. | | [Offline Products (online=false)](/nerve-centre/kpi-cards/salesforce-commerce-cloud/offline-products-onlinefalse) | A high variant count with many offline means a lot of structural SKUs are not actually shoppable. | | [Out-of-Stock Products](/nerve-centre/kpi-cards/salesforce-commerce-cloud/out-of-stock-products) | Deep variation matrices are exactly where out-of-stocks hide, e.g. only one size of a colourway is gone. | | [Low-Stock Products](/nerve-centre/kpi-cards/salesforce-commerce-cloud/low-stock-products) | The early-warning version of the above, deep variant catalogs surface low-stock long-tail SKUs constantly. | | [Top Products by Revenue](/nerve-centre/kpi-cards/salesforce-commerce-cloud/top-products-by-revenue) | Tells you whether the variation depth is earning its keep, or whether a few variants carry the style. | ## Reconciling against Salesforce Commerce Cloud **Where to look in Business Manager:** SFCC's admin tool is **Business Manager**, at a per-realm URL like `https://.business.demandware.net`. To inspect the master/variant structure: * **Merchant Tools, Products and Catalogs, Products**: the product list. Use the **Product Type** filter to separate Master, Variation Group, and Variant (and Standard / Bundle / Set). Filtering to Master gives you the master count; filtering to Variant gives the variant count, the two slices of this card. * **Open a master product** to see its Variations tab, which lays out the variation attributes (colour, size) and the resulting variants. This is the structural view behind the ratio. * **Merchant Tools, Products and Catalogs, Catalogs**: catalog assignment matters, a product can exist in the master catalog but not be assigned to a storefront catalog. This card counts catalog records; assignment and online state are separate dimensions. Set the Product Type filter and read the result counts in the list header to reconcile against the donut. **Why our number may legitimately differ from Business Manager:** | Reason | Direction of divergence | | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------------ | | **Variation groups**. Business Manager's product list includes Variation Group as its own type; this card folds the comparison down to masters vs buyable variants and does not slice variation groups separately. | Card has two slices where BM list has more types | | **Catalog scope**. A product can sit in the master catalog but not a storefront catalog. The card's scope may differ from a single-catalog BM filter. | Either, depends on catalog filter | | **Online filter**. Business Manager lets you filter by online state; this card counts catalog structure regardless of online unless you apply a filter. | Card higher if BM filtered to online-only | | **Standard / bundle / set products**. Products that are not part of a master/variant relationship still exist; how they are bucketed can shift the comparison. | Minor | ## Known limitations / merchant FAQs **What is the difference between a master, a variation group, and a variant?** A master (or base) product is the conceptual item, "Classic Oxford Shirt". A variation group is an optional grouping slice, for example all the blue variants. A variant is the individually buyable, inventoried SKU, "Classic Oxford Shirt, blue, medium". Only variants carry their own stock and are purchasable. This card compares masters to variants because those are the structurally meaningful endpoints. **Why are variation groups not shown as a slice?** Because they are not a buyable unit, they are a navigation and merchandising construct. Including them would muddy the ratio that actually matters for complexity and inventory: how many real SKUs hang off each master. The donut stays a clean two-slice comparison for that reason. **Is a high variant-to-master ratio bad?** No, it is just a fingerprint of your category. Fashion realms naturally run very high (many sizes and colours per style); homewares or digital goods run flat. "Bad" only enters the picture if the depth is not earning revenue or if most of those variants are offline or out of stock, which is why this card is best read alongside the stock and revenue cards. **Does this card count stock?** No. It counts catalog structure, not inventory. A variant can be counted here while being completely out of stock. For availability use [Out-of-Stock Products](/nerve-centre/kpi-cards/salesforce-commerce-cloud/out-of-stock-products) and [Low-Stock Products](/nerve-centre/kpi-cards/salesforce-commerce-cloud/low-stock-products). **Why did my ratio change after a catalog import?** Catalog imports add or remove product records in bulk. A new size run on existing styles spikes the variant slice while masters stay flat; a new product family raises both. Checking this ratio after every large PIM or feed run is a quick way to confirm the import did what you expected. **Is this realm-wide or per-site?** SFCC catalogs are assigned to sites, so scope depends on how your realm structures catalogs. The card counts catalog product records; if multiple sites share a master catalog, the structure is shared. Use the Business Manager catalog filter to reconcile a specific site's assigned products. **Is this real-time?** Yes. It reflects the current catalog state, recomputed as products are added, removed, or restructured. There is no period selector, the time window is `RT`. *** ### Tracked live in Vortex IQ Nerve Centre *Master vs Variant Product Count* is one of hundreds of KPI pulses Vortex IQ tracks across Salesforce Commerce Cloud and 70+ other ecommerce connectors. Nerve Centre runs the detection layer; Vortex Mind investigates the cause when something moves; Ask Viq lets you interrogate any number in plain English. [Start for free](https://app.vortexiq.ai/login) or [book a demo](https://www.vortexiq.ai/contact-us) to see this metric running on your own data.