> 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/example-import.md).

# Example Import

This walkthrough shows the whole flow on a manageable data set. It works well for onboarding new users and for sign-off after configuration.

{% hint style="info" %}
Run the walkthrough in a **sandbox environment**. It creates items, price list lines and BOMs.
{% endhint %}

## Starting point

The walkthrough uses a small sample delivery of around 25 articles:

<table><thead><tr><th width="260">File</th><th>Contents</th></tr></thead><tbody><tr><td><code>DATANORM.WRG</code></td><td>Product groups</td></tr><tr><td><code>DATANORM.RAB</code></td><td>Discount groups</td></tr><tr><td><code>DATANORM.001</code></td><td>Articles with prices and long texts</td></tr><tr><td><code>DATPREIS.001</code></td><td>Price change of roughly +10% on the same articles</td></tr></tbody></table>

## Preparation

{% stepper %}
{% step %}

#### Check the setup

Default vendor, item defaults and number series are set, see [Base Configuration](/datanorm-item-import/datanorm_en_us/getting-started/base-configuration.md).
{% endstep %}

{% step %}

#### Units initialised

**DATANORM Setup → Initialize Units** has been run.
{% endstep %}

{% step %}

#### Duplicate handling on review

Set **Duplicate Handling** to **Mark for Manual Review** so you see the mechanism during the walkthrough.
{% endstep %}
{% endstepper %}

## Step 1: Import the groups

Import `DATANORM.WRG` first, then `DATANORM.RAB`. Both files are small and processed in seconds.

Then check **DATANORM Product Groups** and **DATANORM Discount Groups**. The descriptions should appear as plain text.

{% hint style="info" %}
If the discount groups all show 0%, that is not an error. Many suppliers do not include their terms in the file, see [Discount Groups](/datanorm-item-import/datanorm_en_us/master-data-and-mappings/discount-groups.md).
{% endhint %}

## Step 2: Import the articles

{% stepper %}
{% step %}

#### Import

**Import DATANORM File**, pick `DATANORM.001` and confirm the vendor in the dialog.
{% endstep %}

{% step %}

#### Look at the session

The import session shows the version, the vendor and the number of records processed.
{% endstep %}

{% step %}

#### Check article staging

Open article staging. Spot-check description, unit, list and net price and the product group. Umlauts must be rendered correctly.
{% endstep %}

{% step %}

#### Approve and synchronise

Approve the records and synchronise. Then open one of the new items and check the base unit of measure, posting groups and the extended text.
{% endstep %}
{% endstepper %}

## Step 3: Write the purchase price list

Run **Write Purchase Price List** on the import session. The app reports how many price lines were written.

Open the result with **Show Purchase Price List**. You see a price list for the vendor with one line per article. Details under [Purchase Price Lists](/datanorm-item-import/datanorm_en_us/prices/purchase-price-lists.md).

## Step 4: Build the part lists

If the delivery contains sets, run **Build Part Lists** and then open **Show Part Lists**. An assembly BOM with the set's lines appears on the set item. See [Building Assembly BOMs](/datanorm-item-import/datanorm_en_us/part-lists-sets/building-assembly-boms.md).

## Step 5: Import the price change

{% stepper %}
{% step %}

#### Note the price beforehand

Note the purchase price of one article from the price list.
{% endstep %}

{% step %}

#### Import DATPREIS

Read in `DATPREIS.001`, choosing the same vendor.
{% endstep %}

{% step %}

#### Check price staging

Price staging shows the new prices with their price indicator and validity date.
{% endstep %}

{% step %}

#### Write the price list again

Run **Write Purchase Price List** and look at the article you noted. Its price is now roughly 10% higher.
{% endstep %}
{% endstepper %}

## Sign-off checklist

<table><thead><tr><th width="60">✓</th><th>Check</th></tr></thead><tbody><tr><td></td><td>Product groups and discount groups have plain text descriptions.</td></tr><tr><td></td><td>The article count in staging matches expectations (not double, for V4).</td></tr><tr><td></td><td>Umlauts in article descriptions are correct.</td></tr><tr><td></td><td>Every new item has a base unit of measure.</td></tr><tr><td></td><td>Posting groups are populated.</td></tr><tr><td></td><td>The long text appears as an extended text on the item.</td></tr><tr><td></td><td>The purchase price list has one line per article and is assigned to the right vendor.</td></tr><tr><td></td><td>Sets appear as an assembly BOM on the set item.</td></tr><tr><td></td><td>After the price change the new purchase price is correct.</td></tr></tbody></table>

{% hint style="info" %}
To test behaviour with large catalogues, use a full delivery of several thousand articles. That exercises background processing, see [Import Process](/datanorm-item-import/datanorm_en_us/importing-datanorm-files/import-process.md).
{% 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/example-import.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.