Skip to main content

BMEcat 2005 - ETIM-7.0 Classification export

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, the international classification standard for technical products.

To export data including classification specific attributes we created the BMEcat 2005 - ETIM-7.0 Classification export.

1. Add the BMEcat 2005 - ETIM-7.0 Classification export

Go to Exports and click on the blue Add Export button in the top right corner.

Choose the export ** BMEcat 2005 - ETIM-7.0 Classification** and click on Add.

Add a destination of your choice e.g. the Productsup Server.


2. Setup Dataflow to get classification specific attributes

Go to the Dataflowand connect your data accordingly. The class code column should contain the ETIM like EC012345.

If you export, our platform will check the ETIM within the class code column and generate the classification specific attributes. You can choose the classification in the Dataflow to map the classification specific attributes.


3. Add rules to classification specific attributes

In the Data View for the "BMEcat 2005 - ETIM-7..." you will find a filter for the ETIM class in the classification dropdown.


To see and edit the classification specific attributes you have to select an ETIM class in the classification dropdown (which is "All classifications" by default).

You will see all basic columns like SUPPLIER_PID, PRODUCT@mode or Class code for all classifications also if you only have selected a specific classification. Specific attributes are only shown for the classification they are needed for.


4. Provide Header Information

BMEcat files require detailed information about the supplier and catalog content. This information can be added under the settings tab in the export setup. In most cases the neccessary details will be provided by partner.


5. Indexed Attributes

5.1 What are indexed attributes?

Some attributes can have more than one instance, for example descriptions, which can come in several languages for an item.We are referring to these attribues as indexed attributes. Some of the indexed attributes consist of several sub-attributes. The relationship between these sub-attributes is marked by an index number per attribute in the output file.

5.2 How is that reflected in the setup?

To prevent the user from having to create a field in the dataflow for every instance, Productsup is using a delimiter within the fields, to let the user add several instances.

This is best to be explained with an example:

The attribute Description Short can contain short descriptions for several languages. Sub-attributes are the description itself and the language.The user needs to populate the two sub-attributes DESCRIPTION_SHORT@lang and DESCRIPTION_SHORT, so the output file will be properly populated.It is imported to provide the information for the instances in the same order in every sub-attribute.

  • Description Short DE: Hochwertiges Werkzeug

  • Description Short EN: High quality tool

  • Description Short FR: Outil de haute qualité

This needs to be added to the sub-attributes like this:




Hochwertiges Werkzeug<###>High quality tool<###>Outil de haute qualité

In case one of the sub-attributes is missing for an instance, an empty value needs to be used. Just skipping it will lead to inconsistencies within the output file.

5.3 List of indexed attributes and their sub-attributes

Note: When using the ETIM-7.0 Classification export, the classification will take care of the Product Features, so there is no need to manually adjust them.

Description Short


Description Long


Product Details


Product Features






User Defined Extensions



Description Very Short


Packing Unit


Product Characteristic