A catalog of 20 products can be reduced to a nice grid of cards without thinking about structure at all — at that volume, almost any approach works. A catalog of 300-500 items is a different animal: if the structure isn't thought through in advance, by the third month of use it turns into a mess that neither customers nor the business owner can make sense of. Let's break down where large catalogs most often break and what to do to avoid the same mistakes.

1. Categories are made up by eye, not from what the user searches for. A common mistake is building the category structure the way products are stored in the warehouse, rather than the way a customer looks for them. The result is a hierarchy that makes sense to a warehouse manager but leaves an ordinary visitor lost after the second click. A working structure is built the other way around: first look at how people actually phrase their queries, and only then sort products into that logic.

2. Filters get added one at a time, with no system. Someone asks for a color filter — it gets added. A month later someone asks for a brand filter — that gets added too. Two months after that — size, material, availability. Each decision is reasonable on its own, but together they turn into a panel of fifteen unrelated filters, some of which don't work correctly together. At this catalog size, filters need to be designed upfront as a single attribute system, not stitched on one by one as requests come in.

3. Products have no consistent card standard. Some listings are uploaded with a photo and a full description, others just with a name and price, because «we'll add the photo later». To a customer, this looks like an unserious store, even if the products themselves are excellent. A catalog with hundreds of items needs a mandatory minimum set of card fields — without it, part of the listings stay half-finished for months.

4. Site search only works on exact product names. If someone types «nike sneakers size 42» instead of the exact model name and search returns nothing, they simply leave. On a large catalog, search has to forgive typos, synonyms, and truncated queries — otherwise a significant share of on-site traffic is wasted for nothing, even though the product they wanted is physically in the database.

5. Catalog updates are manual work with no integration. When prices and stock levels are edited by hand in the admin panel for each of hundreds of products, pricing errors and «stale» outdated listings are a matter of time, not chance. At this volume it makes sense to set up an export straight from 1C, Excel, or an accounting system from the start, rather than keeping an employee who syncs the numbers manually.

The overall takeaway from these five points is one and the same: a catalog with hundreds of products can't be built as a scaled-up version of a catalog with twenty — the rules are different here, and some of the decisions that worked perfectly well at a small scale are the first to break at a large one.

If your catalog is already growing and you feel it's heading toward chaos — tell us about it through the «Discuss a Task» form, we'll take a look at your structure and show you what's worth rebuilding first.

« Back to blog