New Collections: Variant-Based Collection Pages May Change Shopify Display Practices

Shopify’s Collections are undergoing a fundamental change.

In the 2026-07 version of the GraphQL Admin API, Shopify replaces the single ruleSet in past collections with a new sources model. More importantly, the new model allows collection sources to target either PRODUCTS or VARIANTS. The official enumeration CollectionSourceTargetType states it clearly: when the target type is PRODUCTS, any variant that meets the criteria will include the entire product in the collection; when the target type is VARIANTS, only the individual variants that meet the criteria will be included.

This means that Shopify’s collection logic is beginning to shift from a product level to a variant level. For merchants dealing in apparel, footwear, home goods, 3C accessories, food combinations, B2B catalogs, and multi-market pricing, this is no small change.

Past Collection Pages Often Required Workarounds

In Shopify, Collections have long been understood as product collections. Merchants can create automated collections using rules based on tags, product types, prices, suppliers, etc., or manually select products.

The problem is that many real display needs do not occur at the product level but at the variant level.

• A T-shirt comes in 12 colors, but the brand only wants to include black and white in the summer basics collection;

• A shoe model has multiple sizes, and the collection page only wants to display available sizes;

• An eBook, paperback, and audiobook are all under the same product, but different promotional pages only sell one format;

• B2B merchants want different customer groups to see different packaging specifications under the same product;

• Multi-market stores want to display only sellable variants in certain regions.

In the past, these needs often had to be solved through workarounds: splitting into multiple products, writing theme logic, relying on third-party apps, or looping through product variants in the collection page and manually filtering. While this approach works, it introduces complexity in SEO, inventory, data maintenance, PDP experience, and analytical metrics.

The significance of the new Collections lies in Shopify starting to incorporate this type of variant-level display into the collection model itself.

Core of the New Feature: Collection Sources

Shopify’s official changelog refers to this change as the New Collection model and APIs.

In the old model, a collection was primarily described by a single ruleSet. In the new model, a collection can have one or more CollectionSources. These sources can include typed inclusion conditions, exclusion conditions, manual selections, sub-collections, and shareable app collection sources created by apps.

The most noteworthy aspect is CollectionConditionsSource.targetType. It can be set to PRODUCTS or VARIANTS: PRODUCTS means that if any variant meets the criteria, the entire product enters the collection; VARIANTS means that only the individual variants that meet the criteria enter the collection.

This allows collections to express more granular product affiliations. The official documentation has also added variant-level collection member fields to the ProductVariant type in Shopify Functions: ProductVariant.inAnyCollection(ids:) and ProductVariant.inCollections(ids:).

The official explanation is clear: when a variant itself is included in a collection, that variant is a collection member; the existing Product.inAnyCollection and Product.inCollections still retain product-level judgments. Developers can no longer just ask if a product is in a collection; they also need to consider whether the business scenario requires checking if a variant is in the collection.

How Will This Affect Collection Page Displays?

The most direct impact is that collection pages have the opportunity to evolve from displaying product cards to displaying sellable variant cards.

Taking an apparel brand as an example, in the past, a product with 8 colors would typically only display one product card on the collection page. Users would then select a color after clicking into the PDP. Under the new model, brands can organize collections around conditions such as color, size, material, inventory status, price range, metafield, etc., allowing qualifying variants to become collection members.

1. Color-Based Products Can Be Displayed More Naturally

Many DTC apparel, footwear, and bag brands encounter a problem: color is the first difference perceived by users, but Shopify’s product structure usually places color within the variant.

If the collection page can only display at the product level, it is challenging for a shoe model’s red, black, and cream colors to appear as three natural visual entry points. Merchants either have to split products, change themes, or use apps.

When collection logic supports variant-level members, color can become a display dimension closer to a first-class citizen. Brands can organize collections around themes like black items, summer blue tones, or holiday red styles, reducing the limitations imposed by the parent product structure.

2. Available Displays Can Be More Accurate

A common experience issue on collection pages is that product cards appear purchasable, but upon clicking, users find that the target size or color is out of stock.

If collection conditions and Functions logic can identify variant-level members, merchants have the opportunity to use sellable variants as the basis for display, promotions, discounts, and recommendations. For categories strongly related to size, this will reduce ineffective clicks and improve conversion paths.

3. Promotional Pages Can Be Organized at the SKU Level

Promotional activities often do not include the entire product but rather specific colors, specifications, packaging, or inventory batches.

In the past, if collections were only added at the product level, discounts, displays, and inventory clearance could easily conflict. Variant-level collections can make promotional pages more like a SKU-level curation tool: only the variants participating in the promotion enter the collection, and developers can then apply discounts, recommendations, sorting, or page displays based on that collection.

4. B2B, Multi-Market, and Catalog Management Will Be More Granular

Shopify’s official changelog mentions that this change affects the Admin GraphQL API and Shopify Functions. Although Collections themselves still serve online stores, sales channels, and marketing scenarios, the variant-level member relationships have particularly promising implications for B2B and multi-market scenarios.

