Skip to main content

ETIM Classification: Classify a Supplier Catalog Step by Step

How to classify a supplier catalog in ETIM: pick the release, match EC classes, fill EF features with EV values and units, check and deliver.

ETIM Classification: Classify a Supplier Catalog Step by Step

ETIM classification of a supplier catalog means giving every article exactly one ETIM class (an EC code such as EC000042) from the release your customers validate against, then filling that class's features (EF codes) with permitted values (EV codes), numbers with the class's units (EU codes), yes/no answers or ranges. What ETIM is and who runs it is covered in the ETIM guide; this post is the working method for a product data manager with a supplier file on the desk.

The short version: fix the release and language first, group the file, match each group to a class, map the supplier's columns to the class features, convert values to codes and units, leave features that do not apply empty, check every article against its class, and deliver in the format the receiving wholesaler or data pool asks for. The worked example below takes one miniature circuit breaker through every step with real ETIM 10.0 codes.

Agree on the ETIM release and language before touching the file

ETIM 10.0, released in December 2024, is the current official release, and official releases come about every three years, according to ETIM International's release policy. Between them, local ETIM organizations can offer dynamic releases that add new and changed classes with change codes. Ask the receiver which one it validates against. The Dutch installation data pool 2BA, for example, follows ETIM Dynamic daily with ETIM 10 as its base version, and data receivers choose which of the two to download. A file classified against a dynamic release can carry classes a strict ETIM 10.0 check does not know.

