For data suppliers who manage their product information on international level, the choice of a data exchange format is often the BMEcat 2005. This is also the recommended format by ETIM International. When suppliers want to use a BMEcat 2005, we strongly recommend to use the ETIM V5.0 guidelines. If you are using an older BMEcat ETIM guideline version, we advice to update as soon as possible.
We have tried to achieve as much similarity as possible between the BMEcat 5.0 (and 4.0) and the Dutch format DICO (previuously named as SALES005) managed by Ketenstandaard. The complete ETIM guideline can be downloaded at the download section of ETIM International
ETIM International has published a revision of the recently released BMEcat 2005 ETIM V5.0 on August 24, 2021. The following changes have been made:
Both changes have been made to our import routine.
Please note that the Guideline and XSD still carry version 5.0 as notation.
If you have files according to previous ETIM guideline versions, we recommend that you upgrade to the latest version release August 24, 2021 (5.0.1) as soon as possible. Point your software or ICT partner to this online documentation of 2BA. It are not rules imposed by 2BA, but Extensible Markup Language rules, a standard of the World Wide Web Consortium.
Developing an XML message based on an XSD and the associated rules is a task that requires XML specialization.
To avoid disappointment, we recommend that you use a specialized software party with sufficient XML knowledge. Of course, there are also various PIM software parties affiliated with 2BA that export a valid dataset via an efficient route so that you can easily deliver your valuable data to 2BA.
2BA is conforming the data pool according to the Dutch standards of Ketenstandaard Bouw en Techniek with the INSBOU and DICO / SALES XML files. The supported exchange formats are mapped to the internal fields of the data model. Some internal fields may differ from the length or type as described in the guideline of the exchange formats. We create as much clarity as possible but there may be differences, which we mention in the mapping. For example, in BMEcat 2005 the short description has a length of 150 characters, in the data model only 70 characters.
The BMEcat 2005 ETIM V5.0.1 file should be validated according to the XSD to be sure of full compliance with 2BA. We recommend using the ETIM BMEcat validation tool (ETIM account needed) to validate your file.
There are a few exceptions in the current XSD (filedate: 2021-06-30).
Every country requires more fields then originally available in the BMEcat 2005 structure. In cooperation with ETIM Netherlands, we have defined country specific guidelines for the Netherlands.
Please use this UDX fields (UDX.EDXF.PRODUCT_CHARACTERISTICS) as defined in the ETIM guideline 5.0 starting at page 157 to page 172. The NL characteristics for BMEcat 2005 ETIM V5.0.1 differ from version 4.0. Please note that NL characteristics that are no longer present will not be accepted when you submit a BMEcat 2005 ETIM V5.0 dataset
The BMEcat 2005 ETIM V5.0 contains clear examples of how to define them in your data file.
A small number of NL characteristics are included in the regular product line. As a result, these have been removed as NL Characteristic:
The header of the BMEcat with ETIM guidelines 5.0 should be like the example below:
<BMECAT xmlns="https://www.etim-international.com/bmecat/50" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="https://www.etim-international.com/bmecat/50 https://www.etim-international.com/bmecat_etim_50.xsd" version="2005">
<HEADER>
<GENERATOR_INFO>Name generator</GENERATOR_INFO>
<CATALOG>
<LANGUAGE>dut</LANGUAGE>
<CATALOG_ID>ETIM-BMEcat-5.0</CATALOG_ID>
<CATALOG_VERSION>01.01</CATALOG_VERSION>
<CATALOG_NAME>Catalogname</CATALOG_NAME>
<DATETIME type="generation_date">
<DATE>2021-07-21</DATE>
</DATETIME>
<TERRITORY>NL</TERRITORY>
<CURRENCY>EUR</CURRENCY>
<MIME_ROOT>optional</MIME_ROOT>
</CATALOG>
<BUYER>
<BUYER_ID type="gln">8714252005929</BUYER_ID>
<BUYER_NAME>2BA</BUYER_NAME>
</BUYER>
<SUPPLIER>
<SUPPLIER_ID type="gln">8712345678910</SUPPLIER_ID>
<SUPPLIER_NAME>Company name</SUPPLIER_NAME>
</SUPPLIER>
<USER_DEFINED_EXTENSIONS>
<UDX.EDXF.VERSION>5.0</UDX.EDXF.VERSION>
</USER_DEFINED_EXTENSIONS>
</HEADER>
</BMECAT>
2BA supports complete or update (mutation) files of the BMECat 5.0. A complete BMEcat files has to contain all active products. A new complete file will overwrite all records in the database!. To define the file as a complete file, use T_NEW_CATALOG. Existing productrecords which are not present in the complete file will be set as “expired”. Existing trade itemsrecords which are not present in the complete file will be deleted.
Delivery of mutation files is also possible.
EXAMPLE complete files:
<T_NEW_CATALOG>
<PRODUCT mode="new">
</PRODUCT>
</T_NEW_CATALOG>
EXAMPLE mutation file:
<T_UPDATE_PRODUCTS>
<PRODUCT mode="update">
</PRODUCT>
</T_UPDATE_PRODUCTS>
2BA distinguishes two entities, the product information and related trade item information. Product information concerns data from the manufacturer about the manufactured product such as attachments and ETIM classification. The related trade item information contains all data indicating how to order the item such as gross price, order unit, minimum purchase amount and delivery time. In many cases (standard manufacturers), this information will be equal to each other, but a distinction can be made here for importers.
SUPPLIER_PID | Trade item number |
UDX.EDXF.GTIN | GTIN trade item |
MANUFACTURER_PID | Product number (smallest unpacked unit) |
INTERNATIONAL_PID type=”gtin” | GTIN product |
The product status codes are different between BMEcat 2005 ETIM V5.0 and the data model. The mapping is based on product status type, the value is informative (except for expired products). The product status will be set at product and trade item level (exept for expired products (model code 130).
The mapping of product status types versus the data model is available here:
EXAMPLE expired products:
<PRODUCT_STATUS type="others">discontinued</PRODUCT_STATUS>
EXAMPLE suspended products:
<PRODUCT_STATUS type="others">suspended<PRODUCT_STATUS>
It is possible for a manufacturer or supplier to distribute more than one type of package for the same product. According to the ETIM International Guidelines there are some strict rules.
For trade items, the logistic information can be given for each unique trade item in the elements UDX.EDXF.PACKING_UNITS, PRODUCT_LOGISTIC_DETAILS and UDX.EDXF.PRODUCT_CHARACTERISTIC. Measurements must be given in meters and weights must to be given in kilograms. If there are more than one trade items for the same product see chapter Multiple packing units for the same product. The mapping below applies to the packaging information for all trade items:
<UDX.EDXF.PACKING_UNITS>
<UDX.EDXF.PACKING_UNIT>
<UDX.EDXF.QUANTITY_MIN>1</UDX.EDXF.QUANTITY_MIN>
<UDX.EDXF.QUANTITY_MAX>1</UDX.EDXF.QUANTITY_MAX>
<UDX.EDXF.PACKING_UNIT_CODE>CT</UDX.EDXF.PACKING_UNIT_CODE>
<UDX.EDXF.PACKING_PARTS>1</UDX.EDXF.PACKING_PARTS>
<UDX.EDXF.WEIGHT>7.6</UDX.EDXF.WEIGHT>
<UDX.EDXF.LENGTH>0.34</UDX.EDXF.LENGTH>
<UDX.EDXF.WIDTH>0.52</UDX.EDXF.WIDTH>
<UDX.EDXF.DEPTH>0.52</UDX.EDXF.DEPTH>
<UDX.EDXF.GTIN>GTIN trade item</UDX.EDXF.GTIN>
</UDX.EDXF.PACKING_UNIT>
</UDX.EDXF.PACKING_UNITS>
The mapping of packing codes versus 2BA is available here
The country of origin is the country of shipment of the order. The country of production is the actual production location. Please use the country specific UDX.EDXF.PRODUCT_CHARACTERISTIC field “Country of production origin” with code “NL_006”, see chapter 11 of the ETIM 5.0 guideline.
<PRODUCT_LOGISTIC_DETAILS>
<CUSTOMS_TARIFF_NUMBER>
<CUSTOMS_NUMBER>12345678</CUSTOMS_NUMBER>
</CUSTOMS_TARIFF_NUMBER>
<COUNTRY_OF_ORIGIN>NL</COUNTRY_OF_ORIGIN>
</PRODUCT_LOGISTIC_DETAILS>
<UDX.EDXF.PRODUCT_CHARACTERISTIC>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_CODE>NL_006</UDX.EDXF.PRODUCT_CHARACTERISTIC_CODE>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_NAME> Country of production origin </UDX.EDXF.PRODUCT_CHARACTERISTIC_NAME>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING>DE</UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING>
</UDX.EDXF.PRODUCT_CHARACTERISTIC>
For each trade item can be defined how the trade item can be ordered, on which unit the price is based and how the product can be used. The mapping of the order and price details in the import of BMEcat 5.0 differs from older guideline versions.
Data model: | Formula: | |
---|---|---|
QuantityOfUseUnits | = | NO_CU_PER_OU |
Gross price | = | PRICE_AMOUNT |
Gross price per purchase unit | = | (PRICE_AMOUNT / PRICE_QUANTITY) * PRICE_UNIT_FACTOR |
Gross price per content unit | = | ((PRICE_AMOUNT / PRICE_QUANTITY) * PRICE_UNIT_FACTOR) / NO_CU_PER_OU |
Please note, the nonbinding recommended (retail) price (nrp), suggested retail price is within BMEcat specified including sales tax. The import proces reduces the specified value with the specified VAT, because the suggested price in the data model is without sales tax.
BMEcat supports an unlimited number of prices per trade item. Future prices can additionally be included in the message where the effective date of the price VALID_START_DATE is in the future. Price information with a future effective date will only be available for an export in BMEcat format when the specified date has been reached.
You cannot remove previously specified future prices from the data pool. If you want to correct a future price, you can submit a new future price with the same effective date as that of the “incorrect” price. The old future price is then overwritten.
The surcharge type “WEEE” is mapped to the Dutch “Afvalbeheersbijdrage”, model code ‘AEO’. Other material surcharge types are mapped to the model code ‘Overig’, model code ‘ADR’. The mapping of surcharge types versus the data model is available here.
<UDX.EDXF.SURCHARGE_LIST>
<UDX.EDXF.SURCHARGE>
<UDX.EDXF.SURCHARGE_TYPE>recycling WEEE</UDX.EDXF.SURCHARGE_TYPE>
<UDX.EDXF.SURCHARGE_MANNER>base</UDX.EDXF.SURCHARGE_MANNER>
<UDX.EDXF.SURCHARGE_PRICE_AMOUNT>0.28</UDX.EDXF.SURCHARGE_PRICE_AMOUNT>
</UDX.EDXF.SURCHARGE>
</UDX.EDXF.SURCHARGE_LIST>
Given the various purposes, different types of descriptions are possible to describe a trade item or product. There are three possibilities:
<PRODUCT_DETAILS>
<DESCRIPTION_SHORT lang="dut">BG/SR 611-4/6-0 SM Brievenbus</DESCRIPTION_SHORT>
<DESCRIPTION_SHORT lang="eng">BG/SR 611-4/6-0 SM Letterbox</DESCRIPTION_SHORT>
<DESCRIPTION_LONG lang="dut">Vrijstaande brievenbus met staande buis voor de opname van een brievenbus- of opbergvakmodule. 8 moduleplaatsen voor de opname van infobordmodules, vlaklampen en functiemodules in het bovenste deel. Spraakmodule en verdere functiemodules in een ergonomisch gemakkelijk te bedienen bereik. Aluminiumprofiel met bodemflens. Brievenbusbehuizing met aluminium achterwand kompleet met coating resp. gelakt. Kompleet met brievenbusbehuizing, staande buis en bodemflens met bevestigingsaccessoires zoals duvels voor zware lasten etc.</DESCRIPTION_LONG>
<DESCRIPTION_LONG lang="eng">Free-standing letterbox with standpipes to accommodate a letterbox or storage compartment module. 8 module slots to accommodate info sign modules, surface area lights and function modules in the upper section. Intercom module and additional functional modules within easy ergonomical operating reach. Aluminium profile with base flange. Letterbox housing with aluminium rear panel with complete coating / paintwork finish. Complete with letterbox housing, standpipes and base flange with fixing accessories such as heavy-duty dowels, etc.</DESCRIPTION_LONG>
</PRODUCT_DETAILS>
<UDX.EDXF.PRODUCT_CHARACTERISTIC>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_CODE>NL_008</UDX.EDXF.PRODUCT_CHARACTERISTIC_CODE>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_NAME>Long ERP description</UDX.EDXF.PRODUCT_CHARACTERISTIC_NAME>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING>This field is used for a long ERP description</UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING lang="dut">NL Dit veld wordt gebruikt als lange omschrijving</UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING lang="eng">ENG This field is used for a long ERP description</UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING>
</UDX.EDXF.PRODUCT_CHARACTERISTIC>
When a Safety Data Sheet (SDS) is applicable, these three elements are mandatory:
<SPECIAL_TREATMENT_CLASS type="SDS">true</SPECIAL_TREATMENT_CLASS>
<UDX.EDXF.MIME>
<UDX.EDXF.MIME_SOURCE>MD03.pdf</UDX.EDXF.MIME_SOURCE>
<UDX.EDXF.MIME_CODE>MD03</UDX.EDXF.MIME_CODE>
<UDX.EDXF.MIME_FILENAME>safety data sheet MD03</UDX.EDXF.MIME_FILENAME>
</UDX.EDXF.MIME>
<UDX.EDXF.PRODUCT_CHARACTERISTIC>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_CODE>NL_005</UDX.EDXF.PRODUCT_CHARACTERISTIC_CODE>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_NAME> List date_MSDS</UDX.EDXF.PRODUCT_CHARACTERISTIC_NAME>
<UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING>2018-05-31</UDX.EDXF.PRODUCT_CHARACTERISTIC_VALUE_STRING>
</UDX.EDXF.PRODUCT_CHARACTERISTIC>
When Registration, Evaluation, Authorization and restriction of Chemicals (REACH) is applicable for the record, these three elements are mandatory:
<UDX.EDXF.REACH>
<UDX.EDXF.REACH.LISTDATE>2021-07-21</UDX.EDXF.REACH.LISTDATE>
<UDX.EDXF.REACH.INFO>true</UDX.EDXF.REACH.INFO>
</UDX.EDXF.REACH>
<UDX.EDXF.MIME>
<UDX.EDXF.MIME_SOURCE>https://www.deeplink.nl/Reach.pdf</UDX.EDXF.MIME_SOURCE>
<UDX.EDXF.MIME_CODE>MD05</UDX.EDXF.MIME_CODE>
<UDX.EDXF.MIME_FILENAME>reach deeplink MD05</UDX.EDXF.MIME_FILENAME>
</UDX.EDXF.MIME>
Pay attention. If the REACH certificate attachment is missing, the value for REACH, as described in the ETIM Guideline, will be exported as ‘no data’ for a BMEcat 2005 export.
The element PRODUCT_FEATURES can be used for the ETIM Classification. REFERENCE_FEATURE_SYSTEM_NAME must be filled with the ETIM version of the data. In the format ETIM-x.x. or like DYNAMIC.
If a value cannot be assigned, according to the ETIM guideline the data supplier has the opportunity to use a minus sign. Values with a minus sign will be skipped by 2BA. Instead use one of the following reasons in FVALUE_DETAILS:
According to the ETIM 5.0 guidelines the UDX.EDXF.MIME_INFO element should be used to exchange attachments. Because of the different export formats the predefined values (MD codes) are mapped to the attachment type code list.
The mapping of MD codes versus the data model is available here
The import routine automatically creates an MD5 Hash from each downloaded attachment/file. A MD5 Hash makes it possible to determine whether it is a new file or a duplicate. The MD5 Hash is sent per attachment with a dataset export using the attachment attribute AttachmentHash. In addition, the original file name published by the data supplier is also included in the OrginalFileSource attribute. Unfortunately, unlike the DICO/SALES005 format, the BMEcat 2005 ETIM exchange format does not provide the ability to communicate such attributes. Optionally, you can also request an overview of attachments including associated attributes via the AttachmentIndex exchange format. The AttachmentIndex is standard within the PAB exchange format.
In the data model reference items will be mapped at product level, not on trade item level.
The mapping of product references versus the data model is available here.