Key takeaways:
- ETIM is the dominant international classification standard for technical products in sectors like electrical installation, HVAC, and building automation
- A PIM system is the natural home for ETIM-classified data because it connects attribute management, channel distribution, and version control in one place
- Without a PIM for ETIM data, maintaining classification compliance across thousands of SKUs becomes a manual, error-prone process that breaks at scale
- AtroPIM supports flexible attribute modeling that maps directly to ETIM classes, features, and value lists, with no constraints on catalog depth or structure
What ETIM Actually Is
ETIM stands for ElectroTechnical Information Model, an international product classification standard for technical products originally developed for the electrical installation sector and now covering HVAC, sanitary, building automation, and other technical domains. Across Europe, it is the default data exchange language between manufacturers, electrical wholesale distributors, and installers, with adoption growing in North America and Australia.
"ETIM is a key element in the digitalisation of the entire supply chain."
- Margaret Fitzsimons, CEO, UK's Electrical Distributors' Association (EDA)
Two levels structure the model: product groups and product classes. Each class carries a fixed set of typed features: alphanumeric (a predefined value list), logical (yes or no), numeric (a single measured value), or range (two numeric values). Every class, feature, value, and unit carries a language-independent identifier, which is what makes ETIM work across 17 languages and dozens of national markets.
eCl@ss (also written eClass) is the closest comparable standard, covering a broader range of industries but less dominant in electrical and HVAC. Many European manufacturers maintain both, which adds another reason to manage ETIM product data inside a dedicated system rather than manually.
For CAD and BIM workflows, the ETIM Modelling Classes (ETIM MC) extension adds 3D geometry parameters to the core model. That layer is optional and leaves the base classification untouched.
ETIM 10.0 was released in December 2024. ETIM 11.0 is in planning.
Where the Data Management Problem Starts
A manufacturer of electrical components, switchgear, or lighting equipment typically manages thousands of product variants. Each product belongs to an ETIM class, and that class may have 20 to 40 attributes, each requiring a valid typed value. Multiply that across a catalog of 10,000 SKUs, and you have a structured product data management problem that spreadsheets cannot handle reliably.
ETIM classes are updated with each release. Features are added, values are renamed, and units are changed. A new version means every product mapped to an affected class needs review and potential re-mapping. If that data lives in spreadsheets or inside an ERP, the update cycle is painful: manual exports, conditional formatting checks, re-imports, and no audit trail.
In projects we implemented for manufacturers of electrical installation materials, a recurring situation was a product catalog that had been partially mapped to an older ETIM version. Distributors in the electrical wholesale sector were requesting ETIM product data in a newer version, but there was no structured way to identify which products were affected and what exactly had changed. The team was doing it field by field, manually.
A PIM system solves this at the data model level, not through process workarounds.
What a PIM System Does for ETIM Data
A product information management system provides a structured data layer specifically designed for product attributes, where you define what attributes a product has, what values are valid, and how they are organized into classifications. Using a PIM for ETIM means that the structure maps directly onto the ETIM data model.
An ETIM class becomes a classification in the PIM. Its features become attributes. The typed nature of ETIM features maps onto PIM field types: select lists for alphanumeric features, boolean fields for logical ones, and numeric and range fields for measured values. Predefined ETIM value lists become attribute options enforced at data entry, preventing invalid values from entering the system.
Version updates are managed at the classification level. Products assigned to a classification inherit the updated attribute set automatically. Filter by classification to find products with missing values for new features, then work through them in sequence. No spreadsheet exports, no conditional checks. The scope of the update is visible from the start.
Beyond attribute management, a PIM for ETIM handles how classified product data reaches different destinations. A wholesale distributor may receive data via BMEcat or the newer JSON-based ETIM xChange format. An e-commerce platform may need a different structure. An internal ERP may use yet another. One canonical ETIM-classified dataset feeds all of them without duplication.
What Breaks Without One
Without a PIM, the typical setup is ETIM product data scattered across ERP exports, spreadsheets, and individual supplier portals. Each of these is a separate copy that drifts from the others. When a product attribute changes, someone has to update each copy manually.
Failure modes are predictable. A value in the ERP does not match what was sent to the distributor portal. An older version of the ETIM standard is still in use for a product line because no one tracked the version at the SKU level. A numeric ETIM feature has a value entered as text because the input was not enforced. A new product is published to a channel without ETIM product classification because there was no mandatory field to prevent it.
These are not edge cases. Our customers in technical wholesale and manufacturing come to us because these situations have compounded into a data quality problem serious enough to affect operations: returns from wrong product selection, failed EDI exchanges, rejected distributor submissions. Managing PIM and ETIM together eliminates the structural conditions that cause these failures.
How PIM Software Handles ETIM Data
Not all PIM systems treat product data classification the same way. For ETIM specifically, the relevant question is how well the system can represent typed attributes, enforce value constraints, and handle classification-level updates that propagate across products. A few systems in the market have built explicit support for this.
Akeneo has native support for ETIM in its B2B edition, with a dedicated ETIM import tool and the ability to map product families to ETIM classes. The practical limitation is that deeper enforcement, like mandatory feature completion per class or version migration workflows, requires additional configuration and is more accessible in higher-tier licenses.
Pimcore supports ETIM through its classification store, a feature that allows class-based attribute sets to be assigned to products independently of the main product schema. Structural mapping works well, and a number of European manufacturers and wholesalers in the electrical sector use it. Setting it up correctly requires significant developer involvement.
Contentserv has positioned itself for technical product data management in manufacturing and includes support for classification standards including ETIM, with built-in data quality tools. It targets larger enterprises and carries a corresponding price point.
AtroPIM takes a different approach. Built on the AtroCore data platform, its attribute and classification architecture is configurable without a fixed schema. Classifications can be created to mirror any ETIM class structure, with custom attribute types and value constraints. This flexibility is available in the free open-source core.
The key capabilities for ETIM management in AtroPIM:
- Classification management: Create classification trees that mirror ETIM product groups and classes. Assign products to one or more classifications. Attributes are inherited from the classification level, so a change to the class definition propagates across all products in it.
- Attribute types: AtroPIM supports the full range of field types needed to represent ETIM features accurately: select (for alphanumeric features with predefined values), boolean (for logical features), float/integer (for numeric features), and range fields. Value lists are controlled at the attribute level.
- Completeness tracking: You can define completeness rules per classification. A product classified under a specific ETIM class will show as incomplete until all mandatory features have values, making ETIM readiness visible and trackable across the full catalog.
- Channel-specific export: AtroPIM supports configurable export templates. A BMEcat export for distributor data exchange, a JSON export for ETIM xChange, and a custom format for your e-commerce integration can all be maintained in parallel from the same source data.
- Version control and audit trail: Attribute changes are logged. When you update a value list to reflect a new ETIM version, you can track which products were affected and when the change was applied.
The core difference between AtroPIM and the alternatives above is the cost-to-flexibility ratio. The configurability that Pimcore requires developer time to achieve, and that Akeneo gates behind higher license tiers, is available in AtroPIM without those constraints. For mid-sized manufacturers with complex ETIM catalogs who do not want vendor lock-in, that is a material consideration.
A Practical Example
A manufacturer of industrial luminaires needed to deliver ETIM-classified data to five distributors with different format requirements, while also feeding their own webshop and a printed catalog.
Before AtroPIM, they maintained a master spreadsheet per product line, mapped to ETIM manually, and exported separate files for each distributor. Each export was a partial copy. Version mismatches between distributors were a recurring issue.
After mapping their ETIM classes into AtroPIM's classification system, all features are entered once, validated against enforced value lists, and exported through channel-specific templates. When ETIM 10.0 was released, they updated classification definitions in AtroPIM and ran a completeness report to identify products with missing values for new features. One controlled workflow, no parallel spreadsheets. The same data now feeds distributor exports, the webshop, and the catalog generation module simultaneously.
Where ETIM and PIM Still Require Careful Setup
A PIM does not eliminate the need to understand the ETIM standard. The product classification structure still needs to be built correctly. Someone on the team needs to know which ETIM class a product belongs to, which features apply, and what constitutes a valid value. That domain knowledge does not live in the software.
Importing an existing ETIM data model from a BMEcat or xChange file is a reasonable starting point for ETIM implementation. AtroPIM's import module can take structured input and map it to the internal attribute model. But the initial mapping and the ongoing governance of classification correctness remain editorial work.
The approach that works well is phased: start with the product groups driving the highest distributor data exchange volume, build the ETIM class structure for those first, and validate against real distributor requirements before expanding. Getting the first group right takes the most time. After that, the pattern is set, and subsequent groups move faster.