Case

Show all

FLUX

System

Pimcore

Project type

Replatforming / PIM implementation

Launch

June 2026

Website

FLUX-GERÄTE GMBH is a B2B manufacturer primarily of pumps, but also of product systems made up of pumps, motors, flow meters, accessories and much more, which markets its products through its own sales channels and a spare parts ecosystem. Together with Y1, the outdated, fragmented system landscape was replaced by a modern, integrated Digital Experience Platform based on Pimcore – with central product and content management, seamless ERP integration and a scalable architecture for future international markets.

Request

FLUX's existing system landscape was technologically outdated and consisted of isolated individual systems with unstructured data flows. Specifically, the following problems existed:

  • Fragmented data storage: Product and content data were maintained decentrally and inconsistently – a central “single source of truth” was missing entirely.

  • No automation possible: Inefficient, manual data flows prevented the business model from scaling and blocked automation potential.

  • Architecture difficult to maintain: The existing system architecture was complex, hardly extensible and tied up a disproportionate amount of resources in maintenance.

  • Lack of integration capability: No end-to-end connection between the ERP (proALPHA), website, spare parts shop and other systems.

  • Limited user experience: The platform offered neither external customers nor internal users a contemporary, consistent experience.

  • No multi-tenancy: The system was not designed for international markets and multilingual requirements.

The pressure to act arose from the combination of growing market requirements, increasing competition and the realization that the existing platform could support neither the current product strategy nor future scaling scenarios (international markets, new sales channels).

Implementation

From data silos to a Digital Experience Platform – one source, one system, unlimited scalability

Technological foundation

  • Introduction of Pimcore as an integrated DXP – combining PIM, DAM and CMS in one platform

  • API-first architecture for maximum integration capability and future-proofing

  • Connection of the ERP system proALPHA via OpenAPI (JSON upsert with error handling, retries and monitoring)

PIM – product data management

  • Development of a complete data model with defined mandatory attributes, value lists and relations

  • Central maintenance structure as the basis for consistent, high-quality product data

  • Automated, script-based product release after data migration

DAM – Digital Asset Management

  • Design of a metadata schema incl. defined renditions (output formats for images and documents)

  • Structured media management for consistent reuse of assets

CMS – website & content

  • Development of an MVP website with prioritized templates and areabricks

  • Implementation of SEO (structured data, XML sitemap, robots.txt, hreflang strategy)

  • Tracking setup via Google Tag Manager, data layer, User Centric (GDPR-compliant), Google Analytics

  • Newsletter integration via Rapidmail (embed script as an areabrick)

  • Spare parts search interface (Spareparts.live)

  • Partner portal bundle

UX & design

  • User-centered UX concept: sitemap, low-fidelity wireframes, moodboard (Figma)

  • UI design based on the validated UX concept

  • Involving business users early (early user involvement) to avoid endless theoretical discussions

Governance & processes

  • Content governance concept: language/region matrix, translation and approval processes, roles & permissions

  • Clearly defined workflows and SLAs for internal and external collaboration

  • Principle of “standard before custom development” (80/20): customizing only where absolutely necessary

Procedure

The project was implemented in an iterative, modular phase model:

Phase 1 – Scoping

  • Analysis of the initial situation, system landscape and business processes

  • Workshops to gather business requirements (PIM, DAM, CMS, ERP integration)

  • Definition of the MVP scope, data model and system architecture

  • Creation of process diagrams, decision log, SEO/tracking plan

Phase 2 – Pilot (proof of concept)

  • Validation of technical and functional feasibility based on Pimcore

  • Building a working PoC for PIM, DAM, CMS and ERP integration

  • Creation of a low-fidelity UX concept (wireframes, moodboard)

  • Review of the Pimcore licensing strategy (Community vs. Professional Edition)

  • First ERP interface to proALPHA tested as an example

  • Early user involvement: business users enter the first products and content themselves

Phase 3 – Implementation of the overall project

  • Iterative implementation of all defined work packages in sprints

  • Regular review meetings, Q&A sessions and close coordination with the customer

Methods & tools

  • Workshops (scoping, requirements engineering, review)

  • Figma (UX/UI design)

  • Decision log & open issues tracking

  • OpenAPI specification for ERP integration

  • Agile development in sprints with defined milestones

info@y1.de

Let's talk about better product data. Tell us briefly about your situation. We'll get back to you.

A decorative image of a mobile phone in pixel representation
info@y1.de

Let's talk about better product data.

A decorative image of a mobile phone in pixel representation
info@y1.de

Let's talk about better product data. Tell us briefly about your situation. We'll get back to you.

A decorative image of a mobile phone in pixel representation