Ecommerce / Product taxonomy
How to Plan Product Taxonomy for an Ecommerce Website
Product taxonomy is the shared language behind categories, filters, search, recommendations, feeds, and reporting. Fixing it after design and migration is slower than defining it before templates are built.
Start with how customers choose products
Collect search queries, filter use, sales and support questions, return reasons, merchandising knowledge, supplier data, and customer language. Identify the attributes that change suitability: product type, use, compatibility, material, size, fit, capacity, style, or another domain-specific factor.
Separate the permanent classification of a product from temporary merchandising. “New,” “gift ideas,” or a seasonal campaign may be a collection, not a product type. Keeping these concepts distinct makes navigation and reporting more stable when promotions change.
Define categories, attributes, values, and relationships
Create a category hierarchy broad enough to browse but specific enough to set expectations. Define product attributes with consistent names, units, allowed values, and formats. Record which fields drive variants, filters, comparison, search synonyms, delivery rules, or structured data.
Decide how bundles, accessories, replacement parts, compatible products, and multi-category items relate to the core catalogue. Use stable internal identifiers even if customer-facing labels change. The product variants guide helps distinguish a selectable variant from a separate product.
Test the model with real and difficult products
Classify a representative sample before designing final navigation. Include bestsellers, long-tail products, incomplete supplier records, unusual variants, discontinued items, preorders, bundles, and products that could fit several categories. Note where people disagree; those conflicts reveal missing definitions.
Prototype browse, search, filters, comparison, product pages, recommendations, and feeds using the sample data. Check that filters are meaningful within each category and that zero-result combinations are handled. A taxonomy is only useful if the interface and operating team can apply it consistently.
Create ownership for catalogue change
Document definitions, examples, required fields, validation rules, and the process for adding a category or attribute. Assign owners across merchandising, product data, ecommerce, search, SEO, and integrations. Suppliers can provide inputs, but the retailer should control the customer-facing model.
Monitor internal search, filter use, zero-result pages, returns, support questions, and uncategorised products after launch. Review the model when the range or customer behaviour changes, but avoid adding a new category for every campaign. Good taxonomy evolves through governed evidence rather than accumulating labels.
Give the catalogue one shared language
Planning a store with complex product data?
Northform can connect catalogue structure, product templates, navigation, filters, and integrations in a coherent ecommerce experience.
Discuss your ecommerce website Explore ecommerce website design →