Back to the wiki

BMEcat

What is BMEcat?

BMEcat is an XML-based standard for exchanging electronic product catalogs between manufacturers, suppliers, retailers, and purchasing companies. It defines how product data is structured in a file. This includes item numbers, descriptions, prices, features, and media references. The receiving system can then import the data without manual rework.

BMEcat was initiated by the German Association for Supply Chain Management, Procurement and Logistics (BME) and developed together with Fraunhofer IAO and several universities. The standard is free to use and especially widespread in B2B environments in German-speaking countries. Typical areas of use include the electrical, HVAC, and construction industries, manufacturing, as well as procurement platforms and marketplaces.

How is a BMEcat File structured?

A BMEcat file is an XML document with clearly defined elements. The most important building blocks are:

  • Header: Information about the catalog itself, such as catalog ID, version, language, currency, sender, and recipient.
  • Catalog structure: Product groups to which the individual items are assigned.
  • Articles or products: For each item, details such as order number, short and long description, manufacturer, GTIN/EAN, and order unit.
  • Features: Technical properties such as dimensions, performance, or material, often structured according to a classification system.
  • Prices: List, net, or customer-specific prices, including price tiers and validity periods.
  • Media data (MIME info): References to product images, data sheets, logos, or safety data sheets, each with file type and intended use.

BMEcat also distinguishes between transaction types: a completely new catalog (T_NEW_CATALOG), product data updates (T_UPDATE_PRODUCTS), and price-only updates (T_UPDATE_PRICES). This means you don’t have to transfer the entire catalog with every change.

In practice, you will mainly come across two versions: BMEcat 1.2, which established itself as the de facto standard and is still widely used, and BMEcat 2005 with extended functionality. The version is stated in the file header. The two versions are not directly interchangeable, so sender and recipient should agree on the version in advance.

BMEcat, ETIM and ECLASS: the Differences

BMEcat is often mentioned in the same breath as ETIM and ECLASS. The difference: BMEcat is the transport format, while ETIM and ECLASS are classification systems. They define which features a product in a specific class has. BMEcat does not prescribe a classification itself. It carries whichever one sender and recipient have agreed on.

StandardTypePurposeTypical Use
BMEcatExchange format (XML)Transfers catalog, price, and media data between systemsCross-industry, mainly B2B in the DACH region
ETIMClassification systemDefines product classes and features for technical productsElectrical, HVAC, construction
ECLASSClassification systemCross-industry standard for product classes and featuresManufacturing, procurement, engineering

For ETIM-classified data, the ETIM BMEcat guideline specifies exactly how BMEcat is populated in this context. You can find more about ECLASS directly at ECLASS e.V.

What Role do PIM and DAM play in BMEcat?

A BMEcat file is only as good as the data it is built from. It is usually generated from a Product Information Management (PIM) system. That’s where you maintain item texts, attributes, and classifications centrally and output them as BMEcat via data export.

The images, videos, and documents themselves are not part of the XML file. BMEcat only contains references to the media files. This is where Digital Asset Management (DAM) comes in. It provides approved assets in the required formats and delivers unique file names or URLs. With clean metadata, it makes sure the right image ends up with the right item. If media is missing or references are outdated, items appear incomplete on the recipient’s side or the catalog needs to be corrected.

Data flow from PIM and DAM via the BMEcat file to the target systems

When your DAM is connected to your PIM and delivers assets to each channel via Channels, the media side of your BMEcat catalogs stays consistent and up to date.