Version changes for classifications - Where are the pitfalls?

Product data classifications such as ETIM and ECLASS are central tools in many industries for uniformly describing and categorizing technical products. They enable standardized product information to be exchanged between manufacturers, retailers, distributors and other market participants. However, switching from one version of the classification to the next often poses challenges and pitfalls that should not be underestimated.

The background: Changing versions of ETIM and ECLASS

ETIM and ECLASS are product data classification systems that are regularly updated to reflect new technological developments and market requirements. A new version can, for example, contain additional product groups, adapt existing attributes (features) or remove obsolete classes.

Such changes are necessary to keep the data flow efficient and current. However, they also affect product mapping and feature mapping, which can be problematic for manufacturers and their partners.and successfully master the version change.

The challenge: adapting product data

With each new version of a classification, manufacturers have to adapt their product data. This concerns both the assignment of products to the corresponding classes and the mapping of features. Making this process run smoothly is often more difficult than it appears at first glance.

In new versions of ETIM or ECLASS, existing classes may be removed or merged. Products that could previously be clearly assigned may no longer fit into a single class. In such cases, manufacturers often have to switch to several classes or revise detailed feature data to ensure correct assignment, and changing or adding features can also lead to problems. Features that were considered important in the old version could be neglected in the new version. Products that were once accurately described suddenly no longer have all the necessary attributes to be classified completeness. This can lead to a considerable amount of extra work when revising the data.

Another problem is that not all data recipients, such as distributors or retailers, are willing to switch to the latest version of the classification. There are often different versions that are used in parallel. Retailers might insist on a particular version that is already integrated into their IT infrastructure. For manufacturers, this means that they may have to maintain their data in several versions in parallel.

This "version chaos" requires a high degree of flexibility in data management and a human and time investment that should not be underestimated. A manufacturer may have to prepare different product data for different partners, depending on which version of the classification they use.Technical and organizational pitfallsThe technical and organizational challenges posed by version changes should also not be underestimated.

The version adjustment process is often only partially automated. Many companies have to check and implement the changes manually, which increases the susceptibility to errors. Especially if product features only change slightly, these adjustments may be overlooked and incorrect information may be transmitted in subsequent product communication. This can be remedied by consistent automation and the use of tools that support the mapping process.

Another problem arises from the lack of coordination between the parties involved. Manufacturers, retailers and distributors do not always use the same classifications or interpret them differently. Communication needs to be improved here to avoid misunderstandings. It can be useful to offer training for partners or to discuss the common standards in regular meetings to ensure that everyone is on the same page.

Strategies to avoid pitfalls

To ensure that the transition to a new version of ETIM or ECLASS goes as smoothly as possible, companies should consider the following strategies:

It is important that manufacturers are prepared for upcoming versions at an early stage. Many classification systems offer beta versions or test data before the official release. These should be used intensively to adapt internal systems and processes. Continuous monitoring of changes is also necessary to ensure that no critical updates are missed.

Automation offers great potential for reducing the effort involved. Specialized software tools can facilitate the mapping of product features and classes and ensure data consistency. These tools are able to automatically reclassify products or suggest how they can be mapped in the new version.

So-called "versioning strategies" can be used to deal with the problem of different versions among data recipients. Here, manufacturers maintain their product data in parallel in several versions and can thus react flexibly to the requirements of different partners. However, this requires well-organized data management and clear processes.

Close cooperation and regular coordination with partners is essential. Distributors and dealers must be informed of upcoming changes at an early stage and trained if necessary to facilitate the introduction of new versions. This cooperation not only reduces frictional losses, but also strengthens business relationships in the long term.

Conclusion

Changing versions of classifications such as ETIM or ECLASS is unavoidable, but also involves risks and challenges. Manufacturers are faced with the task of continuously adapting their product data while at the same time having to take into account the needs of data recipients. A well-planned strategy that includes early preparation, automation and close coordination with trade partners can help avoid the pitfalls.