Skip to main content

BMEcat: The XML Catalog Format, Element by Element

BMEcat explained for suppliers and wholesalers: an annotated BMEcat 2005 file with ETIM features, the three transactions and 11 reasons files get rejected.

BMEcat: The XML Catalog Format, Element by Element

BMEcat is the XML format for exchanging B2B product catalogs, published by the German procurement association BME (Bundesverband Materialwirtschaft, Einkauf und Logistik). One BMEcat file holds a catalog header (who sends it, which catalog, which language) and one transaction: a complete new catalog, a product update or a price update. Each product in it carries the supplier's article number, a short description, order units, prices and, in technical trades, a block of ETIM features.

The current version is 2005.2, according to BME's own BMEcat page, but when an electrical or installation wholesaler asks for "BMEcat" they almost always mean BMEcat 2005 filled in the way the ETIM BMEcat guideline describes. Below is a minimal annotated file, the three transaction types, how a file gets built from data you already have, and the reasons receivers actually reject files, taken from the specification, the ETIM guideline and the Dutch data pool 2BA.

What a BMEcat file is, and who asks for one

BMEcat 1.0 appeared in November 1999 as a common format for electronic product catalogs in purchasing. The BMEcat 2005 specification is written in German first, which is one reason a large share of searches for BMEcat, "BMEcat erstellen" and "BMEcat Format" come from Germany, and why many receivers' import manuals use the German element labels (Kopfbereich, Kurzbeschreibung, Bestelleinheit).

Two groups of receivers ask for it today:

  • Procurement platforms and buyer systems that load hosted catalogs, the counterpart of the live sessions described in our punchout catalog guide.
  • Technical wholesalers and data pools in the electrical, HVAC and plumbing trades, where BMEcat is the carrier for ETIM-classified article data. The Dutch pool 2BA, for example, imports BMEcat 2005 files written to the ETIM guideline 5.0, next to the newer ETIM xChange JSON format that ETIM International now recommends instead of BMEcat.

BMEcat is not a classification. It is the envelope. ETIM or ECLASS supply the class codes and feature codes that go inside it, and the receiver decides which one it expects.

BMEcat 1.2, 2005, 2005.1 and 2005.2: which version a receiver means

BMEcat versions and the ETIM guideline

  1. March 2001

    BMEcat 1.2

    Uses ARTICLE, SUPPLIER_AID and ARTICLE_FEATURES. Defined by a DTD only, no XML schema.

  2. November 2005

    BMEcat 2005

    Renames ARTICLE to PRODUCT and SUPPLIER_AID to SUPPLIER_PID, adds parties and richer feature systems. Every valid 1.2 document is also valid 2005.

  3. 2005.1

    BMEcat 2005.1 (advanced)

    Optional extension modules only, fully backward compatible with BMEcat 2005.

  4. June 2021

    ETIM BMEcat guideline 5.0

    ETIM International's profile of BMEcat 2005 with UDX.EDXF extensions. Revision 5.0.1 followed in August 2021. ETIM called it the last ETIM BMEcat version.

  5. 5

    Current

    BMEcat 2005.2

    The version BME lists as current on its BMEcat page.

The 2005 specification is explicit about compatibility: BMEcat 2005 is fully backward compatible with 1.2, so a 1.2 catalog document also conforms to 2005. The old ARTICLE elements stay in the schema but are marked to be dropped in a later version. ECLASS adds that 2005.1 changes are all optional extensions, so a 2005 file stays valid there too.

In practice the question is not the version number but the profile. A plain BMEcat 2005 file uses the namespace http://www.bmecat.org/bmecat/2005. A file written to the ETIM BMEcat guideline 5.0 declares ETIM's own namespace and schema, puts images, brand, packaging levels and regulatory flags in UDX.EDXF extension elements, and is checked with ETIM's certification tool. ETIM International has said 5.0 is the last ETIM BMEcat version, but it remains in daily use. Ask your receiver which XSD they validate against before you build anything.

A minimal BMEcat 2005 catalog, annotated

The table walks through one catalog document in file order: the header, then one product inside a T_NEW_CATALOG transaction. The product is an illustrative 1-pole C16 miniature circuit breaker from a fictional supplier, classified in ETIM 10.0 class EC000042 (Miniature circuit breaker). Class, feature and value codes are the real ETIM 10.0 codes; the article number, prices and the GS1 demonstration GTIN are examples.

