A store with 30 products doesn’t need a mega menu. It doesn’t need a three-level category hierarchy. It doesn’t need advanced filtering. What it needs is a clean, obvious path from “I’m interested” to “I found it” — and at 30 products, that path is short.
The temptation for small stores is to build navigation like a big store. Install a mega menu app, create dozens of collections, add a search bar with predictive results. The logic is: “if big stores use mega menus, we should too.” But a mega menu on a small store is like a revolving door on a cottage — technically functional, wildly out of proportion.
What small stores need
Three to five top-level categories. If you sell candles, that might be “Scented,” “Unscented,” and “Gift Sets.” That’s it. Each collection has 10–15 products, which is scannable without filters or subcategories.
A clean collection layout. Show products in a grid with clear photos, prices, and names. At 10–15 products, the shopper can scan the entire collection without scrolling far. No need for filters — the visual scan does the filtering.
Strong product pages. When the catalog is small, the product page does more selling than the navigation. The shopper has fewer alternatives to compare, so each product page needs to convince on its own: good photos, clear descriptions, reviews if available.
A simple tabbar on mobile. Home, Shop, Cart. Three buttons. The “Shop” button opens a simple list of three to five categories. The shopper is two taps from any product in the store.
What to avoid
Empty subcategories. Creating a subcategory with two products makes the store feel underpopulated. If a category has fewer than five products, it doesn’t need to be a separate collection.
Mega menus with sparse content. A mega menu dropdown that’s 90% whitespace because there are only three categories feels awkward. A simple dropdown list or a slide menu is more appropriate.
Complex filtering on small collections. Adding size, color, price, and brand filters to a collection with 12 products creates a filter sidebar that’s longer than the product list. The shopper scans the products faster than they navigate the filters.
Too many menu items. Home, Shop, About Us, Contact, Blog, FAQ, Shipping Policy, Return Policy, Size Guide — that’s nine top-level items for a store with 30 products. The navigation is more complex than the catalog. Move secondary items (policies, FAQ, size guide) to the footer.
When to start adding complexity
The signal that simple navigation isn’t enough anymore:
- Collection pages require scrolling past two screenfuls. If the shopper has to scroll significantly to see all products, the collection is getting too long for simple scanning.
- Shoppers are using search. If analytics show increasing search usage, it means the menu isn’t getting people to the right place — either because there are too many products in each category or because the categories don’t match how shoppers think.
- New products don’t fit existing categories. When you find yourself debating where a new product belongs, the category structure is outgrown.
At that point, add one level of subcategories. But until then, simplicity is a feature.
This article is part of the larger guide on How navigation needs change as your catalog grows from 100 to 1000+ products.