Claro
On this page What it checks
  1. What it checks
  2. How the ETIM xChange validator works
  3. Related resources
  4. FAQ

ETIM xChange Validator

Free ETIM xChange validator that checks your JSON file against the standard in the browser — no upload, no login, no size limit. Instant pass/fail.

published validationdistributors

Paste or drop an ETIM xChange JSON file and this ETIM xChange validator checks it against the standard’s structure — required objects, feature codes, value formats, and units — then returns a plain-language pass/fail report. It is built for distributors who receive xChange files from suppliers and need to know whether a file is clean before it touches a PIM, ERP, or downstream feed.

ETIM xChange Validator

The interactive version of this tool is coming soon. It will run entirely in your browser — no login, no upload limits.

Planned tool: etim xchange validator

Need this now? Talk to Claro

What it checks

The validator parses your file and runs each record against the structural rules of the ETIM xChange format, reporting issues at the file, product, and feature level.

  • Well-formed JSON. Catches truncated files, encoding problems, and trailing-comma syntax errors before anything else runs.
  • Required top-level objects. Confirms the supplier block, ETIM release/version reference, and product collection are present and correctly nested.
  • Product-level mandatory fields. Flags products missing a supplier product ID, manufacturer reference, or the ETIM class assignment a downstream system expects.
  • ETIM class codes. Validates that each product references a class code in the expected EC###### shape and that a class is actually assigned.
  • Feature codes and value types. Checks that feature references use the EF###### / EV###### patterns and that alphanumeric, logical, numeric, and range features carry the value type the feature expects.
  • Units of measure. Confirms numeric features that require a unit declare one, so a furniture panel’s dimensions or an MRO pump’s flow rate are not left unitless.
  • Duplicates and orphans. Surfaces repeated supplier product IDs and feature values that reference a class the product was never assigned to.

How the ETIM xChange validator works

ETIM xChange is the JSON-based exchange format from the ETIM International group, designed to carry classified product data — classes, features, values, and units — between manufacturers and distributors without the heavier BMEcat XML envelope. Because the format is structured, most quality problems are deterministic: a feature is either declared with a valid code and value type, or it is not.

  1. 1
    Parse
    The file is read into memory and checked for valid JSON and the expected ETIM xChange skeleton.
  2. 2
    Validate
    Each product and feature is checked against required-field, code-format, value-type, and unit rules.
  3. 3
    Report
    Findings are grouped by severity with the product ID and feature code, so you can hand a supplier a precise punch list.

All parsing and validation run client-side in your browser. Nothing is uploaded to a server, there is no login, and there is no file-size limit beyond what your machine can hold — so a large industrial-distribution range or a CPG assortment stays on your own device.

Structural validation answers “is this file legal?” — it does not answer “is this data correct?” A breaker rated for the wrong amperage or a contactor in the wrong ETIM class will pass structural checks. Catching those errors needs classification and matching logic, which is what Claro’s product-data platform applies once a file is structurally clean.

Glossary

What Is ETIM in BMEcat?

How ETIM classes and features are carried inside exchange files, and how xChange differs from the XML envelope.

Tool

ETIM BMEcat Validator

Validate the XML BMEcat variant of an ETIM-classified supplier file in your browser.

Tool

ETIM Classification Checker

Check whether a product's ETIM class and feature assignments are plausible, not just well-formed.

Playbook

How to Validate an ETIM XML Export

A repeatable workflow for QA-ing supplier ETIM exports before they reach your PIM.

Guide

ETIM vs UNSPSC vs eClass

Choose the right classification standard for your catalog and channels.

FAQ

What is ETIM xChange?

ETIM xChange is a JSON-based format from ETIM International for exchanging classified product data — classes, features, values, and units — between manufacturers and distributors. It carries the same ETIM model as BMEcat but in a lighter, modern JSON structure that is easier for API-first systems to consume.

How is ETIM xChange different from ETIM BMEcat?

Both transport ETIM classifications, but the container differs. BMEcat is an XML format with a catalog envelope; xChange is JSON and focuses on the product, class, and feature payload. If your supplier sends XML, use the ETIM BMEcat Validator instead; if they send JSON, this is the right tool.

Will my product file be uploaded anywhere?

No. The ETIM xChange validator runs entirely in your browser. Your file never leaves your device, there is no account to create, and there is no size limit beyond your machine’s memory — which matters when you are validating a full distribution or MRO range.

Does passing validation mean the data is correct?

Not entirely. Structural validation confirms the file follows the ETIM xChange format — valid codes, value types, and units. It cannot confirm a value is factually right: a furniture item in the wrong class or an industrial part with a transposed rating will still pass. Use classification and matching checks for that layer.

My supplier's file failed — what should I do?

Send them the report. Because findings are tied to a specific product ID and feature code, a supplier can correct the source data without guessing. For a repeatable hand-back process, the ETIM XML export playbook walks through how to QA and return supplier files.

Updated June 9, 2026