Skip to main content

What is a product family?

A product family is a named group of products that should be treated as variations of the same item for merchandising purposes. The most common use case is grouping color variants, material variants, or regional variations of the same style so that a collection page shows a broader assortment instead of six near-duplicate rows of the same style in a row. Product families are a building block for other features:
  • Diversity expressions cap how many products from the same family appear in the top of a collection.
  • Future family-aware merchandising features reuse the same groupings.
A product can belong to at most one family of each family type. The only family type today is canonical, which represents “this is the same underlying product.”

How families are created

Layers supports two sources for a family:
SourceWho manages itWhen to use
ManualA merchandiser, in the Product Families dashboardWhen your grouping logic doesn’t map to a single attribute (for example, you want to hand-curate a capsule collection as one “family”)
AutomaticLayers, from a product attribute you selectWhen a reliable attribute (a metafield, vendor, or calculated attribute) already identifies the group
Manual families always win. If a product is assigned to a manual family and its automatic attribute value later changes, the manual assignment is preserved.

Automatic families from an attribute

You configure which attributes drive automatic families in Settings → Product Families. Each entry points at a single attribute whose value will be used as the family key. Layers supports three kinds of attributes as family sources:
  • Direct product fields and nested keys — for example, vendor, custom.style_code, or named_tags.color.
  • Calculated attributes — any attribute with a code that starts with calculated., such as calculated.style_group. The calculated attribute is evaluated per product and its string result becomes the family key.
  • Metafields — Shopify metafields synced into your catalog.
Array-valued attributes (like tags) and metric attributes are not supported as family sources, because a single product cannot cleanly belong to multiple families through one attribute.

How automatic assignment works

  1. Layers reads the configured attribute for each product during catalog sync.
  2. If the value is non-empty, the product is assigned to a family named Auto: <attribute>:<value>. Products sharing the same value land in the same family.
  3. If the value is empty or missing, the product is removed from any automatically assigned family for that attribute.
  4. Families that become empty are cleaned up automatically.
Automatic families are read-only in the Product Families dashboard — edit the underlying attribute value to change membership.

Prerequisites

Before you can configure automatic family sources, the attribute you want to use must already exist and be synced into your catalog. See Attributes and Metafields to add one.

Manual families

Manual families are fully editable in the dashboard. A manual family has:
  • A name you choose (for example, Heritage Tee — All Colors).
  • A list of member products. A family should contain at least two products to be useful.
When you add a product to a manual family that was previously in an automatic family for the same family type, the product is moved. Manual CRUD wins.

Creating a manual family

See the step-by-step guide at Create a product family.

Editing and deleting

  • Manual families can be renamed, have members added or removed, and can be deleted individually or in bulk from the Product Families list.
  • Automatic families cannot be edited or deleted from the dashboard. To change their membership, update the attribute values on your products. Automatic families disappear on their own when they have no remaining members.

Bulk actions

From the Product Families list you can select multiple manual families and delete them in a single action. Automatic families in the selection are skipped — they remain under sync control.

Cross-references

Inside a collection’s sort order, a Diversity expression pairs with product families to cap how many near-duplicates appear in the top window. See: