Product Variants
Manage parent and variant products with generated combinations, inherited catalog context, variant table editing, variant-specific pricing, media, and inventory, plus sibling navigation inside the product editor.
Variants: Nike Air Max 2024
| SKU | Color | Size | Price | Stock |
|---|---|---|---|---|
| AM-2024-BLK-42 | Black | 42 | $129.99 | 45 |
| AM-2024-BLK-43 | Black | 43 | $129.99 | 12 |
| AM-2024-WHT-42 | White | 42 | $129.99 | 3 |
| AM-2024-WHT-43 | White | 43 | $129.99 | 0 |
Variant handling is a first-class part of the product module. Parent products can load their existing variants, resolve a configured variant template, and expose a variant table with configurable columns, variant pricing, and inventory by location when the inventory app is installed.
New variants can be generated from property combinations. The generator creates every selected combination, links each child back to the parent, copies shared context such as brand, supplier, product group, categories, files, media, and properties, and builds a variant name and slug automatically.
When variants are edited, the controller deliberately keeps core catalog context aligned with the parent by copying parent brand, supplier, product group, categories, and app-specific categories while still allowing variant-specific data such as SKU, media, custom field values, prices, and inventory.
Variant combinations take too long to create manually
Parent products with color, size, or other option groups quickly turn into repetitive data entry.
Solution:
Generate variants from selected property combinations and let the app create child records automatically.
Parents and children drift apart operationally
Shared brand, supplier, product group, and category data often become inconsistent when variants are edited separately.
Solution:
Variant saves copy shared context from the parent so the variant catalog stays aligned.
Variant-level pricing and stock need a usable table view
Teams need to review many children at once without opening each variant in its own screen.
Solution:
The parent editor loads a configurable variant table with price columns, media, and inventory per location when available.
Navigation between sibling variants is awkward
Editing one child in isolation makes comparison and cleanup slower.
Solution:
Variant edit views load sibling variants so teams can move across the family from inside the same product context.
Need parent and variant products managed together?
Use Indexed PIM to generate combinations, inherit shared context, and edit variant pricing, media, and inventory from the product workflow you already use.