> 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/fleet-cards-exxonmobil/appendix/configuring-pos-user-interface-using-configuration-client.md).

# Configuring POS User Interface Using Configuration Client

How to configures buttons on the touch screen has changed. Instead of only having screens with buttons, the user can now configure panels within screens, and have as many item buttons as they want on the panels. The user can swipe to access the ones not displayed on screen.

{% hint style="info" %}
*Refer to Base 53 and Higher User Interface User Reference for more information on the new User Interface.*
{% endhint %}

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.

## Panel Configuration

Go to **Store Operations > Touch Screen > Panel Configuration**to configure panels and to configure items assigned to panels.

Panels are of the following types:

* Item Panel
* Parked Menu Panel
* Fuel Panel

A screen can have multiple item panels. A screen can have only one fuel panel and one parked menu panel. Also, only one fuel panel and parked menu panel can be assigned to a POS register; but, these fuel panel and parked menu panels can be included in multiple screens on the register.

**Item Panels**

Use Item Panels form to configure panels that have PLU, Department, MOP, Function or Menu Key items.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/jXDFoJcz1iCYjfMf9FOn/Unknown%20image)

1. Click **Add.**
2. Enter Name of the Item Panel.
3. Click **Add Item**.
4. Click Type and select the type of item from PLU, Department, MOP, Function or Menu Key and add the item.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/N6hGO6tALWxuWnxW7t6g/Unknown%20image)

Click **Preview**to change item properties like line1, line2, background color and label color.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/U1Q8l7zU0TQCUE8A4nqV/Unknown%20image)

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/GPNkIrakSLQtWlmnUfmN/Unknown%20image)

Items can be moved in the panel by selecting the item and dragging and dropping to the desired position

Click **Save**.

Click on Preview/edit button to view the item panel on the POS screen for the selected item panel.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/3SCDwaXGI0T3gtnlsFhY/Unknown%20image)

**Item Panel Preview for Topaz/Ruby2 POS**

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/G3D9JE9Iyn42M2H2qtod/Unknown%20image)

**Item Panel Preview for C18 POS With Utility Panel**

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/vFUrph0cc3WqtzssTg2v/Unknown%20image)

Item Panel Preview for C18 Without Utility Panel

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/oL29Tvxq8727RQcOBOtj/Unknown%20image)

{% hint style="info" %}
Select an Item panel and click Duplicate to create a duplicate item panel from the existing item panels.
{% endhint %}

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/3SCDwaXGI0T3gtnlsFhY/Unknown%20image)

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/OkaetrgsH1jxpqw2U73S/Unknown%20image)

**Parked Menu Panels**

Use Parked Menu Panels form to configure Parked Menu. This feature displays each menu item on individual buttons of the parked menu panel so that a single touch adds the

item to the transaction. Refer to the **Menus**chapter in Commander Site Controller User Reference to see how different types of menus are configured.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/DG1diaK7ORgWMk9rJzbQ/Unknown%20image)

1. Click **Add**.
2. Enter a name for the Parked Menu panel.
3. In Menu Properties, select a Default Parked Menu. Refer to the **Menus**chapter in Commander Site Controller User Reference to see how menus are configured.
4. Select the text color and the background color for the items in the panel.
5. Click **Save**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/arDIM4bFdLSDI1VeHRVT/Unknown%20image)

Select a Parked Menu Panel and click Duplicate to create a duplicate parked menu panel from the existing parked menu panels.

**Fuel Panels**

Use Fuel Panels form to configure fuel keys for the POS touch screen.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/upD9sv7SkHql8q7c4DRr/Unknown%20image)

1. Click **Add**.
2. Enter a name for the Fuel Panel.
3. In Properties, specify the ID of the beginning fueling position and the number of fueling positions to be included in the fuel panel.
4. Click **Save**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/arDIM4bFdLSDI1VeHRVT/Unknown%20image)

Select a Fuel panel and click Duplicate to create a duplicate Fuel Panel from the existing Fuel Panels.

## Screen Configuration

After the panels are created, create screens and assign panels to screens.

* * There can be a maximum of three panels on a screen.
  * A screen can have multiple item panels.
  * A screen can have only one fuel and parked menu panels.
  * A register can only have one fuel and parked menu panels.
  * These fuel and parked menu panels can be included in multiple screens on the register.

POS screen configured with a Fuel, Item and Parked Menu panels.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/wCMR0kOVlngWYY13UR7p/Unknown%20image)

POS Screen configured with three Item panels.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/hmX6hDhy320FfWQUi3at/Unknown%20image)

1. To create a new screen, click **Add**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/9YR4YWrE6B5sJhjnr3CE/Unknown%20image)

1. Enter a name for the screen.
2. Click **Add Panel**.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/hirxsDt25uhXVrPyIQo1/Unknown%20image)

1. Select the panel to assign to the screen area.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/ebw2ojMZKG0PBWooqUmJ/Unknown%20image) ![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/3ivHt7SFdoJGcoZrbqD1/Unknown%20image)

*Only one type of Fuel Panel and Parked Menu Panel is allowed per register and the assignment of Fuel Panel and Parked Menu Panel to the Register is done on the Register Configuration form.*

1. ![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/Vyy3LFE7jVE1Pf0NOyot/Unknown%20image)Selecting Item Panel takes you to a screen to select the Item Panel from the list of Item panels. More than one item panel can be selected and those will be merged into a single panel.
2. Select a panel and click **Move Up**or **Move Down**to move the panel.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/hmX6hDhy320FfWQUi3at/Unknown%20image)

## Register Configuration

Use Register Configuration form to assign screens to register.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/Rnp59Medeb0j8yXMdO8V/Unknown%20image)

1. Select **Register**.
2. In Panel Selection section, select the Fuel panel and Parked Menu Panel.
3. From the **Available**section, add the screens you want on the register to the **Selected**

section.


---

# 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/fleet-cards-exxonmobil/appendix/configuring-pos-user-interface-using-configuration-client.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.
