Which filters does a product catalogue actually need?

Start with a question that excludes unsuitable products

Imagine a designer choosing chairs for an outdoor space. Intended use, stackability and material might help them decide. An internal collection code may mean little to a first-time visitor. Collect the conditions raised in sales conversations, then check whether the corresponding information exists consistently across the catalogue.

Not every attribute needs a filter. A detail shared by only one item might belong on its product page. Missing data can make suitable products disappear from filtered results. Standardise the values before designing the controls: outdoor, garden and exterior should not become three separate options if they describe the same condition in your catalogue.

Describe the selection logic in a sentence

Do two choices from one group broaden or narrow the results? Seeing wood or metal products is different from requiring products that are both suitable outdoors and stackable. Write this behaviour into the design specification. Drawing the selected checkboxes does not establish how the result set should behave.

When a mobile panel closes, show how many conditions remain active. Provide understandable selection labels above the results and a way to remove each one. Clearing all filters should reset those conditions without sending someone to an unrelated homepage. If selecting and applying are separate steps, explain what the apply button will do.

Inspect an example filter decision

Provide a way out of an empty result

When incompatible conditions leave no products, do more than display zero. Keep the active choices visible and offer a way to remove one. Silently changing the conditions can make unsuitable products appear to meet the original request. Present a suggested change as an explicit choice instead.

Explain whether a count refers to the whole catalogue or the current selection. Preserve filters, and where possible the previous position, when someone returns from a product detail. Test empty, single-item and large result sets; the most attractive mockup is not the only state the interface will encounter.

Separate shareable selections from search landing pages

Google explains that combinations of filters can produce many URLs and increase crawling overhead. Decide before launch which combinations genuinely deserve discovery through search. Do not treat every colour and sorting combination as a separate SEO page. Let that scope guide the technical decisions about URLs and crawling.

A shareable selection can help a customer without needing its own indexed search result. Give a stable category page and a temporary filter state distinct responsibilities. Do not assume that one canonical tag automatically resolves every possible URL problem. Record the intended behaviour so content changes do not accidentally expand the crawlable catalogue.

Review delivery with a concrete buying task

Ask someone to find a metal model suitable outdoors and share the selection. Observe which terms make them hesitate. Check that the same conditions still work as the catalogue grows. Our pagination guide separately covers moving through results.

Our Erhan Mobilya project presentation is a real portfolio reference for product-focused work, not a claim that these proposed filters were implemented there. Include data cleanup, selection logic and mobile return behaviour as explicit deliverables in your website design scope.