ETIM in BMEcat: Structured Product Classification for Technical Catalogs

Supplier feeds arrive every week with a different take on the same product: one file calls the field “Rated Voltage,” the next buries it in a description string, and a third omits it entirely. Without a shared classification layer, every onboarding cycle turns into a manual attribute reconstruction project. ETIM in BMEcat solves that at the source by forcing each article to declare its class and supply a fixed, named set of features before the file ever reaches your PIM or ERP. Claro reads those structured feeds, resolves product identity across suppliers, fills any attribute gaps with provenance-tracked enrichment, and writes trusted records back into your existing systems — so you stop cleaning data by hand.

What ETIM in BMEcat means

BMEcat is an open XML format for exchanging electronic product catalogs between suppliers and buyers. It provides the transport envelope: article identifiers, prices, media, logistics data, and feature blocks. ETIM — the European Technical Information Model — is a separate, open classification standard that defines product classes, the features that describe each class, and the allowed values or units for those features.

When people say “ETIM in BMEcat,” they mean a BMEcat file whose article records reference ETIM class codes and populate the corresponding ETIM feature blocks. A class code such as EC000042 identifies the product type (miniature circuit breaker). The associated features — rated current, number of poles, trip characteristic, breaking capacity — are then populated as structured attribute-value pairs inside the same record, not buried in a description string.

In practice the two standards are layered. BMEcat supplies the container; ETIM supplies the controlled vocabulary that turns a loose product description into a machine-readable record. A BMEcat file can also carry ECLASS, UNSPSC, or custom classification blocks, but ETIM dominates technical-product trade across electrical, plumbing, HVAC, construction, and industrial supply because it standardizes attributes — not just product categories.

Why it matters for catalog data quality

Most catalog problems are attribute problems. A distributor onboards three suppliers of the same valve family. Without classification, matching identical or near-identical items means comparing free-text titles and guessing at units. With ETIM features present, the system can directly compare class, connection size, pressure rating, and body material — which sharpens both catalog matching and duplicate detection across the entire range.

That structure matters far outside electrical and plumbing. An MRO distributor can compare bearing bore diameter and seal type as discrete features. A furniture retailer can align seat height and frame material instead of parsing marketing copy. A CPG team can match net content and pack configuration before a new supplier feed hits the ERP. In every case the bottleneck is identical: unstructured attributes prevent automation, and ETIM in BMEcat is the mechanism that removes the bottleneck at source.

Clean, classified attributes also feed AI search. When a buyer or an AI assistant asks for a 16 mm stainless fitting rated to a specific pressure, only structured features can answer reliably. ETIM-classified records are easier to validate, easier to map to a retailer or marketplace taxonomy, and easier to surface as a canonical product record.

How Claro fits the ETIM-in-BMEcat pipeline

Receiving a well-formed ETIM-in-BMEcat feed is the start of the work, not the end. Real catalogs layer complexity on top: different ETIM versions across supplier feeds, missing features for edge-case products, conflicting attribute values when two suppliers describe the same item differently, and class codes that drift as ETIM releases new versions. Claro validates the ETIM class codes and required features on ingest, resolves product identity across suppliers even when class codes disagree, fills missing attributes with provenance-tracked enrichment, and writes the clean records back into your PIM or ERP. Every decision — which source won, what was added — carries a confidence score and an audit trail so your team can review, override, and trust the output rather than just hoping the automation was right.

ETIM feature types at a glance

ETIM defines four value types for features. Understanding them helps teams validate feeds before import and catch errors that break downstream filtering.

Common errors in ETIM-in-BMEcat feeds

1. Wrong or outdated EC class code. ETIM releases new class versions; using a deprecated code means downstream validators reject the record or map features incorrectly. Always pin the ETIM version the feed targets.

2. Missing mandatory features. Each ETIM class defines which features are required. A record that omits a mandatory feature is incomplete and will not pass retailer or marketplace validation.

3. Value outside the allowed list. For EV-type features, only codes from the ETIM value list are valid. Suppliers who populate these fields with free text break classification entirely.

4. Unit mismatch on numeric features. Numeric features require a specific UN/ECE unit code. Sending 16 with no unit, or the wrong unit, causes silent errors in filtering and comparison.

5. Mixing ETIM versions in one feed. Combining classes from ETIM 7 and ETIM 8 in one BMEcat file produces inconsistent feature sets and confuses any system that expects a single version.

Related

FAQ

Is ETIM the same as BMEcat? +

No. BMEcat is the catalog exchange format — the XML container that carries articles, prices, media, and logistics data. ETIM is a classification standard that defines product classes and their features. ETIM in BMEcat simply means the BMEcat file references ETIM class codes and populates ETIM feature values inside its article records.

Can a BMEcat file use ETIM and ECLASS at the same time? +

Yes. BMEcat can carry more than one classification system, so a single article record can reference both an ETIM class and an ECLASS class. Distributors sometimes do this when different trading partners require different standards, though maintaining both means keeping two sets of features in sync and validating each independently.

What does an ETIM class code look like? +

ETIM class codes follow an EC prefix plus a numeric identifier, such as EC000042 for a miniature circuit breaker or EC000141 for a contactor. Each class defines a fixed set of named features, and each feature carries an allowed value type: a value list, a numeric range, a logical yes/no, or a free numeric value with a unit of measure.

Why do distributors require ETIM-classified BMEcat feeds from suppliers? +

Classified feeds load with far less manual cleanup. When every product arrives with a known ETIM class and standardized features, matching, deduplication, enrichment, and publishing to a webshop or marketplace can be automated. Free-text feeds force the buying team to reconstruct that structure field by field, which is slow, inconsistent, and never truly finished.

Does ETIM in BMEcat help with AI search and shopping assistants? +

Yes. Structured, attribute-level data is what lets an AI assistant answer precise specification queries and cite a product confidently. ETIM features give models discrete, comparable values — voltage, connection size, IP rating — instead of marketing prose, which substantially improves how reliably products surface in AI-driven and generative search.

What happens when ETIM class codes are missing or wrong in a BMEcat feed? +

Records fall back to free-text matching, which slows onboarding, raises error rates, and produces duplicate or misclassified SKUs in the catalog. Downstream systems — PIM, ERP, webshop — lose the structured attributes they depend on for filtering and comparison. Validating ETIM class codes and required features before the feed is accepted is the simplest way to prevent that cascade.