Shopify’s modern Online Store > Navigation editor lets you nest menu items 3 levels deep. For most stores that’s plenty. But if you sell parts, hardware, or anything with thousands of SKUs spread across deep sub-categories, you’ll hit that ceiling fast. Legacy nesting in Breadcrumbs Uncomplicated, Categories Uncomplicated and Menus Uncomplicated is the clean way through.
Why the 3-level limit exists
The modern Menus admin interface caps nesting at 3 levels, and the dropdown most themes ship with doesn’t render well past that anyway. But Shopify’s data model has no such cap - it has always supported deeper trees via the older “menu item points at another menu by name” pattern. That’s what legacy nesting in the app exploits.
The naive workaround (and why it fails)
Merchants often try to fake a 4th level by duplicating sub-menus or creating sibling menus that overlap. Shopify can’t tell two same-named menu items apart, so duplicate collection names and URLs confuse the URL resolver. The symptom in your breadcrumbs is a trail that randomly snaps to the wrong branch on some products, with no apparent pattern - because the resolver picked whichever duplicate it saw first.
Legacy nesting in the app
Menu nesting lives in Category list > Menu nesting (or Floatlist settings > Menu nesting in Menus Uncomplicated).
- Modern nesting (the default) - mirrors Shopify’s admin, capped at 3 levels.
- Legacy nesting - matches a menu item to another menu by title, so the matched menu becomes a sub-tree under that item. No depth cap.
Legacy nesting is how Shopify navigation worked before the modern editor existed, and the data model still supports it. To go past 3 levels you create a 4th-level (or deeper) menu in Online Store > Navigation whose title matches the leaf menu item it should hang off. The app stitches them together at render time.
The trade-off, called out in the settings tooltip itself, is that titles must be globally unique across all menus - if two menus or menu items share a title, Shopify (and the app) can’t tell which is the parent.
A worked example: a 5-level fasteners tree
A 5-level fasteners tree, of the kind a serious hardware catalogue needs:
- Fasteners
- Screws
- Machine screws
- Stainless steel machine screws
- 18-8 stainless steel machine screws
- Stainless steel machine screws
- Machine screws
- Screws
The structure on the Shopify side: one menu called main-menu with Fasteners > Screws > Machine screws (3 levels, the modern limit), then a separate menu named Stainless steel machine screws whose first item is 18-8 stainless steel machine screws. The app sees the title match between the 3rd-level item and the second menu, and stitches them together as if they were one tree. The breadcrumb on an 18-8 product reads Home > Fasteners > Screws > Machine screws > Stainless steel machine screws > 18-8 stainless steel machine screws.
Every title in that tree is globally unique - that’s what keeps legacy nesting’s title-matching working.
Performance considerations
Deep trees mean more menu items, which means slightly larger snapshots and a slightly slower Refresh Categories. In practice a 6-level, ~500-item tree refreshes in a few seconds on a typical store, and the per-page render is unchanged because the snapshot is cached.
Limitations
- Titles must be globally unique across all menus. Two menu items (or two menus) sharing a title will confuse the title-matching that legacy nesting relies on - the app will flag duplicates, but you have to fix them in Online Store > Navigation.
- Shopify’s main-menu dropdown in most themes won’t display past level 3 even if your data is deeper - you’ll need a mega-menu app for the dropdown itself. The breadcrumbs will still be correct.
- Shopify Search results return short-form
/products/...URLs, which lose the full path context (see the multi-collection post for how the app handles that).
Summary
If you’ve ever felt boxed in by Shopify’s 3-level menu cap, legacy nesting in Breadcrumbs Uncomplicated, Categories Uncomplicated or Menus Uncomplicated lets you build the deep taxonomy your customers expect, without hacks or duplicate collections - provided every menu and menu item has a unique title.