Where I Look First When Shopify Collection Filters Vanish

The Shopify Search & Discovery app, the one merchants get told to install when their Shopify collection filters disappear, has a 3.4-star rating on the Shopify App Store. That number isn't an indictment of the app, exactly. It's a count of merchants who configured filters correctly, opened their storefront, and found nothing there.

I see this complaint about three times a week. The reasons are rarely what the merchant suspects. After a few hundred of these audits, the order I check things in has changed. Search & Discovery is now the last thing I open, not the first.

The order I check things, and why I changed it

For about two years I used to start with the app. Open Search & Discovery, look at the configured filters, verify the metafields, sigh, try again. Most of the time the app was fine. The problem was somewhere else entirely.

Now I check in this order, and it resolves six out of ten of these cases in under five minutes:

1. The per-template "Enable filtering" toggle in the Theme Editor.
2. The collection size.
3. The browser the merchant was using when they configured the app.
4. Whether anyone has touched main-collection-product-grid.liquid.
5. The metafield types in the filter sources.
6. Tag filters vs. metafield filters.
7. The pricing source (B2B catalog, multi-currency markets, dynamic pricing).

The first one alone catches more cases than I can keep count of. It lives at Online Store > Themes > Customize > [your collection template] > Product grid section > "Filtering and Sorting" > Enable filtering. It is per-template. If a store has a custom "Summer" collection template, that template can have the toggle off even when the default is on. A Shopify Staff member named Erin first pointed me at it in a 2023 Community thread reply. I still think about how rarely it shows up in YouTube setup tutorials.

The 5,000-product cliff almost nobody hears about

Shopify's documentation, as of this spring, says collection pages stop displaying filters once the collection contains more than 5,000 products. No error, no warning, no graceful fallback. The filter container still renders in the DOM. It's just empty.

Merchants who add products gradually cross this threshold without noticing. The conversation usually starts the same way: "Filters worked last quarter. They don't work now. Nothing changed." Something did change. The collection got bigger.

Two things to flag about this cliff. First, the limit has moved. In 2022 it was 1,000 products. By 2024 it was 5,000. There was no announcement either time. So when you read advice online, check the date. Second, there is no native workaround. The two apps the community keeps pointing to are Boost AI Search & Filter and Smart Product Filter & Search. Both work. Both cost real money annually. Both have their own product and result ceilings. If you're getting close to 5,000 and you've never priced those out, do it now, not the morning you ship a catalog expansion.

Tag filters lie about what you selected

This is the one I still find frustrating to explain. A merchant creates a "tags" filter in Search & Discovery, picks the four tags they want to expose, saves, and opens the storefront. The filter renders with twenty tags, including ones from products that are nowhere near this collection.

What's happening is that tag filters are fully dynamic. The selection you made in the app UI is not persisted. Whatever tags exist on any product in that collection get rendered, regardless of what you ticked. When you reopen the configuration to fix it, your earlier selections are gone, because they were never saved.

The fix, every time, is to replace tag filters with metafield-backed filters. Tags share one namespace across the whole store, and any typo or marketing label leaks into your filter UI. Metafields give you a typed, deliberate attribute per product. A color_family metafield reads "Blue" in the filter while the product page reads "Midnight Cobalt." That separation is what most merchants actually wanted when they reached for tags.

If your catalog is under ~100 products and you're tempted to start with tags because they're faster to set up, my honest advice is: don't. The migration cost from tags to metafields later is higher than starting with metafields. I've done both. The second one is always smoother.

Six metafield types that quietly never index

When I do open Search & Discovery, the first thing I check is whether the merchant's filter source dropdown is empty for a metafield they're trying to use. Search & Discovery silently excludes a handful of metafield types from its filter sources. The types that work are: single-line text, single-line text (list), product reference (and list), true/false, collection reference, page reference, and metaobject reference.

The types that don't appear, with no error, no UI hint, nothing: number (integer), decimal, weight, volume, dimension, and multi-line text.

The wallpaper merchant who carefully sets up a "Width (mm)" dimension metafield and wants to filter by width gets stuck here. The fix is annoying. You create a parallel single-line text metafield, copy the values across, and use that one as the filter source. The dimension metafield can keep driving display logic. It just can't drive filters. I haven't seen Shopify publicly commit to changing this.

The Safari admin bug that wastes whole afternoons

This is the one I get the most angry-merchant DMs about. The Search & Discovery "select source" dropdown spins forever in Safari and the Shopify iOS app. It never loads. So a merchant configures their filters in Safari, hits save, and saves an empty filter definition. Then they open the storefront, watch the filter come back blank, panic, and reconfigure. They are looping on nothing.

The fix is to switch to Chrome, which is awkward advice to give a Mac-loyal merchant. But this is the one. If a merchant tells me they've "configured filters six times and nothing sticks," the next question I ask is what browser they used. About half the time, that's the whole conversation.

What I tell merchants on dynamic pricing or B2B catalogs

This is where I have to be honest about the limits of what a quick check can do.

If your store overrides displayed prices through a third-party pricing tool or a JavaScript layer, Shopify's filter and sort index still uses the static admin price. That means "sort by price low to high" can produce an order that doesn't match what customers see. There is no documented native workaround as of early 2026. The honest answer is either a custom build, a third-party search app with its own price index (Searchanise and Boost both maintain their own indexes), or accepting the mismatch.

If you're on Shopify's B2B catalog pricing and your price slider reads "£0 to £0," the problem is the same shape: Search & Discovery reads from standard admin pricing, not from your B2B catalog. The Community thread that finally resolved this one ended with "the only fix is custom code rerouting S&D's price source." That's true, and it's the kind of Shopify collection filters problem that genuinely benefits from a second pair of eyes before you ship a fix; if you're sizing that out, the first fifteen minutes with a help1 expert is free and is usually enough to scope whether it's a one-afternoon job or a multi-week project.

For multi-currency markets, the price filter only displays in the shop's default currency. That's a documented limitation. No native fix. Same workaround set.

A note on Horizon

Horizon's collection page does something different from Dawn that I keep tripping over. By default, the hamburger/funnel filter toggle button is hidden on desktop. The theme renders individual filter chips instead. Some merchants prefer this. Some have 15+ filter categories and the chip row turns into visual noise.

There's no theme setting to swap them. The community fix is a small block of Custom CSS that overrides the media query and brings the toggle back on desktop. Class names in Horizon change between theme versions, so this is the kind of override I always note in the audit summary with "re-test after every Horizon update." If you're chasing Horizon-specific weirdness more broadly, I've written about a separate cluster of Horizon bugs that often shows up alongside Shopify collection filters issues on the same store.

What I haven't figured out

A few things I genuinely don't have a clean answer for.

I haven't confirmed whether the 5,000-product limit varies by Shopify plan. Documentation says it doesn't, but I've only seen it in the wild on Basic, Shopify, and Advanced. I have not tested it on Shopify Plus with a fresh catalog over 5,000. If you're on Plus and you've crossed the threshold, I'd genuinely like to hear what you see.

I also don't have a good answer for the Sidekick filter suggestions problem one merchant raised on r/shopify back in March, where Sidekick recommended 14 filters for a small jewelry collection and 13 of them had near-zero search volume. The right filters are partly a product-data problem and partly an SEO problem, and Sidekick only sees the first half. I keep meaning to write a checklist for cross-checking filter suggestions against actual search demand. I haven't.

Most of the work in keeping Shopify collection filters healthy is noticing they broke at all. The store keeps loading, the products keep showing, and the absent filter sidebar is invisible to the merchant until a customer goes looking for it.