Shopify's New Collections Model (2026): Multi-Source, Variant and Sub-Collections Explained

Shopify's new collections model replaces the old smart vs manual split with sources, variant targeting and sub-collections. What changed in 2026, the limits, what it means for your apps, and how to use it well.

Shopify's new collections model is the biggest change to how collections work since automated collections arrived. For as long as most merchants can remember, every Shopify collection was one of two things: a manual collection, where you picked the products by hand, or a smart collection, where conditions picked them for you. In 2026 Shopify replaced that split. A collection is now built from sources, which can combine conditions, hand-picked products, exclusions, other collections and sources provided by apps, and it can target individual variants rather than whole products.

This post explains what changed and when, based on Shopify's changelog, help centre and developer documentation; what the new capabilities are good for on a real store; the limits you should know about; and the part that is easy to miss, which is what it means for the apps and integrations that read and write your collections. We build a Shopify app that works with collections, so we have been reading the details closely.

What changed, and when

• 17 June 2026: Shopify's developer changelog announced the new collection model and APIs, arriving in GraphQL Admin API version 2026-07, and marked it as requiring action from developers.
• 1 July 2026: API version 2026-07 was released, with the new model available to apps that use it.
• 16 July 2026: Shopify's merchant changelog announced that collections now support multi-source and variants, alongside an article on Shopify's own blog introducing the new collections experience.

Shopify's help centre now says that a new collections model is replacing the legacy manual and smart collections model, and that where the new experience is available, previous collections have been automatically converted to the new type. Shopify's changelog says existing collections continue to work and are updated in the new admin experience automatically, so you do not need to delete or recreate them. The help centre keeps separate pages for legacy smart and manual collections, for stores that do not have the new experience yet.

Why the old split was a problem

Under the legacy model, the type of a collection was fixed when it was created. Shopify's legacy help page is direct about it: you cannot change an automated collection to a manual one; you create a new manual collection instead. So every collection forced an early decision between two imperfect options. A manual collection stayed exactly as curated, but went stale the moment new products arrived. A smart collection stayed current, but offered no clean way to add one product that did not match the rules, or leave out one that did.

Merchants filled the gap with tags. A product that needed to appear in a smart collection got a special tag; a product that needed to be left out got another. Over a few years, many catalogues accumulated tags that exist only to steer collections, which nobody remembers the reason for. The new model's manual additions and exclusions are a direct answer to that habit.

Shopify's new collections model in one sentence

Shopify's developer documentation puts it simply: a collection is a union of sources. Each source contributes products, or variants, and the collection's members are everything its sources include, minus anything they exclude. Instead of choosing once, at creation, whether a collection is automatic or hand-picked, you combine the two in whatever mix suits the collection.

The help centre describes four ways to control what is in a collection:

• Automatically include products that match conditions.
• Manually add specific products.
• Automatically exclude products that match conditions.
• Manually exclude specific products.

That sounds like a small change. In practice it removes the most common workaround in Shopify merchandising: creating a special tag just to force one product into, or out of, a smart collection.

Multi-source collections

A single collection can now draw on more than one source. According to Shopify's changelog, you can combine automated conditions, hand-picked products, exclusions, other collections and sources from apps in one collection. The developer documentation describes three kinds of source.

• Conditions sources: conditions plus explicit product or variant selections. These are the evolution of the old smart collection rules, with the ability to add and remove specific items by hand.
• Sub-collection sources: a source that takes its members from other collections.
• Shareable sources: conditions sources owned by an app and linked by reference into as many collections as needed.

For a merchandiser, the everyday benefit is the mix of automatic and manual. A Summer Dresses collection can include everything tagged summer and of type dress, add three hero pieces that are not tagged, and exclude two products that are being discontinued, all in one place, without inventing tags to make it work.

Conditions have also become more expressive. Shopify's documentation says a single condition can now match a list of values, such as several product types at once. And the help centre lists condition attributes that include product and variant titles, type, vendor, category with subcategories, tags, product status, price, compare-at price, weight, inventory stock, metafields and metaobject references.

Variant collections

The second big change is that a collection can now target variants rather than whole products. Shopify's own example is a Valentine's Red Edit that includes only the red and pink variants of your products. According to Shopify, variant-level collections carry through to your online store, point of sale and Shop, and can be used for filters, discounts and taxes.

In the developer documentation, a source can be set to target variants, in which case conditions are evaluated for each variant, only the matching variants are members, and products with no matching variant do not appear at all. That is a real difference from the old behaviour, where Shopify's help centre notes that a product condition matches if any variant matches, so the whole product was included.

Where it helps:

• Colour and material edits, such as a Gold Edit that shows only the gold variant of pieces that also come in silver.
• Size-led collections, such as a Petite collection that shows only petite variants.
• Tax and discount rules that genuinely differ by variant, now that Shopify says collections, including variant-level ones, power discounts and taxes.

Variant collections are also the feature with the tightest limit, 100 per shop according to Shopify's documentation, so they are best used deliberately for the edits that need them rather than as a default.

Sub-collections: collections built from collections

A collection can now be built from other collections. Shopify's example is an Activewear collection built from existing Leggings, Tops and Shorts collections, which updates automatically when any of them changes. The documentation restricts sub-collections to a depth of one, so collections of collections cannot be nested several levels deep, and a source can include up to 10 sub-collections and exclude up to 5.

For stores with a deep catalogue, this is the feature that cuts maintenance the most. Parent categories such as Women, Jewellery or Gifts no longer need their own copy of every rule from their children. Change the child, and the parent follows.

App sources

Apps can now provide sources that merchants add to collections. Shopify's example is an app that maintains a list of products to exclude from promotions: add that source to several collections, and whenever the app updates the list, all of them reflect it. According to Shopify's developer documentation, these shareable sources persist when they are unlinked from a collection or the collection is deleted, and they survive the app being uninstalled unless the app deletes them.

That persistence is worth remembering when you remove apps. A source an app created may still be shaping a collection after the app has gone, so check your collections' sources after uninstalling anything that worked with them.

The new admin and Sidekick

The merchant-facing side of the change is a redesigned collections admin. Shopify's announcement describes a visual grid for dragging and reordering products, a switch between grid and list views, and control of sort order by price, alphabetically or manually. The help centre lists the sort options as most relevant, based on sales performance; best selling, based on the all-time number of orders; title; price; date created; and manual. It also says products are sorted by most relevant by default when you create a new collection.

Sidekick, Shopify's AI assistant, can now set up collections from a plain-language request. Shopify's example is asking for a New Arrivals collection that removes items after two weeks. The help centre says Sidekick can help with sorting too. As with any assistant, review what it builds before you publish it, especially conditions and exclusions, because a small mistake in a condition can quietly include or drop hundreds of products.

The limits worth knowing

Shopify's developer documentation lists the limits for the new model. The ones most likely to matter to a merchant are these:

• Collections per shop: 100,000, of which up to 5,000 can be conditions-based.
• Variant-level collections per shop: 100.
• Collections that use sub-collections: 50 per shop.
• Collections that exclude by reference to another collection: 5 per shop, and a source can exclude the members of up to 5 other collections.
• Sources per collection: 10.
• Conditions per source: 60, with each value in a multi-value condition counting separately. The help centre also gives 60 conditions as the maximum per collection.
• Manual exclusions per source: 1,000 products.

The help centre adds that condition-based exclusions are limited to category, tag, type and vendor conditions, and that the contains operator needs at least three characters. Collections are not available on Shopify's Starter plan.

What it means for your apps and integrations

This is the part most merchants will not see in the admin, and the part most likely to cause problems. Shopify's developer documentation is explicit: apps using API version 2026-07 see every collection, including those built with new features. Apps on 2026-04 or earlier continue to read and write legacy-shaped collections as before, but get a not found error for collections that use any new feature. Shopify's partner blog puts it more plainly: API versions before 2026-07 cannot represent new-model collections, so those collections are filtered out.

The documentation also defines which collections still count as legacy-shaped. Roughly, a collection stays readable by older apps if it has exactly one conditions-based product source using only attributes the old model understood, consistent all-or-any matching, no exclusions, and no mix of manual selections with conditions. Add a second source, a variant target, a sub-collection or an exclusion, and older apps can no longer see it.

In practice that means:

• A collection you rebuild with the new features may disappear from any app that has not moved to 2026-07, such as a filter app, a feed app, a sorting app or a custom integration.
• Nothing will warn you in the admin. The app simply stops seeing that collection.
• Shopify's changelog tells merchants directly: if your store uses third-party or custom apps that interact with collections, ask your developers to update to API version 2026-07.

Several older collection operations are also deprecated in 2026-07, though still available, including the mutations that add and remove products from a collection and the old rule set field. Developers can migrate step by step, but the direction is clear.

Where SellRank stands today

In the spirit of the questions above, here is our own answer. SellRank, our collection-sorting app, currently talks to Shopify on Admin API version 2026-04. Under Shopify's rules, that means SellRank sees and sorts collections that are still legacy-shaped, which today includes every collection a store had before the new model and any collection that keeps a single, simple source. A collection rebuilt with multiple sources, variant targeting, sub-collections or exclusions will not appear in SellRank until it moves to 2026-07.

