ETIM classification means assigning each product an ETIM class and filling the features that class defines, so customers, buying groups and wholesalers can use your data without remapping it. The class is the easy half. The value is in the features. SKULaunch classifies your catalogue to ETIM from the data you already hold, fills the class features from datasheets and supplier data, and exports the result in the format your customers ask for.
The problem
Electrical wholesalers, buying groups and larger installers increasingly expect ETIM. Your own data may sit in a bespoke taxonomy, an ERP with short descriptions, or a mix of supplier files. Classifying by hand means finding the right class among thousands, then completing each feature with the right value and unit. Most teams either pay for an outside service, or do the top sellers and leave the rest.
Doing only the top sellers looks sensible but rarely holds. Trade customers load the whole range, and a catalogue that is half ETIM still needs remapping on their side. The long tail is where the gaps show.
Before and after
An illustrative example from an electrical wholesale catalogue, for a cable gland.
Before: what your ERP holds
CG20BR, CABLE GLAND M20 BRASS IP68, pack 10.
After: classified to ETIM in SKULaunch
- ETIM class: Cable gland
- Thread type: Metric. Thread size: M20
- Material: Brass
- Degree of protection: IP68
- Cable diameter range: taken from the datasheet
- Remaining features filled from the supplier datasheet, with gaps left visible for review
How it works in SKULaunch
- Map your categories to ETIM classes. Each end node in your taxonomy is linked to the matching ETIM class, so classification follows your structure.
- Classify products. Products are assigned an ETIM class from their category, title and attributes, and reviewed before approval.
- Fill the class features. Values already held are mapped to ETIM features, and missing features are extracted from datasheets and manufacturer pages, with values and units in ETIM form.
- Export for customers. Send ETIM-classified data to trade customers and buying groups in the structure they request.
How ETIM classes and features fit together
ETIM groups classes into product groups, and each class carries its own list of features. Every feature has a defined type, and the type decides what a valid value looks like:
- Alphanumeric features take a value from a fixed ETIM value list, such as a material or a thread type. Free text is not valid.
- Numeric features take a number in a defined unit, such as a length in millimetres.
- Range features take a minimum and a maximum, such as the cable diameter a gland accepts.
- Logical features take yes or no, such as whether a product is halogen free.
That structure is why ETIM data is so useful to a wholesaler. Every supplier describes a cable gland with the same features and the same values, so products can be compared and filtered without anyone reading a datasheet. It is also why ETIM is hard to do by hand. Each value has to be translated into ETIM form, not copied across. For the full background, see what ETIM is.
ETIM classification at scale: rules that keep data loadable
- Classify on what the product is. A gland sold in a kit with a locknut is still a cable gland. Do not let the title decide.
- Use the value list, always. "Brass, nickel plated" in free text will not load. Map it to the ETIM values that describe it.
- Convert units before you load. If the class wants millimetres, a datasheet value in inches is converted, not pasted.
- Keep "not applicable" and "not known" apart. A blank that means "does not apply" and a blank that means "we have not found it" look the same to a customer, and only one of them is a gap.
- Fix the version. Classify to the release your customers ask for and map supplier data from other releases across. See ETIM 8 vs ETIM 9 for what moves between them.
- Work by class, not by supplier. Filling every cable gland at once makes inconsistencies obvious.
Run ETIM alongside your own taxonomy
You do not have to restructure your website around ETIM. ETIM classes are built for exchanging technical data, not for shopper navigation, and many sit at a level of detail that makes poor website categories. The practical approach is to keep your own taxonomy for the site and hold the ETIM class and features on each product as a second classification. Your customers get ETIM, your shoppers get categories that make sense, and SKULaunch keeps the two in step.
What changes
ETIM stops being a project and becomes part of how products are set up. SKULaunch has delivered a 95% ETIM match rate, so review time goes on the genuine exceptions. Trade customers get data they can load straight away, and you no longer turn down data requests because your catalogue is not in the right shape.
Common questions
Which ETIM version do you classify to?
The version your customers require. Data received in other versions is mapped across.
Do we need ETIM data from suppliers to start?
No. Supplier ETIM helps, but SKULaunch can classify from your own data and fill features from datasheets. Where suppliers do send it, you can import supplier ETIM data without parsing XML.
Can we keep our own category structure?
Yes, and we recommend it. ETIM is held alongside your taxonomy rather than replacing it.
What is the difference between an ETIM class and an ETIM feature?
The class says what the product is. The features describe it, each with a defined type, value list or unit. Customers need both.
How do I classify products to ETIM when my descriptions are short?
Start from your category mapping, then extract feature values from supplier datasheets and manufacturer pages. A short ERP description is enough to choose a class, but rarely enough to fill it.
Is ETIM only for electrical products?
It started in electrical and is now used in plumbing, heating and other technical ranges. The same approach applies.
More on ETIM data mapping, sending product data to trade customers and buying groups, and product data for electrical wholesalers.

.avif)