How to build your product category structure

Your product category structure — what Shopify calls collections, what WooCommerce calls categories — is the navigation backbone of your shop. It decides which products show up on which page, what your menu looks like, and which keywords you can rank for. It's also the place where most resellers make their first structural mistake: they copy how their supplier organises the catalog instead of building around how their customers actually shop.

What collections actually do

A collection is three things at once: a navigation node (what shows up in your menu), a landing page (with its own URL, H1, intro text, and SEO weight), and a filter bucket (every product in that collection appears on its page). Get the structure right and a single decision pays off in three places. Get it wrong and you have menu items that lead to thin pages, products that don't surface for the keywords you want, and customers who can't find what they're looking for.

This means a collection should only exist when it earns its keep on all three fronts. A "Plants under €20" collection that has 4 products is a dead end — thin page, weak SEO signal, looks like an empty shop. A "Pet-friendly plants" collection with 35 products and a clear customer question behind it does work — strong landing page, real search demand, navigation that matters.

The best-practice basis set for a plant shop

If you're starting from scratch, this is the structural minimum that covers most plant resellers in NL/BE/DE:

• Houseplants — your year-round backbone. Most resellers' biggest collection by SKU count.

• Outdoor plants — garden plants, terrace plants, balcony plants. Heavily seasonal but huge during peak windows.

• Artificial plants — separate audience, separate intent. Don't bury them inside Houseplants.

• Gifts — same products, different framing. A Calathea is a houseplant; the same Calathea in a gift wrap with a card is a gift product.

• Value bundles — multi-buys, starter sets, plant-and-pot combos. Drives AOV.

• Sale / Discount — always rightmost in the menu, often a different colour. Customers actively look for it.

Six top-level collections. That's the floor. Most plant shops shouldn't need more than 7 in their main menu — anything beyond that and you're forcing the customer to choose from a list rather than scan a navigation.

Optional extensions, depending on your niche

Once the base is in place, you can add depth — but only where you have real volume and a real customer question. A few that work for plant shops:

• Per plant species: Monstera, Calathea, Philodendron, Ficus. Works if you stock 10+ varieties of one species and you're seeing search demand on the species name.

• Terrariums: a self-contained niche with its own buyer profile. Becomes a category once you carry the plants, the glass, and the substrate.

• Border packages: pre-composed garden borders. Strong category for outdoor-focused shops, especially in spring.

• Themed: Pet-friendly, Low-light, Air-purifying, Easy-care. These tend to be your highest-converting category pages because they answer a specific question the customer is already asking.

When does something become a category vs. a filter?

This is the question that resellers consistently get wrong. The rule of thumb:

• It's a category when (a) you have 25+ products that fit, (b) there's a distinct customer question driving the search, and (c) the page would have value as a standalone landing page (you can write a useful intro, you can rank for it, you'd link it from a blog post or campaign).

• It's a filter when it modifies a search within an existing category. "Pot size 12cm" is a filter — it's not a destination, it's a refinement. "Pet-friendly" can be either: a filter on Houseplants, and (if you have 25+ products) also its own collection.

Practical example: Monstera in your shop. If you stock 6 Monstera variants, "Monstera" is a search query and a filter inside Houseplants. It's not a category yet. If you stock 22 Monstera products across 5 species (deliciosa, adansonii, obliqua, dubia, standleyana) in 4 sizes, "Monstera" earns its own collection page — there's enough depth, there's a clear customer question ("I want a Monstera, show me what you have"), and a "Buy a Monstera" landing page has real SEO and ad-campaign value.

One product, multiple collections

A product is not married to a single collection. The same Calathea Orbifolia can live in:

• Houseplants (because it is one)

• Pet-friendly (because cats won't get sick from it)

• Low-light (because it tolerates north-facing rooms)

• Gifts (when you wrap it for Mother's Day)

• Calathea (if you have a species-level collection)

This is a feature, not a problem. Each collection is a different doorway into the same product. The customer searching "low-light plants for the bathroom" and the customer searching "pet-safe houseplants" are both legitimately looking for that Calathea — give them both a path.

Why Everspring deliberately does not push a category structure

This trips up new resellers, so it's worth saying explicitly: the Everspring integration syncs products, prices, stock, and content — but not categories. We could push a default taxonomy. We don't, because every reseller is different.

One example: the same Phalaenopsis orchid sits in Mother's Day in one reseller's shop, in Valentine's Day in another, in Sympathy & Funeral in a third, and in Office plants in a fourth. All four are correct for their audience. If we'd forced a structure, three of them would be wrong every time. The taxonomy is yours because the customer is yours.

The corollary: we also won't tell you what your top-level collections should be. The basis set above is a starting point. The themed collections, the bundles, the seasonal pages — those reflect your brand and your market.

Don't clone supplier categories

It's tempting, especially when you're standing up a new shop, to mirror the structure your supplier uses. Don't. Suppliers categorise around production logic — by grower, by container shipment, by botanical family, by code. Customers categorise around use cases — by room, by light, by gift moment, by care level. Those two structures rarely overlap, and the supplier's structure will leave you with menu items like "Tropical foliage — type B" that nobody searches for.

Dynamic collections (Shopify automated, WooCommerce categories with rules)

Shopify's automated collections (and similar in WooCommerce) let you fill a collection by rule rather than by hand. A product matches the collection if it meets a condition — a tag, a spec, a price range. Strong use cases for plant shops:

• Under €25 — populated automatically by price.

• Pet-friendly — populated automatically by a "pet-safe: yes" product tag or specification field.

• Currently flowering — populated by a tag you maintain seasonally.

• New arrivals — populated by date added.

• On sale — populated by discount price > 0.

The trade-off: a dynamic collection is only as clean as your underlying product data. If your "pet-safe" tag is missing on 20% of pet-safe products, the collection is wrong. See how to set up filters and product attributes for the data discipline this depends on.

Examples worth studying

Look at a few plant shops that have figured this out. Without naming specific competitors: scan three or four of the larger plant retailers in NL/BE/DE and notice the patterns. Most converge on 6–8 top-level collections, with themed sub-collections (Pet-friendly, Low-light, Easy-care) that consistently outperform raw species-based navigation. The shops that don't convert tend to either flood the menu (15+ items) or under-build (3 items: Indoor / Outdoor / Sale).

Categories rotate with the seasons

Your category structure is not static. Christmas trees belongs in the menu in November and December — and is depublished in January. Spring bulbs appears in February. Mother's Day gifts goes live four weeks before the second Sunday of May. The structural decisions in this article are about the year-round backbone; the rotating layer sits on top. Read Seasonality: rotating your plant assortment year-round for how to phase seasonal collections in and out without leaving stale menu items behind.

The 10-second navigation test

Before you ship a category structure, run this test: pull a friend or family member who isn't a customer of your shop, sit them in front of your homepage, and ask them to name 5 products they'd be able to find from your menu, in 10 seconds. If they can't, your menu is unclear. If they name 5 broad things ("plants", "garden plants", "gifts") but not specific ones, your menu is too top-level. The fix is usually a sub-category or two.

What to do tomorrow

Open your shop, list every collection you have, and mark each one as Keep, Cut, or Merge. Anything below 25 products with no clear customer question goes in Cut or becomes a filter. Anything in your menu that you wouldn't write a 200-word intro for goes in Cut. Then check the basis set above and add what's missing. After that, read the next three articles in this checklist — menu structure, mega menu, and filters and attributes — because the category structure decisions you just made cascade into all three.