Let buyers narrow the catalogue without losing their place.
A filterable catalogue helps visitors select products with comparable properties. ImbaHub can implement focused filters, sorting and clear reset controls using approved product data. We also plan how choices affect URLs and crawler access. Every possible combination does not automatically become a landing page.
- Facts
Approved properties describe products.
- Choices
Filters narrow and sorting orders.
- State
Selections, URL and return navigation share a model.
Useful filters need accurate data and a clear way back.
A buyer selects material and then changes sorting. Should the selection disappear?
Not if sorting only changes order. Test filtering and sorting as separate state changes.
Choose filters that distinguish useful alternatives
Start with buyer decisions and fields with reliable values. Materials, dimensions and formats need definitions and units. An internal label should not become a filter simply because it exists in the export.
Fictional example: a storage-box catalogue offers size and material. Test a limited family and representative combinations before adding more attributes. The tool narrows a list; it does not certify suitability for every application.
Decide how choices combine and reset
Define whether multiple values within a group mean either/or and how groups combine. The same interface should not mean different things across categories without explanation. Show active selections, result count and clear routes to remove one choice or reset everything.
Sorting changes order, while filtering changes the collection. When buyers open a product and return, the catalogue should follow the agreed state model. A bookmarked address must not silently display a different selection.
| Element | Decision before development | Acceptance exercise |
|---|---|---|
| Attributes | Which values are reliable? | Filters select the correct records |
| Combination | How do groups and values interact? | Reference selections match expected outcomes |
| Reset | What can the buyer change? | Remove one selection or all selections |
| State | What do shared URLs and Back preserve? | The intended selection returns |
| Indexing | Which addresses should crawlers reach? | The agreed URL policy is implemented |
Plan URLs before combinations multiply
Filters can generate many addresses with similar or empty selections. Separate a visitor's shareable state from deliberately approved landing pages with their own purpose. Categories, filters, sorting and pagination need documented roles.
Choose technical signals around actual content and intent. Canonical is not a substitute for deciding which combinations should be crawlable. A selection intended as a search destination needs relevance, stable content and useful internal links, rather than an automatically changed title.
Deliver a mobile catalogue workflow with checks
An initial delivery can cover one category, a few attributes, sorting, reset and a URL model. Pricing, stock, ordering and compatibility selection are separate capabilities. Imported catalogue data needs its own update procedure.
Test mobile, keyboard operation, empty selections, Back navigation and reference sets. Handover documents fields, filter logic and URL policy. We propose scope and price after examining the catalogue and buyer tasks.
Continue with the related task
Sources and further reading
Questions, answered
Should every filter combination be indexed?
No. Decide which destinations serve their own task and which simply represent a visitor's temporary selection.
Is a filterable catalogue an online shop?
Not automatically. Ordering, payment, prices and stock need separate working workflows.