BMEcat and PIM: catalogue exchange, guidelines and dialects

What is BMEcat and who governs it?

BMEcat is an XML format for exchanging electronic product catalogues, created and published by BME, the German association for materials management, purchasing and logistics. BMEcat lets suppliers send product data, prices and classification to customers, procurement platforms and data pools without inventing a format per customer. The 2005 specification modules were written with the University of Duisburg-Essen and Fraunhofer IAO.

ECLASS e.V. documents four BMEcat versions in use: 1.2, 2005, 2005.1 and 2005.2. ECLASS published its 2005.2 specification document on 15 August 2023. BMEcat 2005 reworked classification handling: the classification module, finalised on 14 November 2005, removed the older FEATURE_SYSTEM element.

BMEcat itself is a container. The content model comes from a classification standard, applied through a guideline: the ETIM BMEcat guideline or the ECLASS BMEcat guidelines. That split matters for a PIM buyer. The PIM must hold the classification in its data model and produce the container on export. BMEcat is one of seven standards in the product data standards overview, and it appears in several shortlists in PIM by industry.

Which industries use BMEcat?

BMEcat is the default catalogue format in German-speaking and Dutch B2B supply chains for technical products. Wholesalers, procurement platforms and data pools in electrical, installation, building, industrial supplies and tools expect BMEcat files from manufacturers.

In PIMvendors selections, BMEcat is a hard requirement for three buyer types:

• Manufacturers delivering to technical wholesalers and buying groups, where BMEcat with the ETIM guideline is the norm.
• Manufacturers selling to large industrial buyers through e-procurement platforms, where BMEcat with the ECLASS guideline is common.
• Distributors receiving supplier catalogues in BMEcat and publishing their own catalogue to customers in BMEcat.

The Dutch data pool 2BA illustrates the transition. 2BA documents BMEcat 2005 ETIM imports, prefers the BMEcat 2005 ETIM 5.0 guidelines over older versions, and supports ETIM xChange 2.0 for import and export. ETIM International itself previously recommended BMEcat and has now released ETIM xChange. Local ETIM organisations choose the preferred format per country. For buyers in the Netherlands, Belgium and DACH, that means two export formats for the same data during the coming years.

What does BMEcat mean for the PIM data model?

BMEcat sets the export structure, while ETIM or ECLASS set the attribute model. The PIM data model needs four elements to produce valid BMEcat files:

The transaction row is the one buyers underestimate. Update files only work when the PIM knows what changed since the last successful delivery to each recipient. That is a channel-level change log, and many PIMs only track changes at product level.

User-defined extensions are the second trap. The 2BA guideline adds Dutch fields through UDX.EDXF, such as a field for country of production origin. Each recipient's extensions need a home in the PIM data model, or they end up in spreadsheets next to the PIM.

What should you test in a PIM demo for BMEcat?

Test BMEcat with the guideline and validation tool your customers use. PIMvendors' scenario method runs each test on buyer sample data. Five BMEcat scenarios cover the critical behaviour:

1. Export 50 sample products as a full BMEcat 2005 file under the ETIM guideline your largest customer specifies, and validate it with that guideline's validation tool.
2. Change 5 products, then export an update file and show that only those 5 products are included.
3. Export the same products under the ECLASS BMEcat guideline, from the same attribute values.
4. Import a supplier BMEcat file with ETIM data, show the mapping to your data model and the rejection report for invalid values.
5. Export the same 50 products as ETIM xChange 2.0 JSON and compare the content with the BMEcat file.

Scenario 2 exposes the change-tracking question, and scenario 4 matters most for distributors. The Demo Theatre scenario library holds the script format. For distributors, the supplier data onboarding page covers the import side in detail.

Common BMEcat pitfalls in PIM selections

BMEcat failures are almost always dialect failures. A Computerwoche article from 2001 already noted that most customers and marketplaces bend BMEcat in their own direction. In PIMvendors selections, the same pitfalls recur 25 years later:

• One export template for all customers: each wholesaler or platform applies its own guideline version and extensions, so a single template fails for half of them.
• Missing change tracking: the PIM can only send full catalogues, and recipients reject or delay large files.
• Classification outside the PIM: the team maps ETIM or ECLASS in the export connector, so the PIM cannot validate classification data before export.
• No rejection loop: recipients reject products, and nobody sees which products failed or why.
• Outdated guidelines: 2BA states that previous BMEcat ETIM guideline versions do not match current data needs.

The fix starts before the RFP. Collect the guideline, the validation tool and a sample file from your 5 to 10 most important recipients. Those files become the test data for every vendor demo and the acceptance criteria in the contract.

Where BMEcat shows up across industries

BMEcat requirements appear on four industry pages in this hub:

• PIM for wholesale distribution: supplier BMEcat import and customer BMEcat export.
• PIM for building materials: BMEcat ETIM to data pools and buying groups.
• PIM for industrial manufacturing: BMEcat with ECLASS for e-procurement platforms.
• PIM for DIY and garden: BMEcat for trade channels next to GS1 data for retail.

BMEcat connects to three other standards on this hub. ETIM and ECLASS supply the classification inside the BMEcat file. UNSPSC codes are sometimes added for international procurement customers. Write all four into the integration requirements, with one row per recipient and guideline version.

That recipient table is the most useful single artefact in a BMEcat-heavy selection. It lists each recipient, the format, the guideline version, the classification release, the delivery frequency and the validation tool. Vendors respond to concrete rows, and the evaluation team can score each row in the demo.

{{list:requirements:IN}}