Skip to main content

DATANORM Explained: Versions, Record Types, UGL and ELDANORM

DATANORM for the German SHK and electrical trades: versions 3, 4 and 5, every record type, price unit traps, ELDANORM, UGL and how it compares to BMEcat.

Diego Nijboer

DATANORM Explained: Versions, Record Types, UGL and ELDANORM

DATANORM is the German standard file format for sending article master data and prices from manufacturers and wholesalers to their customers in the building trades: plumbing, heating and air conditioning (SHK), electrical, roofing, metal and tiles. The record layouts were set by the DATANORM-Arbeitskreis, a working group of trade associations, manufacturers, wholesalers and software houses. DATANORM.de dates the first published version (version 3) to 1986 and says development inside the working group ended with version 5 in 1999.

Two versions are in daily use: DATANORM 4 and DATANORM 5. Which one you deliver depends on the trade software your customers import with. DATANORM.de's FAQ puts it plainly: version 4 is still the most common, and you need version 5 if you want to send image references. A DATANORM file carries commercial data (article number, short texts, prices, discount and product groups, long texts, surcharges). It does not carry ETIM classes or features; that is what BMEcat with ETIM and ETIM xChange are for.

DATANORM 3, 4 and 5: what each version added

Each version was written for the storage and software of its time, and those constraints still shape the files people send now. Version 3 used fixed 128-character records, the size IBM floppy disks were formatted for. Version 4 switched to semicolon-separated fields. Version 5 aligned field lengths with EDIFACT subsets and GAEB transfer records, according to the DATANORM 5 page.

DATANORM from 1986 to today

  1. 1986 to 1990

    Manufacturers, wholesalers and software houses agree a shared format under the sanitary industry association VSI.

  2. 1994

    Semicolon field separators (except in the header record) shrink the files.

  3. May 1999

    Published as a paperback; development in the working group is declared complete.

  4. January 2002

    The transition phase for data creators and software houses ends.

  5. 5

    2026

    Newer formats such as ETIM xChange allow 35-character article numbers.

The version comparison on DATANORM.de also lists the character set: codepage 850, with the German umlauts and ß allowed and the characters ; [ ] { } \ | ~ not allowed in content. The same page adds, dryly, that not everyone sticks to this. A file saved as UTF-8 from a spreadsheet is a common way for a DATANORM delivery to break on import.

DATANORM record types, letter by letter

