Everything you need to know about BMEcat

Table of Contents

• What is a BMEcat?
• Why BMEcat?
• Differences between BMEcat 1.2 and BMEcat 2005
• How can a BMEcat be created?
• Which fields does simple system read?
• Supported quantity units
• Common errors and solutions
• FAQ

What is a BMEcat?

BMEcat is a standardised, XML-based exchange format for electronic product catalogues. The name stands for Bundesverband Materialwirtschaft, Einkauf und Logistik e.V. – catalog. The standard was developed in 1999 by the BME in collaboration with leading companies and research institutions, and is the dominant catalogue exchange format in German-speaking and European B2B e-commerce.

A BMEcat enables the automated exchange of product data between vendors and purchasing organisations or procurement platforms such as simple system. The catalogue contains structured information about articles — from article numbers and descriptions to prices and order units, as well as images and data sheets.

Why BMEcat?

Unlike proprietary formats (e.g. Excel spreadsheets), BMEcat provides a uniform structure that can be processed automatically by all parties involved. This means fewer manual errors, faster catalogue updates, and higher data quality. For simple system, BMEcat is the only accepted format for catalogue uploads.

Basic structure of a BMEcat

• HEADER — Contains metadata about the catalogue: catalogue ID, language, currency, vendor information, validity period (not used by simple system).
• TRANSACTION AREA — Contains the actual product data and product categories. There are three transaction types, which are processed identically on simple system:
  • T_NEW_CATALOG — Transfers a completely new catalogue
  • T_UPDATE_PRODUCTS — Updates individual products in an existing catalogue
  • T_UPDATE_PRICES — Updates prices only

For simple system, "T_NEW_CATALOG" is generally used, as each upload transfers the complete catalogue anew.

Differences between BMEcat 1.2 and BMEcat 2005

The most obvious difference concerns the naming of elements. In version 1.2, products are referred to as "Article"; in version 2005, as "Product":

Functional differences

BMEcat 1.2 is the older, leaner version. It is well-suited for simple product catalogues with standard prices and is backwards-compatible with BMEcat 1.01. Most simple system vendors use this version successfully.

BMEcat 2005 additionally offers extended capabilities: support for configurable products, dynamic pricing models (price formulas, price factors), extended logistics information, improved multilingualism and internationalisation, and support for multi-vendor catalogues.

How can a BMEcat be created?

Several options are available for creating a BMEcat catalogue:

• PIM systems (Product Information Management) — Professional PIM systems (e.g. Akeneo, Contentserv, mediacockpit, Stibo STEP) offer integrated BMEcat export functions. These systems are suited to companies with large product assortments and regular catalogue updates.
• ERP systems (Enterprise Resource Planning) — Many ERP systems (SAP, Microsoft Dynamics, etc.) have modules or extensions for BMEcat export. Check whether your ERP offers this functionality.
• simple system Offline Generator (free) — The Offline BMEcat Generator from simple system is a free HTML tool that enables BMEcat 1.2 creation directly in the browser. It is specifically tailored to the validation rules of the simple system platform and produces a ready-to-use, validated XML file.
  • How it works: Enter your product data into the provided Excel template, drag the file into the tool, and download the generated BMEcat XML.
  • Advantages: Runs entirely offline in the browser (no data leaves your computer), no installation required, integrated plausibility check per article with error and warning log.
  • Requirements: Current browser (Chrome, Edge, Firefox) and Microsoft Excel (2007 or later) or LibreOffice/OpenOffice for the template.
  • Full instructions are available here.
• Paid catalogue service from simple system — If you are unable to create a BMEcat yourself, simple system can also connect you with service partners who can handle catalogue creation on your behalf. Contact Vendor Management at vendormanagement@simplesystem.com.
• Sepia BMEcat Converter (third-party) — The Sepia BMEcat Converter is a free open-source tool that enables BMEcat creation from an Excel file. It is used by many simple system vendors and is the recommended tool for vendors without their own PIM system.
  • How it works: Enter your product data into an Excel template and then convert it into a valid BMEcat XML file using the converter.
  • Requirements: Microsoft Excel (version 2000 or later) or LibreOffice/OpenOffice.
  • Download and installation: The converter is available at sepia.de.
• Specialised catalogue software — Providers such as nexoma, e-proCAT, or Pro3Con offer specialised software for creating and validating BMEcat catalogues.

Which fields does simple system read?

The following overview shows all fields supported by simple system, grouped by data category. Mandatory fields are marked with "Yes".

Article master data

