WooCommerce product filters, categories and display
Configure WooCommerce product filters from structured attributes and categories, then check results, sorting and a clear route to the selected variant.
- Published
- Last updated
A WooCommerce product filter narrows your catalogue using recorded product facts, such as size or material. Set up consistent attributes first, choose controls that work with your product display, then follow the results through to a purchasable variation.
A jacket can appear under both navy and medium even when its navy-medium variation is unavailable. Your filter setup needs to distinguish a matching product from an available combination.
Prepare the attributes and categories
Use categories for browsing groups, tags for non-hierarchical labels and attributes for comparable product differences. WooCommerce’s taxonomy guide explains these separate roles and the distinction between global and product-specific attributes.
Before selecting a filter, prepare a small catalogue sample in a staging store. You need permission to edit products and the relevant shop template. Keep payment processing in test mode for any basket-to-checkout checks.
- Define a category tree customers recognise, such as Clothing with Jackets beneath it. Assign each sample product to its intended category.
- Create shared attributes for facts customers compare across the range. Use one size convention and one allowed value for each colour. Consolidate “navy”, “Navy blue” and “dark navy” only when they describe the same colour.
- Normalise measurements before adding range controls. Store jacket length in centimetres consistently, with the unit visible to customers. An absent length remains unknown.
- Separate parent-product facts from variation facts. Record which size-colour combinations exist and which have their own stock or price. Confirm that the chosen filter uses those combinations before describing its results as available variations.
For a fictional sample, create Harbour Jacket in navy-medium and navy-large, plus Reed Jacket in navy-medium. Give Harbour a cotton attribute and Reed a wool attribute. Add a black cap in Accessories to expose category-scope errors later.
Incorrect setup: record cotton only in Harbour’s description, then expect an attribute filter to find it. Correct setup: assign the cotton term to the product’s supported attribute field and confirm the filter reads that field.
Choose the filter and display method
Choose the native Product Filters block when its supported filters fit a Product Collection. Consider an extension when your existing display or required query behaviour needs a different method.
The core Product Filters documentation describes attribute and availability controls alongside category and other filters. Its controls filter the relevant collection. Active Filters lets customers remove selections or clear them together.
For a block-theme catalogue, open Appearance > Editor > Design > Templates and select Product Catalog. Add Product Filters near the Product Collection. Choose each attribute and decide whether its control displays counts. Preview the result before editing another template.
Compare methods against the buying task
| Method | Suitable starting point | Checks before adoption |
|---|---|---|
| Core Product Filters | A Product Collection with supported catalogue facts | Correct collection scope, available attribute terms and a usable mobile overlay |
| Product Filters for WooCommerce extension | A compatible archive or documented product shortcode | Theme selectors, selection logic and the documented limits on Blocks |
| A product-table extension | Customers ordering familiar items by code or specification | Required columns, supported variation selection and the route to full product details |
Product Filters for WooCommerce has a separate filter editor under WooCommerce > Filters. Its documentation describes AND/OR selection rules and sorting integration. It states that its filter shortcode doesn’t filter WooCommerce Blocks. Keep that limitation separate from the native block’s capabilities.
For either method, test search with active filters and change the sort order without losing selections. Inspect keyboard focus and readable control labels. Customers need to identify their selection without relying on colour alone and reach reset controls on a phone.
Before buying an extension, compare its supported store versions with your installation and read its maintenance history. Assign someone to repeat the checks after updates. A feature list alone doesn’t establish compatibility with your theme.
A WooCommerce product table suits repeat ordering when customers know the item code and need several rows at once. Keep pack size and other deciding facts visible. A table that hides garment photographs or fit information can make a first purchase harder. Use the same product sample to compare the table with product cards before changing the whole catalogue.
Verify the customer’s result set
Work through the fictional products in the storefront your customers will use, including the category page and its mobile filter controls. Write the expected matching products down before selecting anything.
- Open Jackets with all filters cleared. Expect Harbour and Reed, with the cap excluded. Compare the displayed total with the products across all result pages.
- Select cotton. Expect Harbour only. Remove that selection and confirm both jackets return.
- Select navy and medium. Both jackets have that combination in this sample. Inspect each result and its selected variation. A parent-product match alone doesn’t establish that the combination is purchasable.
- Add cotton to the navy-medium selection. Expect Harbour only. If selecting multiple values within one attribute, test the configured AND/OR rule separately.
- Select wool and large. This sample has no matching variation. Expect an empty result or a disabled impossible choice, according to the method’s documented behaviour. The customer must still be able to remove the selection.
- Clear the filters, apply cotton again and change the sort order. Expect the same matching set. With several matching products, verify their order against the displayed prices or other selected sort value.
- Make Harbour’s navy-medium variation unavailable in staging. Repeat the combination test, then open Harbour. Confirm that the product page prevents purchase of that unavailable variation and explains the remaining choices.
If the filter still lists Harbour because another variation is available, judge that result against the store’s intended product-level behaviour. Don’t label it as proof that navy-medium is in stock. Change the filter method or its promise if customers need variation-level availability.
Check the browser’s back button after opening a product. Confirm selections and category scope remain understandable on return. Open the mobile overlay with a keyboard, change a selection and close it. Focus must remain usable, and the resulting count must describe the updated list.
Keep the results consistent
Give catalogue data and display behaviour separate owners, then repeat the same result checks after a change. Incorrect attributes need a data correction. A control filtering the wrong collection needs a display correction.
Change Harbour’s material in staging and confirm the corresponding result changes after saving. Then change its stock and repeat the availability case. Record any import, search-index or cache step between the edit and the visible result. Use the selected extension’s documented refresh process where it has one.
For Product Filters for WooCommerce, the documentation identifies a Product Filter Cache tool for missing category filters. Diagnose category assignment and display rules before clearing that cache. A cache refresh won’t supply a missing product fact.
Run the same checks against any connected shopping assistance. Ask for the changed material and the unavailable size-colour combination. Compare its result with the saved catalogue record and the product page. If the connection refreshes separately, its owner must account for that delay.
Give the catalogue owner responsibility for attribute values and variation records. The storefront owner maintains filters, sort controls and product links. Repeat the fictional cases after a theme or extension update, and release the setup when the result set and purchase path agree.
Give your store its own shopping agent
Customers ask in their own words. Your agent finds, compares and checks out from your catalogue, right on your site.