ETIM EC000042: Miniature Circuit Breaker

When a distributor merges a new supplier feed, the same miniature circuit breaker often arrives in dozens of forms — “MCB 1P 16A Type C,” “circuit breaker 16 amp single pole,” a bare MPN with no description, and a German-language BMEcat record that a procurement team manually mapped by hand. Without a shared classification anchor, matching breaks down, duplicates slip through, and AI search cannot find the right product from a spec-level query.

ETIM EC000042 is that anchor. It is the ETIM classification code for a miniature circuit breaker (MCB) — a low-voltage protective device that trips on overcurrent or short-circuit conditions. The class is not just a label: it carries a defined set of technical features and controlled value lists that make any MCB record machine-readable, regardless of brand or language. Claro uses EC000042 and the full ETIM feature set as validation rules when it resolves duplicate records, fills missing attributes, and writes trusted data back to your PIM or ERP — so classification work pays off in clean, search-ready SKUs rather than one-off spreadsheet fixes.

Definition

In the ETIM model, every product type maps to a class code in the form ECxxxxxx. The code etim ec000042 identifies the class “Miniature circuit breaker.” The class is not just a label: it carries a defined set of technical features — for example rated current, number of poles, tripping characteristic, rated breaking capacity, and width in modules — and for each feature a controlled list of permitted values or a numeric unit. A correctly classified MCB therefore arrives with a predictable, machine-readable spec sheet rather than free-text marketing copy.

Because ETIM is maintained as an international standard with translated feature and value names, EC000042 means the same thing to a wholesaler in Germany, a contractor in the Netherlands, and a marketplace in the US. The class code stays constant; only the display language changes. That stability is what makes ETIM useful as a shared vocabulary across catalogs, ERP systems, and electronic data exchange formats such as BMEcat and ETIM xChange.

Why consistent EC000042 classification matters

A class code is only valuable if every record that should be EC000042 actually is — and nothing else sneaks in. In real catalogs, the same breaker shows up as “MCB,” “miniature circuit breaker,” “circuit breaker 1P 16A,” and a dozen supplier-specific descriptions. Without a canonical class, matching and deduplication break down: two records that are the same physical product look different to your systems, and two records that merely share a keyword look identical. Assigning etim ec000042 consistently gives matching engines a hard anchor to group, compare, and merge against.

The same failure mode appears far outside the electrical aisle. An MRO distributor merging supplier feeds has to decide whether a fastener belongs in one class or three. A CPG team syndicating to retailers must map an internal bucket onto each retailer’s required taxonomy. In each case mislabeled records poison search, enrichment, and any downstream AI that reads your catalog. When an AI shopping assistant answers “show me a 16A type C single-pole breaker,” it can only do so if the underlying records expose the EC000042 features cleanly — vague text is invisible to it.

This is where a canonical product-data layer earns its keep. Claro resolves duplicate and variant MCB records to a single identity, then validates that each one carries the correct ETIM class and complete, in-range feature values before the data is written back to your PIM or feed. The goal is not just a tidy code in one field — it is a record that matching, enrichment, and AI search can all trust.

Key features inside EC000042

The table below lists the core features defined in the ETIM MCB class. Exact feature codes and the full value lists live in the official ETIM release; consult the current version for authoritative coverage.

How to apply EC000042 in practice

1. Identify all MCB records in your catalog

   Pull every record whose description, supplier category, or existing classification suggests a miniature circuit breaker. A first pass on keywords (“MCB,” “circuit breaker,” “Leitungsschutzschalter”) surfaces candidates; a classification checker can score confidence.

2. Assign class EC000042

   Map each confirmed MCB record to EC000042. If your PIM stores the ETIM class in a dedicated field, populate it there; if you are preparing a BMEcat export, the class goes in the ETIM_FEATURE_SYSTEM block. See What Is ETIM in BMEcat? for the exact placement.

3. Populate required features

   For each record, fill rated current, number of poles, tripping characteristic, rated breaking capacity, and rated voltage. Use only values from the controlled lists — do not invent values or encode them as free text. Missing or out-of-range values are the most common cause of partner validation failures.

4. Validate and resolve duplicates

   Run validation to catch missing mandatory features, out-of-range numerics, and disallowed values. Then check for duplicates: two MCB records with identical class, rated current, poles, and tripping characteristic are almost certainly the same product. Resolve them to a single canonical record before syndicating.

5. Write back and syndicate

   Push the validated, deduplicated records back to your PIM or ERP. When syndicating to partners, include the ETIM class and features in the agreed exchange format (BMEcat, ETIM xChange, or a flat-file structure your partner accepts).

Related

FAQ