Product Catalog Integrated with PIM
Magento implementation as a product catalog integrated with Pimcore PIM - 8 language versions, automated data synchronization, and comprehensive SEO remediation.
- Client
- Electrical equipment manufacturer (B2B)
- Industry
- Industrial / manufacturing
- Scope
- Magento (Adobe Commerce) implementation as product catalog frontend, Pimcore PIM integration, multilingual support, SEO, maintenance and development (SLA)
- Technologies used
- Magento (Adobe Commerce)PimcoreWordPressGraphQLPHP
Results
Client's Problem
The client is an established manufacturer operating in European markets, with an extensive product catalog sold through a network of distributors and installers. Before the implementation, the web platform could not keep up with business needs:
- Product catalog disconnected from reality: product data lived in internal spreadsheets and systems, and updating the website required manual work from multiple people.
- No multilingual versions: the company operates in European markets, but the platform only supported one language - other versions were maintained ad hoc or did not exist at all.
- Architecture without scalability: the existing solution made it impossible to build advanced product features - filtering, technical search, and relationships between products and accessories.
- Poor SEO state: missing H1 tags, 500 errors on filter pages, missing breadcrumbs, incorrect no-index - organic visibility was minimal despite a broad catalog.
- Scattered content management: blog and product content were in different systems with no consistent navigation or search mechanism.
Proposed Solution
We proposed an architecture based on two complementary systems: Pimcore as PIM (the source of truth for products) and Magento (Adobe Commerce) as the catalog frontend layer - without the transactional module, since the client's sales model relies on distributors rather than direct sales. WordPress completed the setup as the content platform.
PIM → Magento Integration
Pimcore became the sole source of product data. We built synchronization of attributes, category hierarchies (parent → subcategory → product variants), and value mappings - including technical attributes (RAL colors, operating modes, power supply types).
Multilingual Support - 8 Language Versions
The platform serves 8 language versions from a single domain, with consistent navigation and correct hreflang/x-default implementation. Each language version went through URL validation and indexing configuration.
Product Page - Dedicated Templates
We built a custom product page template system covering: a model list with name-based search, related accessories, a mounting options section, downloadable certificates with ZIP export, meta tags, and structured data. Each product page fetches and displays certificates synchronized from Pimcore.
SEO - Comprehensive Remediation
301 redirects, fixing 500 errors on filter pages, correct H1 and title tags for parameterized pages, structured data (Article, LocalBusiness), breadcrumbs, preload and fetchpriority for LCP images, and footer page index.
Project Approach
The project was executed in an iterative model - the implementation was divided into a backlog and ongoing SLA. Prioritization followed a recurring cycle: the client submits a batch, the team estimates and implements, followed by client-side validation.
One of the key challenges was the complex product data model - a three-level hierarchy (parent / subcategory / children) with attributes inherited and overridden at different levels. This required precise mapping on the Pimcore side and building synchronization logic that respects the hierarchy without value conflicts.
A non-transactional catalog platform is an uncommon case in Magento implementations - disabling the cart and checkout while retaining full product functionality required custom configuration to avoid generating SEO and UX errors.
Achieved Results
- One system as the source of truth: the client's team manages products exclusively in Pimcore - changes land in the online catalog automatically, with no manual editorial work.
- 8 language versions: the platform is consistent across all European markets, with correct multilingual implementation.
- Improved SEO visibility: fixing technical SEO issues (H1, breadcrumbs, structured data, redirects, LCP) improved indexing of the extensive product pages.
- Product page as a sales tool: sales teams and distributors have access to complete technical data, downloadable certificates, and related accessories in one place.
- Stable SLA: ongoing maintenance and development in a ticket → estimate → implementation → testing model, with a clear backlog and priorities.
See next
More case studies
Next.js
PWA for an Automotive Sales and Leasing Service
Native mobile experience without an app store - one codebase covers web, PWA and Google Play using Next.js, Service Worker and Firebase FCM.
Symfony
Custom CRM for an Automotive Sales and Leasing Service
From spreadsheets and phone calls to a purpose-built CRM for the leasing sales process - 6 modules, e-signature integration, and full sales analytics.
Have a specific challenge?
Don't just read about it - let's talk about your case.