If you came here from a blog promising an "Add sub-collection" button, close that tab. That button does not exist in the Shopify admin, and the pages telling you it does are years out of date. What follows is how the structure actually gets built in a store you already run.
What "collections within collections" actually means on Shopify
Shopify is mid-transition between two collection models, and which one your store has changes the answer. Most operators still know the legacy model: a manual collection you hand-pick, or a smart (automated) collection that fills itself from conditions. Neither legacy type can contain another collection — a legacy collection holds products, full stop.
The newer collections model is the exception. It is a single collection type that can automatically include products or variants by condition, manually include specific items, and — the part you want — reference another collection as a source. That is the closest Shopify gets to real nesting.
Either way, collections require the Basic plan or higher; the Starter plan does not support them at all, according to Shopify's collections documentation. So before you architect anything, confirm which model and plan the store is on.
The new collections model: the closest thing to true nesting
On the new model, a "parent" collection can be defined to include the products of a "child" collection, so updating the child flows up automatically. This is genuine nesting, but it comes with hard caps worth knowing before you build a deep tree.
Shopify documents the ceilings plainly: your store can have a maximum of 5,000 collections that contain any conditions, a maximum of 50 collections that contain another collection, and a maximum of 100 collections that contain manually or automatically added variants, per Shopify's collection types reference. The fifty-collection nesting cap is the one that bites — a large catalog with a nested category for every sub-niche hits it faster than you would guess.
One more rule that trips up operators on the legacy model: you cannot flip a collection's type after creation. "You can't change an automatic collection to a manual collection," Shopify states — the fix is building a new collection of the other type. Choose deliberately at creation, because deletion is permanent too.
The menu workaround most stores actually use
If you are on the legacy model, or you just want shoppers to browse a hierarchy without rebuilding your catalog, the menu is where "collections within collections" really lives. You build the tree in navigation and point each item at a collection.
Shopify's drop-down menus support depth: a top-level item can have up to two levels of nested drop-down menus — three levels in total — though "most themes support up to two levels," per Shopify's drop-down menu docs. Test your theme before committing to a three-deep tree, because the admin will let you build depth the storefront then fails to render.
Two practical moves from the same source. To make a "Shop" header that only opens the menu rather than linking anywhere, enter # in its link field. And Shopify's own crowding guidance is to "add seven or fewer top-level menu items to avoid overcrowding" — a useful discipline when you are tempted to surface every collection at once. Note the footer can only display top-level items; drop-downs do not work there.
The clean division of labor for an operating store: collections do the grouping, menus do the exposing. Point a menu item at an automated collection and your navigation stays current as products flow in — you only touch the menu when the taxonomy changes, not when the catalog does. If you want the step-by-step on simulating sub-collections without the new model, our deep dive on whether you can create sub-collections in Shopify walks the exact menu-and-tag setup.
The tag-and-automate pattern that scales
Here is the pattern that makes a nested-looking storefront almost maintenance-free. Tag every product on upload, then let automated collections do the sorting, so the "sub-collections" populate themselves.
Smart collections support up to 60 selection conditions each, matched on an all-conditions or any-condition basis, according to Shopify's smart collections documentation. That is far more logic than most stores ever need, which means you can carve a catalog into dozens of tight, self-maintaining groups.
Say you run a print-on-demand store with 800 designs. You tag each upload (dogs, hiking, funny) and set a product type (tee, hoodie, mug). "Hiking Tees" becomes all of [tag = hiking] + [type = tee]; a "Gift Shop" becomes any of [tag = gift] or [tag = holiday]. When 40 new hoodies import next month with the right tags, every relevant collection updates itself — zero manual curation, and your menu tree keeps pointing at collections that are never stale.
Each collection also carries a default sort order — most relevant, best selling, price, date, or manual — with the admin paginating at 60 products per page, per Shopify's collection layout docs. Pairing automated conditions with a performance-based sort is the lowest-maintenance combination for stores adding products weekly. For the conversion side of this — how a shopper actually lands and buys once they reach a collection — see our breakdown of a high-converting Shopify product page.
The profit angle the ranking pages all skip
Every SERP result treats "collections within collections" as purely a navigation question. For an operating store it is also a margin question — because burying a product three menu levels deep changes how many people ever find it, and that flows straight to profit.
Walk a quick example. Say a tee costs you $12.40 from your supplier and sells for $28, and payment plus transaction fees run about $1.10 on that order. Gross profit before ads is $28 − $12.40 − $1.10 = $14.50 per unit.
Now add acquisition. If that tee lives in a top-level collection and converts cold traffic at a $6.00 ad cost per order, you net $14.50 − $6.00 = $8.50. Bury it two menu clicks deeper and suppose click-through to it halves, so your effective ad cost per order doubles to $12.00 — net profit collapses to $14.50 − $12.00 = $2.50 on the same shirt. The structure did not change the product; it changed the economics.
That is the calculation the ranking pages never run, and it is the one worth running per collection before you decide how deep to nest. The deeper the tree, the fewer shoppers reach the bottom, and your best-margin products should rarely be the hardest to find.
Where Victor fits for a store already doing this
Keeping a nested collection structure honest means knowing which collections actually earn — and that requires seeing orders, ad spend, and supplier costs in one place. That is what Victor, the AI employee from PodVector AI, does.
Victor connects to Shopify, Meta Ads, Google Ads, Printify, Printful, Gelato, and Klaviyo, so he sees every order, every ad dollar, and every supplier cost together and computes the true per-order profit on each product — the $8.50-versus-$2.50 math above, done across your whole catalog. Because he also knows your Printify, Printful, and Gelato costs before the first sale, he can flag a buried, high-margin collection worth promoting.
Victor is not a dashboard you read. With your approval on every write, he can act inside Shopify, Meta, Google Ads, and Klaviyo — reorganize a collection's products, adjust a campaign budget behind an underperforming collection, or change a price — and deliver the reports to your Google Drive. You can put Victor to work on your store and see the per-collection profit picture for yourself.
Once you know which collections convert, the next lever is price presentation — our guide to showing a discount on the product page covers that. And if you are running multiple storefronts, Shopify Plus multi-store management shapes how collection taxonomy carries across them. For the full operating picture, start with our Shopify store operations guide.
FAQs
Can you put a collection inside a collection in Shopify?
Not as a literal folder-style nest on the legacy model — a legacy collection holds products, not other collections. On Shopify's newer collections model, a collection can reference another collection as a source, which is the closest thing to true nesting, capped at a maximum of 50 collections that contain another collection per store, per Shopify.
How do I create sub-collections without the new model?
Use menus and tags. Build a drop-down menu tree pointing at automated collections, and tag products so those collections fill themselves. Shopify menus support up to two levels of nested drop-downs below a top-level item, per Shopify's menu docs — enough for a Shop → Category → Sub-category feel without any real nesting.
Why do old guides mention an "Add sub-collection" button?
Because they are outdated. That button does not exist in the current Shopify admin, and native folder-style nesting was never a standard feature. Treat any guide referencing it as unreliable, and verify UI paths against Shopify's own documentation.
Does nesting collections hurt my store?
It can, if you nest for its own sake. Extra menu depth means fewer shoppers reach the products at the bottom, which raises your effective ad cost per order on those items. Keep your best-margin products shallow, and only nest where shoppers genuinely browse that way.
How many collections can a Shopify store have?
On the new model, a store can have a maximum of 5,000 collections that contain any conditions, with the nesting and variant sub-limits noted above, according to Shopify's collection types reference. That is far more headroom than most catalogs require — the constraint you will hit first is the fifty-collection nesting cap, not the overall total.
Can automated collections power a nested menu?
Yes, and it is the lowest-maintenance setup. Point each menu item at a smart collection built from tags, and the menu stays accurate as products import — you only edit navigation when your taxonomy changes. Smart collections support up to 60 conditions each, per Shopify, so the logic is rarely the limiting factor.