> 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/master-data-and-mappings/product-groups.md).
# Product Groups
## Where they come from
Product groups come from the **S record** of a DATANORM delivery, usually in a separate file with the extension `.WRG`. An S record carries the product group number and its description.
On import the app creates entries in **DATANORM Product Groups**. Articles reference those entries through their product group.
## Import order
{% hint style="info" %}
Read the product group file **before** or together with the article file. Then articles carry a product group whose description is already known.
{% endhint %}
Reading the article file first does not cause an error: the articles carry the product group number, only the plain text description is missing. Importing the `.WRG` file later fills in the descriptions.
## Main group and subgroup
Alongside the product group, DATANORM knows a **main product group**. The app keeps both values on article staging so you can follow the supplier's structure.
Field on article staging
Contents
Product Group
The article's product group.
Main Product Group
The parent group, where the supplier provides one.
## Use in Business Central
The DATANORM product group is a structure of its own and does not replace the Business Central item category. New items get their item category from **Default Item Category Code** in the setup, see [Base Configuration](/datanorm-item-import/datanorm_en_us/getting-started/base-configuration.md).
Product groups are useful to
* follow how the supplier organises their range,
* filter the articles of an import,
* pass the grouping back out on [export](/datanorm-item-import/datanorm_en_us/export/export-wizard.md).
## Switching processing off
If you do not need product groups, turn off **Process Product Groups** in the **Record Filters** section of the setup. S records are then skipped.
---
# 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/master-data-and-mappings/product-groups.md?ask=&goal=
```
`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.