> For the complete documentation index, see [llms.txt](https://commanderhelp.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://commanderhelp.verifone.com/feature-references/features-and-products-references/open-plu/configuring-open-plus/configure-an-open-plu-on-the-touch-screen.md).

# Configure an Open PLU on the Touch Screen

The touch screen configuration is divided into three parts:

* Panel Configuration
* Screen Configuration
* Register Configuration

**Register**: Each Register/POS can be configured to have one or more screens.

**Screens**: Each screen has a name and can be configured to have up to three panels. All screens appear as tabs on the register.

**User Panel**: The area within a screen with these panels is collectively referred to as User Panel.

{% hint style="info" %}
*See the Release 53 & Higher UI Reference for more information on configuring the Touch Screen UI.*
{% endhint %}

After an Open PLU is created, it must be assigned to a POS touch screen.

{% stepper %}
{% step %}
**Touch Screen**

From the Verifone Configuration Client, go to: **Store Operations > Touch Screen**.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FAmywaGeah9eGItByPmNl%2Fimage.png?alt=media&amp;token=e65a7183-6f04-4995-a5dd-ccfa117019b3" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Panel Configuration**

Select Panel Configuration and Item Panel in Panel Configuration.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fotf7db6WfrMs7FKzJQdw%2Fimage.png?alt=media&amp;token=cab823f2-70d4-4c22-b03d-c89c3d6cc30c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Add Item**

Click Add Item to add an open PLU.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fv1kBDVXJBuSRp4tslYqS%2Fimage.png?alt=media&amp;token=893c20d4-2e5e-47e4-b89e-fa97d78626ef" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}
**Type Column**

From the type column, select PLU.
{% endstep %}

{% step %}
**Open PLU**

Select the Open PLU to be added.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2FKcnkiHjkYNoEJSueNU9D%2Fimage.png?alt=media&amp;token=db5e97eb-aa1f-4f74-b74b-99b1d24688d9" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The PLU should be created as an Open PLU in **Store Operations > PLU**.
{% endhint %}
{% endstep %}

{% step %}
**Item Panel**

If not already assigned, go to **Store Operations > Touch Screen > Screen Configuration** to assign the Item Panel with the Open PLU to a screen.
{% endstep %}

{% step %}
**Screen**

If not already assigned, go to **Store Operations > Touch Screen > Register Configuration** to assign the screen to a register/POS.

{% hint style="info" %}
Refer to the Release 53 & Higher UI Reference for more information on configuring the Touch Screen UI.
{% endhint %}
{% endstep %}
{% endstepper %}


---

# 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://commanderhelp.verifone.com/feature-references/features-and-products-references/open-plu/configuring-open-plus/configure-an-open-plu-on-the-touch-screen.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.
