Shopify Collections: Multiple Sources and Variants

Shopify collections can now combine multiple sources and target specific variants. Here is what changed in the July 2026 changelog and how to plan for it.

Stacked isometric layers in indigo, blue, cyan and green representing a Shopify collection built from multiple sources

Shopify collections just stopped being a flat list. On July 16 Shopify shipped multi-source collections and variant-level collections, which means one collection can now combine automated conditions, hand-picked products, exclusions, other collections, and app sources, and it can target a single size or color instead of a whole product. The merchandising strategies that used to need duplicate lists or a third-party app are now native.

Video: Shopify collections now support multiple sources and variants

What a collection used to be

Two things, and only two. Automated by conditions, or hand-picked by you. If you wanted "everything in the summer line except the three SKUs we are discontinuing," you built a second list and maintained it by hand, or you paid an app to do it. That is the workaround tax this release removes.

Collections are now building blocks

A single collection can pull from several sources at once: automated conditions, hand-picked products, exclusion rules, sources supplied by apps, and other collections. That last one is the quiet workhorse. Add a collection as a source inside another collection and the parent stays in sync when the source changes.

Practically, that means you can build small, precise base collections once and compose the big ones out of them. Update "Clearance" and every parent that references it follows. No duplicate lists, no nightly sync job, no drift between what merchandising thinks is live and what customers actually see.

Variant-level collections are the real unlock

Collections can now be built around specific variants rather than whole products: a size, a color, a finish. Those variants show up on collection pages, in filters, and in supported sales channels, including Online Store and POS.

This is the piece worth planning around, because variant-level merchandising is where most stores have been faking it. A "Size 12 in stock" page, a metallic-finish landing page, a clearance run that only covers the odd sizes: all of that used to mean tags, duplicate products, or an app. Now it is a collection. For merchants whose catalog complexity lives at the variant level, like parts sellers working with fitment data, this changes what is worth building.

Verify storefront rendering before you launch a campaign on it

Admin support shipped ahead of storefront support. Variant-scoped rendering, meaning swatches, price ranges, and filters that reflect only the included variants, was still rolling out behind a flag as of July 2026. Your theme probably does not need code changes if its product cards already read from variant data, but do not assume it works store-wide. Build the collection, look at the live page on your own store, then plan the campaign.

One collection, many jobs

Because collections are reusable, the same list powers other work. Discounts and taxes both accept collections, including variant-level ones. Build the segment once, then point promotions and tax rules at it instead of rebuilding the same logic in three places.

Pair that with the discount stacking release from earlier in July and your promo setup gets a lot more precise: a variant-level collection defines exactly what is eligible, and tag-based stacking defines how offers combine on it. Model the worst-case stack either way; a tighter segment does not protect your margin by itself.

The admin got a redesign too

A visual grid for drag-to-reorder and bulk moves, a list view when you need detail, and real control over the sort order customers actually see on the collection page. Sidekick can build and update collections from the admin and on mobile. Small stuff, but merchandising teams live in this screen, and manual sort order has been a source of quiet pain for years.

The part your apps will feel

Under the hood, the Admin API replaced the single ruleSet field with a multi-source model. Each collection now carries one or more CollectionSource objects covering typed inclusion conditions, exclusions, manual selections, and referenced sub-collections. Shopify Functions get two new ProductVariant fields, inAnyCollection and inCollections, for variant-aware logic.

Here is the trap. Existing collections keep working and there are no breaking changes, but collections that use the new capabilities are filtered out of responses on API versions before 2026-07. An app or integration still on an older version will not error. It will just quietly not see those collections. If you run an ERP sync, a feed manager, a PIM, or any custom integration that reads collections, confirm it is on 2026-07 before you start building multi-source collections your operations depend on.

What to do before Black Friday planning locks in

Four things, in order. Audit the duplicate collections and tag hacks you built as workarounds, and mark which ones collapse into a single multi-source collection. Confirm every app and integration that reads collections is on API version 2026-07. Build one variant-level collection and verify it renders on your live storefront. Then decide which promotions should target variants instead of products, before the BFCM calendar is set in stone.

Worth noting: this is a change to how you organize the catalog, and catalog structure is increasingly what AI shopping agents read. Cleaner, more precise collections are the same work as optimizing your product data for AI search. Two problems, one cleanup.

At Ambaum we track every changelog release so our merchants do not have to. If you want a second set of eyes on which of these to act on before Black Friday planning locks in, hit us up.

Video transcript
Read the full transcript

Shopify shipped a few updates in July. The big one was discount stacking, which I covered last week. But the release that really caught my eye: collections now support multiple sources and variants.

Until now, a collection was one of two things. Automated by conditions, or hand-picked by you. Anything more complex meant duplicate lists, manual upkeep, or a third-party app doing the work.

Now, a collection can pull from several sources at once. Conditions, hand-picked products, exclusions, app sources, and even other collections. Nest one collection inside another, and the parent stays in sync when the source changes.

Here's the one worth planning around. Collections can now be built around specific variants: a size, a color, a finish. Those variants show up on collection pages, in filters, and in supported sales channels, including the online store and point of sale.

Because collections are reusable, the same list powers other work. Discounts and taxes both accept collections, including the variant-level ones. Build the segment once, then point your promotions and tax rules at it.

The collections admin also got a redesign. A visual grid for drag-to-reorder and bulk moves, a list view when you need detail, and real control over the sort order customers actually see.

The takeaway: more merchandising control natively in Shopify, with fewer apps in the middle. At Ambaum, we track every changelog release so our merchants don't have to. Want a second set of eyes before Black Friday planning? Reach out.

Frequently Asked Questions
What are multi-source collections in Shopify?
Multi-source collections let one Shopify collection pull from several inputs at once: automated conditions, hand-picked products, exclusion rules, other collections, and sources supplied by apps. Shopify shipped the change on July 16, 2026. Before it, a collection was either fully automated or fully manual, never both.
Can Shopify collections contain other collections?
Yes. A collection can be added as a source inside another collection, so you can nest one inside another. The parent stays in sync automatically when the source collection changes, which removes the duplicate lists and manual upkeep merchants used to maintain by hand or through an app.
What is a variant-level collection in Shopify?
A variant-level collection targets specific product variants rather than whole products, such as every red item or every size 12. Those variants appear on collection pages, in filters, and in supported sales channels including Online Store and POS, and the same collection can drive discounts and taxes.
Do I need to update my apps for the new Shopify collection model?
Yes, if they read collections through the Admin API. The new model replaces the single ruleSet field with CollectionSource objects in API version 2026-07. Collections that use the new capabilities are filtered out of responses on older API versions, so an un-migrated app can silently miss them.
Will variant-level collections render correctly on my storefront?
Not necessarily yet. Admin support shipped ahead of storefront rendering, and variant-scoped display of swatches, price ranges, and filters was still rolling out behind a flag as of July 2026. Verify the behavior on your own store before launching a customer-facing campaign that depends on it.
No pitch. No pressure. Just perspective.

Get the strategic input you’ve been missing