If you already run a store — real orders, real ad spend — you are not asking "what are sub collections?" You are asking which method won't break your theme, won't create a maintenance treadmill, and won't quietly hide your best-converting products three clicks deep. This guide answers that.
Most pages ranking for sub collections shopify stop at "drag a menu item under another one." That works, but it skips the limits that bite at scale and the question that actually moves money: are your nested collections built to curate themselves, or will you be editing membership by hand every time you upload designs?
Shopify doesn't have "sub collections" — here's what it has
There is no collection type in Shopify called a sub collection or a child collection. What you have is flat collections plus two layering tools: navigation menus and theme templates. "Shopify nested collections" and "shopify sub collections" are merchant shorthand for stacking those tools into a hierarchy.
Collections themselves require the Basic plan or higher — the Starter plan doesn't support them at all, per Shopify's collections documentation. So before you design a three-tier menu, confirm your plan can hold the collections underneath it.
One structural ceiling matters for big catalogs. On Shopify's current collections model, your store can have a maximum of 50 collections that contain another collection — the platform's own nesting cap. Fifty parent-child relationships is plenty for a focused POD store, but worth knowing before you plan a sprawling taxonomy.
Method 1: Nested menus (no code, fastest)
This is the route most operating stores should use. You create each collection normally, then expose the hierarchy through the storefront menu.
Go to Content > Menus, open your main (header) menu, and add a top-level item — say "T-Shirts." Then add the children — "Funny Tees," "Dog Tees," "Hiking Tees" — and drag each one so it sits indented under the parent. Save, and your header shows a drop-down. The grouping lives in collections; the menu just exposes it, which is exactly the pattern a store adding products weekly wants. If you need a refresher on building the collections first, our walkthrough on how to add products to collections on Shopify covers the membership side.
The depth limit that breaks deep trees
A top-level item can carry up to two levels of nested drop-downs — three levels total — but most themes support only up to two levels of nested drop-down menus. Build a third level and some themes silently fail to render it on the storefront.
Test on a live preview after you build any tree deeper than one level. A menu that looks perfect in the admin and renders broken on mobile is one of the quieter conversion leaks on an operating store.
The non-clickable parent header trick
Often you want "Shop" or "T-Shirts" to open the drop-down without being a clickable destination itself. Enter # in the link field for that parent item and it becomes a header that only opens the menu.
Two more facts worth banking: footer menus display only top-level items — drop-downs don't work in the footer — and Shopify recommends seven or fewer top-level menu items to avoid overcrowding. So your sub-collection strategy belongs in the header, grouped under a small number of parents.
Method 2: A collection page that lists its children (theme template)
The menu route organizes navigation; it does not give the parent collection its own landing page showing the child collections as tiles. For that you use a theme template.
In Online Store > Themes > Edit code, create a new collection template — merchants commonly name it something like collection.sub-collections.liquid — and add a "Collection list" section (or Liquid that outputs the child collections). Then assign that template to the parent collection from the product-organization panel on the collection page. Now "T-Shirts" is a real URL that shows "Funny," "Dog," and "Hiking" as clickable blocks.
This is the method that earns dedicated, link-worthy landing pages — a genuine SEO edge the menu-only approach misses. It costs a little theme work, so weigh it against how much organic traffic those parent pages could realistically pull.
Method 3: Apps — when to actually pay
Apps exist that add true parent-child collection objects, breadcrumb trees, and automatic sub-collection pages. They are worth it when you have a genuinely deep taxonomy (think category → sub-category → sub-sub-category) that the native two-level menu can't express, or when you want the hierarchy managed without touching theme code.
For most POD stores, the honest answer is you don't need one. A clean two-level menu plus a couple of templated parent pages covers the job. Pay for an app only when the native limits above are actually the thing blocking you — not before.
Make the children automated, not manual (the maintenance math)
Here is the part every other guide skips. Whether a child collection is a legacy smart (automated) collection, a legacy manual one, or a collection on the new model changes how much work it costs you forever.
Automate the membership. A legacy smart collection populates itself from conditions — you can add up to 60 selection conditions per collection — so "Hiking Tees" can be defined as tag equals hiking and type equals tee, and it fills itself as you upload.
Say you run 800 products and tag every design on upload (dogs, hiking, funny) with a product type (tee, hoodie). Automated child collections mean next month's 40 new hiking tees land in the right sub collection with zero manual curation. The same catalog on manual collections means editing membership by hand on every import — the treadmill the condition system exists to kill. Our guide to bulk editing Shopify products pairs well here for getting those tags and types consistent at scale.
One trap on the legacy model: you can't change an automatic collection to a manual collection after creation — you'd have to rebuild. Choose the type deliberately the first time. And remember collections don't round-trip through CSV: collections won't export in a product CSV, so your hierarchy isn't something a spreadsheet backs up for you.
A merchandising note: each collection page defaults to a most-relevant sort and shows 60 products per page. On an automated child collection, a performance-based sort keeps your best sellers on top as the catalog churns — manual sorting silently leaves new products wherever they land.
The profit angle every other guide skips
Reorganizing collections feels like housekeeping, but for an operating store it's a revenue lever — if you know which collections actually earn. Most merchants don't, because the collection page shows units sold, not profit.
Say your store does 340 orders a month at a $31 average order value with $2,800 a month in Meta spend. That's roughly $8.24 of ad cost per order. A tee that sells for $31 with a $14 Printify base-plus-shipping cost and about $1.20 in payment fees nets $31 − $14 − $1.20 − $8.24 = $7.56 per order. Now suppose your "Funny Tees" sub collection converts cold Meta traffic while "Dog Tees" only sells to repeat buyers at near-zero CAC — those two child collections have completely different margins, and burying the profitable one under a broken third menu level costs real money.
This is where PodVector AI's Victor earns its place. Victor is an AI employee that runs your Shopify store operations — including collections — alongside Meta Ads, Google Ads, Printify, Printful, Gelato, and Klaviyo, and it computes true per-order profit so you can see which collections actually make money before you reshuffle the menu. Every write action is approval-gated: Victor proposes, you approve, then it executes. It's not a dashboard you log into to read charts — it's an employee that does the reorganizing with you.
Once your hierarchy is clean, the next lever is usually pricing and promotions on those pages — see how to show a discount on the product page for that. For the full admin workflow around products, collections, and feeds, the Shopify store operations guide is the hub, and if you run Google Shopping, bulk-editing your Google Shopping fields keeps those collection products feed-ready.
FAQs
Does Shopify have native sub collections?
No. Shopify has no collection type called a sub collection or child collection. You create the appearance of a hierarchy by nesting collections in a navigation menu or by pointing a parent collection at a theme template that lists child collections. Apps can add true parent-child objects if you need them.
How many levels deep can Shopify menus nest?
A top-level item supports up to two levels of nested drop-downs, but most themes render only up to two levels reliably. Treat two levels as your working ceiling and always preview deeper trees on the live storefront, especially on mobile, before you rely on them.
Should sub collections be manual or automated collections?
Automated, in almost every case. A condition-based collection fills itself as you upload tagged products, while a manual one makes you edit membership by hand on every import. On the legacy model, remember you can't convert an automatic collection to a manual one later, so pick automated at creation.
Do sub collections help SEO?
They can, but only the theme-template method gives each parent collection a real, indexable landing page — menu nesting alone just reorganizes links. Dedicated category pages targeting specific terms are the SEO payoff; building them is a trade-off against the theme work involved, and there's no guaranteed ranking lift.
Can I put sub collections in my footer?
No drop-downs. Footer menus display only top-level items, so a nested hierarchy won't expand there. Keep your sub-collection structure in the header menu, grouped under a small number of parents — Shopify recommends seven or fewer top-level items to avoid crowding.