> For the complete documentation index, see [llms.txt](https://docs.verifone.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.verifone.com/feature-references/features-and-products-references/kitchen-printer/appendix/design-the-menu.md).

# Design the Menu

{% stepper %}
{% step %}
Place sandwiches in the same relative location

Place sandwiches in the same relative location on each menu.

1. The 6" and 12" Sub menus below represent the first menu in each of two menu chains. A selection from either menu is automatically assumed to be an item.
2. Subitems (components of these items) are printed in the same sequence. When planning subitems, consider how a sandwich is built.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/v9HDrLFX3gFVCXi5zz6C/images/image71.jpeg) ![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/tWA5FgIFxQ1sE62zsguL/images/image72.jpeg)
{% endstep %}

{% step %}
Create bread menus

Bread options vary by size; create menus for the bread selections for both 6" and 12" menus.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/NODkuGlWo4MExl0dcsX0/images/image73.jpeg)

The bread for a 12" sub still requires a menu to offer it as an "option," even if it is the only option available.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/KUk69BDjb8qgYhKpuWYx/images/image74.jpeg)
{% endstep %}

{% step %}
Create cheese menus

Create menus for the cheese selections for both 6" and 12" menus.

* Cheese is included in the sandwich price, but extra cheese is an upsell.
* Not all customers order cheese. The clerk can press the \[NEXT] option to make a no cheese selection, then proceed to the next menu in the chain.

{% hint style="info" %}
The same options can be grouped in the same relative positions with different PLUs for the upsells.
{% endhint %}

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/5fQ3qIvE07aDrw5QoAb1/images/image75.jpeg)

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/uFZDS6N3i8sIsnb93mKF/images/image76.jpeg)
{% endstep %}

{% step %}
Create bacon menus

Create menus for the bacon selections for both 6" and 12" menus.

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/4eExT4aTE0uXicZGe6Nd/images/image77.jpeg)

![](https://content.gitbook.com/content/5nJgnNKJ9ZrZeEdr7pqh/blobs/Ez5Hf4IQNen1CFWvRh5F/images/image78.jpeg)
{% endstep %}

{% step %}
Create a toppings menu

Create one menu for free topping selections for both 6" and 12" menus.

<figure><img src="https://1800087076-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5nJgnNKJ9ZrZeEdr7pqh%2Fuploads%2Fbu8tGwpyy1XJKCk0ADfv%2Fimage.png?alt=media&amp;token=2d550e6c-2413-48db-aaea-ea6da407d025" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
One menu is sufficient for both size subs because a single menu can be used in multiple menu chains, and sales are not being tracked for free toppings.
{% endhint %}

The user may be tempted to add these additional items to other menus (i.e. bacon on the cheese menu). However, if a customer wants a specific type of cheese as well as bacon, this would imply a multi-select menu.

The POS terminal permits only one multi-select menu in the chain and it must be the last menu. Bacon would need to be its own separate menu because toppings haven't require multiple-select options.
{% endstep %}
{% endstepper %}

## Configure POS Terminal Menus

The POS terminal configuration is completed in several stages:

{% stepper %}
{% step %}
Configure each worksheet as a POS Menu

* All menus are "Expanded Single-Select" except Toppings.
* The Toppings menu should be "Expanded Multi-Select."
  {% endstep %}

{% step %}
Configure the Menu Chain for each item type

* Select \[Menu Chain] as the menu type.
* Select \[Order Menu].
  {% endstep %}

{% step %}
Select the menus in order

* 6" Subs
* 6" Bread
* 6" Cheese
* 6" Bacon
* Toppings
  {% endstep %}

{% step %}
Assign menu chains

Assign menu chains to a \<key> on the POS terminal.
{% endstep %}

{% step %}
Test each chain

Test each chain to verify the ordering process flows properly.
{% 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://docs.verifone.com/feature-references/features-and-products-references/kitchen-printer/appendix/design-the-menu.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.
