> For the complete documentation index, see [llms.txt](https://docs.bossithq.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bossithq.com/pos/summary-screen.md).

# Summary Screen

The **Summary Screen** provides a real-time overview of all product components that need to be prepared.

When the **Summary Screen** is **enabled** for a venue. products can have **product component relations** defined in their configuration. The running total of the required components are displayed on the Summary Screen.

> **Example:**
>
> Product: Double Beef Burger
>
> Components:
>
> * Burger Buns — Quantity: 1
> * Beef Patty — Quantity: 2
>
> When a customer orders one Double Beef Burger, the Summary Screen will show:
>
> * Burger Bun: 1
> * Beef Patty: 2
>
> If multiple orders come in, the Summary Screen updates to reflect the **total number of each component** **required** across all active orders.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2F0fiDDWzFE13o96jaCNpk%2Fimage.png?alt=media&amp;token=7309d6bf-dd5f-4419-a4e3-95cd84dc2fc8" alt=""><figcaption></figcaption></figure>


---

# 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.bossithq.com/pos/summary-screen.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.
