ETIMxChange is the first product and trade item exchange standard fully managed by ETIM International and its community, with a focus on global use. ETIMxChange is based on the European Master Data Guidelines (EMDG) taking into account national exchange standards such as DICO, BMEcat and FAB-DIS). The exchange format is based on JSON, including JSON schema for validation.
The complete documentation of ETIMxChange 1.0 (release 2024-02-19) can be found in the downloadsection of ETIM International.
Given the impact on the 2BA data model and planning, the implementation is fragmented into:
1. Import limited to current 2BA data model + subtree LcaEnvironmental
2. Schema validation not yet available
1. Import minor improvements
2. Schema validation
1. Selective number of new fields to be recognized in the mapping
2BA conforms the data pool to the Dutch standards of Ketenstandaard Bouw en Techniek. The supported exchange formats are mapped to the internal fields of the data model. Some internal fields may differ from the length or type described in the interchange format guideline. We create as much clarity as possible, but there may be differences, exceptions are noted in the mapping.
The code lists used within the exchange format do not always match the code lists from the data model. Always use the code lists associated with the exchange format used. Consult the mappings per code list below:
There are no validation checks available.
It may happen that a country requires more fields than originally available in the ETIMxChange structure.
The ETIMxChange Country Specific Guideline contains clear examples of how to define these in your data file. Use the CSItemCharacteristics fields as defined in the ETIM guideline section 3.13 from page 50.
The ETIMxChange header does not contain an option to specify the exchange format. To recognize the format, the term ETIM_XCHANGE or ETIMxChange must be included in the file name. If this term is missing, the dataset will not be recognized by the import routine.
2BA supports complete or update (mutation) files of ETIMxChange. A complete dataset must contain all active products and articles. A new complete file overwrites all records in the database! Use CatalogType to define the dataset as a complete or mutation file. Existing product records that are not present in the complete file are marked with status code 130 as “expired product”. Existing trade records that are not present in the complete file will be deleted.
The advice is to work with complete data sets. By working with complete datasets, the published data remains most similar to your source data. If you have such a large range with a large number of attachments and regular changes, we recommend updating mutation files and periodically publishing a complete file.
From ETIM version 8 it is possible to communicate country-specific characteristics. ETIMxChange 1.0 does not support this functionality. We have made an adjustment to the import schedule in advance to be able to process country-specific characteristics within the data pool.
Consult the mapping of the ETIM version versus data model. Within the ETIMxChange documentation it is indicated that the EtimDynamicReleaseDate is mandatory when the ETIM version ‘DYNAMIC’ is specified. We overrule that business rule within the data pool.
If a value cannot be assigned, the data provider has the option to use a minus sign according to the ETIM guideline. Values with a minus sign are not imported. Instead, use one of the following reasons:
There is also a mutation code at line level within the model. This value cannot be provided with the ETIMxChange standard. There is a mutation code at file level (for both the article and product message). In addition, a status code has been defined at line level. The combination of both codes is interpreted in the following way:
Within ETIMxChange, the logistics data is only included in the trade item section..
For each trade item it can be defined how the trade item can be ordered, on which unit the price is based, which discount group the trade item falls into and how the trade item can be used.
A good description makes it clear which product it concerns. Customers use these within the (web) catalogue, on transaction messages and within calculations. In addition, the trade item or product can also be found based on the description. The industry standard has two description formats: short and long, and there is also room for an extensive marketing text.
Wholesalers uses the structure of brand, serie, type as a filtering method and search engine optimisation (SEO), for example on their webshop. For this reason these fields are mandatory for each product record. Some manufactures don’t use serie and type grouping. In this case use the value RNV_NA. More information click here.
No specific certificate structure is included within ETIMxChange 1.0. When the type of an attachment certificate is related, a certificate record is generated where possible.
By default, the import routine will download an attachment and add it to the product data. Due to the different export formats, the predefined values (MD codes) are assigned to the attachment type code list.
The import routine automatically creates an MD5 Hash for each downloaded file. An MD5 Hash makes it possible to determine whether it is a new file or a duplicate. ETIMxChange 1.0 does not include the ability to specify the MD5 Hash and OriginalFileSource.
In the data model, references and relationships are only mapped at product level, not at trade item level.
ETIMxChange assumes an implicit unit for a specified quantity; Since it is an trade item (or product) to trade item (or product) relationship, units are assumed (PCE). A part or accessory of a product can be specified with relationship type ‘SELECT.’