<ARTICLE_DETAILS>
    <SUPPLIER_AID>123456</SUPPLIER_AID>
    <BUYER_AID>ABC-789</BUYER_AID>
    <MANUFACTURER_AID>M-001122</MANUFACTURER_AID>
    <MANUFACTURER_NAME>Example Manufacturer GmbH</MANUFACTURER_NAME>
    <EAN>4006381333931</EAN>
    <DESCRIPTION_SHORT>Article name</DESCRIPTION_SHORT>
    <DESCRIPTION_LONG>Detailed and comprehensive article description with all relevant information.</DESCRIPTION_LONG>
    <DELIVERY_TIME>3</DELIVERY_TIME>

    <!-- optional multiple KEYWORD entries -->
    <KEYWORD>Screw</KEYWORD>
    <KEYWORD>Stainless steel</KEYWORD>
    <KEYWORD>M4x20</KEYWORD> 
</ARTICLE_DETAILS>

Classification 

<ARTICLE_FEATURES>
    <REFERENCE_FEATURE_SYSTEM_NAME>ECLASS-5.1</REFERENCE_FEATURE_SYSTEM_NAME>
    <REFERENCE_FEATURE_GROUP_ID>40010101</REFERENCE_FEATURE_GROUP_ID>
</ARTICLE_FEATURES>

Catalogue Group System

The CATALOG_GROUP_SYSTEM allows vendors to define their own product category hierarchy in the BMEcat. simple system processes this group structure as a navigation structure in the vendor catalogue. Articles without a group assignment can be imported in full — the group structure is entirely optional.

The CATALOG_GROUP_SYSTEM is specified in the T_NEW_CATALOG block. Articles are assigned to groups via ARTICLE_TO_CATALOGGROUP (BMEcat 1.2) or PRODUCT_TO_CATALOGGROUP (BMEcat 2005).

Fields in CATALOG_GROUP_SYSTEM

Fields in ARTICLE_TO_CATALOGGROUP

<!-- Definition of group structure (in T_NEW_CATALOG block, before ARTICLE elements) -->
<CATALOG_GROUP_SYSTEM>
    <GROUP_SYSTEM_NAME>Product Categories</GROUP_SYSTEM_NAME>

    <CATALOG_STRUCTURE type="root">
        <GROUP_ID>1</GROUP_ID>
        <GROUP_NAME>Tools</GROUP_NAME>
        <GROUP_ORDER>1</GROUP_ORDER>
    </CATALOG_STRUCTURE>

    <CATALOG_STRUCTURE type="node">
        <GROUP_ID>1.1</GROUP_ID>
        <GROUP_NAME>Hand tools</GROUP_NAME>
        <PARENT_ID>1</PARENT_ID>
        <GROUP_ORDER>1</GROUP_ORDER>
    </CATALOG_STRUCTURE>
</CATALOG_GROUP_SYSTEM>

<!-- ... all ARTICLE elements ... -->

<!-- Article-group assignment: AFTER all ARTICLE elements, at the end of T_NEW_CATALOG -->
<ARTICLE_TO_CATALOGGROUP>
    <ART_ID>123456</ART_ID>
    <CATALOG_GROUP_ID>1.1</CATALOG_GROUP_ID>
</ARTICLE_TO_CATALOGGROUP>
<ARTICLE_TO_CATALOGGROUP>
    <ART_ID>123456</ART_ID>
    <CATALOG_GROUP_ID>1</CATALOG_GROUP_ID>
</ARTICLE_TO_CATALOGGROUP>

 Do not confuse: GROUP_ID vs. REFERENCE_FEATURE_GROUP_ID 

 hese two fields serve different purposes and are processed independently: 

Possible errors and pitfalls

Order information

<ARTICLE_ORDER_DETAILS>
    <QUANTITY_MIN>1</QUANTITY_MIN>
    <QUANTITY_INTERVAL>1</QUANTITY_INTERVAL>
    <ORDER_UNIT>PCE</ORDER_UNIT>
    <NO_CU_PER_OU>24</NO_CU_PER_OU>
    <CONTENT_UNIT>PCE</CONTENT_UNIT>
</ARTICLE_ORDER_DETAILS>

Price information

