Electrical and installation suppliers increasingly send product data as ETIM, often inside a BMEcat XML file, and most teams have no easy way to import ETIM data into the systems they actually use. SKULaunch loads those files directly, decodes the ETIM classes, features, values and units into readable attributes, and maps them to your own model. The result is data that works on your website and in your PIM, with no XML work.
The problem
ETIM is excellent structured data, but it arrives in a form most teams cannot use. A BMEcat file is XML, features are codes rather than names, values are codes too, and units are referenced rather than stated. Without a developer or a specialist tool, the file sits unopened while someone retypes specs from the supplier's PDF.
The irony is that the most structured data you receive ends up being keyed by hand. And when it is keyed by hand, it loses the consistency that made ETIM worth having in the first place.
Before and after
An illustrative example from a luminaire supplier's BMEcat file.
Before: what is in the ETIM file
An EC class code for the product type, then a list of EF feature codes, each paired with a number, a true or false value, or an EV value code, with units referenced by EU code. No attribute names and no units in plain text.
After: what SKULaunch imports
- Category: Downlights, mapped from the ETIM class
- Rated voltage: 230 V
- Lamp type: LED
- IP rating: IP44
- Units resolved and normalised to your standard
- ETIM class retained on the record for customers who need it
How it works in SKULaunch
- Upload the ETIM or BMEcat file. No XML parsing, scripting or developer time.
- Decode classes, features and values. Codes become readable attribute names and values in the version the supplier used.
- Map to your model. ETIM features are matched to your own attributes, and ETIM classes to your taxonomy, with mappings saved for the next file.
- Fill what ETIM does not cover. Descriptions, titles and any attributes outside the ETIM class are enriched from the datasheet and manufacturer site, then sent for approval.
ETIM in one paragraph
ETIM is an open classification model for technical products, maintained by ETIM International and its national organisations. Each product type is a class, each class has a defined set of features, and each feature has either a numeric value with a unit, a logical value, or a value chosen from a controlled list. Versions are released periodically, so the same product may be described against ETIM 8, 9 or 10 depending on the supplier. The value of ETIM is consistency across suppliers. The cost is that the raw format is built for machines, which is why decoding and mapping matter. For more background, see what ETIM is.
How to import ETIM data without a developer
There are three usual routes. A developer writes a parser for the supplier's BMEcat, which works until the next supplier sends a slightly different file. A PIM with an ETIM module loads it, which works if your own model is ETIM, and most retail and website taxonomies are not. Or someone retypes from the PDF, which defeats the point.
The practical route is to decode the file once, map ETIM features to your own attributes once per class, and reuse those mappings for every later file from any supplier using the same class. The first file from a new class takes a mapping session. The tenth takes minutes. Our explainer on what BMEcat is covers the file structure if you want to see what is being decoded.
Checks before you import ETIM data
- Which ETIM version. Features are added, renamed and retired between releases. Know which version each supplier is on. See ETIM 8 vs ETIM 9.
- Is the class right. Suppliers sometimes classify to a near neighbour. A downlight filed as a surface-mounted luminaire brings the wrong feature set.
- How many features are filled. A class may define dozens of features and the supplier may fill a third. Know the gaps before you promise complete filters.
- Not applicable versus unknown. ETIM allows a feature to be marked as not applicable. That is different from blank, and should be kept different.
- What else is in the file. BMEcat often carries prices, image references and descriptions in several languages. Decide which of those you want to load.
- Units. ETIM fixes the unit per feature, which may not match yours. Convert on import, not on the website.
What changes
A 95% ETIM match rate between supplier ETIM features and your model, with the remainder raised for a one-off mapping decision. ETIM files become the fastest data to load rather than the slowest.
Common questions
How do I import ETIM data into my PIM?
Load the supplier file into SKULaunch, map ETIM to your model, enrich the gaps and push the approved records to your PIM through an export or an integration such as Akeneo or Plytix.
Do we have to use ETIM as our own taxonomy?
No. SKULaunch maps ETIM to whatever taxonomy and attribute model you use, and keeps the ETIM class on the record for customers who ask for it.
What if suppliers are on different ETIM versions?
Each file is decoded in the version it was written in and mapped to your model, so mixed versions end up consistent.
What is the difference between BMEcat and ETIM xChange?
BMEcat is an XML catalogue format that can carry ETIM classification inside it. ETIM xChange is a newer format from ETIM International designed specifically for ETIM data. BMEcat is still what most suppliers send. If yours send ETIM xChange or an ETIM spreadsheet, share a sample file and we will confirm how it maps.
Can we export ETIM back out?
Yes. Products classified to ETIM can be exported with their ETIM class and features for trade customers and buying groups. See sending product data to trade customers.
More on ETIM: ETIM, BMEcat and GS1 data mapping and how to classify your own products to ETIM.

.avif)