Class versions run separately from the release number. In ETIM 10.0 the miniature circuit breaker class EC000042 is at class version 9, so "version 9" in a class viewer does not mean an old release. Record the release (for example ETIM-10.0, the notation ETIM's guidelines prescribe) next to every classified family, because the codes only mean something together with it.

Language matters for the labels, not the codes. The model and ETIM English are free under the Open Data Commons Attribution licence, and so are the Belgian Dutch and Belgian French translations. The Netherlands Dutch version (nl-NL) is maintained by ETIM Nederland and needs a national membership, per ETIM's licence information. Codes are identical in every language, so a Dutch wholesaler and a Belgian manufacturer exchange the same EC000042.

Step 1: group the supplier file into batches that share one class

Classify groups, not rows. A supplier file of 3,000 articles usually holds a few dozen product types, and every article of one type ends up in the same ETIM class. Before matching anything, make sure the file has these columns, because you will need them in every later step:

  • Supplier article number and GTIN, so a later delivery can update the same article instead of creating a duplicate.
  • Short and long description, which is where the class hints and half the feature values hide ("MCB 1P C16 6kA").
  • The supplier's own product group or your category, which gives you the first grouping for free.
  • Technical columns as delivered, untouched. Keep the raw values next to the ones you convert, so you can show the supplier what you changed.

Sort by your category, then split any group that mixes product types. A category called "Modular devices" that holds circuit breakers, residual current devices and surge protectors is three ETIM classes, not one.

A saved import profile per supplier keeps the column mapping, so the next delivery from the same supplier lands in the same fields before you classify it.

Step 2: match each group to one ETIM class

Search the class list by name, code and synonym. Synonyms carry most of the matching work: EC000042 lists synonyms such as "Circuit breaker" and "Automatic protection", and in the Belgian Dutch release it is called "Installatieautomaat/Modulaire vermogenschakelaar". You can browse any class in ETIM's class viewer, which shows the latest dynamic content, so compare features against the 10.0 release file if 10.0 is what you deliver.

The hard part is near-siblings. In ETIM 10.0 a circuit breaker can land in EC000042 Miniature circuit breaker (MCB), EC002694 Miniature circuit breaker (MCB) with auxiliary device or EC000271 Miniature circuit breaker (MCB) plug model. Read the class features before you choose: the class whose features describe the article is the right one. If none fits, do not force the closest class. Leave the group unclassified and raise it with your local ETIM organization, because a wrong class makes every feature value in it meaningless to the receiver.

Choosing the ETIM class for one product group

Loading diagram
A group only gets a class when its features describe the products; otherwise it stays unclassified until the question is settled.

Step 3: map supplier columns to the class features

With the class fixed, the class defines what to fill. EC000042 has 27 features in ETIM 10.0. Map each supplier column, or each fragment of the description, to one feature. The table follows one illustrative supplier row, "MCB 1P C16 6kA, 230/400V AC, 1 module, IP20, -25...+55 °C", through the mapping. Codes and feature types come from the ETIM 10.0 release file; the supplier values are an example, not a real product.

One miniature circuit breaker mapped to ETIM 10.0 class EC000042

Char. CEF000889 Release characteristicAEV000084 (C)none
16AEF000227 Rated currentN16EU570459 (A)
1PEF008618 Number of poles (total)N1none
1PEF005548 Number of protected polesN1none
6kAEF009556 Rated short-circuit breaking capacity Icn according to EN 60898 at 230 VN6EU570170 (kA)
230/400VEF000228 Rated voltageNone number, agreed with the receiverEU570079 (V)
ACEF000187 Voltage typeAEV000460 (AC)none
1 moduleEF002950 Width in number of modular spacingsN1none
IP20EF005474 Degree of protection (IP)AEV006405 (IP20)none
-25...+55 °CEF007515 Ambient temperature during operatingR-25 and 55EU570073 (°C)
Showing 10 of 10 rows
Alphanumeric features take a value code, numeric and range features take numbers in the class unit, and feature counts like poles take no unit at all.

Two things show up in almost every supplier file. One supplier value often feeds two features ("1P" fills both pole counts). And one supplier value can be ambiguous for a numeric feature: "230/400V" is two voltages, while EF000228 takes one number. Do not type the slash into a numeric field. Decide with the receiver which value the class expects for that product type and apply that rule to the whole group.

Step 4: convert each value to an EV code, a class unit or a range

ETIM has four feature types, and each needs its own conversion:

  • A (alphanumeric): pick a value from the class's permitted list and deliver its EV code. "C-curve", "Char. C" and "Type C" all become EV000084. A value outside the list is invalid, even when it reads correctly.
  • N (numeric): one number in the unit the class sets for that feature. Convert 16000 mA to 16 A before delivery, never after. Counts such as "Number of poles" have no unit.
  • R (range): two numbers, a lower and an upper limit, with the class unit. "-25...+55 °C" becomes -25 and 55.
  • L (logical): yes or no. EF007517 Flush-mounted installation: yes is a logical feature, not a text field.

Units and value lists are set per class, not per feature. ETIM's classification guidelines use the example of EF000007 Colour, whose value list can differ in every class that uses it. Build your value translations per class, and keep them as a maintained list of supplier spellings, the same way you keep reference data for colors or countries. For unit conversion rules and the codes that go with them, see the guide to units of measure in product data.

Step 5: keep "not applicable" apart from "we don't know yet"

Both look like an empty cell, and they mean opposite things. A feature that does not apply to the product (an ambient temperature range on a part that has none) is finished. A feature the supplier simply did not send is a gap you have to chase.

ETIM's guidelines are explicit about the first case. A value "not applicable" is not allowed in ETIM: features that are not relevant for the product are left blank, and in a BMEcat exchange you deliver a minus sign "-", optionally with the code "NA" in the FVALUE_DETAILS field. The value "None" is only for cases where a buyer may want to select products that lack something, not as another way to write "not applicable".

For the unknowns, ask the supplier for the missing values per class, not per article. A list that says "all 40 MCBs in this file are missing EF009556 breaking capacity" gets answered; 40 separate questions do not.

Step 6: check every article against its class before delivery

Score each article on the share of its class features that carry a valid value. Valid means more than filled: the code is in the permitted list, the number is numeric and in the class unit, and the range has a lower limit below its upper limit. Run the checks below per class, so a systematic error (every article of one supplier with amperes in milliamperes) shows up as one finding.

Pre-delivery ETIM check per product group

0 of 8 done0%

Step 7: deliver in the exchange format the receiver names

The classification model is the same everywhere; the exchange format is not. ETIM International now has its own JSON-based format, ETIM xChange, next to ETIM BMEcat, and its exchange format page notes that some countries keep national formats as their sector standard. Ask the receiver which one it imports. In an ETIM BMEcat file, the class and features of one article sit in an ARTICLE_FEATURES block:

  • REFERENCE_FEATURE_SYSTEM_NAME: ETIM-10.0
  • REFERENCE_FEATURE_GROUP_ID: EC000042
  • FEATURE: FNAME EF000889, FVALUE EV000084
  • FEATURE: FNAME EF000227, FVALUE 16 (no FUNIT: ETIM fixes this feature's unit, ampere)
  • FEATURE (range): FNAME EF007515, two FVALUE elements -25 and 55 (degrees Celsius, fixed by ETIM)

Before the first full delivery, send a small sample, one group per class, and ask for the receiver's validation report. Rejections on a 20-article sample cost an afternoon; rejections on 3,000 articles cost a delivery cycle. If you want a second pair of eyes on one supplier file before that, the product data readiness check is a free review of one file by a person, discussed on a call.

Six reasons a classified supplier file comes back

Receivers validate before they import, and the same causes come back across product types. Check for these before you send anything:

  1. Release mismatch. The file says ETIM-10.0 but uses a class or feature that exists only in a newer dynamic release, or the other way round.
  2. Free text in alphanumeric features. "C curve" in EF000889 instead of EV000084. It reads fine to a person and fails every automated check.
  3. Wrong or extra units. Millimetres where the class expects metres, or a unit sent with a count such as number of poles.
  4. Placeholders as values. "n/a", "0", "see datasheet" or "TBD" in a feature. Blank is better than a placeholder.
  5. No stable key. Without GTIN and supplier article number on every row, the next delivery creates duplicates instead of updates.
  6. A forced class. A mixed group put into one class, so half the articles carry features that describe something else.

ETIM classes per product family in WISEPIM

In WISEPIM the ETIM tools live in the optional Classification module, which loads ETIM 10.0 with English labels plus the Belgian Dutch and French translations. On the Classification standards page you search ETIM classes by name, code or synonym and adopt a class into a product family; every product in that family inherits the class and its features, which matches the group-first method above. Classes are assigned per family, not per single product, so split mixed families before adopting. Mapping review proposes links from your own attributes to ETIM features (from earlier choices, exact and fuzzy matches, and optionally an AI mapping run), and a person approves every suggestion.

In the product editor, the ETIM tab shows an ETIM Conformance score ("X of Y class features are valid"), and Auto-fill with AI fills only missing or invalid features for one credit, re-validating every value before it is saved. Feed Hub exports a BMEcat 2005 (ETIM) file and leaves out products whose family has no ETIM class. The product classification feature page shows the screens; for the wider choice between ETIM and its cross-industry counterpart, see the ECLASS guide. The Classification module covers ETIM and GS1 GPC; WISEPIM does not support ECLASS or UNSPSC.

Diego Nijboer

CTO and Co-Founder at WISEPIM, building AI-powered solutions that transform product data management for e-commerce businesses. Over 10 years of experience solving complex technical challenges in e-commerce and PIM systems.

Frequently asked questions

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

A class (EC code) describes one product type and carries the features you fill, such as EC000042 for a miniature circuit breaker with 27 features in ETIM 10.0. A group (EG code) only orders classes for management; EC000042 sits in EG000020 Circuit breakers and fuses. Products are classified to a class, never to a group, and every class belongs to exactly one group.

Fill every feature that applies to the product and that you can verify. ETIM does not allow a value "not applicable": features that do not apply stay blank, and in a BMEcat file you deliver a minus sign, optionally with NA in FVALUE_DETAILS. Receivers often score completeness per class, so unknown values are worth chasing with the supplier.

Yes. ETIM International publishes the model and ETIM English under the Open Data Commons Attribution licence, so you can use and redistribute it with attribution. Some local language versions are open too, such as Belgian Dutch and Belgian French. Others, including Netherlands Dutch and German, are maintained by national ETIM organizations and need a national membership.

Use the release the receiving wholesaler or data pool validates against. The current official release is ETIM 10.0 from December 2024, and official releases come about every three years. Some local organizations also accept dynamic releases with newer classes. ETIM International plans ETIM 11.0 for 1 December 2026, so check which release your receiver switches to and when. Record the release in the file header (ETIM-10.0) and per classified family.

No. In an ETIM delivery each article has exactly one ETIM class. If an article seems to fit two classes, compare their features and pick the class whose features describe the product; a breaker with a built-in auxiliary contact, for example, has its own class in ETIM 10.0 (EC002694) next to the plain MCB class (EC000042).

Keep exploring

Hand-picked next steps to go deeper.

Better product data, better results.Get more sales.

4.7