<ARTICLE_PRICE_DETAILS>

    <!-- Standard price -->
    <ARTICLE_PRICE price_type="net_list">
        <PRICE_AMOUNT>12.50</PRICE_AMOUNT>
        <PRICE_CURRENCY>EUR</PRICE_CURRENCY>
        <PRICE_QUANTITY>1</PRICE_QUANTITY>
    </ARTICLE_PRICE>

    <!-- Tiered price example -->

    <!-- Standard price (tier 1 from quantity 1) -->
    <ARTICLE_PRICE price_type="net_list">
        <LOWER_BOUND>1</LOWER_BOUND>
        <PRICE_AMOUNT>12.50</PRICE_AMOUNT>
        <PRICE_CURRENCY>EUR</PRICE_CURRENCY>
        <PRICE_QUANTITY>1</PRICE_QUANTITY>
    </ARTICLE_PRICE>

    <!-- Tiered price 2 (from 10 units) -->
    <ARTICLE_PRICE price_type="net_list">
        <LOWER_BOUND>10</LOWER_BOUND>
        <PRICE_AMOUNT>11.00</PRICE_AMOUNT>
        <PRICE_CURRENCY>EUR</PRICE_CURRENCY>
        <PRICE_QUANTITY>1</PRICE_QUANTITY>
    </ARTICLE_PRICE>

</ARTICLE_PRICE_DETAILS>

Features / product properties

<ARTICLE_FEATURES>

    <!-- Feature 1 -->
    <FEATURE>
        <FNAME>Length</FNAME>
        <FVALUE>20</FVALUE>
        <FUNIT>mm</FUNIT>
    </FEATURE>

    <!-- Feature 2 -->
    <FEATURE>
        <FNAME>Material</FNAME>
        <FVALUE>Stainless steel</FVALUE>
    </FEATURE>

    <!-- Feature 3 (multiple values example) -->
    <FEATURE>
        <FNAME>Colour</FNAME>
        <FVALUE>Red</FVALUE>
        <FVALUE>Black</FVALUE>
    </FEATURE>

</ARTICLE_FEATURES>

Media / MIME data

<MIME_INFO>

    <!-- Recommended main image (as URL) -->
    <MIME>
        <MIME_SOURCE>https://example.com/images/product_123_main.jpg</MIME_SOURCE>
        <MIME_TYPE>image/jpeg</MIME_TYPE>
        <MIME_PURPOSE>normal</MIME_PURPOSE>
        <MIME_DESCRIPTION>Product image</MIME_DESCRIPTION>
    </MIME>

    <!-- Detail image local (optional) -->
    <MIME>
        <MIME_SOURCE>images/product_123_detail.jpg</MIME_SOURCE>
        <MIME_TYPE>image/jpeg</MIME_TYPE>
        <MIME_PURPOSE>detail</MIME_PURPOSE>
        <MIME_DESCRIPTION>Detail view</MIME_DESCRIPTION>
    </MIME>

    <!-- Data sheet as URL -->
    <MIME>
        <MIME_SOURCE>https://example.com/docs/product_123_datasheet.pdf</MIME_SOURCE>
        <MIME_TYPE>application/pdf</MIME_TYPE>
        <MIME_PURPOSE>data_sheet</MIME_PURPOSE>
        <MIME_DESCRIPTION>Data sheet (PDF, online)</MIME_DESCRIPTION>
    </MIME>

</MIME_INFO>

Product references

simple system processes PRODUCT_REFERENCE elements in the BMEcat. These elements allow articles to be linked to one another — for example as accessories, spare parts, or similar products. The links are displayed on the product detail page on the platform, improving discoverability and supporting buyers' purchasing decisions.

<!-- Accessory -->
<PRODUCT_REFERENCE type="accessories">
    <PROD_ID_TO>Wera_05134001001</PROD_ID_TO>
</PRODUCT_REFERENCE>

<!-- Spare part -->
<PRODUCT_REFERENCE type="sparepart">
    <PROD_ID_TO>Wera_05134001001</PROD_ID_TO>
</PRODUCT_REFERENCE>

<!-- Similar product -->
<PRODUCT_REFERENCE type="similar">
    <PROD_ID_TO>Wera_05134001001</PROD_ID_TO>
</PRODUCT_REFERENCE>

Important notes

• The linked article (PROD_ID_TO) must exist in the same catalogue with the same SUPPLIER_AID/PID — otherwise the link is ignored.
• Multiple PRODUCT_REFERENCE elements with the same or different type attributes can be specified per article.
• The link is one-directional: if article A points to article B, article B is not required to link back.
• Invalid PROD_ID_TO references (e.g. pointing to non-existent articles) are ignored and do not cause the catalogue upload to abort.

 Supported quantity units (ORDER_UNIT / CONTENT_UNIT) 

simple system supports the following unit codes:

If an unsupported unit is used, it is accepted but displayed without translation.

Common errors and solutions

General errors

Field-level errors

Structural errors

• Character encoding: BMEcat files should be encoded in UTF-8.
• MIME_ROOT: Specifying a MIME_ROOT in the header is not recommended. If used regardless, all image paths must be relative to this root.
• Tiered prices: For articles with tiered prices, add another row with the same SUPPLIER_AID/PID, a new price, and a different LOWER_BOUND.