Tag: Faceted Navigation

Q: What are product attributes in ecommerce?

Product attributes are the specific properties that describe a product within its category — Colour, Size, Material, Brand, Weight, Dimensions, and any category-specific properties like Waterproof Rating for outdoor clothing or Processor Speed for laptops. Attributes are the building blocks of product filters, search matching, and channel feed data.

Product Attributes in Ecommerce: How to Create Filters That Help Customers Buy

Product attributes are the structured properties that describe what a product is and how it differs from other products — Colour, Size, Material, Brand, Processor Speed, Number of Seats, Waterproof Rating. They are the data layer that powers your site filters, your search matching, your channel feeds, and your product comparison functionality. Get them right and customers find what they need. Get them wrong and filters return empty results, searches miss matching products, and Google Shopping underperforms.

Types of Product Attributes

Universal attributes

Attributes that apply to virtually every product regardless of category: Brand, Price, Colour, Material, Weight, Dimensions. These are the foundation of most filter systems and are required for channel feeds like Google Shopping.

Category-specific attributes

Attributes that only apply within a specific category or subcategory. Size and Size System for apparel and footwear. Processor and RAM for laptops. Number of Seats and Configuration for sofas. IP Rating and Fitting Type for lighting. These are defined in your taxonomy’s attribute set for each subcategory — they do not appear in the filter panel for irrelevant categories.

Technical specification attributes

Precise technical values with units: Screen Size (inches), Storage Capacity (GB), Battery Life (hours), Waterproof Rating (IP rating), Thread Standard (M6, M8), Tensile Strength (MPa). These are the primary purchase decision attributes for high-consideration products like electronics and industrial components. See the Electronics Taxonomy guide for the full attribute sets required per subcategory.

Compliance and certification attributes

Required for regulated products: CE Marking, ATEX certification, RoHS compliance, allergen declarations for food, organic certification for food and textiles. These are not typically filterable but are mandatory product data in the relevant categories.

Required vs Optional Attributes — The Practical Distinction

The traditional distinction between required and optional attributes needs a practical reframe for ecommerce. The question is not “can we publish this product without this attribute?” — technically many attributes are not hard-blocked. The question is “does missing this attribute cost us customers?”

Attribute	Formal Status	Practical Impact If Missing
Colour (fashion)	Required for Google Shopping variants	Product invisible in colour filters, wrong image may show
Size (fashion)	Required for Google Shopping variants	Product invisible in size filters
Occasion (fashion)	Optional	Product invisible in “Occasion = Formal” filter searches — often high-intent
Battery Life (laptops)	Optional	Invisible to buyers filtering by battery life — significant buyer segment
Number of Seats (sofas)	Optional	Invisible in “3-seater” filter searches — primary buyer decision point

Any attribute that drives significant filter usage should be treated as effectively required, regardless of its formal status. Run your site search and filter analytics to identify which attributes buyers filter by most — those are your de facto required attributes.

Controlled Vocabularies — The Foundation of Working Filters

A controlled vocabulary is a defined list of acceptable values for an attribute. Without controlled vocabularies, teams enter attribute values manually and inconsistency accumulates — “Navy”, “Dark Navy”, “Midnight Blue”, “Storm Blue”, “Deep Blue” all represent the same colour but appear as separate filter options.

Define a controlled vocabulary for every filterable attribute before any product data is entered. For colour: 10–15 normalised values (Blue, Red, Green, Black, White, Grey, Yellow, Pink, Purple, Brown, Orange, Beige, Multi). For size: the exact size labels used on your products (XS, S, M, L, XL, XXL). For material: the primary material categories relevant to your catalog (Cotton, Polyester, Nylon, Leather, Wool, Linen, Silk).

Attribute Completeness — The Filter Coverage Problem

An attribute that is missing from 30% of your products means a filter on that attribute returns 30% fewer results than it should. A buyer filtering for “navy” gets an incomplete result set — products that exist in navy but are missing the colour attribute are hidden.

Target completeness thresholds by attribute priority:

Required attributes: 100% target. Any product below 100% is incomplete and should not be published until fixed.
High-impact filter attributes: 95%+ target. Attributes that drive significant filter usage should be as close to complete as possible.
Recommended attributes: 80%+ target. Aim for high coverage but acknowledge that some edge-case products may not have applicable values.

Run regular completeness audits using the Completeness Checker to monitor which attributes are falling below target thresholds as your catalog grows.

Attribute Design Mistakes That Kill Conversion