A DATANORM file is a sequence of records, and the first character of each record says what it is. The field positions are documented only in the DATANORM books from Krammer Verlag, which are copyrighted and not available as free downloads, so this post gives no field positions. The table lists only record letters that DATANORM.de names on its version pages or that two independent import implementations agree on (Hamburger Software's DATANORM import module and an open-source DATANORM parser). For any other letter in a file you receive, check the books.

DATANORM record types and what they carry

VVorlaufsatzHeader: data creator, currency (EUR), from version 5 also the kind of data and the creator's address
KKundennummern-KontrollsatzControl data checked against the recipient's customer number
AHauptsatz AThe article: article number, short texts, price, unit, discount group, EAN
BHauptsatz BVersion 4: second half of the article data. Version 5: only deletions and article number changes, with discontinuation date and replacement article
TLangtextsatzLong text and specification text (Ausschreibungstext), in lines of 40 characters
PPreisänderungssatzPrice maintenance without resending the articles (the DATPREIS file)
RRabattsatzDiscount group names and discounts (the .RAB file)
SWarengruppensatzMain product group and product group names (the .WRG file)
ZZu-/AbschlagsatzFrom version 4: surcharges and reductions, tiered prices, raw material surcharges such as copper
JArtikel-Set-SatzSets and bills of material; version 5 splits the set record in two by function
CLeistungssatzLabor times linked to articles or service sets
GGrafikanbindungssatzVersion 5 only: up to 99 links per article, typed as image, CAD drawing, video or audio
Showing 12 of 12 rows
P, R and S usually travel as separate price, discount group and product group files (DATPREIS, .RAB and .WRG). Version 5 also adds an end record with the record count.

Version 5 changed the meaning of the B record, and that trips up mixed setups. According to the DATANORM 5 page, the article data from A and B in version 4 was merged into A, and B is now used only for deletions and article number changes. A version 5 deletion can announce a discontinuation date and name a replacement article, so the installer's software can swap the replacement into running jobs and calculation lists. A version 4 importer reading a version 5 file has no idea what to do with that.

Price units, quantity units and copper surcharges

Most wrong prices in a DATANORM import are not wrong numbers. They are right numbers read against the wrong unit. Three fields decide what a price means: the quantity unit, the price unit and, in the electrical trade, the raw material surcharge.

  • Price unit. In version 4 the price indicator could only say per 1, 10, 100 or 1,000. Version 5 enters the price unit directly. A cable priced per 100 m and read as per 1 m is a hundred times too expensive.
  • Quantity unit and calculation unit. Version 5 restricts the free-form units of earlier versions and adds a calculation unit with a conversion factor. The DATANORM 5 example is a 4 m pipe that is delivered by the bar but calculated per meter. Before version 5, software houses worked around it by creating a separate per-meter article that the supplier did not know.
  • Raw material surcharges. The version table marks copper surcharges with a weight share as common in the electrical trade, and surcharges for silver, aluminum and brass as well. They travel as surcharge records (Z), so a file without them understates the price of every cable.
  • New price types. Next to list price and net price, version 5 can send a drop-shipment price (Streckenpreis), a recommended retail price and a guide price.

The official checker for all of this is paula, which, according to DATANORM.de, the working group named its test software in 1989. It checks every record type against the books and issues a test certificate for error-free files. Since 2021 certificates are only issued from the subscription version, because certificates made with outdated desktop versions had let faulty files through. For the general unit problem across formats, see the unit of measure guide.

ELDANORM: the electrical trade's own record format

ELDANORM is the record structure the German electrical trade agreed for article master data from manufacturer through wholesaler to the electrical contractor. It is published by the Arbeitskreis ELDANORM of three associations: VEG (electrical wholesale), ZVEH (electrical trades) and ZVEI (the installation equipment division). The ELDANORM 2000 specification traces it back to version 05/90, then 01/96, and Version 2000, valid from 1 January 2000 with a last correction in July 2012. Labor positions for calculation live in a companion format, ZVEHNORM.

ELDANORM looks like DATANORM at first sight, a text file of lettered records, but the details differ in ways an importer has to know:

  • Different letters. Version 2000 has H (main record), I (identification), K (class and feature), P (price), R (discount group), S (search terms), T (text), U (origin), V (header), W (product group), X (article number change) and Z (surcharge).
  • Every article starts with I. The identification record carries the status (S for standard, L for delete), the EAN (up to 14 digits), the manufacturer number (up to 35 characters) and the wholesale number (up to 15). The H record follows.
  • No update status. Version 2000 dropped the maintenance status: a file either creates or overwrites the complete record, or deletes it. Whether existing fields get overwritten is the importing software's decision.
  • Variable separator. The second byte of the V record sets the field separator for the whole file, and empty fields mean no value, not zero.
  • Free-text features. The K record can carry free-text features, for example a feature named "Leistungsaufnahme" with value "600" and unit "Watt". The working group decided a shared nomenclature could not be built and asks creators to use the usual spelling ("Farbe, nicht Color"). That gap is exactly what ETIM later filled.

The ELDANORM spec gives the clearest illustration of the price unit trap. A price always refers to the quantity unit and the price unit, never to the packaging. With quantity unit "13" (meter) and price unit "100", the price is for 100 m, whether the drum holds 785 m of cable or any other length. With quantity unit "23" (kg) and price unit "1000", it is the price per tonne.

UGL is for orders and documents, not article data

UGL (Übergabeschnittstelle lang) is often named in the same breath as DATANORM, but it does a different job: it carries transaction documents such as requests, quotes, orders, delivery notes and invoices between the contractor's software and the wholesaler. It is not an article data format. The wholesale group GC-Gruppe describes UGL as an interface it created in the late 1990s and presented UGL 5.0 as its latest version in 2019.

For a product data team the distinction matters because UGL documents carry article numbers and prices that the contractor's software has to recognize. If the article master that arrived as DATANORM uses one article number and the order confirmation another, the contractor's software cannot match them. Article number changes belong in the article data (the B record in DATANORM 5, the X record in ELDANORM), not in a note on the delivery note.

DATANORM, ELDANORM, BMEcat and ETIM xChange side by side

The flat record formats and the XML and JSON formats are not competitors for the same file. DATANORM and ELDANORM feed the commercial core of trade software: what is it called, what does it cost, which discount group. BMEcat, the XML catalog standard of the German purchasing association BME (current version 2005.2), and ETIM's own exchange formats carry the technical description as classes and features. The BMEcat walkthrough goes through that format element by element.

Article data formats in the German building and electrical trades

DATANORMDATANORM-ArbeitskreisText records, semicolon-separated from version 4, codepage 850None in ETIM terms; version 5 can carry DIN 4000 feature lists, rarely used5 (1999); 4 still most common
ELDANORMArbeitskreis ELDANORM (VEG, ZVEH, ZVEI)Text records, variable length, separator set in the headerFree-text class and feature pairs in the K record2000 (last correction 2012)
BMEcat with ETIMBME (BMEcat), ETIM International (ETIM BMEcat guideline)XMLETIM classes, features, values and unitsBMEcat 2005.2; ETIM BMEcat guideline 5.0 (2021)
ETIM xChangeETIM InternationalJSON with a JSON schemaETIM classes, features, values and unitsV2.0
Only the XML and JSON formats carry ETIM classes and features; the record formats carry the commercial core.

ETIM International announced with the ETIM BMEcat guideline 5.0 in June 2021 that it would be the last version and that a new international exchange format would follow; that format is ETIM xChange. If a wholesaler asks you for DATANORM and a BMEcat file, the usual reason is that they feed two systems: the trade software that prices and orders, and the online catalog or PIM that needs the features. The ETIM classification walkthrough shows how a supplier catalog gets its classes and features, and ETIM vs ECLASS covers when a recipient wants the other classification.

Why German wholesalers and contractors still ask for DATANORM

The format is old, but its reach is not. DATANORM.de's developer page states that every commercial software package for the building trades has a DATANORM 4 or 5 import, so a contractor can load supplier articles straight into the article master for tenders, quotes and invoices. For a small installer that import is the whole integration. No XML parser, no feature model, just articles and prices.

That is why a manufacturer that already delivers rich ETIM data still gets asked for DATANORM: the richer file goes to the wholesaler's catalog, the DATANORM file goes to the contractor's software. In the SHK trade the industry data quality guideline (DQR) and the data pools built on it now define the richer delivery. DATANORM stays the lowest common denominator underneath.

Checks before you send a DATANORM file

DATANORM delivery check

0 of 8 done0%

Keeping the article data behind a DATANORM file in one place

WISEPIM does not read or write DATANORM, ELDANORM or UGL, and it has no connector to German trade software. The DATANORM file itself comes from your ERP or a dedicated DATANORM tool. What WISEPIM covers is the work before any of those files: one record per article with EAN, manufacturer part number, brand, units and dimensions, classified into ETIM 10.0 classes per product family through product classification, with an ETIM conformance score that shows which class features are still missing or invalid.

From that record, WISEPIM exports BMEcat 2005 with ETIM features through the Feed Hub for recipients that take BMEcat, and CSV or Excel files for those that work from spreadsheets. Incoming supplier lists come in through the CSV and Excel import with a saved profile per supplier, which notices when a delivery's columns change.

A saved supplier profile reuses the accepted column mapping for the next delivery and shows what changed between deliveries.

If you want a second pair of eyes on one supplier file before you build anything, the data readiness check is a free review of a single file with a person on a call. For a wider view of what the installation trade needs from its article data, see PIM for plumbing and HVAC.

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

DATANORM 5 (1999) merged the A and B article records, uses B only for deletions and article number changes, enters the price unit directly instead of a 1/10/100/1,000 indicator, restricts quantity units, adds calculation units, up to 99 media links per article and an end record. DATANORM 4 (1994) is still the most common version for simple article data.

Development inside the DATANORM working group ended with version 5 in 1999. DATANORM.de reports that, because newer formats such as ETIM xChange allow longer article numbers, an update or new version is being considered, but no decision has been made. Treat versions 4 and 5 as the formats your customers will ask for.

Not reliably. DATANORM files are record-based text in codepage 850, and each record type has its own field order, so a spreadsheet shows mixed columns and broken umlauts. Use a DATANORM viewer such as the online services on DATANORM.de or the paula checker, which display records by type and flag format errors.

The record descriptions for versions 3, 4 and 5 are published as books by Krammer Verlag in Düsseldorf. They are copyrighted and not available as a free download. DATANORM.de offers the DATANORM-Ergänzungen, a free supplement with corrections and clarifications, on request by email.

No. DATANORM carries commercial article data: numbers, texts, prices, groups and surcharges. Version 5 can transfer DIN 4000 feature lists, but DATANORM.de describes that as extremely rare. ETIM classes and features travel in BMEcat files built to the ETIM BMEcat guideline or in ETIM xChange.

Keep exploring

Hand-picked next steps to go deeper.

Better product data, better results.Get more sales.

4.7