> 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/configuring-the-kitchen-printer/pre-installation-menu-preparation.md).

# Pre-Installation Menu Preparation

The following pre-installation list will facilitate setup and maintenance of the Kitchen Printer feature.

{% hint style="info" %}
To specifically review how to configure menus and menu chains, see the "POS Menu User Reference."
{% endhint %}

## **PLUs**

{% stepper %}
{% step %}
Create the PLUs

Create the PLUs for all food service products including condiments and toppings.
{% endstep %}

{% step %}
Link the PLUs

Link only PLUs to Departments that contain kitchen printer menu items. Include all zero priced PLUs (i.e. condiments and subitems) in the PLU price book.
{% endstep %}

{% step %}
Delete obsolete menus

Delete obsolete menus or menu items.
{% endstep %}

{% step %}
List food service items

List all food service items including PLU#, description, price and department assignment.
{% endstep %}

{% step %}
List condiments and upsells

List all condiments and upsells, i.e. lettuce, tomato, mayo, cheese, extra cheese, etc.
{% endstep %}

{% step %}
Establish PLU codes

Establish a range of available PLUs Codes housed in the price book to be used specifically for food service items.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
If an item is sent to the kitchen printer, it must have an associated PLU.
{% endhint %}

## **Food Service Items**

{% stepper %}
{% step %}
Group the food service items

* Placing a food service order on a POS terminal is different from placing a food service order on a self-service kiosk.
  * On the kiosk, the next screen is determined by the selection that is made.
  * With the POS terminal, the next screen is always the same regardless of the selection made.
* Do not combine 6" subs and 12" subs on the same menu unless the options and upsells are the same; 12" upsells are more expensive.
  {% endstep %}

{% step %}
Configure menus as single-select

All menus should be configured as single-select. Only the last menu in the chain is configured (optional) as multi-select.

* When placing a food service orders at the POS terminal, it uses a linked menu feature to lead clerks through a series of menus to build the item order.
* A sandwich order can include a menu with sandwich types (items) and a series of subitem menus (breads, cheeses, condiments, etc).
* The first item is always the menu item and all subsequent items are subitems.
  {% endstep %}
  {% endstepper %}

## **Meal Deals**

{% stepper %}
{% step %}
Implement signage

Implement signage to inform customers of food service promotions.
{% endstep %}

{% step %}
Utilize promotions

Utilize Verifone Integrated Promotions (VIP) NAXML Combos and Mix and Match to configure automatic discounts.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
See the "VIP NAXML Mix and Match Feature Reference" to configure automatic discounts on the Commander Site Controller.
{% endhint %}

## **Design Menus**

{% stepper %}
{% step %}
Utilize the menu worksheets

Utilize the menu worksheets provided (see Appendix) to facilitate food service menu preparation. Worksheets include 4x4 grids to accommodate 16 item entries to be displayed for menu item selection.
{% endstep %}

{% step %}
Insert a menu header

Insert a menu header (name) to include when a food service order is placed.
{% endstep %}

{% step %}
Complete each block

Complete each block with an appropriate PLU#, description and price.
{% endstep %}
{% endstepper %}

{% hint style="info" %}
The PLU description and number identify the correct PLU for menu assignment. Prices help differentiate between item size, subitems upsells and zero-priced items.
{% endhint %}


---

# 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/configuring-the-kitchen-printer/pre-installation-menu-preparation.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.
