Shopify product filters: the free app most stores skip

Shopify ships a free first-party app that adds product filters, better search and recommendations, and most stores never install it. It is called Search & Discovery, it is made by Shopify, it costs nothing, and it does the job that a large share of merchants are paying a third-party filter app between $15 and $50 a month to do. If your collection pages have no filters and your catalogue is past a few dozen products, the first thing to do is not to shop for an app. It is to check whether the free one is already sitting uninstalled in your admin.

This walks through what the native app actually covers, the specific points where it stops being enough, and how to tell which of those two situations you are in before spending anything.

Why filters matter more as the catalogue grows

Filtering is one of the few features whose value scales sharply with catalogue size, which is why advice about it is so inconsistent. On a store with 12 products, filters are clutter, because a visitor can see everything by scrolling and any filter bar just adds a decision before the products appear. Somewhere past roughly 50 products the maths inverts. A visitor who wants a black one in a large is now scrolling through dozens of items that fail one of those two tests, and each screen of irrelevant products is another chance to leave. Past a few hundred products, a collection page without filters is functionally a wall, and the shopper’s only realistic route to the thing they want is the search box, which then carries a load it was never configured for.

The practical read is that filters are not a conversion tactic in the way a trust badge or a countdown is. They are navigation. The gain does not come from persuading anyone, it comes from removing the work of finding, and it shows up most on the stores where finding is hardest. That is also why the effect is easy to miss on a small store and hard to miss on a large one.

What Search & Discovery does for free

The native app covers more than most merchants expect, which is exactly why it is worth checking before shopping.

Two rows there decide most cases. Metafield filtering is the one merchants assume requires a paid app and does not, which matters because metafields are how you store the attributes that are specific to your catalogue rather than to Shopify’s schema, such as fabric weight, roast level or skin type. And search term redirects are the quiet win: they let you send a search for a misspelled or discontinued term straight to the right collection, which turns a dead-end into a landing.

Where the free app actually stops

Three limits are real and worth knowing before you commit to it, and none of them is the one merchants usually worry about. The common fear is that a free first-party tool must be a stripped-down version of the paid ones, holding back capability to push you toward a Shopify plan upgrade. That is not the shape of it here. The filtering logic itself is close to complete: options, price, availability, type, vendor and metafields all work, which covers the overwhelming majority of catalogues under a few thousand SKUs. Where it falls short is at the edges rather than the centre, and the edges are specific enough that you can usually tell within 10 minutes whether any of them apply to you. Check them in this order, because they get progressively less common: presentation, then scale, then merchandising depth.

The first is presentation. Search & Discovery exposes the filters, but how they look and behave is your theme’s job, so if the default rendering is a plain sidebar list and you wanted a horizontal bar with swatches, that is theme work rather than an app setting. This is a genuine cost, and it is also the point where the decision usually gets made for the wrong reason: merchants install a paid app to get the appearance, and inherit a subscription plus another script bundle on every collection page in order to avoid a one-off theme job. The rent versus build test applies exactly here, and filtering styling sits firmly on the build side because it is display rather than ongoing service.

The second is scale. On very large catalogues, filter performance depends on how the theme queries and renders results, and stores in the thousands of SKUs can hit noticeable delays. Paid apps that maintain their own search index exist mostly for this case, and on a catalogue that size the fee is straightforwardly worth it.

The third is merchandising depth. If you need to pin specific products to the top of specific filtered views, run rules by margin or stock age, or personalise the ordering per visitor, that is merchandising rather than filtering and the native app does not do it. Worth being honest about how rare this genuinely is: most stores asking for it are describing a wish rather than a constraint, and the underlying problem is usually that the default ordering is arbitrary rather than that it needs to be personalised. Setting a deliberate sort order per collection solves more of this than any rules engine, and costs nothing.

The setup that actually helps shoppers

Turning it on is not the same as configuring it well, and the default state helps less than people expect. Start by deciding which filters your catalogue genuinely needs rather than exposing everything available: a filter set of 4 or 5 options that matter beats a wall of 12 that mostly return the same products. Every filter that never gets used is a decision imposed on every visitor for nothing. Then check the filters on a phone, because filter interfaces are where mobile layouts most often break, and mobile is now over 70% of ecommerce traffic. A sidebar that works on desktop and collapses into an unusable stack on a phone has made the majority experience worse, which is the same pattern we measured on product pages in the mobile PDP audit.

Then use the search data. Search & Discovery reports what visitors typed, and that list is the cheapest customer research available: terms with no results tell you what you are not stocking or not naming correctly, and high-volume terms tell you what deserves its own collection. Set synonyms for the words your customers use but your product titles do not, and set redirects for terms that should land somewhere specific.

How this fits the wider app decision

The filter question is a good test case for the whole app stack, because it has the shape that catches merchants out most often. There is a free native option, a paid alternative that is genuinely better in a narrow set of cases, and a presentation gap in the middle that tempts people to buy a subscription in order to avoid a one-off build. On an average store reaching us there are around 15 apps installed, and more than 60% of the stores we audit have performance problems serious enough to cost sales, with app scripts a regular contributor. Adding a filter app to a collection page that the free tool already handles is a straightforward way to make both numbers worse.

The rule that holds across the stack is the same one that applies here: rent the ongoing service, own the display. Filtering logic is a service Shopify already provides free through Search & Discovery; how the filters look is display, and display belongs in the theme, which is the argument set out in what custom sections cost and delivered by our custom sections and dev work.

FAQ

Does Shopify have free product filters?

Yes. Search & Discovery is a free first-party Shopify app adding filters, search synonyms, redirects and recommendations. Most stores never install it and pay a third-party app instead.

When do I need a paid filter app?

Catalogues in the thousands of SKUs where performance suffers, or merchandising needs such as pinning products, rules by stock age, or personalised ordering. Those are beyond native filtering.

How many filters should a collection have?

4 or 5 that genuinely narrow the catalogue. Every filter nobody uses is a decision imposed on every visitor, and long filter lists perform worst on phones.

Can I filter by metafield?

Yes, natively. This is the capability merchants most often assume needs a paid app, and it is how you filter on attributes specific to your catalogue.

Do filters slow down a collection page?

The native app adds little weight because the filtering happens server-side. A third-party app adds its own script bundle to every collection page, which is a real cost on a store already carrying 15 apps.

What is the fastest filter win?

Reading the zero-result search report. It shows the words customers use that your catalogue does not answer, which is free research into both naming and range gaps.

Not sure whether your collection pages need an app or a theme pass? Send us the store and we will tell you honestly which one your catalogue actually needs. Free, no obligation, usually a reply within the hour.