Blog / Shopify & e-commerce /

When to revisit product taxonomy after assortment growth

A catalogue grows quietly. A few new product lines arrive, a collection gets added for a campaign, and filters pile up because each one looked useful on its own. Then a shopper can’t find a product, and the team can’t agree which collection belongs in the main navigation.

That’s usually the moment to ask whether the taxonomy still reflects how people browse.

Taxonomy isn’t a naming exercise. It’s the structure that helps shoppers and search engines understand how products relate. Revisit it when the assortment or customer language has changed enough that the old map creates friction. Don’t reorganise just because a spreadsheet got untidy.

Watch for signals of a mismatch

Start with problems you can observe. Are relevant products hard to reach through navigation? Do collections overlap so much that their purpose is unclear? Do filters use inconsistent values, or make shoppers choose between terms that mean the same thing? Do product teams keep creating exceptions because the structure can’t represent the range?

Search data shows how people describe categories, but query volume alone doesn’t decide the hierarchy. Review internal site-search terms, support questions, merchandising logic and the products themselves. With a small range, a deep category tree adds clicks, not clarity. With a broad range, one catch-all collection is just as unhelpful.

Separate the shopper’s model from the team’s model

Internal teams often organise by supplier, department or workflow. Customers start from a problem, a use case, a material or a compatibility need. Both views matter, but the main navigation should make sense to the visitor. Operational categories can live in the admin or reporting layer without becoming customer-facing sections.

Ask people unfamiliar with the catalogue to find a few representative products, give them tasks in ordinary language, and watch where they hesitate. A short, informal exercise reveals confusing labels faster than a debate among people who already know the range. Record the words they use, but don’t treat a handful of observations as a representative study.

Map the current structure before changing it

Export or document the existing collections, URLs, menu links, filters and important landing pages. Note which receive organic visits, external links or internal references. Look for products in multiple collections, empty pages, near-duplicates and categories without a clear purpose. That inventory is your baseline and shows the migration risk.

Then sketch the proposed structure before touching the live store. For each category, write its scope, inclusion rules and audience. If two collections differ only by wording, decide whether to merge them, differentiate them with clearer criteria, or leave them because they serve distinct needs. A taxonomy nobody can explain is hard to maintain.

Design for change

A structure should absorb plausible additions without needing a new level for every edge case. You can’t predict every future product, but you can agree on the principle for where new products go and who approves exceptions. Use product attributes for characteristics that apply across categories, where the platform and theme can support them cleanly.

Be careful with filters that generate crawlable combinations or indexable URLs. A useful shopper filter doesn’t automatically deserve a search landing page. Weigh each indexable combination’s value, unique content and maintenance burden, and keep the page rules explicit so future teams don’t multiply thin URLs.

Migrate deliberately

Renaming a category can change its URL, navigation placement and internal links. Keep URLs where practical. If one must change, map the old destination to the most relevant replacement and verify the redirect. Update menus, breadcrumbs, collection descriptions, internal links and any structured data that depends on the page, and test the journey on mobile as well as desktop.

Stage the changes so they’re easy to review. I’d avoid changing taxonomy, theme, URLs and copy all at once if I can help it. After launch, inspect indexation, crawl patterns, impressions and customer behaviour, and note concurrent changes before drawing conclusions.

Check the impact beyond navigation

Taxonomy changes reach further than the menu. Collection descriptions, breadcrumb paths, structured data, campaign links and merchandising reports may all rely on the old names or URLs. List the dependencies with the people who own those systems. In Shopify, also check how the theme handles collection membership and filters, because the admin doesn’t always show the customer-facing result.

Set a baseline first: representative URLs, search visibility, internal links and a few customer tasks. Verify the same things afterwards. It can’t prove causation, but it makes problems easier to detect and stops every movement being blamed on the restructure.

A review is also a chance to retire categories nobody can explain. Keep the reason and the redirect plan, and make sure the replacement is genuinely useful. Redirecting every old category to a broad parent keeps a response code and confuses the person who expected something specific.

Create a maintenance rule

Write down who can create a collection, what naming convention applies, which filters are allowed and when a page gets retired. Add a review point after meaningful assortment changes instead of waiting for confusion to spread.

If the structure feels strained today, pick one confusing path and test a clearer version with real users before reorganising the whole store. Which part of your catalogue has changed enough to deserve that review?