> 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/kitchen-printer/configuring-the-kitchen-printer/final-steps-and-testing.md).

# Final Steps and Testing

{% stepper %}
{% step %}
Place a food service order

Place a food service order at the POS terminal.
{% endstep %}

{% step %}
Complete the transaction

Suspend (transaction must be recalled) or tender (complete the transaction) the transaction.
{% endstep %}

{% step %}
Verify the kitchen printer output

A second copy containing only food service items should print on the kitchen printer.

{% hint style="info" %}
See the Using the Kitchen Printer section for food service ordering steps and receipts.
{% endhint %}
{% endstep %}

{% step %}
Troubleshoot printing issues

If there are any printing issues:

1. Recheck the configuration settings. Specifically recheck the Kitchen Printer assignment within Rule Manager and confirm the information saved and the correct kitchen printer ID is assigned.
2. Go to Tools > Refresh Configuration.
3. Log out of the register and log back in and run another test.
4. Reboot the Commander Site Controller or RubyCi and retest.

{% hint style="info" %}
If the Back Office application specifically restricts any zero priced PLUs, contact the application's Support Desk to accommodate zero priced PLUs.
{% 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/kitchen-printer/configuring-the-kitchen-printer/final-steps-and-testing.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.