Annotated BMEcat 2005 catalog with one ETIM-classified product

BMECAT (attribute version)2005YesRoot element. Its namespace decides which schema validates the file: plain BMEcat 2005 or the ETIM guideline profile.
HEADER > CATALOG > LANGUAGEdeu (default), engYesSpracheThree-letter ISO 639-2 codes, not de or en.
HEADER > CATALOG > CATALOG_IDDEMO-SCHALT-2026YesKatalog-IDStable across versions of the same catalog.
HEADER > CATALOG > CATALOG_VERSION001.004YesKatalogversionRaise it with every new full catalog.
HEADER > SUPPLIER > SUPPLIER_NAMEDemo Schaltgeraete GmbHYesLieferantIn BMEcat 2005 you may use SUPPLIER_IDREF plus a PARTY block instead.
T_NEW_CATALOG > PRODUCT (mode new)YesProduktARTICLE is the 1.2 name for the same element and still validates.
PRODUCT > SUPPLIER_PIDDS-C16-1PYesArtikelnummer des LieferantenMax 32 characters; the spec warns some systems keep only 18 (SAP).
PRODUCT_DETAILS > DESCRIPTION_SHORTMiniature circuit breaker 1P C16 6 kAYesKurzbeschreibungMax 150 characters; make the first 40 unique, since SAP OCI and R/3 process only 40.
PRODUCT_DETAILS > INTERNATIONAL_PID (type gtin)9506000134352NoInternationale ProduktnummerOptional in the base standard; check the digit before sending.
PRODUCT_DETAILS > MANUFACTURER_PIDDS-C16-1PNoHerstellerartikelnummerOften identical to SUPPLIER_PID for a manufacturer's own catalog.
PRODUCT_FEATURES > REFERENCE_FEATURE_SYSTEM_NAMEETIM-10.0Yes (ETIM)MerkmalsystemNotation ETIM-x.y for an official release.
PRODUCT_FEATURES > REFERENCE_FEATURE_GROUP_IDEC000042Yes (ETIM)MerkmalgruppeThe ETIM class. Must exist in the release named above.
FEATURE: FNAME / FVALUEEF000889 / EV000084Yes (ETIM)MerkmalRelease characteristic = C. Alphanumeric features carry an EV value code, not the text C.
FEATURE: FNAME / FVALUEEF000227 / 16Yes (ETIM)MerkmalRated current 16 A. No FUNIT: ETIM fixes the unit per feature.
FEATURE: FNAME / FVALUE / FVALUEEF007515 / -25 / 55Yes (ETIM)MerkmalAmbient temperature during operating, a range feature: two FVALUE elements, lower then upper.
FEATURE: FNAME / FVALUE / FVALUE_DETAILSEF000218 / - / UNYes (ETIM)MerkmalBuilt-in depth not known yet: a minus sign plus the reason code.
PRODUCT_ORDER_DETAILS > ORDER_UNITC62YesBestelleinheitUnit code (C62 = piece), not Stk or pcs. Prices refer to this unit.
PRODUCT_ORDER_DETAILS > CONTENT_UNITC62YesInhaltseinheitThe unit inside one order unit.
PRODUCT_ORDER_DETAILS > NO_CU_PER_OU1NoVerpackungsmengeContent units per order unit; defaults to 1.
PRODUCT_PRICE_DETAILS > PRODUCT_PRICE (price_type net_list) > PRICE_AMOUNT7.85YesProduktpreisDot as decimal separator. PRICE_CURRENCY EUR sits next to it.
MIME_INFO > MIME > MIME_SOURCEds-c16-1p.jpgNoMultimediale ZusatzdatenThe ETIM guideline moves images to UDX.EDXF.MIME_INFO with MD codes.
Showing 21 of 21 rows
Illustrative example: read top to bottom, this is the element order the XML must follow; a correct value in the wrong position still fails schema validation.

Notice how little is mandatory in the base standard: a catalog ID, version and language, a supplier, and per product an article number, a short description, an order unit, a content unit and one price. Everything a wholesaler actually sells from, such as GTIN, brand, images, packaging levels and features, is optional in BMEcat itself and made mandatory by the receiver's guideline.

How ETIM feature values are written inside a BMEcat file

