Skip to main content
Product Groups let Everest present separate Shopify products as one connected group. Instead of relying only on native variants, the theme reads metaobject data and renders linked options that send customers to the matching product page while preserving a grouped shopping experience on cards and product pages. Product Groups overview

​
What this feature controls

  • Links separate products into one grouped selection flow
  • Displays grouped items on product cards and product pages
  • Chooses how groups appear on cards versus product pages
  • Uses text, image, swatch, or product-image style outputs
  • Supports custom labels and custom option images through metaobjects
  • Extends the Product Variant Picker block on the product page

​
Getting started

1

Prepare the Product Groups metaobject

Create a Shopify metaobject definition for grouped products. Everest expects fields such as the grouped product list, the grouping label, the display type on cards, the display type on pages, and the optional custom label toggle.
2

Prepare optional option-value data

If you want custom text or images for grouped options, create a second metaobject definition for product option value data.
3

Connect both handles in Theme settings

In Theme settings -> Products, fill in the text fields for the Product Groups metaobject handle and, if used, the Product Options Type Values metaobject handle.
4

Enable card output if needed

Turn on Show product groups on product card if grouped options should also appear on collection cards and other standard product cards.
5

Review the product template

Check the Product Variant Picker block on the product page because Everest renders Product Groups through that block before the native variant picker.
Product Groups location in Theme Customizer

​
Theme settings

Controls whether grouped product options appear on standard product cards when variant options are also enabled there.Default: Enabled
Stores the handle of the Shopify metaobject definition that Everest should read for grouped product relationships.This is a text field, so the handle needs to match the actual Shopify metaobject handle exactly.
Stores the handle of the optional metaobject definition used for custom text or image values.Everest uses this when group options should render with custom labels or custom images instead of only product titles and featured images.

​
Display behavior

On the product page, Everest renders Product Groups above the native product variant picker inside the Product Variant Picker block.The legend uses the group label and can show a custom current value when the grouped metaobject enables custom labels on page.
On product cards, Product Groups render only when card variant options are enabled and the global Product Groups card setting is turned on.Card interactions link directly to the grouped product URL instead of switching a native variant.
Everest supports different outputs depending on the metaobject value:Swatch uses Shopify color-pattern data or custom swatch imagery.
Image uses custom option images when available, otherwise the grouped product image.
Text uses a matched custom text value or the option text.
Fallback image style uses the grouped product featured image.

​
Important dependencies

The snippet reads specific metaobject fields directly. If field names or data structure do not match what Everest expects, grouped options will not render correctly.
Swatch groups rely on Shopify’s shopify--color-pattern data when the group type is set to swatch.
The Product Variant Picker block still affects the page experience through settings such as picker type, swatch shape, and spacing.

​
Best practices

  • Treat Product Groups as linked products with their own URLs, content, and pricing rather than as a replacement for simple native variants.
  • Keep group labels consistent so customers understand what attribute is being changed.
  • Use custom option values only when the product title alone is not enough for a clear selection experience.
  • Test grouped products on both cards and product pages because the interaction pattern is different in each context.