Free-text attributes for filterable properties — a free-text Colour field cannot be used as a filter reliably. Filterable attributes must use controlled value lists.
Too many attributes per category — if a category has 30+ attributes, data entry completeness drops because teams skip fields. Keep required attributes to 8–12 per subcategory.
Global attributes applied to irrelevant categories — a “Number of Seats” attribute on all home goods products adds noise to furniture and lighting simultaneously. Category-specific attributes belong in category-specific attribute sets.
Attributes without unit standards — storing weight as “2kg”, “2 kg”, “2.0 KG”, and “2000g” in the same field breaks sorting and filtering by weight. Define units per attribute and enforce them.
Marketing names as attribute values — “Dusty Rose” as a colour value is correct for product copy but wrong for a filter attribute. Store marketing names separately; use normalised values for filterable attributes.

The LynkPIM Product Data Modeling feature enforces controlled vocabularies, required attribute validation, and completeness tracking at the category level — preventing attribute quality degradation as catalogs scale. Start free at lynkpim.app/pricing. Also see Faceted Navigation and Product Taxonomy for how attributes connect directly to your filter system.

Frequently Asked Questions

What are product attributes in ecommerce?

Product attributes are the structured properties that describe what a product is and how it differs from others — Colour, Size, Material, Brand, Processor Speed, Number of Seats, Waterproof Rating. They power site filters, search matching, channel feeds, and product comparison functionality. Without structured, consistent attribute data, none of these functions work reliably.

What is the difference between required and optional product attributes?

Required attributes are those without which a product cannot be correctly sold or displayed. Optional attributes improve discoverability and filtering. In practice, any attribute that drives significant filter usage should be treated as effectively required — missing it hides products from buyers who use that filter, regardless of its formal classification.

Why should product attribute values use controlled vocabularies?

Controlled vocabularies prevent inconsistent values that break filters and search. Without them, you end up with Navy, Dark Navy, Midnight Navy, Storm Blue, and Ocean Blue as separate filter options instead of a single Blue. Controlled vocabularies ensure every product with a blue attribute uses exactly the same value — making filters accurate and site search effective.

How many attributes should each product category have?

Most subcategories need 5–8 required attributes and 5–10 recommended attributes. More than 15–20 required attributes creates data entry burden that reduces completeness — teams start skipping fields. The right number depends on the product type and the filtering decisions buyers make in that category. Start with the attributes that drive filter usage and add more based on analytics.

May 7, 2026

Faceted Navigation: How Product Taxonomy Powers Your Filter System

Faceted navigation is the filter sidebar on your category pages. It is one of the highest-impact conversion tools in ecommerce — when it works. When it does not work, customers face unusable filter options, incomplete results, and irrelevant products. The difference between a working and a broken faceted navigation system almost always comes down to the quality of the product taxonomy underneath it.

What Is Faceted Navigation?

Faceted navigation is a multi-dimensional filtering system that allows customers to narrow a product set by applying multiple attribute filters simultaneously. Each filter dimension — colour, size, brand, material, price range — is a “facet”.

When a customer lands on a “Women’s Running Shoes” category page and uses the filters to select: Size = 8, Colour = Black, Brand = Asics — faceted navigation returns only the products matching all three criteria simultaneously. This is fundamentally different from traditional category browsing where customers can only drill down one level at a time.

Faceted navigation significantly increases the probability that a customer with specific requirements finds what they are looking for — which directly increases conversion rate on category pages. But it only works if the attribute data powering the filters is structured, consistent, and complete.

The Taxonomy-Navigation Connection

The filter options available on any category page come directly from the attribute values assigned to products in that category. Your product taxonomy determines:

Which attributes exist as filters — only attributes defined in your taxonomy attribute set for that subcategory can become filters
Which values appear in each filter — only the distinct values present in your product data for that attribute appear as filter options
How many products each filter returns — if 30% of products are missing an attribute, filtering by that attribute returns an incomplete set

This means a product taxonomy decision — what attributes to assign to a subcategory, what values to allow for each attribute — directly determines what filters customers see and how useful those filters are. For the foundation on building taxonomy correctly, see What Is Product Taxonomy and How to Build a Product Taxonomy From Scratch.

Why Flat Taxonomy Breaks Faceted Navigation

A flat taxonomy — one level of categories with no subcategories — forces all products in a top-level category to share the same filter set. In a home goods store with a flat structure, the “Furniture” category contains sofas, dining tables, bed frames, and desk lamps. The filter panel must serve all of them simultaneously.