The ETIM BMEcat guideline adds rules the base standard does not have, and most feature-level rejections come from them:

  • Every feature of the class must be present. If a product is assigned to an ETIM class, all of that class's features go in the file, apart from local standard features (codes like EFUK0001).
  • No value is written as a minus sign. Deliver FVALUE "-" and, optionally, a reason in FVALUE_DETAILS: NA (not applicable), MV (no correct value exists in this ETIM version) or UN (unknown for now). A range feature with no value gets one minus sign, not two.
  • Value types are strict. Numeric and range features take numbers, logical features take true or false, alphanumeric features take the EV code from the class's permitted value list.
  • Units stay out. The guideline says FUNIT is not necessary and usually not desired for ETIM features, because the class definition fixes the unit. Convert to that unit before you write the number (see our unit of measure guide for why mm and cm mix-ups are the classic error).

New catalog, product update or price update: the three transactions

BMEcat defines three transactions, and the transaction element sits directly under BMECAT, after the header:

  • T_NEW_CATALOG transfers a complete catalog. The receiver loads it as new and takes nothing over from earlier versions. Every receiver supports it.
  • T_UPDATE_PRODUCTS sends only new, changed or deleted products, each marked with mode new, update or delete.
  • T_UPDATE_PRICES sends only price information, replacing all stored prices for the products in the file.

The update transactions carry a prev_version attribute that counts the updates since the last full catalog: 0 for the first, 1 for the second, and so on. The ETIM guideline spells out the consequence: if one update is missing on the receiver's side, every following update is invalid and you have to send a new full catalog. Whether a receiver accepts updates at all is a bilateral agreement. ETIM also defines its own light transaction, T_NEW_PRODUCTDATA, for the most important data of new products; it is not part of BMEcat itself.

Why receivers reject BMEcat files: eleven causes

These come from the BMEcat 2005 specification, the ETIM BMEcat guideline 5.0 and the list of common mistakes the Dutch data pool 2BA publishes for BMEcat 2005 ETIM 5.0. The first six are schema errors a validator catches in seconds; the last five pass the schema and fail at the receiver.

  1. Wrong header. Namespace, schema location or version attribute that do not match the profile the receiver validates against.
  2. Missing mandatory elements, most often ORDER_UNIT or CONTENT_UNIT, or a FEATURE block missing for an ETIM-classified product.
  3. Elements out of order. The schema defines a sequence (SUPPLIER_PID, details, features, order details, prices, media). Generators that append fields at the end break it.
  4. Empty optional elements, such as an empty EAN or KEYWORD tag. Leave the element out instead.
  5. Unescaped special characters, above all a bare ampersand in a description (Schalter & Taster). It must be written as &.
  6. Broken XML: an opening tag without a closing tag or the other way round, usually from hand edits.
  7. Incomplete feature sets: features left out instead of delivered as "-" with a reason code.
  8. Text instead of codes: C16 written into an alphanumeric feature instead of EV000084, or Stk instead of C62 as order unit.
  9. Values longer than the receiver stores. BMEcat allows 150 characters for DESCRIPTION_SHORT; 2BA's data model keeps 70. SUPPLIER_PID allows 32; some ERP systems keep 18.
  10. A broken update chain: a T_UPDATE_PRODUCTS with a prev_version that skips one, which forces a full new catalog.
  11. Country text rules. For Germany and Austria the ETIM guideline bans font formatting, semicolons, quotation marks, long dashes and apostrophes in short and long descriptions, all-caps words and HTML (unless escaped), and asks not to repeat article numbers or manufacturer names in them.

Building a BMEcat file from your own product data

Whether you use a converter, an ERP module or a PIM, the work is the same, and most of it happens before any XML exists:

  1. Get the receiver's profile. Plain BMEcat 2005 or the ETIM guideline 5.0, which ETIM release (for example ETIM-10.0), which languages, which price type (net_list, net_customer, nrp) and which optional fields they treat as mandatory.
  2. Fix identifiers first. One unique supplier article number per product, valid GTINs (test them with the EAN/GTIN validator), manufacturer part numbers where they differ.
  3. Classify every product into an ETIM class of that release (our ETIM classification walkthrough covers this step by step) and fill its features, with "-" and NA, MV or UN where a value does not exist or is not known.
  4. Map units to codes. Order unit, content unit and pieces per order unit as UN/ECE codes (C62 for piece, PK for pack), feature values converted to the unit ETIM prescribes.
  5. Shorten and clean texts to the receiver's lengths and country rules.
  6. Generate the file and validate it against the receiver's XSD. ETIM members can use ETIM International's BMEcat certification tool; anyone can run a generic XSD validator.
  7. Send a small test file first, with a handful of products from different classes, and ask the receiver for their import log, not just "received".

