ETIM xChange Validator

Paste or drop an ETIM xChange JSON file and this ETIM xChange validator checks it against the official ETIM xChange JSON Schema (version 1.1 or 2.0, picked from the file’s SchemaVersion) and a set of consistency rules — required objects, feature codes, value formats, and duplicates — 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.

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 each feature carries exactly one well-formed value — a value code, a number, a logical, or a complete range with the lower bound first — or a ReasonNoValue.
• Numbers and units. In xChange the unit of a numeric feature comes from the ETIM model, so the file carries only the number. The validator checks that numbers match the format the schema allows (a dot, up to four decimals) and rejects unit fields the schema does not define.
• Duplicates and identifiers. Surfaces repeated supplier item numbers, features listed twice in one class, and GTINs with a wrong check digit.

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.

The ETIM dictionary itself is licensed and is not bundled, so the validator does not check that a class exists in the declared release or that a feature belongs to its class. 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.

Related resources

FAQ