Cookie Settings

    We use cookies to improve your experience on our website. You can choose which cookie categories you want to accept. Learn more

    Responsible Party
    Contact Form
    uNaice
    Back to Blog
    Data Management

    BMEcat – Standard for Electronic Product Catalogs in B2B

    Andreas WenningerMarch 09, 202610 min read
    BMEcat – Standard for Electronic Product Catalogs in B2B

    Companies in B2B commerce need to exchange large amounts of product information between different systems. Manufacturers supply data to retailers, retailers to marketplaces or purchasing systems. Without standardized formats, this exchange often leads to manual post-processing, data loss, or inconsistencies.

    An important standard for solving this problem is BMEcat. The standard defines a structured format for electronic product catalogs and enables the automated exchange of product data between different IT systems.

    BMEcat has established itself as the standard for electronic catalog exchange, particularly in German-speaking countries, and is supported by many ERP, PIM, and e-procurement systems.

    What is the BMEcat standard?

    The BMEcat standard is an XML-based exchange format for electronic product catalogs in the B2B environment. It defines how product information must be structured so that different systems can process it automatically.

    The standard was initiated by the German Association for Materials Management, Purchasing and Logistics (BME) and developed in collaboration with industrial companies and research institutions. Further information can be found at Wikipedia or at Mittelstand Digital.

    The central goal of BMEcat is to standardize the electronic exchange of product catalogs between suppliers and purchasing systems. This enables companies to automatically transfer product data and process it further in their systems.

    Typical data transferred via BMEcat includes item numbers, product descriptions, technical characteristics, prices, delivery information, and references to images or documents.

    Background and development of the BMEcat standard

    The development of BMEcat began in the late 1990s, when companies were increasingly introducing electronic procurement processes. At that time, digital product catalogs already existed, but there was no uniform standard for exchanging this data.

    The German Federal Association for Materials Management, Purchasing and Logistics therefore launched an initiative to develop a standardized catalog format. Among others, companies from industry and software development as well as research institutions such as the Fraunhofer Institute were involved.

    The most important versions of the standard are shown in the following overview:

    VersionPublicationSignificance
    BMEcat 1.01999first version of the standard
    BMEcat 1.22001extensions for classifications
    BMEcat 20052005extensions for complex product and price structures

    In practice, BMEcat 1.2 and BMEcat 2005 are primarily used today.

    Technical basis: BMEcat and XML

    The BMEcat standard is based on XML (Extensible Markup Language). XML is a structured markup language that can be used to clearly define data and store it in a machine-readable format. XML enables systems to automatically interpret, import, and validate data.

    A greatly simplified example of a BMEcat entry looks like this:

    <PRODUCT>
       <PRODUCT_ID>12345</PRODUCT_ID>
       <PRODUCT_NAME>Industrial drill bit 10 mm</PRODUCT_NAME>
       <DESCRIPTION_SHORT>Drill bit for metal</DESCRIPTION_SHORT>
       <PRICE_AMOUNT>12.50</PRICE_AMOUNT>
    </PRODUCT>

    In real catalogs, the structures are much more extensive and contain numerous additional fields for technical characteristics, logistics data, or classifications.

    Structure of a BMEcat catalog

    A BMEcat document follows a clearly defined structure. This structure ensures that systems can interpret the information contained therein unambiguously.

    Header

    The header contains metadata about the entire catalog. This includes, for example, the name of the catalog, the language, the currency used, and information about the supplier and recipient of the catalog.

    It may also contain information about the date of creation or the validity of the catalog. This information helps the receiving systems to classify the catalog correctly.

    Product information

    The main part of a BMEcat document contains the actual product data.

    CategoryExamples
    product identificationitem number, manufacturer ID
    scalabilitygrowth without system change
    product descriptionproduct name, short description, long text
    price informationunit price, graduated prices
    logistics datapackaging units, delivery times
    technical featuresmaterial, dimensions, technical properties

    Additional fields can be added depending on the industry.

    Multimedia data

    In addition to structured product information, additional content can also be transferred, such as product images, technical data sheets, assembly instructions, or certificates. This content is usually stored in the BMEcat catalog as references.

    Schema: Structure of a BMEcat catalog

    A BMEcat catalog follows a clearly defined XML structure, which can be simplified as follows:

    BMECAT
    │
    ├── HEADER
    │     ├── Catalog Information
    │     ├── Supplier Information
    │     └── Buyer Information
    │
    ├── CATALOG STRUCTURE
    │     ├── Product Categories
    │     └── Classification References
    │
    ├── PRODUCT
    │     ├── Product Identification
    │     ├── Product Description
    │     ├── Product Features
    │     ├── Prices
    │     ├── Logistics Data
    │     └── Multimedia References
    │
    └── USER_DEFINED_EXTENSIONS
          └── Optional custom attributes

    The most important elements can be summarized as follows:

    AreaContent
    HEADERmetadata for the catalog, supplier, language, currency
    CATALOG STRUCTUREcategories and classification systems
    PRODUCTactual product data
    USER_DEFINED_EXTENSIONSadditional, customer-specific fields

    This structure makes it possible to transfer complete product catalogs in a single file.

    BMEcat in conjunction with classifications

    The BMEcat standard primarily describes the structure of a product catalog, but not the semantic classification of products. Additional classification systems are therefore often used to classify products.

    The most important classifications include:

    ClassificationArea of application
    ECLASS (eCl@ss)cross-industry product classification
    ETIMelectrical engineering and technical products
    UNSPSCinternational classification system for procurement

    By combining BMEcat with such classifications, products can be clearly described and identified across systems. For more information, see our articles on ECLASS and ETIM.

    Classification is usually stored in the BMEcat catalog via corresponding references. This allows systems to automatically categorize and compare products.

    BMEcat vs. ECLASS vs. ETIM – Differences between the standards

    BMEcat is often used in conjunction with classification standards such as ECLASS (eCl@ss) or ETIM. These standards fulfill different tasks in product data management.

    While BMEcat describes the exchange of product catalogs, ECLASS and ETIM define the classification and structure of technical characteristics of products.

    StandardTypePurposeExample
    BMEcatdata exchange formattransfer of complete product catalogscatalog export from a manufacturer
    ECLASS (eCl@ss)classification standardstructured product classificationclassification of technical products
    ETIMclassification standardstandardized product featureselectrical engineering products

    A typical scenario looks like this:

    A manufacturer creates its product catalog in BMEcat format. Within this catalog, products are assigned an ECLASS or ETIM classification. This enables a retailer's purchasing system not only to import the catalog, but also to automatically categorize products and compare technical features.

    Typical areas of application for BMEcat

    The BMEcat standard is primarily used in the B2B environment, where large product catalogs are regularly exchanged between companies.

    E-procurement

    Many companies use electronic procurement systems. Suppliers provide their product catalogs in BMEcat format so that they can be automatically imported into the purchasing system. Purchasers can then order directly from these electronic catalogs.

    B2B marketplaces

    B2B marketplaces also frequently use BMEcat as an import format for product data. Retailers can provide their product catalogs in a standardized format so that marketplaces can automatically integrate the data.

    PIM and ERP systems

    Product information management (PIM) and ERP systems often use BMEcat as an exchange format for product data.

  1. manufacturer → retailer: product catalog is provided
  2. retailer → marketplace: product data is exported
  3. PIM → online shop: structured data export
  4. Typical challenges with BMEcat data

    Although BMEcat is a clearly defined standard, challenges often arise in practice when creating or processing BMEcat catalogs.

    A common reason for this is that although the standard specifies the structure, many fields are optional. Companies sometimes interpret these fields differently or use individual extensions.

    ChallengeDescription
    inconsistent product attributesdifferent names for the same characteristics
    missing classificationproducts are not classified with ECLASS or ETIM
    incomplete datamissing technical characteristics or descriptions
    individual extensionsadditional fields outside the standard
    different BMEcat versionse.g., mixture of BMEcat 1.2 and BMEcat 2005

    These challenges often mean that imported catalogs must first be normalized, structured, or enriched before they can be used in target systems.

    You can find out why data preparation is so important in our articles Data preparation explained simply and Data quality: Definition, consistency, and data integrity in practice for companies.

    BMEcat and Product Information Management (PIM)

    In many companies, BMEcat is closely linked to Product Information Management (PIM). PIM systems are used to centrally manage and structure product data and make it available for various channels.

    A typical process looks like this:

    1.data collection: product data is collected in the PIM system
    2.data structuring: attributes and classifications are assigned
    3.data enrichment: images, documents, or additional features
    4.export: product catalog is generated in BMEcat format

    The BMEcat format is often used in this process as an export or exchange format for transferring product catalogs to partner companies or purchasing systems.

    Importance of BMEcat for modern product data processes

    With the increasing digitization of supply chains and procurement processes, the structured exchange of product data is becoming increasingly important.

    Standards such as BMEcat play a central role in this because they create a common technical basis for data exchange between companies.

    In combination with classifications such as ECLASS or ETIM and PIM systems, this creates an infrastructure that enables companies to efficiently manage, exchange, and process product data.

    Especially in the B2B environment with large product catalogs, BMEcat therefore often forms an important building block for scalable data processes and automated procurement systems.

    Automated preparation of product data for BMEcat

    In practice, product data is often available in different formats—for example, in Excel files, ERP systems, or databases. Before this data can be exported to a BMEcat catalog, it usually first needs to be structured, normalized, and enriched.

    This is exactly where DataNaicer comes in.

    DataNaicer is a software solution for the automated preparation of product data. It supports companies in analyzing existing data sources, structuring product attributes, and supplementing missing information. The aim is to prepare product data in such a way that it can be reused consistently and in a standardized manner.

    In the context of BMEcat, this means, for example:

  5. merging product data from different sources
  6. standardizing and structuring attributes
  7. assigning classifications such as ECLASS or ETIM
  8. preparing product data for export in standardized formats
  9. This allows product data to be efficiently transferred into a structure that can then be used for BMEcat exports or other exchange formats.

    If you want to check how your product data can be automatically structured and prepared for standards such as BMEcat, you can test DataNaicer for 100 data records free of charge!

    Conclusion

    The BMEcat standard is an established format for the exchange of electronic product catalogs in B2B commerce. Its XML-based structure enables automated data exchange between manufacturers, retailers, marketplaces, and purchasing systems.

    The standard supports not only basic product information, but also technical features, price structures, multimedia data, and classifications. This allows complete product catalogs to be transferred across systems.

    For companies that manage large amounts of product data or regularly exchange it with partners, BMEcat forms an important basis for efficient and scalable data processes.

    DataNaicer can also help companies prepare their data for BMEcat so that they are well positioned for the future.

    Ready for the next step?

    Contact us for a no-obligation consultation about your data project.

    Contact us now

    FAQ about BMEcat

    Teilen:
    Try DataNaicer now
    Andreas Wenninger

    About the Author

    Andreas Wenninger

    Andreas is founder and CEO of uNaice. He is an expert in AI-based solutions for content automation and data management.