> For the complete documentation index, see [llms.txt](https://docs.rmhpos.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rmhpos.com/store-manager/manage-items/use-the-import-utility-to-add-and-update-items/importing-items-import-utility-mapping-rules.md).

# Mapping rules for the Import Utility Wizard

When you are importing items or aliases using the Import Utility Wizard, ensure you follow the applicable mapping rules.

## **Rules for Items**

* The **Item Lookup Code** column must be mapped. This is mandatory for item import.
* If you are mapping the **Category Code**, the **Department Code** must also be mapped. This is a requirement because of the relationship between Department and Category in the database.
* Any **Supplier Code**, **Department Code**, **Category Code**, **Tag Along Item Lookup Code**, **Tax Code**, **Parent Item Lookup Code**, or **Item Message Code** included in the import file must exist in the database prior to import. You cannot use the Import Utility Wizard to add these codes to the database.
* You cannot use the Import Utility Wizard to update the **Item Lookup Code** for existing items.

## **Rules for Aliases**

* The **Item Lookup Code** and **Alias** columns must be mapped. This is mandatory for alias import.


---

# 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.rmhpos.com/store-manager/manage-items/use-the-import-utility-to-add-and-update-items/importing-items-import-utility-mapping-rules.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.