Skip to main content

ETIM xChange: The JSON Successor to ETIM BMEcat Explained

What ETIM xChange is, how its JSON structure and ETIM fields compare with ETIM BMEcat, which versions exist, who accepts it and how to switch.

Diego Nijboer

ETIM xChange: The JSON Successor to ETIM BMEcat Explained

ETIM xChange is ETIM International's JSON format for exchanging product master data between manufacturers, wholesalers and data pools. It replaces the ETIM BMEcat guideline as ETIM's recommended exchange format: version 1.0 came out on 19 February 2024, and the current version, 2.0, was released on 27 November 2025. Unlike BMEcat, which is a German procurement standard that ETIM wrote a guideline for, xChange is owned and developed by ETIM International and its community.

For a supplier the practical change is threefold: the file is JSON with a published JSON Schema instead of XML, product data is split from trade item data (what is made versus what is sold), and ETIM classification becomes optional at international level while every feature of a class still has to be delivered once you classify. Below is how the format is built, how its ETIM block compares with BMEcat field by field, who accepts it today, and how ETIM releases affect what you send.

Why ETIM built its own exchange format after BMEcat

In May 2021 ETIM International announced it would develop a new international exchange format to replace ETIM BMEcat. Its reasons, from that announcement: the base BMEcat format was frozen years ago with no way to request changes, so every extension had to be built as a user-defined extension (the UDX.EDXF elements) to keep files valid, which made the format confusing. ETIM BMEcat got one last update, guideline 5.0 in June 2021, and ETIM said no further version would follow. Our BMEcat guide covers that format element by element.

The new format took longer than planned. A first attempt built on the Dutch DICO standard was restarted in 2022 with the European Master Data Guideline (EMDG) as its foundation. EMDG is published by FEST, the European federation of sanitary and heating wholesalers, and defines the common master data attributes for products. The ETIM xChange guideline says the team also harmonized content from ETIM BMEcat, DICO and the French FAB-DIS format where possible.

What came out has three properties a BMEcat user notices first. It is JSON with a JSON Schema for validation, which ETIM also positions as better suited to web and API exchange than file-only XML. It is published under the Apache License 2.0. And one file can carry several suppliers, which ETIM notes makes it especially suitable for data pools.

From announcement to xChange 2.0: the release history

ETIM xChange release history

  1. May 2021

    New ETIM exchange format announced

    ETIM International decides to replace ETIM BMEcat with a format of its own.

  2. June 2021

    ETIM BMEcat guideline 5.0

    Final ETIM BMEcat version, with only the most needed changes.

  3. 19 February 2024

    ETIM xChange 1.0

    First official release, with a mapping file from xChange fields to ETIM BMEcat fields.

  4. 27 August 2024

    Version 1.1 and validation tool

    Patch release for imperial and local standard feature codes and the customs code length. Files made for 1.0 still validate.

  5. 27 November 2025

    ETIM xChange 2.0

    Adds environmental (LCA/EPD) fields, packaging material data, serial number support and MDX attachment codes.

  6. 6

    December 2025

    Validation tool supports 2.0

    The members-only validation tool detects the schema version of an uploaded file.

One trap when you research it: ETIM International's exchange format page still says "Currently, ETIM xChange 1.1 is applicable", while its own news post on the 2.0 release and the downloads section carry version 2.0. Build against 2.0 unless your receiver tells you otherwise; the Dutch data pool 2BA, for example, accepts 1.0, 1.1 and 2.0 but recommends basing new development on 2.0.

Inside an xChange file: catalogue, supplier, product, trade item

ETIM xChange file hierarchy

Loading diagram
Only the Product level is mandatory; trade items and packaging units are added when the file carries commercial and logistic data.

The root of the file is the catalogue: SchemaVersion (2.0), CatalogueId, CatalogueType, validity dates, languages, currency. Under it sits an array of suppliers, and under each supplier an array of products. The 2.0 sample file from ETIM shows the levels a full delivery fills in:

  • Product (what is produced): ProductIdentification with ManufacturerName and ManufacturerProductNumber (both mandatory), ProductGtin, BrandName and CountryOfOrigin; ProductDetails with status and descriptions; ProductRelations; Legislation (RoHS, REACH, WEEE, hazardous goods); LcaEnvironmental; ProductAttachments; EtimClassification; and OtherClassifications, where codes from ECLASS, UNSPSC or a company classification can travel next to ETIM (our ETIM vs ECLASS comparison explains when you need both).
  • TradeItem (what is sold): ItemIdentification with the mandatory SupplierItemNumber plus ItemGtin; ItemDetails; ItemLogisticDetails with net dimensions and weight; Ordering with OrderUnit, MinimumOrderQuantity and OrderStepSize; Pricing with PriceUnit, PriceQuantity, GrossListPrice and VAT.
  • PackagingUnit: packaging type code, quantity and dimensions for each packaging level of a trade item.

