How to organise products when your catalogue starts growing
Build categories, filters and product paths around how customers shop rather than how your stockroom is arranged.
Start with how customers choose
When a catalogue is small, a simple product grid may be enough. As more products arrive, the same grid can become a wall of similar items. Shoppers need a way to understand the range, decide where to begin and narrow the options without learning the structure of the business behind the shop.
Begin by collecting the words and decisions customers already use. Look at internal searches, support questions, product comparisons, sales conversations and the terms used in advertising or search results. A category should help someone answer “Which group should I explore?” rather than reproduce an internal department name.
Separate different shopping intentions. People may browse by product type, use case, audience, size, material, problem or collection. These are not all good top-level categories. Choose the primary path that matches the most important decision and support other ways of finding products with filters, links or curated collections.
Create a category system that can grow
Use a small number of clear top-level categories. Each should have a recognisable purpose, enough products to justify its existence and a name shoppers understand without explanation. If a category contains one product or overlaps heavily with another, it may be a filter, collection or temporary campaign instead.
Keep the levels predictable. A shopper should be able to understand what belongs in a category and what the next click will show. Avoid deep trees that require repeated backtracking. If the range is complex, use a broad category page with helpful subgroups rather than forcing every item into a long chain of folders.
Define rules for borderline products. Write down whether an item belongs by primary use, dominant material, audience or another consistent principle. Clear rules prevent two people from filing similar products differently and make future imports easier.
Use filters for real decisions
Filters work best when they reduce a choice that matters. Size, colour, price, availability, compatibility, capacity and material can be useful when customers actually use them to narrow products. Do not add every field in your product database to the filter panel. Technical data is not automatically shopping guidance.
Use labels that match customer language and order filters by likely importance. Show how many results remain where the system supports it, and make selected filters visible so shoppers understand why the list changed. On mobile, make filtering easy to open, review and clear without losing the current context.
Check combinations that create no results or only one item. Empty filter states should explain what happened and offer a simple way back. If an attribute is rarely used or inconsistently filled in, improve the product data before making it a central navigation feature.
Design useful category and collection pages
A category page should orient shoppers, not just display a title above a grid. Add a short explanation of what belongs there, who the products suit and how to choose among them. Keep the introduction concise and put detailed buying guidance where it supports the decision.
Use collections when products belong together for a reason that does not justify a permanent category. A seasonal range, starter set, gift guide or solution for a particular task can create a useful path. Give the collection a clear purpose and review it when stock, prices or availability change.
Make product cards consistent. Show the information needed for initial comparison, such as product name, price, key option, availability and a useful image. Avoid forcing visitors to open every card to learn the basic difference between items.
Keep search, links and labels aligned
Internal search is a safety net for visitors who know what they want. Make sure common product names, synonyms, spelling variations and useful attributes lead to relevant results. Review searches with no results and decide whether to add products, synonyms, redirects or clearer category links.
Use links to guide between related needs without creating a maze. A category can link to a buying guide, a collection can link to its component products and a product can point to compatible accessories. Each link should answer a likely next question rather than exist only to increase clicks.
Keep URLs, page titles, headings and labels consistent. Remove or redirect old paths when the structure changes, and check that search engines are not indexing endless combinations of filters. Clear naming helps visitors, maintenance and discoverability at the same time.
Review the catalogue as it changes
Assign ownership for category rules, product attributes and navigation changes. When new products are added, decide where they belong before publishing them. When products are removed, check for empty categories, broken links, outdated collections and filters that no longer make sense.
Use analytics and customer feedback to review the structure. Look at category entrances, internal searches, exits, filter use, product views and add-to-basket actions. A popular category with poor progression may need better grouping or explanation. A category nobody visits may have an unclear name or no useful reason to exist.
Test the structure with someone who does not know the catalogue. Ask them to find a product by need, compare two options and return to a broader group. If they need internal knowledge, revise the path. A growing shop stays manageable when its organisation remains understandable to the person buying, not only the person managing stock.
Sources
- Google Merchant Center product data specification · Google Merchant Center product data specification
- Web Accessibility Initiative · W3C
Frequently asked
- How many product categories should an online shop have?
- Use as many as help customers make a real distinction, but keep top-level navigation focused. Categories need enough products and a clear purpose to remain useful.
- Should categories be based on product type or use case?
- Choose the path that matches the strongest customer decision. Support other useful ways of browsing with filters, collections and internal links.
- When should I use a filter instead of a category?
- Use a filter for an attribute that helps narrow products within several groups. Use a category when it represents a meaningful starting point or shopping purpose.
- How do I prevent catalogue navigation from becoming outdated?
- Assign owners, document rules, review product data and check empty categories, links, filters and collections whenever the range changes.
Sjors Hooijen Builds ChatBuild and writes about getting a business online without turning it into a project. Questions about this article? Email hi@chatbuild.com.