The result: a filter panel that includes Number of Seats (relevant to sofas only), Bed Size (relevant to beds only), Bulb Type (relevant to lamps only), and Seating Capacity (relevant to dining tables only) — all visible at once, none relevant to all products. Customers see a confusing, cluttered filter panel and abandon filtering entirely.

Hierarchical taxonomy solves this by enabling category-specific filter sets. Sofas get their own filter panel with Number of Seats, Configuration, and Fabric. Lighting gets its own panel with Fitting Type, Dimmable, and IP Rating. Each subcategory shows only the filters relevant to it. The Flat vs Hierarchical Taxonomy guide covers when each approach is appropriate.

The 4 Attribute Rules for Effective Faceted Navigation

Rule 1: Normalise attribute values

Every attribute that becomes a filter must use controlled, consistent values. Colour cannot have 40 variations of blue — it must have one “Blue” value (plus specific shades as a secondary attribute if needed). Size cannot have “S”, “Small”, “SM”, “size S”, and “SMALL” — it must have one normalised “S” value. Unnormalised values create filter option lists that customers cannot navigate.

Rule 2: Ensure completeness for filter attributes

A filter attribute that is missing from 40% of products returns a result set that excludes 40% of matching products. If a customer filters by Colour = Blue and 40% of your blue products are missing the colour attribute, the filter is hiding products the customer would buy. Run completeness checks on every filter attribute — any attribute below 90% coverage is undermining your conversion rate.

Rule 3: Define filter attributes per subcategory, not globally

Different subcategories need different filters. Do not apply a global attribute set across all categories. Define which attributes become filters for each subcategory — this is a taxonomy design decision, not a platform configuration decision. The attribute set in your taxonomy is what drives the filter panel.

Rule 4: Keep facet option counts manageable

5–15 options per filter facet is the usable range for most attributes. A colour filter with 40 options is unusable. A brand filter with 200 options needs a search-within-filter feature. Use controlled attribute value lists to prevent facet option counts from growing beyond the usable range as your catalog expands.

Common Faceted Navigation Failures and Their Taxonomy Root Causes

Symptom	Root Cause	Fix
Filter returns zero results despite products existing	Products missing the filter attribute	Attribute completeness audit + bulk fill
Colour filter has 40+ options	Unnormalised colour values	Colour normalisation — map to controlled value list
Filter returns wrong product types	Products miscategorised in wrong subcategory	Reclassify affected products
Same filter appears on every category regardless of relevance	Flat taxonomy — no subcategory-specific attribute sets	Migrate to hierarchical taxonomy with per-subcategory attribute definitions
Filter option counts are highly inconsistent	Attribute values assigned inconsistently across catalog	Controlled vocabulary enforcement + bulk standardisation

The root cause of most faceted navigation failures is not a platform problem — it is a product data problem. The Completeness Checker identifies which attribute gaps are most significant across your catalog. The PIM Readiness Score gives you a full picture of where your taxonomy and attribute governance has gaps affecting both faceted navigation and channel performance. Also see How Bad Taxonomy Kills Your Site Search for the broader impact beyond filters.

Frequently Asked Questions

What is faceted navigation in ecommerce?

Faceted navigation is a filtering system that allows customers to narrow a product set by applying multiple attribute filters simultaneously — for example, filtering shoes by Size = 8, Colour = Black, Brand = Nike, and Style = Running to show only matching products. Each filter dimension is a “facet” derived from structured product attributes in your taxonomy.

Why does product taxonomy affect faceted navigation?

Because the filters on any category page come directly from the attribute sets assigned to that category in your taxonomy. If your taxonomy assigns different attributes to different products in the same category, or uses inconsistent attribute values, the filter options become incomplete or unusable. The taxonomy is the data layer that faceted navigation is built on.

What is the difference between faceted navigation and site search?

Site search retrieves products matching a keyword query. Faceted navigation filters an existing product set by attribute values. They work together — a customer searches “running shoes” (site search), then uses facets to filter by size and colour (faceted navigation). Both depend on the same underlying product data quality, which means taxonomy problems typically affect both simultaneously.

How many filter options should each facet display?

5–15 options per facet is the usable range. Fewer than 5 suggests the attribute is not differentiated enough to warrant a filter. More than 15–20 options on a single facet is typically unusable — customers cannot scan that many options efficiently. Use controlled attribute value lists and normalisation to keep facet option counts manageable as your catalog grows.

May 3, 2026