The split matters for wholesale data. ETIM's own example is a cable you can buy per meter, as a 100-meter box or as a 1,000-meter reel: one product, classified once, with several trade items that each have their own article number, price and order unit. In a flat article list, each of those is a separate article that repeats the technical data. Where a manufacturer has no separate code for the unpacked technical product, the guideline accepts listing the smallest trade item at product level and repeating its identifiers.

Full catalogues, change catalogues and product status

Where BMEcat uses three transactions, xChange uses one field. CatalogueType FULL means a complete catalogue with all products and trade items offered to the buyer. CatalogueType CHANGE means the file only holds products that are new, changed or deleted, and then ChangeReferenceCatalogueVersion is mandatory: it names the earlier catalogue version the changes apply to. Agree with each receiver how often they want a FULL file to resynchronize, because a missed change file leaves their copy out of step just as a missed BMEcat update does.

Lifecycle travels in status codes rather than in the transaction. ProductStatus and ItemStatus take PRE-LAUNCH, ACTIVE, ON HOLD, PLANNED WITHDRAWAL or OBSOLETE, so a wholesaler can see that a product is still in stock but no longer manufactured. If your item master only knows active and inactive, that is a field to add before the first xChange delivery.

Format rules that catch first xChange files

  • Field names are exact. PascalCase as in the schema, and every object is closed with additionalProperties false, so a field the schema does not define fails validation.
  • Optional means absent, not empty. You may leave an optional field out, but if it is in the file it must hold a valid value. 2BA lists empty optional arrays and missing mandatory arrays among its common xChange mistakes.
  • Numbers are mostly strings with a pattern. GrossListPrice, for example, is a string of up to 11 digits, a dot and up to 4 decimals. No thousands separator.
  • Codes, not words. OrderUnit takes a unit code such as C62; languages are tags like en-GB or nl-NL; GTINs are 8 to 14 digits.
  • Attachments are links. 2BA notes that the 2.0 schema has no way to include physical files, only URLs, so images and data sheets need stable public addresses.

ETIM features in xChange next to ETIM BMEcat

If you already deliver ETIM BMEcat, most of the work is mapping. ETIM publishes a mapping file between the two; the table below follows its field pairs and the 2.0 guideline's field definitions.

ETIM BMEcat 5.0 versus ETIM xChange 2.0

ETIM releaseREFERENCE_FEATURE_SYSTEM_NAME, e.g. ETIM-10.0EtimReleaseVersion, e.g. 10.0, or DYNAMIC plus EtimDynamicReleaseDate
ETIM classREFERENCE_FEATURE_GROUP_ID (EC000042)EtimClassCode (EC000042), optional EtimClassVersion
FeatureFNAME (EF000227)EtimFeatureCode (EF000227)
Alphanumeric valueFVALUE with an EV codeEtimValueCode
Numeric valueFVALUEEtimValueNumeric
Range valueTwo FVALUE elementsEtimValueRangeLower and EtimValueRangeUpper
Logical valueFVALUE true or falseEtimValueLogical (JSON boolean)
No valueFVALUE - with FVALUE_DETAILS NA, MV or UNReasonNoValue NA, MV or UN
Is ETIM mandatory?Feature block mandatory for ETIM-classified productsEtim subtree optional; if a class is given, all its features must be sent
Supplier article numberSUPPLIER_PID, max 32SupplierItemNumber, max 35
Main descriptionDESCRIPTION_SHORT, max 150UniqueMainProductDescription, max 255
Very short descriptionUDX.EDXF.DESCRIPTION_VERY_SHORT, max 40MinimalProductDescription, max 80, mandatory
Full or partial deliveryT_NEW_CATALOG, T_UPDATE_PRODUCTS, T_UPDATE_PRICESCatalogueType FULL or CHANGE, plus ChangeReferenceCatalogueVersion
Country-specific dataUDX.EDXF.PRODUCT_CHARACTERISTICSCountrySpecificFields and CountrySpecificExtensions
Showing 14 of 14 rows
The ETIM content is the same model; what changes is typing (one FVALUE field becomes typed value fields), lengths and how empty features are explained.

Two rows deserve attention. First, ETIM classification moved from mandatory to optional at international level, so a manufacturer can send xChange before every product is classified. That does not mean receivers accept it: each ETIM country can make optional fields mandatory, and a data pool that sells classified data will ask for the class. Our step-by-step ETIM classification guide covers that part of the work. Second, the reason codes are unchanged: NA (not applicable), MV (no correct value exists in this ETIM version) and UN (unknown for now). If your BMEcat export already writes "-" plus a reason code, the logic carries over.

Who accepts ETIM xChange today

