Planning Evolution CMS Catalogs for 10,000–20,000 Products

A catalog with a few hundred items is one thing. A catalog with ten or twenty thousand products is an architectural question. At that size, every assumption about resources, TVs, filtering, imports, and caching becomes more expensive.

The original discussion captured that transition point well: the current site worked for a few hundred products, but the future target required thinking ahead instead of simply scaling the same habits.

What large catalogs need early

• a clear data model for products and attributes,
• disciplined filtering strategy,
• careful use of TVs so they do not become the bottleneck,
• import/update workflows that do not require manual editing,
• real caching and indexing strategy.

At this scale, performance is not just about server power. It is about reducing expensive parsing, minimizing broad queries, and avoiding content models that turn every product page into a special case.

The sooner a project treats a large catalog like an application, not just a page tree, the easier Evolution remains to work with.