A PIM implementation for a manufacturer builds one data model for technical attributes, variants, documents and certificates, fills it from the ERP and from supplier files, and sends the same data to the website, to distributors and to print catalogues. In our projects the analysis takes 2 to 6 weeks, and a first working system with an ERP integration and one or two channels usually takes 3 to 4 months.
On this page 8 sections
The partner you choose matters as much as the software: ask for public references from manufacturing, experience with ETIM and BMEcat, and a demo on your own products.
This guide is written by LemonMind, a Pimcore Platinum Partner from Gdańsk, Poland, that has implemented PIM systems since 2010. We describe how such a project runs, what a manufacturer should check, and how we do it on Pimcore.
What does a manufacturer need from a PIM?
A retailer mostly needs marketing content. A manufacturer needs that too, but the hard part is technical data that has to be right in every channel. In the projects we run for manufacturers the same requirements come back:
- Technical attributes with units. Dimensions, materials, power, pressure, colour temperature, with fixed units and allowed values instead of free text.
- Variants and relations. One product family with dozens of sizes or finishes, plus spare parts, accessories and replacement products linked to each other.
- Documents and certificates. Data sheets, declarations of conformity, safety data sheets, manuals and certificates, each linked to the right product and version.
- Classification standards. Wholesalers in the electrical, installation and HVAC trades ask for ETIM or ECLASS classes and for BMEcat files.
- Many languages and channels. The same product goes to the own website, a B2B portal, distributors' templates, marketplaces and the printed catalogue.
- Supplier data. Components and traded goods arrive as PDF data sheets and spreadsheets in formats nobody controls.
If several of these sound familiar, a spreadsheet and the ERP will not carry the load for long. A PIM gives that data an owner, a structure and one place to live.
PIM or ERP: who owns which data?
The ERP stays the source of item codes, prices, stock and logistics. The PIM takes what the ERP does not hold well: descriptions, technical attributes, images, documents, translations and the version of the data each channel needs. The two systems are connected, so nobody retypes an item code. Agreeing this split in writing at the start saves weeks of arguments later in the project.
How do ETIM, ECLASS and BMEcat fit in?
ETIM and ECLASS describe a product in a shared vocabulary: a class, its features and the allowed values. BMEcat is the XML format that carries this description to a wholesaler. A manufacturer usually needs one classification and BMEcat, and the PIM is where the classified data lives. If you are not sure which standard to start with, read ETIM vs ECLASS: differences and how to choose or see how we run ETIM and BMEcat in a PIM.
How does a PIM implementation for a manufacturer run?
The stages below are the ones we use. The durations are typical for our projects, not a promise for yours: the number of integrations, the size of the catalogue and the quality of the source data change them most.
Stage | What happens | Result | Typical time |
|---|---|---|---|
Pre-implementation analysis | Goals, data sources, channels and data quality reviewed with your team | Data model, integration map, plan and estimate | 2 to 6 weeks |
First version | The data model built on your real products | A working first version your team can test | about 6 weeks |
Integrations and migration | ERP and one or two channels connected, data cleaned and moved | A first full implementation | usually 3 to 4 months in total |
Go-live and growth | Training, launch, then more channels, markets and automations | A live PIM and a plan for growth | large multi-market projects take 6 to 12 months |
Two things decide most projects. The first is the data model: classes, attributes, variants and relations designed for your real catalogue, not for a demo. The second is ownership: a named person for each step of creating, enriching, approving and publishing data.
How does LemonMind do it with Pimcore?
We implement Pimcore, Akeneo and Ergonode, and for most manufacturers with a complex catalogue we recommend Pimcore. It lets us model classes, objects, relations and classifications freely, and it runs PIM, DAM, MDM and CMS on one platform. In practice:
- Data model. Classes and attributes for your product families, variants and relations, with classifications such as ETIM in the same model.
- ERP and channels. Integrations through Pimcore Datahub and APIs: item data comes in from the ERP, product content goes out to the shop, the B2B portal and marketplaces.
- ETIM and BMEcat. Our own ETIM Mapper assigns product categories to ETIM classes and sets feature values; Pimcore then generates BMEcat files for each wholesaler.
- Documents from data. Catalogues, data sheets and declarations of conformity generated from the product data, so a change in one attribute updates every document.
- Supplier data. Supplier PDFs and spreadsheets read by openProd, our AI import tool, or uploaded by suppliers through a supplier portal, with a person approving each change.
For a manufacturer that will run its product data on Pimcore for years, we recommend the Enterprise edition. Long-term support (LTS) with security fixes for older versions is part of Pimcore Enterprise and Enterprise PaaS, not of Professional, according to Pimcore's documentation. The Pimcore license comparison explains the editions.
Who is a PIM implementation for, and when is it too early?
It pays off for manufacturers with technical products sold through several channels or countries, with distributors who ask for structured data, and with a team that spends days preparing a product launch or a catalogue. A PIM comes too early when the product range is small, sold through one channel, and the ERP already holds everything the website needs. In that case, start with a data review and decide later.
How to choose a PIM implementation partner for a manufacturer
Most manufacturers compare two or three companies. These questions separate them quickly:
- Which manufacturers have you implemented, and can we read the case studies under the clients' names?
- Have you delivered ETIM or ECLASS classification and BMEcat export in a live project?
- Which ERP integrations have you built, and who maintains them after go-live?
- What is your partner level with the vendor? Pimcore lists its partners and their tiers in its partner directory.
- Will you show the system on our own products before we sign?
- Who supports the system after launch, and how are version upgrades handled?
Shortlists usually mix three types of providers: large consultancies that implement a PIM as part of a wider programme, boutique agencies that specialise in one or two platforms, and partners listed in the vendor's own directory. Any of them can fit. The questions above work for all three.
Who implements this: LemonMind
LemonMind is a Pimcore Platinum Partner, one of two in Poland, based in Gdańsk and working since 2010. We have more than 35 PIM implementations and more than 45 Pimcore clients, and Pimcore's partner directory lists 31 Pimcore certifications in our team (as of 4 November 2026). We are also an Ergonode partner and we implement Akeneo.
Projects for manufacturers you can read about:
- Marcopol: catalogue, data sheets and declarations of conformity generated from Pimcore data.
- GTV: Pimcore extended with ETIM classification, BMEcat export and the ETIM Mapper.
- VOX: Pimcore as the central product data hub for a furniture and interiors manufacturer.
- Ceramika Paradyż: a central product data and presentation hub for a ceramic tile producer.
- Polbruk: Pimcore PIM, DAM and CMS next to the ERP for a paving stone producer.
- Holzpiloten: PIM and digital commerce for a German maker of custom furniture.
The first step is a 30-minute call about your catalogue, your systems and your channels. See the scope of our PIM implementation work or talk to us.
Sources
- Pimcore Docs: Pimcore Editions · accessed 2026-11-19
- Pimcore Docs: Platform Versions · accessed 2026-11-19
- Pimcore Docs: Datahub · accessed 2026-11-19
- Pimcore: ETIM · accessed 2026-11-19
- Pimcore: find a solution partner · accessed 2026-11-19
- ETIM International: classification model · accessed 2026-11-19
- ECLASS: BMEcat · accessed 2026-11-19