BMEcat pre-send check

0 of 8 done0%

If you receive BMEcat files rather than send them, the same list works in reverse as an intake check: a supplier file that fails points 3, 4 or 8 will fail again next month unless the source data is fixed. If you want a second opinion on one supplier file, our free data readiness check is a person going through it with you.

Generating BMEcat 2005 with ETIM features from WISEPIM

In WISEPIM the export is a Feed Hub channel called BMEcat 2005 (ETIM). You fill in the catalog header (supplier name and ID, catalog ID and version, territory, buyer) and pin the ETIM release for that feed (ETIM 10.0 is the release loaded in WISEPIM today). Products get their ETIM class through their product family in product classification; a product whose family has no ETIM class is left out of the file and counted as skipped, because an article that claims a feature system without a class is invalid.

Feed Hub's channel picker. The BMEcat 2005 (ETIM) channel sits under the Wholesale & trading partners tab, separate from the retail shopping channels shown here.

Be clear about what the file is, because it is not what an ETIM guideline 5.0 receiver validates against. WISEPIM writes a T_NEW_CATALOG under the plain BMEcat 2005 namespace, using the BMEcat 1.2 element names (ARTICLE, SUPPLIER_AID, ARTICLE_FEATURES) rather than the 2005 PRODUCT names, with one price per article and order unit, content unit, minimum quantity and pack size taken from attributes. It writes no update transactions and none of the guideline's UDX.EDXF extensions. Whether a receiver takes that file depends on its importer, so send a small test file and ask for the import log before you deliver the full range. The same applies in the other direction: Feed Hub's XML import reads the ETIM feature blocks of BMEcat files that use the ARTICLE names, but not of files written with the 2005 PRODUCT names, so try one supplier file before you plan an intake around it.

Whatever tool writes the XML, the file is only as good as the record behind it: one article number, a valid GTIN, an ETIM class with every feature answered, unit codes instead of words. Fix those once in the product data and BMEcat, CSV or XLSX exports for each receiver become a setting rather than a project.

Diego Nijboer

CTO and Co-Founder at WISEPIM, building AI-powered solutions that transform product data management for e-commerce businesses. Over 10 years of experience solving complex technical challenges in e-commerce and PIM systems.

Frequently asked questions

Still have questions?

Can't find the answer you're looking for? Please get in touch with our team.

Contact Support

BMEcat 2005 renamed the ARTICLE elements of version 1.2 to PRODUCT (SUPPLIER_AID became SUPPLIER_PID, ARTICLE_FEATURES became PRODUCT_FEATURES) and added parties, richer feature systems and more price and logistics fields. It is fully backward compatible: a valid 1.2 catalog is also a valid 2005 catalog. The old names are marked to be dropped in a future version, so new files should use the PRODUCT names unless a receiver asks otherwise.

No. BMEcat is an XML exchange format for catalog data, published by the German association BME. ETIM is a classification model for technical products, with class codes (EC), feature codes (EF), value codes (EV) and unit codes (EU). An ETIM BMEcat file uses BMEcat as the envelope and ETIM to describe each product inside its PRODUCT_FEATURES block. ETIM International published guidelines for using BMEcat 2005 this way.

Validate it against the XML schema your receiver uses. For plain BMEcat 2005 that is the BME schema; for files written to the ETIM BMEcat guideline 5.0 it is the ETIM XSD, and ETIM members can upload files to ETIM International's BMEcat certification tool. Schema validation catches order, missing and empty elements. It does not catch content problems such as missing feature values, wrong units or text that breaks a country rule, so check those separately.

BME lists BMEcat 2005.2 as the current version. Most technical wholesalers and data pools still ask for BMEcat 2005 filled in according to the ETIM BMEcat guideline 5.0 from June 2021, which ETIM International has said is the last ETIM BMEcat version. ETIM now recommends its JSON-based ETIM xChange format for new implementations, and some pools accept both.

Yes, with the T_UPDATE_PRICES transaction, if the receiver has agreed to accept it. The file carries only price information for the products it lists, and the receiver replaces all stored prices for those products. Each update carries a prev_version number that continues the chain since the last full catalog; if the receiver misses one update, the next ones are invalid and a new T_NEW_CATALOG is needed.

Keep exploring

Hand-picked next steps to go deeper.

Better product data, better results.Get more sales.

4.7