> For the complete documentation index, see [llms.txt](https://support.kea.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.kea.ai/kea-ai-customer-faqs/why-is-there-a-kea-mark-up-line-item-on-my-clover-pos-ticket.md).

# Why is there a "Kea - Mark Up" line item on my Clover POS ticket?

### If the menu you have visible to Kea has a different price than what is in in your POS (Clover) this line item is added to align revenue expectations and see the markup / additional revenue gained per channel. <a href="#hs_cos_wrapper_kb-article-module-4" id="hs_cos_wrapper_kb-article-module-4"></a>

For example, if you have a different menu visible to Kea>Stream than what your in-house staff is using to take orders, then your POS will automatically add or subtract the difference.&#x20;

This is common with Online Ordering or DoorDash menus being visible to Kea while servers use a different menu with internal charges.&#x20;

* You may see Kea sending a ticket through that says:\
  Cheese Pizza $5.50
* But your in-house menu rings up Cheese Pizzas as $7
* The Kea ticket will show a total of $5.50 but the ticket that prints in house will show:
  * Total = $7
    * Kea - Markup -$1.50&#x20;

To ensure the customer is being charged the same amount across all channels.&#x20;


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://support.kea.ai/kea-ai-customer-faqs/why-is-there-a-kea-mark-up-line-item-on-my-clover-pos-ticket.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.