Skip to content
Magento Glossary · Product Types

What is a Magento configurable product?

A Magento configurable product presents a family of simple-product variations on one page. Each valid combination, such as size and color, identifies a child SKU with its own inventory. The parent organizes the choice; pricing and availability must be evaluated for the selected variation and sales context.

Understand the parent/child relationship before choosing attributes, pricing scope or inventory integrations. The examples below distinguish a variation from a component bundle or personalization field.

Type: DefinedTerm Guide: variants and stock Product-model guide Product catalogue guide
What is a Magento configurable product?
TL;DR Definition

Configurable product = parent + child simples linked by attribute combinations

The parent provides the shared product-family presentation. Each variation identifies a child simple product. Standard cart and order handling retain the configurable relationship, so integrations must understand both the configured purchase and its selected child rather than assume only one record exists.

  • Magento product types: simple · configurable · bundle · grouped · virtual · downloadable (6 native types)
  • DB tables involved: catalog_product_super_link · catalog_product_super_attribute · catalog_product_relation
  • Scale review: Test the actual variant family and storefront workload
  • Best for: apparel, electronics, furniture: anywhere customers pick a pre-built variant
How it works

From a product family to a selected variation

Follow the relationship from variation attributes to the selected child, its availability and the resulting order data.

  1. 1

    The parent presents one product family

    A configurable product presents choices such as size and color on one product page. Each valid combination identifies a separate simple product with its own SKU. The parent groups those variants for discovery; it does not turn all combinations into one shared inventory item.

  2. 2

    Variation attributes describe meaningful choices

    Variation attributes must meet the supported input, required-value and global-scope settings. Include them in the attribute set and give each child a unique combination. A free-text engraving instruction usually belongs in a custom option rather than generating a new stock-tracked variant for every message.

  3. 3

    Child products supply the purchasable variation

    The selected child supplies the variation data used for price and inventory. Configurable cart and order handling retain parent/child relationships, so an integration must understand that structure rather than assume the parent disappears and only a child record remains.

  4. 4

    Availability depends on the relevant child and sales context

    Check the child SKU, website assignment and inventory stock when a choice cannot be purchased. A parent being enabled does not prove every variant is salable. Search indexes, prices and cached storefront data have their own update paths.

  5. 5

    The selector and downstream workflow need testing

    Test valid and unavailable combinations, price changes, images, cart editing and order exports. A swatch rendering correctly is only one part of acceptance. Extensions, pricing rules and the chosen storefront can change how the complete interaction behaves.

When to use it

Where separate variant SKUs fit

These examples show when separate variant SKUs fit and when a different product model may be clearer.

  • Clothing

    Size and color

    Use separate variants when stock and replenishment are tracked for each size/color combination. Do not create combinations the business does not actually sell.

  • Electronics

    Capacity and finish

    A device family can share a product page while each capacity or finish has its own SKU. Warranty instructions or service add-ons may require a different model.

  • Standardized variants

    One selected variation

    A configurable product fits a purchase that resolves to one variant. If customers assemble several independently selected components, examine the bundle model instead.

  • Personalization

    Shared SKU with an instruction

    A message, date or engraving field can be a custom option when it does not identify separate inventory. Decide from fulfillment and SKU requirements rather than the visual appearance of a dropdown.

Common mistakes

Four variant-model assumptions to check

Check the actual child records, pricing scope and storefront behavior before treating a catalog symptom as a parent-product setting.

  • Generating every possible attribute combination

    More attributes can multiply the number of child records and choices. Model only saleable combinations and test representative catalog and storefront workloads. There is no universal safe variant count that applies to every store.

  • Treating store views as independent product-price scopes

    Standard catalog price scope is global or website, not an arbitrary price for each store view. Coordinate child prices, website assignments and any shared-catalog or custom pricing layer.

  • Changing parent stock to repair a missing variant

    Inspect the chosen child SKU and its actual inventory context first. Parent availability is derived from associated products and relevant rules. Do not treat the parent as an independent warehouse quantity.

  • Assuming theme support proves extension compatibility

    A standard product type and a custom selector, price rule or inventory integration are separate things. Test the installed theme and extension combination through cart and order handling rather than promising universal compatibility.

FAQ

Six questions stores ask before committing to configurable

  • Configurable vs simple: when do I pick which?
    Use a simple product for one independently stocked SKU. Use a configurable parent when a shopper chooses one of several separately stocked simple variations on a shared page. Custom options are useful for choices that do not need independent SKU inventory. The fulfillment model should decide the structure.
  • Configurable vs Bundle: what’s the actual difference?
    A configurable purchase resolves a variation such as a shirt size and color. A bundle lets the shopper choose component items, such as the parts of a kit. Their selection, pricing and order-item relationships differ. See the bundle definition before using variants to simulate a component builder.
  • How many variants is too many?
    There is no dependable universal ceiling. Attribute combinations, child count, indexing, price rules, extensions and the selector implementation affect the workload. Avoid generating unavailable combinations, and test the largest realistic family with representative requests and order flows.
  • Can I override a variant’s price per region or store?
    Standard catalog pricing can be global or website-scoped. A store view is not an independent base-price scope. Set the supported website-level context where needed and verify each child price and assignment. Customer-group, shared-catalog and custom pricing introduce additional rules that need their own tests.
  • How does inventory work, at parent or child level?
    Inventory is managed for the associated child SKUs, while parent salability reflects the usable choices. With Inventory Management, evaluate the child against the website stock, source quantities, reservations and configuration. The inventory glossary explains those separate responsibilities.
  • Are configurable products fully Hyvä compatible?
    Compatibility must be checked for the installed theme version and integrations. A standard configurable selector, a third-party swatch extension and a custom pricing module are not the same implementation. Test choices, unavailable variants, price updates and cart/order behavior on the actual storefront.

Building a fashion or apparel catalog?

Describe the real variation structure, inventory ownership and storefront requirements when planning the catalog. Those details establish the implementation scope without a universal variant ceiling.

See Magento for fashion
Kishan Savaliya Online 10 AM to 7 PM IST Chat on WhatsApp