For as long as most merchants have been on Shopify, a collection could be one of two things. A smart collection, built from rules. Or a manual collection, curated by hand. You chose at creation, and you lived with the choice. That single either-or decision is the quiet root cause of an enormous amount of app spend, tagging gymnastics, and navigation hacks across the Shopify ecosystem.
On July 16, Shopify removed it. The collections update that shipped with API version 2026-07 is, in my view, the most significant change to Shopify merchandising in years, not because it adds a flashy feature but because it deletes a constraint that thousands of merchants have been engineering around.
What Changed in Shopify’s Collections Update
A collection is no longer either rule-based or hand-picked. One collection can now combine multiple sources: automated conditions, individually selected products, exclusions, other collections, and sources provided by apps. (If you are newer to the platform, our guide to how Shopify works covers what collections do in the first place.)
That word “exclusions” deserves attention on its own. Until now, if your rules pulled in one product you didn’t want, your options were to tighten the rules until they distorted everything else, or to tag your way around the problem. Now you exclude the product and move on.
But the two changes that matter most are subcollections and variant-level collections.
Shopify Subcollections Are Finally Native
If you have ever searched for how to nest collections in Shopify, you know the answer merchants have been given for years: you can’t. The community threads follow a pattern. A merchant asks how to put collections inside a parent collection, and experienced users explain, correctly, that this is a platform limitation rather than something the merchant is doing wrong. The suggested fixes were always the same three: fake the hierarchy with navigation menus, duplicate the logic with tags, or pay for a third-party app that simulates a parent-child structure.
That era is over. A collection can now use another collection as a source. Build “Summer Dresses” and “Summer Sandals,” add both as sources to “Summer Shop,” and the parent stays in sync automatically as the source collections change. No tag duplication, no menu sleight of hand, no app subscription whose only job is to link collections together.
Variant-Level Collections: Shop by Size or Color Without Splitting Products
The second change fixes a problem that is easy to underestimate until it is yours. Collections could previously only contain whole products. If you wanted a “Shop Small” or “Everything in Red” page, and red was a variant rather than a separate product, you were stuck.
One case from the merchant community has stayed with me. A candle maker sells each scent in several sizes, all as variants of one product, which is exactly how Shopify wants you to model it. She wanted customers to shop by scent and by size. The only real path was splitting every size into its own product, which would have broken the unified inventory tracking that made her choose Shopify in the first place. So she paid for apps to fake it.
Collections can now include specific variants instead of whole products. Only the red ones, only size Small, only the 8oz. Those variants carry through to collection pages, storefront filters, and supported sales channels including POS and Shop. And because variant-level collections work with discounts and taxes, you can run a promotion scoped to exactly the variants in the collection. Twenty percent off travel sizes, without touching the full-size inventory, is now a native capability rather than a scripting project.
Shopify also redesigned the collections admin around these features: a visual grid with drag-to-reorder, bulk operations, and direct control over the sort order customers see. And this is a non-breaking change. Existing collections keep working, legacy fields keep working, and nothing needs to be deleted or recreated.
Before You Rebuild Anything: The App Compatibility Caveat
This is the section to forward to your dev team or agency.
Apps that have not updated to API version 2026-07 cannot see collections that use the new features. That means any collection with multiple sources, exclusions, subcollections, or variant targeting. There is no error message. The collection simply does not come back when the app asks for it.
Think about what silently reads your collections: product feed apps for Google and Meta, marketplace sync tools, import/export utilities, discount apps that target collections, ERP and inventory connectors. If one of those is on an older API version and you rebuild your core collections with the new features, your feed does not break loudly. It just quietly stops including those collections, and you find out when the traffic drops.
So before rebuilding, ask each relevant app vendor one specific question: are you on API version 2026-07 or later? If your stack includes custom apps or middleware, this is the same version check your developer would make during any Shopify app and API integration work, and it takes minutes to confirm.
One more technical note. Theme code that loops through a product’s variants, such as custom color swatches, will still render every variant regardless of what the collection includes, because Liquid does not expose collection-level variant scoping. If your theme has custom variant displays, have your developer review them before you lean on variant-level collections.
What This Means for You
Some concrete before-and-after cases:
- Seasonal sale rollups. Before: rebuild rules each season or maintain a parallel tagging scheme. After: one parent “Sale” collection sourcing your seasonal collections, plus hand-picked additions, minus exclusions.
- Shop by size or color. Before: duplicate products or a paid app. After: a variant-level collection, with filters and channels handled natively.
- A promotion on one size or color. Before: discount workarounds and careful tag hygiene. After: a discount applied to a variant-level collection.
- Collection-linking apps. Before: a monthly fee to simulate hierarchy. After: native subcollections. Confirm nothing else depends on the app before cancelling.
Sensible Next Steps
- List every app that reads your collections and confirm its API version with the vendor.
- If you plan to use variant-level collections, have your theme audited for variant loops.
- Pilot the new features on one low-stakes collection and verify it appears correctly in your feeds and channels before restructuring anything important.
- Remember that nothing breaks if you wait. This is the rare Shopify change where the risk sits entirely in adopting early with unready apps, not in the platform itself.
If you want a second set of eyes on your collection architecture before you rebuild it, that is exactly the kind of work we do. Get in touch and we will walk through your catalog and app stack with you.
Frequently Asked Questions
Do I need to rebuild my existing Shopify collections?
No. The update is non-breaking. Existing smart and manual collections keep working exactly as before, legacy fields remain supported, and every collection appears in the redesigned admin automatically. You only need to touch a collection if you want it to use the new features.
Can a Shopify collection contain other collections now?
Yes. As of the July 2026 update, a collection can use other collections as sources, which creates a native parent-child structure. The parent collection stays in sync automatically when a source collection changes, so no tagging workarounds or collection-linking apps are required.
Can a Shopify collection include only certain variants of a product?
Yes. Variant-level collections can include specific variants, such as one color or one size, instead of the whole product. Included variants carry through to collection pages, storefront filters, and supported sales channels including POS and Shop, and they work with discounts and taxes. Note that theme code which loops through all of a product’s variants will still display every variant.
Why do collections built with the new features not show up in some apps?
Apps that have not updated to Shopify API version 2026-07 cannot see collections that use multiple sources, exclusions, subcollections, or variant targeting. There is no error message; the collections are simply missing from the app’s results. Ask each app vendor to confirm they are on API version 2026-07 or later before you rebuild collections around the new features.