50k+ SKU 4imprint-scale catalog architecture, how does Magento handle it?
The biggest promo catalog I ship runs ~62,000 branded SKUs across 8,500 product families and holds a 94 Lighthouse mobile.
The model is Magento configurable + simple products with EAV attributes for color, size, decoration zone, MOQ tier, supplier source. The performance gotchas:
- Daily PromoStandards feed ingest from suppliers (SanMar, Alphabroder, S&S Activewear, Vantage, PCNA, Edwards). Catalog pulls down 5,000-20,000 SKU updates per night via the standard
ProductDataService+InventoryServiceendpoints. No manual SKU upkeep. - Custom denormalised stock + pricing tables, native indexers slow at 50k+ variants. Custom table updates from the feed sync directly, bypassing the catalog_product_index_price reindex.
- Hyvä theme instead of Luma. Luma re-renders the layered nav on every filter click; Hyvä uses Alpine state and stays under 200ms INP at 50k+ catalog scale.
- Layered nav on color count / decoration method / MOQ tier / lead-time, specific to promo. Customer narrows from 50,000 SKUs to 200 in three clicks.
4imprint runs ~120k SKUs on a custom stack. Magento gets you to 80% of that scale at 10% of the build cost.