> 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/customize-the-pos-screen/items-enabling-line-item-details.md).

# Enable line item details in transaction lists

This topic describes how to enable the line item details row in the Transaction tab in POS.

Stores have the option to enable line item details in transaction lists. The line item details offer more information about an item, such as the quantity available in the store, the current price, whether the item is on sale, and the bin location.

If line item details are not enabled, you can only see a summary line for each item in the transaction list:

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-83db9ef4b3fb4bd16e7cf132ee1c9578781b5df3%2FPOS_line_item_detail_off.png?alt=media" alt=""></div>

If line item details are enabled, however, an arrow displays on the summary line. Click this arrow to display the item details line below the summary line:

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-e7619598a3900d9191d644f0ad9c21acfc81a546%2FPOS_line_item_detail_on.png?alt=media" alt=""></div>

Enabling line item details is a two-step process:

1. Enable line item details in the POS profile.
2. Assign the POS Profile to the register(s).

## **Enable line item details in the POS profile**

1. In Store Manager, click **Setup**.
2. Expand **Hardware**.
3. Click **POS Profiles**.
4. Do one of the following:

* Double-click an existing POS profile to open and edit it.
* Click **New** and create a new POS profile.

5. Select **Enable line item detail row**.
6. Click **Save And Close**.

## **Assign the POS profile to the register(s)**

1. In Store Manager, click **Setup**.
2. Expand **Hardware**.
3. Click **Register List**.
4. Do one of the following:

* Double-click an existing register to open and edit it.
* Click **New** and create a new register.

5. On the **General** tab, from **POS Profile**, select the POS profile with line item details enabled.

<div align="left"><img src="https://2921455087-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fjgsd9U4TRO2qgcIBegi7%2Fuploads%2Fgit-blob-ddc17c38f05474b4da0f847f54d693c8d542d9be%2FSM_Register_POS_Profile_Selected.png?alt=media" alt=""></div>

6. Click **Save And Close**. Line item details are now enabled for the register(s) using the POS profile.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rmhpos.com/readme-1/customize-the-pos-screen/items-enabling-line-item-details.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
