> 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/readme-1/process-a-basic-transaction/items-looking-up.md).
# Look up items
The easiest way to look up items is to scan them. However, if scanning doesn't work, there are other ways to look up items in POS.
## Entering the item lookup code
Every item has a unique **item lookup code (ILC)**. It is usually printed on the price tag or shelf tag. If you have the ILC, type it into the **lookup field** and press **Enter** to see matching items.
## Entering an item name or alias
If you don't have the ILC, or the ILC you have doesn't work, tap **Items** | **Lookup Item** or press **F2** to display the **Item Lookup** screen. From this screen you can try looking up the item by **item name** or **alias**. An alias is a unique nickname for an item. Aliases are optional and may not be defined for every item.
## Entering a department or category name
If you don't have the ILC, and weren't able to look up the item by item name or alias, you can also try looking up the item by **department** or **category** name.
## Entering a combination of item name, alias, description, and category
If the item lookup produces too many results and you don't have time to scroll through all of the results to find the item, try narrowing the results by entering a combination of item name, alias, description, and category.
## Entering a partial item name, alias, description, or category
You don't have to type the full item name, alias, description, or category into the lookup field. You can save time by entering just part of the word.
---
# 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/readme-1/process-a-basic-transaction/items-looking-up.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.