For most Shopify stores, collection pages carry more organic revenue than any other page type on the site. Product pages convert. Collection pages are how people find the products worth converting on in the first place.
In the US that matters more than it does anywhere else, because collection pages are where you compete with Amazon and Walmart. You will not outrank a marketplace on a bare product term. You can outrank one on a well-built category page that answers a more specific question than a marketplace listing ever does.
So when Shopify rebuilds how collections work at a structural level, that is not a small admin update. That rebuild landed in July 2026, and it changes more than most merchants realize yet.
What Actually Changed
Until this update, every Shopify collection was locked into one of two types. A custom collection held whatever products you added by hand. A smart collection filled itself automatically from rules: tag equals "summer," price under $50, and so on. You chose a lane when you created the collection, and you lived with its limits from then on.
That constraint pushed a lot of stores toward workarounds that never quite fit: duplicating a collection to add a handful of manual products on top of a rule set, building tag systems whose only real job was faking a hierarchy, or paying for a third-party app just to combine automation with curation in one place. None of that was a failure of any individual store's setup. It was the platform forcing a binary choice that real catalogs don't respect.
That split is gone. As of the 2026-07 GraphQL Admin API, stable from July 1, a collection is built from one or more Sources: automated conditions, manual product picks, individual variants, other collections, and even products supplied by an app.
You can combine as many as a single collection needs, and Shopify keeps the result current as your catalog changes, so a "bestsellers" collection no longer needs re-curating by hand every week.
Two other changes came with it. Collections can now exclude products as well as include them. And as of July 16, a collection can source other collections directly, which means real parent-child structure is possible for the first time without an app or a menu dropdown standing in for it.
The One Detail That's Already Tripping People Up
There's a detail in the new model that's easy to get wrong, and it's worth understanding before you touch a live collection.
When a collection has more than one source, Shopify doesn't intersect them. It combines them. The final product list is everything any source resolves to, added together, not the overlap between them.
Picture a supplements brand building a "Vegan Protein" collection. The obvious approach is two sources: a Collection source pointing at the existing "Protein Powder" collection, and a Products source filtered to the "Vegan" tag. Set both, and the reasonable expectation is protein powders that also happen to be vegan.
That's not what comes out. The result is every product in Protein Powder, vegan or not, plus every vegan-tagged product across the whole catalog, protein powder or not. Two sources on one collection combine with OR, not AND.
The fix is to stop stacking inclusion sources and start using exclusion instead. Build the collection from the Protein Powder source, then add an Exclude condition for anything not tagged vegan. What's left is the intersection that was wanted in the first place, built by subtraction rather than addition.
It's a small shift in how to think about the model, but it's the difference between a collection that serves the wrong slice of the catalog for months before anyone notices, and one that does exactly what it was built to do.
What This Opens Up: Real Category Structure
For stores with a catalog that outgrew a flat list of collections a long time ago, nesting is the more interesting change. A parent collection can now source its children directly. A homewares store's "Living Room" collection can pull from "Sofas," "Coffee Tables," and "Rugs" automatically, updating as each child changes, without duplicating a single product or building a menu structure to fake the hierarchy.
For a lot of Shopify stores, this solves a problem that's been splitting link equity for years: near-duplicate collections that only existed because there was no clean way to group products at two levels at once. Three collections sharing 90% of the same products with a slightly different filter aren't three good landing pages. They're one good landing page and two competitors to it. Nesting is the chance to merge them into a single, coherent hierarchy instead of leaving Google to guess which one deserves to rank.
Who This Matters Most For
Every Shopify store gets this update eventually, but it changes the most for catalogs that outgrew a flat structure years ago. Multi-brand stores, anything with heavy variant counts across colorways, sizes, or materials, and stores running the same core products across several audience-specific collections are sitting on the most duplicate structure right now.
US stores tend to hit this earlier than most, simply because catalogs here get large faster. If your collection list has grown mostly by adding new collections rather than restructuring old ones, that is usually a sign the underlying logic has been held together with tags and menu tricks for longer than anyone would like to admit.
The New Way to Get This Wrong
Nesting brings its own risk, and it's the kind that shows up in an organic traffic report months later with no obvious cause.
A parent collection is easy to create and just as easy to leave empty of anything except its children. If "Living Room" simply mirrors the combined product list of "Sofas," "Coffee Tables," and "Rugs," with no copy of its own and no search intent that's meaningfully different from its children, it's a thin page wearing the shape of useful structure. It might look tidy in the admin. To a search engine, it's a duplicate wrapper around pages that already existed.
The stores that get real value out of nesting are the ones that treat every new parent collection as a page that has to earn its place: on-page copy that isn't a summary of the children, a search intent that's actually distinct (a buying guide, a seasonal edit, a style comparison), and internal links that make the hierarchy legible to a visitor, not just to Shopify's admin.
That confusion isn't only a Google problem, either. AI shopping assistants and answer engines pull from the same structured product data, and a catalog full of near-identical collections is exactly as confusing to an LLM trying to recommend the right page as it is to a search algorithm trying to rank one.
What Hasn't Changed
A few things are worth confirming directly, because it's easy to assume this update went further than it did.
Collection URLs are untouched. A nested collection still lives at the same flat /collections/handle structure as before. Nesting is a relationship defined in the admin, not a URL structure, so there's no folder-style path appearing in the address bar and nothing to redirect.
Breadcrumbs and category-tree navigation aren't automatic either. The new model lets a store define how collections relate to each other. It doesn't render that structure on the storefront. That's still down to the theme, or an app, exactly as it was before. A tidy parent-child structure in the admin won't put a breadcrumb trail on the page by itself.
What To Do About It
If collection pages carry meaningful organic revenue for your store, work through this in order:
- Check whether the new model has actually reached your store. The rollout is staged, and if the Collections screen still shows the old smart-or-manual choice, it hasn't landed yet.
- Audit any collection already running more than one source before assuming it's working as intended. Pull the live product list and check it against what was expected. Union behavior hides well in a collection that looks fine at a glance.
- Confirm any apps or custom theme code that read your collections are on API version 2026-07. Anything reading an older version won't see collections built on the new model at all, which can mean products disappearing from a feed or a search integration without warning.
- Map near-duplicate collections before nesting anything. Nesting is only worth doing where it replaces actual duplication, not where it just adds a layer on top of collections that were already fine as flat siblings.
- Write real copy for every new parent collection. It's a landing page the moment it exists, so treat it like one.
Quick Answers
Did Shopify remove smart and custom collections?
Functionally, yes. Every collection now runs on the same Sources model. Existing collections converted automatically and keep working, so nothing forces a change to a collection that isn't broken.
Do multiple sources on one collection work as AND or OR?
OR. A collection's product list is the union of every source added to it, not the overlap. To narrow a source down, use an Exclude condition rather than adding a second inclusion source.
Does nesting collections change store URLs?
No. Collection URLs stay in the flat /collections/handle format whether or not a collection is nested.
Is migrating existing collections urgent?
No. Existing collections convert automatically and keep working under the logic they were built with. What's worth checking straight away is whether any apps or custom code reading your collections are updated to API version 2026-07.
Where This Leaves You
Shopify does not rebuild a core system like this often. The stores that treat it as a structural opportunity, auditing their sources, fixing the union-versus-intersection mistake, consolidating real duplicates through nesting, will end the year with cleaner collection architecture and stronger organic revenue than they started with. The stores that leave their collections exactly as they were will be fine for now, and increasingly behind by next year.
If you want a second set of eyes on what this means for your specific catalog, that is exactly the kind of audit we run. Kia Ora Digital are certified Shopify partners. Book a free SEO growth call and we will walk through your current collection setup before you change anything.
