Shopify sub-collections and layered collections: what you can build now

If you run a Shopify store, you have almost certainly hit the wall. You built a "Sale" collection with a rule (everything tagged sale), and then you wanted to also force in one hero product that was not tagged, or quietly pull out two items you did not want on sale after all. Shopify said no. A collection was either fully automatic (rules) or fully manual (you pick every product), and never both. So you fought the tool: retagging products, keeping a spreadsheet, or paying for an app just to keep one list honest.

Shopify's 2026 collections update, part of the new source-based collections model, removes that wall. This post is the plain-language tour of what you can actually build now, with sub-collections as the headline, whether you run the store or build it for someone who does.

What a sub-collection is

A sub-collection is a collection that gets its products from one or more other collections. Instead of adding products directly, you point it at existing collections and say "include everything in these."

The classic example is a store-wide sale. Say you already keep three tidy sale collections: Men's Sale, Women's Sale, and Kids' Sale, each with its own rules. Before, building a single "All Sale" page meant duplicating all those rules and keeping four things in sync by hand. Now you create one All Sale collection with a sub-collection source that references the other three. When a product drops into Women's Sale, it appears in All Sale automatically. Nothing to re-sync, nothing to remember.

The bigger idea: a collection is a recipe

Sub-collections are one ingredient. The real shift is that a collection is now a recipe combining several kinds of ingredient, which Shopify calls sources, plus a list of exclusions. In one collection you can layer:

• Automated rules. "Anything tagged sale," "under 50 dollars," "in the Coffee category." Shopify keeps membership current as products change.
• Hand-picked products. Specific items you always want in, whether or not they match the rules. Your merchandiser's judgment, preserved.
• Other collections (sub-collections). Pull in the membership of existing collections, kept in sync.
• Exclusions. Specific products (or specific variants) you always want out, even if a rule would otherwise include them. The exception list you always wished you had.

Three things you can build today

1. A sale that is automatic but has exceptions

Rule: everything tagged sale. Then force in the two hero products you are promoting, and pull out the three items that are technically on sale but you would rather not feature. One collection, no app, no retagging. This single use case is the one merchants asked for most, and it was flatly impossible under the old smart-versus-custom split.

2. A base collection that feeds many

Build Winter Essentials once. Then reference it as a sub-collection inside a homepage feature, a campaign landing page, and a wholesale collection. Update the base once and every surface that references it updates too. This is how you stop maintaining five near-identical lists that drift apart over time.

3. A "shop the red" edit (with a caveat)

The new model can scope a collection to individual variants, not just whole products. A collection can hold only the red and navy shirts, or only the in-stock sizes, instead of dragging in the whole product because one variant qualified. Powerful for seasonal edits and color stories.

Are there limits?

Yes, and they are sensible. Sub-collections are capped at one level of nesting, as above. Shopify's docs also list caps on how many sources, conditions, and exclusions a single collection can hold, and how many collections per shop can use certain source types. The exact numbers are generous for normal merchandising and are the kind of thing that changes over time, so check the current Use the new collections model docs for the live figures before you design something enormous. For a typical store building a layered sale or a few shared bases, you will not come close.

Do you have to do anything?

For your existing collections, no. They keep working exactly as they are. The new capabilities are additive: they show up as new ways to build collections, not a migration you are forced through. If you are a developer or an app builder, there is a real (but non-urgent) migration story, and we wrote a separate guide on whether you actually need to migrate.

The mental upgrade worth keeping is small but powerful: stop thinking of a collection as a fixed list or a fixed rule, and start thinking of it as a recipe you compose. Rules for the bulk, picks for the highlights, exclusions for the exceptions, and other collections for the parts you have already curated. That is how the best merchandising teams already think. Shopify's tools finally match it.

Sources: Shopify Partners, Introducing the new Collections API; and Shopify Dev, Use the new collections model.