The range of products visible to different customer groups, regions, and sales channels often falls at the variant level. Variant-level collections can serve as a more granular organizational method between catalogs, pricing, promotions, and shipping rules.

What Should Developers Pay Attention To?

This change has a more direct impact on developers than on ordinary merchants.

First, the way to read collections needs to migrate. Shopify has marked Collection.ruleSet as deprecated and recommends using Collection.sources. The collectionCreate(input:) and collectionUpdate(input:) methods have also been deprecated; the new syntax is to define sources through collectionCreate(collection:) and collectionUpdate(collection:).

Second, API versions need to keep up. The official documentation states that in the 2026-07 version and later, collections using the new sources model will appear in collections queries, collection(id:) queries, and other fields returning collections. Earlier API versions will filter out collections using new features due to the old ruleSet’s inability to represent these new characteristics.

This is crucial: if an app is still on the old version API, it may not see part of the new collections.

Third, product-level membership and variant-level membership need to be distinguished. The official documentation clearly states that Product.inAnyCollection / Product.inCollections continues to return product-level results; if a function needs to determine variant-level collection membership, it should call the new fields on ProductVariant.

For discount apps, search filter apps, recommendation apps, PIM/ERP synchronization, and theme enhancement apps, this will affect data models and boundary judgments.

Can Merchants Use This Directly Now?

According to official materials, this capability first manifests in the 2026-07 Admin GraphQL API and Shopify Functions. It does not mean that all themes will automatically display variants as independent product cards.

Merchants need to clarify three things. First, collection member relationships now support a more granular model expression, especially regarding source, conditions, exclusions, target type, and other API capabilities. Second, how the front-end collection page displays still depends on the theme, Liquid templates, Storefront API usage, apps, and sales channel implementations. Third, variant-level collections will drive themes and apps to adapt.

For merchants who want one color per product card or specific specifications to enter promotional pages, they may see more native capabilities, theme upgrades, or app solutions developed around this model in the future. A more cautious judgment is that Shopify has already advanced the underlying expression of collections to the variant level, and the front-end experience and merchant backend workflows will gradually catch up.

Insights for Independent Site Operations

Behind this change is a descent of e-commerce display logic.

In the past, brands often organized websites around products: new collections, bestsellers, discount collections, category collections. However, consumers’ purchasing decisions in many categories are not based on abstract products but on color, size, specifications, capacity, packaging, material, inventory, and price.

When collections can understand products at the variant level, operational actions will be closer to the real purchasing unit: clearing inventory can be done by specified variants; content marketing can organize products by color, material, and usage scenarios; discount rules can be more closely aligned with inventory and gross profit; search and recommendations can reduce friction from discovering unpurchasable items only after clicking; and data analysis can differentiate between product popularity and specific variant popularity.

This is especially important for Shopify merchants. Many brands, in pursuit of better collection page displays, have previously struggled with whether to split colors into different products. Splitting can benefit exposure and SEO but complicates PDP, inventory, reviews, related recommendations, and data attribution. If variant-level collections are fully utilized by themes and the app ecosystem, it may reduce this structural trade-off.

Several Questions Still to Observe

This update has already released a direction, but there are several issues worth continuing to watch for implementation.

• To what extent will the Shopify Admin backend open up visual operations? If most capabilities still rely on APIs, ordinary merchants will need support from apps or service providers.

• How will Online Store themes present variant-level collections? Will they maintain product cards as the primary display or gradually support variant cards, variant URLs, variant images, variant availability, and other more detailed displays?

• How will the Storefront API, search sorting, filters, and analytical reports handle the differences between product-level and variant-level metrics? If only some variants are in the collection, product cards, price ranges, inventory statuses, and URL redirects will need clearer specifications.

• Will there be compatibility issues with third-party apps? Shopify has already warned that older API versions may filter out new collections, and apps relying on ruleSets will need to migrate.

Conclusion

The new Collections are not just an ordinary API field adjustment. They advance Shopify collections from a single rule model to a new model with multiple sources, exclusions, reusability, and targeting products or variants.

For merchants, the most anticipated aspect is the more granular display capability: color, size, specifications, inventory, promotional variants, all of which may become the basic units for organizing products on collection pages.

For developers and service providers, it is now time to check three things: whether to read Collection.sources, whether to migrate to the 2026-07 API, and whether to use ProductVariant’s collection membership judgment when needed.

Collection pages were previously product groupings. Moving forward, they may evolve into a display system closer to SKUs and purchasing intentions.

References

• Shopify Developer Changelog: New Collection model and APIs now available (2026-06-17)

• Shopify Admin GraphQL: CollectionSourceTargetType

• Shopify Admin GraphQL: CollectionConditionsSource

• Shopify Developer Changelog: Publish and unpublish product variants independently from product (2026-05-07)