When WooCommerce struggles with a large product catalog, the cause is rarely WooCommerce itself. It is usually unclear data ownership and fragile integration flows. ERP and PIM integrations decide whether a large catalog stays accurate, fast and manageable — or turns into duplicate products, wrong prices and slow search.
Why ERP and PIM integrations decide whether WooCommerce scales
At a few thousand products, you can manage data by hand. At hundreds of thousands or millions of SKUs, every product field has to come from somewhere reliable. ERP owns commercial and stock data, PIM owns rich product information, and WooCommerce presents and sells it. If those boundaries are unclear, the catalog drifts out of sync and the storefront becomes the symptom.
Which data should be owned by ERP, PIM and WooCommerce
A clear ownership model is the foundation of a stable integration:
- ERP — prices, stock, customers, orders, invoicing and agreements
- PIM — product attributes, descriptions, media, categories and relations
- WooCommerce — presentation, search, cart, checkout, customer accounts and the buying experience
Typical data flows: products, categories, prices, stock, customers, orders
Product data and categories typically flow from PIM into WooCommerce, while prices, stock and availability come from ERP. Customers and orders flow both ways: B2B customers and agreements come from ERP, and orders placed in WooCommerce are written back for fulfilment and invoicing. Each flow needs a clear direction, an update frequency and a way to handle failures.
Where large catalogs fail
Most problems at scale come from a handful of recurring issues: imports that run synchronously and block the site, duplicate products from missing unique keys, slow search and filtering on an unoptimized database, wrong prices from race conditions between systems, and caching that either breaks personalization or serves stale data. These are integration and architecture problems, not WooCommerce limits. See Can WooCommerce handle 1 million SKUs? for the performance side.
How dealer-specific pricing and B2B views should be built
Dealer-specific pricing and product access should be driven by the agreements in ERP, not maintained manually in WooCommerce. The integration resolves the right price and assortment per customer group or dealer, and caching is designed so personalization works without sacrificing performance for logged-in users.
Kellox: Navision, PIM, WooCommerce, 1.2M SKUs and 500k updates
For Kellox, Maksimer connected WooCommerce to Navision (ERP) and a PIM system, with dealer-specific pricing, B2B self-service and bulk updates of up to 500,000 products at a time across a catalog of nearly 1.2 million SKUs — while keeping page load times under two seconds. See how Maksimer helped Kellox run 1.2 million SKUs on WooCommerce.
Checklist before you build a WooCommerce integration with ERP/PIM
- Decide which system owns each data type before writing any code
- Define direction and frequency for every data flow
- Use queues and async processing for large imports and updates
- Enforce unique keys to avoid duplicate products
- Plan caching around personalization and customer-specific pricing
- Add monitoring and alerting so failed syncs are visible
- Test with production-scale data volumes, not samples
Plan your WooCommerce project
Maksimer builds integrated WooCommerce platforms for established B2B and B2C companies. For the wider context, read WooCommerce for enterprise ecommerce: what actually needs to scale? or talk to us about your WooCommerce project.
