If you buy from B2B suppliers in DACH, BMEcat files land in your inbox sooner or later. Here's what the standard is, what it is not, and how to work with it.
BMEcat is one of those standards you rarely choose — it simply arrives. A B2B supplier sends a catalog, and it comes as a BMEcat XML file rather than the spreadsheet you were hoping for. Understanding what it is makes the difference between a file you dread and a structured data source you can actually use.
BMEcat is an XML-based standard for exchanging electronic product catalogs between suppliers and buyers. It was initiated by the German BME — the association for supply chain management, procurement and logistics — and is widely used in B2B trade, particularly in the DACH region.
Its job is to make a catalog machine-readable in a predictable structure: instead of every supplier inventing their own column layout, a BMEcat file describes products, their attributes, prices and media in a defined XML format.
This is the single most useful distinction to internalise:
| BMEcat | ETIM / eCl@ss | |
|---|---|---|
| What it is | Transport format (XML) | Classification system |
| Defines | How the file is structured | Which categories and attributes exist |
| Answers | “How do I send the catalog?” | “What kind of product is this, and which properties describe it?” |
They are not alternatives — they are used together. A BMEcat file typically transports articles that are classified according to ETIM or eCl@ss. If you want the classification side in depth, see GDSN, ETIM & eCl@ss explained.
The two versions you will encounter in practice are BMEcat 1.2 and BMEcat 2005 (including 2005.1). Which one applies is usually not your decision: buyers and procurement platforms specify the version and the mandatory fields in their own guidelines. Always check the partner's specification before generating a file.
The standard is well defined, but real files vary. Suppliers fill different levels of detail, attribute depth differs by product group, and the classification may be partial or missing on the longtail. The result is familiar: the core assortment is clean and machine-readable, while accessories and niche items arrive thin.
That gap is exactly the work a PIM takes over — consolidating BMEcat input with other formats, normalizing attribute names, filling gaps, and then producing the export each partner and channel expects from one consistent data set.
Book a demo — we'll show how supplier catalogs are consolidated and exported per channel.
Get started