How I Manage a Catalogue With Thousands of Products Without Losing My Mind

Direct answer — Past 3,000-5,000 SKUs, manual management inside the eCommerce back office stops working. The fix is to separate roles: the ERP is the source of truth for prices, stock and master data; the PIM (Akeneo or Pimcore) is the source of truth for product content, attributes, translations and media; the eCommerce platform (Magento/Adobe Commerce, Shopify) is just the sales channel. Armah implements this architecture on catalogues ranging from 5,000 to over 500,000 SKUs.

The 5-step method

Key takeaway 1. 1. Data clean-up — deduplicate SKUs, standardise units of measure, remove unused attributes.

1. Data clean-up — deduplicate SKUs, standardise units of measure, remove unused attributes. Usually 20-30% of attributes serve no one.
2. A single data model — define product families and mandatory attributes per family; set completeness rules (a product can't publish below 80% completeness).
3. PIM as the hub — import from ERP and suppliers, enrich once, distribute to eCommerce, marketplaces, PDF catalogues, retail.
4. Automated supplier onboarding — import templates, automatic validation, error queues, so new products go live with no manual work.
5. Ongoing governance — owners per area, scheduled quality checks, KPIs: average time-to-publish, completeness rate, returns caused by incorrect listings.

Signs you need a PIM

Key takeaway 2. You update products via Excel sheets emailed back and forth.

• You update products via Excel sheets emailed back and forth.
• Translations get lost or are inconsistent across markets.
• Publishing a new product takes more than 30 minutes of manual work.
• Marketplace and website show different data.
• Returns due to "product different from description" exceed 5%.

Measurable impact

Key takeaway 3. On mid-market projects with Akeneo connected to Magento, typical results after 6 months include: time-to-publish reduced from days to hours, listing completeness above 95%, fewer customer-service tickets caused by…

On mid-market projects with Akeneo connected to Magento, typical results after 6 months include: time-to-publish reduced from days to hours, listing completeness above 95%, fewer customer-service tickets caused by wrong data, and better long-tail organic search coverage because every listing has real content.

FAQ

When does it make sense to introduce a PIM?

Once you pass a few thousand SKUs, sell across multiple channels or languages, or have several people touching the same product data. Under 1,000 SKUs on a single channel, the platform's back office is enough.

Akeneo or Pimcore?

Akeneo is more immediate and product-data oriented, with a great UX for marketing teams. Pimcore is more flexible and includes DAM and content management, but needs more development. Armah implements both and chooses based on who will use the tool daily.

How much does a PIM project cost?

A mid-market PIM implementation typically starts at €25,000-€45,000 for the first market and channel, with additional cost for each extra integration (marketplace, ERP, DAM).

How do you sync stock and prices with the ERP?

With frequent incremental feeds (often every 5-15 minutes) via dedicated APIs, never with full nightly exports: those reduce data freshness and cause overselling.

BOFU — related links

Key takeaway 4. Best Ecommerce Platform Guide Connect Retail Store & Ecommerce Free eCommerce Audit

• Best Ecommerce Platform Guide
• Connect Retail Store & Ecommerce
• Free eCommerce Audit