Adoption is uneven, and the honest answer is "ask each receiver". What the governing body and the pools publish:

  • Netherlands: 2BA supports ETIM xChange 2.0 for import and export, including the LCA environmental elements, and still accepts 1.0 and 1.1. It lists xChange next to BMEcat 2005 ETIM 5.0 and the Dutch formats in its current exchange formats.
  • Italy: in February 2026 METEL, which represents the electrotechnical industry within ETIM Italy, adopted a hybrid approach: use structured xChange data where available and integrate step by step.
  • Austria, Germany and Finland are the only countries with country-specific regulations in ETIM's country guideline for xChange 2.0 (version 2.01, April 2026). Germany sets text rules for descriptions, expects at least one main picture per trade item and asks for WEEE registration numbers; Austria makes Country AT, FullProductDescription and ProductKeyword mandatory; Finland caps MinimalProductDescription at 30 characters. The Netherlands and Belgium list no extra regulations, although 2BA defines Dutch characteristics as country-specific fields.
  • Everywhere: ETIM International notes that some countries still use national formats as their sector standard, next to or instead of xChange and ETIM BMEcat.

ETIM International describes xChange adoption as rapidly growing. Treat that as the standard body's view: for your own planning, the receivers that matter are the two or three wholesalers or pools that take most of your volume, and many of them will keep accepting ETIM BMEcat for some time.

What ETIM releases change in an xChange delivery

Every classified product in an xChange file names its ETIM release in EtimReleaseVersion, and the class code is only valid for that release. Three rules from the 2.0 guideline matter when releases change:

  • Release and class version are different numbers. EtimClassVersion counts changes to one class; a class that did not change between releases keeps its version. It is optional, but mandatory if you also send ETIM MC (modelling class) data.
  • The dynamic release is allowed. Instead of 10.0 you can write DYNAMIC, and then EtimDynamicReleaseDate becomes mandatory. Check that your receiver accepts dynamic-release data before you use it.
  • The class drives the feature list. All features of the class in that release have to be sent, apart from local standard features (codes such as EFUK0001). A new release can add features to a class, so a product that was complete in 10.0 may need new values in the next release.

The next major release is close: ETIM International has planned ETIM 11.0 for final release on 1 December 2026, after a change request deadline of 30 June 2026. Receivers move to a new release on their own schedule, so expect to deliver ETIM 10.0 to some and 11.0 to others for a while, and keep the release as an explicit setting per receiver rather than "latest". Our ETIM guide explains the class, feature and value model behind those codes.

Switching a supplier delivery from ETIM BMEcat to xChange

BMEcat to xChange switch checklist

0 of 9 done0%

Run both formats side by side for at least one full cycle. A receiver's import log tells you more than a valid schema check: it shows which fields they actually map, and where their data model is shorter or stricter than the standard.

Getting ETIM data ready in WISEPIM before any xChange export

WISEPIM does not export ETIM xChange. What it does cover is the content an xChange file is built from. In product classification you adopt ETIM 10.0 classes per product family, products inherit the class, feature values are checked against the class's permitted values and units, and an ETIM conformance score shows how many class features are valid per product. From there, Feed Hub writes a BMEcat file with ETIM features (plain BMEcat 2005, not the ETIM guideline 5.0 profile), and a CSV or XLSX export can carry the ETIM feature attributes as columns you pick, for a converter or data pool upload that writes the JSON. Test one file with each receiver before you rely on either route.

If you are not sure your supplier files are ready for either format, the free data readiness check is a person reviewing one file with you and pointing out what a receiver would reject.

Diego Nijboer

CTO and Co-Founder at WISEPIM, building AI-powered solutions that transform product data management for e-commerce businesses. Over 10 years of experience solving complex technical challenges in e-commerce and PIM systems.

Frequently asked questions

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

ETIM xChange is a JSON-based exchange format for product master data, owned and developed by ETIM International. It carries catalogue, supplier, product, trade item and packaging data, plus ETIM classification and features, and comes with a JSON Schema for validation. Version 1.0 was released in February 2024 and version 2.0 in November 2025. It replaces the ETIM BMEcat guideline as ETIM's recommended format.

It replaces ETIM's BMEcat guideline, not BMEcat itself. ETIM International published its last ETIM BMEcat guideline, version 5.0, in 2021 and now recommends xChange. BMEcat remains a standard of the German association BME, and many wholesalers, data pools and procurement platforms still accept ETIM BMEcat files. In practice suppliers often deliver both formats until each receiver has confirmed it imports xChange.

Use version 2.0 unless a receiver asks for something else. It was released on 27 November 2025 and ETIM's validation tool supports it since December 2025. Version 1.1 was a backward-compatible patch of 1.0, so 1.0 files validate against 1.1. The Dutch data pool 2BA accepts 1.0, 1.1 and 2.0 but recommends basing new development on 2.0.

Not at international level: the Etim subtree and its features are optional, so unclassified products can still be exchanged. Once a product carries an ETIM class, all features of that class must be included, with ReasonNoValue NA, MV or UN where no value can be given. Individual ETIM countries and data pools can make optional fields mandatory, so check each receiver's requirements.

Validate it against the JSON Schema in ETIM International's documentation package; any JSON Schema validator can do that. ETIM members can also upload files to the ETIM xChange validation tool, which checks the schema and the referenced ETIM classification, detects the schema version and can issue a validation certificate. Access uses the ETIM CMT login from your local ETIM office.

Keep exploring

Hand-picked next steps to go deeper.

Better product data, better results.Get more sales.

4.7