Theme development
Variant-level collections in Shopify: what theme developers can (and can't) build yet
The new 2026-07 collections model lets a collection hold individual variants, not whole products. Powerful, but the storefront side is still rolling out. Here's what works on a collection page today, and what to verify before you rely on it.
Bas Lefeber
Founder, learnshopify.dev · July 8, 2026 · 5 min read
The single most exciting line in the new source-based collections model, if you build themes, is variant-level targeting. A collection can now hold individual variants rather than dragging in the whole product because one variant qualified. "All the red items," "only the in-stock sizes," "just the 500ml bottles": these become real, queryable collections instead of a merchandising fantasy you fake with tags and hope.
Before you rebuild your collection templates around it, though, there is a timing detail that will save you a wasted afternoon. The new model is stable in the Admin API. The storefront side, how that variant-scoped collection actually renders on a collection page, was still being switched on gradually when the model went stable. This post is about the gap between those two facts, and what it means for what you can safely ship today.
The one thing to take away
You can create variant-scoped collections through the Admin API right now. Whether a given storefront renders them correctly (swatches, filters, and price ranges scoped to just the included variants) depended on a beta flag that Shopify was rolling out gradually as of July 2026. So do not build a live merchandising feature that assumes variant-level collection pages render correctly until you have verified it on the target store.
What variant-scoped actually changes on a collection page
Think about what a collection page assumes today. It loops products, and for each product it renders a card: a title, a price (or a "from" price across variants), maybe swatches for every color the product comes in. The filters in the sidebar count and narrow by product-level facets. Every part of that quietly assumes the unit of the page is the product.
A variant-scoped collection breaks that assumption in a good way. If the collection only includes the red and navy variants of a shirt that also comes in six other colors, then on that collection page the card should show only red and navy: two swatches, not eight. The price range should reflect only the included variants. The filters and facets should scope to the included variants, not the whole product. Per Shopify's docs, that is exactly the intended behavior: on a variant-scoped collection, filters and facets scope to included variants, and swatches and selected variants reflect only the included variants.
The good news: it's meant to be transparent
Here is the genuinely encouraging part. In the developer-preview thread, Shopify's Diana Cheptene (Merchandising team) was explicit that when storefront support is live, it needs no theme changes on the developer's end. The collection would display only the included variants with their swatches, price ranges, and filters scoped accordingly, and existing theme code would pick that up.
In other words, this is not a "learn a new Liquid object and rewrite every product card" migration. If your theme already renders swatches and price ranges from the product's variants correctly, a variant-scoped collection is supposed to just flow through and show the narrowed set. The scoping happens at the platform level, below your Liquid.
A note on the mixed signals
You will see two framings across the docs and the thread. The migration guide stresses that existing storefront theme APIs are unaffected (your code keeps working). The preview thread says variant-scoped storefront rendering was still rolling out behind a beta flag. Both are true and not in conflict: your theme code does not need to change, but the platform behavior that makes variant scoping visible was being enabled gradually. "No code change" is not the same as "live on every store today."
What you can safely do today
- Create and inspect variant-scoped collections in the Admin API. The model is stable in 2026-07. You can build them, read them, and see the membership.
- Audit your product card for variant honesty. Make sure your swatches, "from" price, and price range are actually derived from the product's variants, not hardcoded or pulled from a metafield string. If they are variant-derived, you are already positioned to benefit the moment scoping goes live.
- Check your filters scope to variants, not just products. Color and size facets that reason about variants will narrow correctly; ones that only reason about product-level tags will not.
- Verify on the specific store before you ship. Enable it on a development or staging store, build a variant-scoped collection, and load the collection page. Confirm the card shows only the included swatches and the narrowed price range before you promise a merchant the feature.
Don't do this yet
Do not build a customer-facing merchandising campaign ("Shop the red edit") whose correctness depends on variant-scoped collection pages rendering right, until you have confirmed the behavior on that exact store. If the flag is not yet enabled there, the page may fall back to showing whole products, and "the red edit" quietly shows every color. Verify, then promise.
Learn this properly · free lesson
Build the collection page layout
Build a collection page and product card against a live storefront, so you know exactly which markup variant scoping flows into. Free, runs in your browser.
Try this lesson — freeWhy this is the professional's read on the news
An AI assistant summarizing the announcement will tell you variant-level collections exist, and it will be right. What it will not tell you, because it lives in the changelog and a forum thread and not in the tidy feature bullet, is that the Admin model and the storefront rendering shipped on different clocks. That gap is exactly the kind of thing that turns into a broken client demo if you take the headline at face value.
The durable skill here is not memorizing which flag is live this week. It is the instinct to ask, for any new platform capability, "which layer is this actually in, and has the storefront caught up?" Admin API, Storefront API, and Liquid move on their own timelines constantly. Reading a feature announcement like an engineer means separating "the data can now be modelled this way" from "the buyer can now see it," and verifying the second one yourself. That habit outlasts every individual API version.
Sources: Shopify Dev, Use the new collections model and Migrate to flexible collections; and the developer-preview community thread (Diana Cheptene, Shopify Merchandising).
Frequently asked questions
Can I use variant-level collections in Liquid on the storefront yet?
Not universally at launch. The variant-level collections model is stable in the 2026-07 Admin API, but storefront rendering of variant-scoped collections (swatches, filters, and price ranges scoped to the included variants) was still rolling out behind a beta flag as of July 2026. Shopify says it requires no theme changes once enabled, but you should verify it is live on the specific store before relying on it.
Do I need to rewrite my theme for variant-scoped collections?
According to Shopify's Merchandising team, no theme changes are required. If your product card already derives swatches and price ranges from the product's variants, a variant-scoped collection is meant to flow through automatically and show only the included variants. The scoping happens at the platform level below your Liquid.
What does a variant-scoped collection change on a collection page?
It narrows the unit of the page from the whole product to specific variants. A product card in a variant-scoped collection should show only the included variants' swatches, a price range covering only those variants, and filters and facets scoped to them, rather than the full product with every color and size.
Is the new collections model safe to adopt now?
The Admin API side is stable in 2026-07 and the migration is non-breaking, so modelling variant-scoped collections is safe. The caveat is purely storefront rendering: because it was rolling out gradually, do not ship a customer-facing feature whose correctness depends on variant-scoped collection pages until you have confirmed the behavior on that exact store.
Start free
Ready to become a Shopify developer?
You just read how it works. Now write it yourself: real tickets from a live store, in an editor where the storefront updates as you type. Module 1 is free, no card.
Free · No credit card · Your first win in minutes
About the author
Bas Lefeber, Founder, learnshopify.dev
Bas builds learnshopify.dev, where developers learn production-grade Shopify theme development against a live storefront. He writes about Liquid, theme architecture, and the parts of the job that still matter now that AI writes the code.
Keep going in the curriculum
