Plan product categories before choosing menus, URLs, or a platform theme. The category map should reflect how a buyer looks for an item and how the team maintains the catalog. A neat design cannot rescue a structure that places the same product under confusing labels or buries an important range several clicks away.
Start with products and buyer tasks
Export a sample of the catalog with SKU, product type, variant attributes, intended audience, and current category. Include ordinary products and awkward exceptions: bundles, gifts, spare parts, seasonal stock, and items that fit more than one occasion. Ask a customer-facing colleague what buyers call each group. Write down the tasks: “find a black evening bag,” “replace a part,” or “compare gifts under a budget.” These tasks are more useful than an internal warehouse label.
Make a first-pass tree with a small number of understandable top-level categories, then add subcategories only when they help a shopper narrow a meaningful choice. Color, size, price, and availability usually work as filters on a category rather than a new permanent branch for every combination. A filter may need its own search landing page later, but that is an SEO decision, not a reason to create hundreds of empty categories during the build.
A worked planning map
This is an illustrative map for an accessories retailer, not the published navigation of a Megvi client:
| Buyer task | Primary category | Useful filters | Page to test |
|---|---|---|---|
| Choose a daily carry bag | Bags → Everyday bags | Size, material, color | Everyday bags category |
| Find a gift | Gifts → Accessories | Recipient, budget, occasion | Gift collection with an explicit purpose |
| Find a specific style | Shoes → Trainers | Size, color, stock | Trainers category, then product |
For each row, ask whether a first-time visitor would recognize the label and reach a suitable product in two or three sensible decisions. A product can appear in a curated collection and a primary category without needing duplicate product URLs. Record a preferred product URL and keep internal links consistent.
Test the structure with real constraints
Give three people who did not design the menu a short task list. Ask them to find a specified item on a phone, explain why they chose a category, and say what they expected on the landing page. Note wrong turns, empty results, and filter combinations that hide stock. Change labels or grouping when the same confusion repeats. Keep the tested task and result as launch evidence.
Megvi’s public Fyonka case documents a migration involving 6,000 variations across 1,500 SKUs, plus staff training. Those figures show why catalog structure and maintenance matter; this article’s category map is illustrative and does not claim to be Fyonka’s actual taxonomy.
Turn the map into a build specification
- List every planned category, owner, purpose, and example products.
- Mark which filters come from structured variant attributes rather than free-text labels.
- Specify the canonical product URL, navigation links, breadcrumbs, and sitemap inclusion.
- Check mobile menus and internal search against the task list before importing all products.
- Assign a person to maintain categories after launch and define how a new product type is proposed.
Google’s ecommerce site-structure guidance explains why crawlable navigation and links between categories and products matter. Once the site is live, the separate category-page SEO checklist helps improve each destination rather than redesigning the whole tree. For a full project scope, use the store launch checklist and discuss an ecommerce website build with Megvi.
Elneil
https://megvidigital.comAhmed Elneel is a certified digital marketer and entrepreneur with over 5 years of experience helping brands grow through Search Engine Optimization (SEO), paid advertising, and CRM automation.