> For the complete documentation index, see [llms.txt](https://docs.solutioo.de/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/importing-datanorm-files/differences.md).

# Differences Between DATANORM 4 and 5

## Side by side

<table><thead><tr><th width="230">Aspect</th><th width="290">DATANORM 4</th><th>DATANORM 5</th></tr></thead><tbody><tr><td><strong>Article data</strong></td><td>split across A record and B record</td><td>entirely in the A record</td></tr><tr><td><strong>Additional details</strong></td><td>EAN, match code, catalogue page, copper weight in the B record</td><td>contained in the A record</td></tr><tr><td><strong>Units</strong></td><td>free German abbreviations such as <code>ST</code>, <code>Stck</code>, <code>M</code></td><td>ISO codes such as <code>PCE</code>, <code>MTR</code></td></tr><tr><td><strong>Price record</strong></td><td>up to three articles per P record line</td><td>one article per line</td></tr><tr><td><strong>Price notation</strong></td><td>integer, decimals via the price indicator</td><td>explicit decimal notation</td></tr><tr><td><strong>Text length</strong></td><td>shorter fields</td><td>longer fields for descriptions</td></tr></tbody></table>

## What this means in practice

### Record count in staging

A DATANORM 4 file with 4,637 articles contains roughly 9,274 article lines, because each article consists of an A and a B record. Staging still shows **4,637** records. The merge is intentional.

### More price records than lines

A V4 price file with 9 lines can produce 25 price records, because one line carries up to three article blocks. Price staging holding more entries than the file has lines is therefore correct.

### Units

With DATANORM 4 you meet unit codes that need their own mapping more often. **Initialize Units** covers the widespread German abbreviations; add rare ones in the [unit mapping](/datanorm-item-import/datanorm_en_us/master-data-and-mappings/unit-mapping.md).

### Price indicator

The price indicator distinguishes list price (1) from net price (2). The app stores both in separate fields so they cannot overwrite each other. Which one becomes the purchase price is controlled by **Purchase Price Source**, see [Purchase Price Lists](/datanorm-item-import/datanorm_en_us/prices/purchase-price-lists.md).

## Detection and export

On **import** the version is detected from the header record – nothing to configure.

On **export** you choose the version deliberately. The default comes from **Default DATANORM Version** in the setup and can be overridden in the wizard. See [DATANORM Export](/datanorm-item-import/datanorm_en_us/export/export-wizard.md).

{% hint style="info" %}
For new data deliveries DATANORM 5 is the better choice: fewer record types, unambiguous units and clear decimal notation. DATANORM 4 remains supported because many suppliers still use it.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.solutioo.de/datanorm-item-import/datanorm_en_us/importing-datanorm-files/differences.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.