We would rather say that plainly than have a merchant discover it. If you rely on SellRank to sort a collection, keep that collection's membership rules simple for now, or talk to us before converting it to use the new features.

How to adopt the new model without breaking anything

1. 1List every app and integration that reads or writes collections: filters and search, product feeds, sorting, bundles, discounts, ERP or inventory sync, and your headless storefront if you have one.
2. 2Ask each developer whether they are on API version 2026-07 and whether they support collections with multiple sources, variants and sub-collections.
3. 3Pick one low-risk collection to try the new features on, not your main category pages.
4. 4After converting it, check it in every app from the list. If a collection vanishes from an app, that app has not migrated.
5. 5Convert high-traffic collections only once every app that touches them supports the new model.
6. 6Keep a note of which collections use new features, so that anyone installing a new app later knows what to check.

Three worked examples

The capabilities make more sense against real collections. Here are three that are common on Indian D2C stores, and how each could be built under the new model compared with the old one.

A Festive Edit for a fashion store. Under the old model, this was usually a smart collection on a festive tag, plus a set of extra tags added by hand to force in a few hero products from other ranges, and a separate collection for anything that should be kept out. Under the new model it can be one collection: a conditions source for products tagged festive, manual additions for the hero pieces, and a manual exclusion for the two styles that are low on stock. Nothing about the product data has to change to make the collection look right.

A Gold Jewellery collection for a store that sells the same designs in gold and silver. Under the old model, a product-level condition would include a design if any variant matched, so the silver versions came along too and the product card might show a silver image. With a variant-targeted source, only the gold variants are members, which is what a shopper browsing gold expects to see. This is a good use of one of the 100 variant collections.

A Gifts collection built from other collections. Many stores maintain a Gifts page by tagging products one by one, and it drifts out of date quickly. Under the new model it can be built from existing collections, such as Gifts Under ₹999, Gift Sets and Personalised, with a manual exclusion for anything that cannot be delivered in time. Update the child collections, and Gifts follows.

Common mistakes with the new model

• Converting the main category pages first. The collections with the most traffic are the ones where a missing app or a wrong condition costs the most. Start small.
• Using exclusions as a permanent fix for bad product data. Excluding a mis-tagged product by hand hides the problem in one collection and leaves it everywhere else. Fix the tag when you can.
• Forgetting that manual additions do not expire. A product added by hand for a campaign stays in the collection until someone removes it. Put removal dates in your campaign plan.
• Building deep structures to get around the depth limit. If a structure needs collections of collections of collections, it is usually a sign the catalogue taxonomy needs attention, not the collections.
• Assuming an app has migrated because it still works. It may still work on your old-style collections and silently miss the new ones.

Questions to ask your developer or agency

If an agency, freelancer or in-house developer maintains apps or integrations for your store, these are the questions that tell you whether the new model is safe to use.

• Which of our apps and integrations read or write collections, and which API version is each one on?
• For each one on 2026-04 or earlier, when will it move to 2026-07?
• Does our headless storefront, if we have one, render collections that use the new features correctly?
• Do our feeds to marketplaces, ad platforms and comparison sites depend on collection membership?
• Do any of our discount or tax rules depend on collections that we are planning to change?

Nobody needs every answer to be yes before trying the new model. They need to know which collections are safe to change and which are not.

What the new model does not change

The new model changes which products are in a collection. It does not change the question of what order they appear in. A multi-source collection still has a single sort order, chosen from the same options: most relevant, best selling, title, price, date created or manual. And the limitations of those options have not gone away. Best selling still counts all-time orders, so last year's winners can outrank this week's. Price and date sorts ignore stock and conversion. Manual order is still a snapshot that someone has to keep up to date by hand.

That is the gap SellRank fills. It ranks the products in a collection by real performance, such as views, add-to-carts, orders, revenue, conversion or profit, lets you compose the order in percentage slots with pins and demotions, and writes the result into Shopify's own manual sort on a daily or weekly schedule. Membership and order are two separate jobs. Shopify's new model makes the first one much better. The second one still needs a plan.

Good first uses of the new collections model

• Clean up tag workarounds. If you created tags only to force products into or out of smart collections, a manual include or exclude now does the job directly.
• Build parent categories from sub-collections, so a Jewellery collection is simply Rings, Earrings and Necklaces together.
• Create one or two variant edits for campaigns where colour or material really matters.
• Replace duplicated sale exclusions with a single source reused across collections.
• Try Sidekick for a first draft of a complex collection, and review its conditions before publishing.

Used this way, the new model removes a lot of busywork. Just make sure your apps can see what you build. If you want help checking which of your apps are ready for 2026-07, or a second pair of eyes on a collection migration, get in touch through our contact page.