BMEcat
BMEcat is an open XML standard for exchanging structured product catalog data between a supplier and a buyer's ERP, PIM, or e-procurement system as a single file rather than a live connection. It carries item numbers, descriptions, classification codes (commonly ETIM or eCl@ss), prices, units of measure, and links to images or documents in a fixed schema both sides already agree on. It is maintained by BME e.V., the German association for materials management, purchasing, and logistics, and is most entrenched in DACH-region industrial and electrical distribution.
What a BMEcat file carries
A BMEcat document is XML with three broad parts: header information (who the supplier and buyer are, currency, language, the catalog's validity dates), a product section (one entry per item, with item number, description, classification, price, and unit of measure), and optional supplementary data such as image references and technical documents.
What separates it from a plain price list is the classification field. Most BMEcat catalogs in electrical, HVAC, and industrial supply carry ETIM or eCl@ss codes alongside each item, so the receiving PIM or procurement system already knows which class, and therefore which structured features, apply to that part before a human touches it.
BMEcat vs. PunchOut/cXML vs. a flat file
These get confused because they all move product data from supplier to buyer, but they solve different problems.
| Format | What it is | When data updates |
|---|---|---|
| BMEcat | A static XML catalog file, imported into the buyer's local system | Only when a new file is sent |
| PunchOut (cXML) | A live, authenticated session into the supplier's hosted catalog | Real time, every session |
| Amazon-style flat file | A tabular file (often CSV/Excel) for a single retailer's schema | Only when a new file is uploaded |
BMEcat and a flat file are close cousins: both are batch files a buyer loads into their own system. BMEcat's advantage is a richer, standardized schema with built-in support for classification and multiple price scales, instead of a spreadsheet with retailer-specific columns. A PunchOut catalog is a different mode entirely: nothing is imported, the buyer's procurement system opens a session on the supplier's site for each shopping trip.
Versions and where it's used
The specification has moved through several versions, most notably 1.2 and the current 2005 line (2005.2), each widening the model and product categories it covers. It's an open standard, free to implement, which is part of why it spread across so many small and mid-size suppliers who couldn't justify a custom EDI build for every customer.
Adoption concentrates in Europe, especially German-speaking industrial, electrical, and MRO distribution, where BMEcat and ETIM classification are often published together in the same file. Outside that region, GDSN and retailer-specific flat files do more of the same job.
Where BMEcat catalogs break down
The format is well specified; the data feeding it isn't always.
- Classification version drift. A supplier ships ETIM 7 codes into a system expecting ETIM 8, or an eCl@ss version the buyer's PIM hasn't updated to yet.
- Description quality varies wildly by supplier. BMEcat enforces structure, not content — a description field can still be a terse internal SKU name.
- It's a snapshot, not a sync. Unlike GDSN's publish-subscribe model, a BMEcat file goes stale the moment the supplier changes a price or spec and doesn't resend it.
- One file per relationship. Suppliers without a PIM often hand-build a slightly different BMEcat export per major customer, which multiplies maintenance work instead of centralizing it.
Frequently asked questions
Is BMEcat the same as an Excel price list?
No. A price list is unstructured beyond rows and columns you define yourself. BMEcat is a fixed XML schema with dedicated fields for classification codes, multiple price scales, units of measure, and document references, so the receiving system can parse it the same way regardless of who sent it.
Does BMEcat replace PunchOut catalogs?
No, they're complementary and often used by the same buyer for different suppliers. BMEcat imports a static catalog into the buyer's own system; PunchOut opens a live session on the supplier's hosted site for each order. Some suppliers offer both.
Who maintains the BMEcat standard?
BME e.V. (Bundesverband Materialwirtschaft, Einkauf und Logistik), the German materials management, purchasing, and logistics association. It's an open, freely implementable specification, currently on the 2005.2 revision.
Do I need BMEcat if I don't sell into Germany or Europe?
Usually not as a requirement, though nothing stops you from using it. North American distributors and retailers are more likely to ask for GDSN participation, a retailer-specific flat file, or PunchOut/cXML instead.