> 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/kitchen-display-system-kds/order-visibility-in-kds.md).

# Order Visibility in KDS

The KDS screen is designed to show only the orders that are relevant for preparation at a given time. The KDS does not display orders that are not yet to be prepared. The following rules determine when and which orders appear on the KDS:

## Order Status

The KDS displays **only** orders with the status **"In Progress"**. Orders in any other status will not appear.

## Start Preparing At Timestamp

The system calculates when the preparation time should start, influenced by workload modes. Orders are displayed once the **current time** is **equal or later than** the order's **Start Preparing At** timestamp.

**For scheduled orders:** If the current time is earlier than the Start Preparing At time, the order will remain hidden from the KDS. This means that scheduled orders will **not** appear on the KDS immediately. [Workload Mode for Scheduled Orders](https://docs.bossithq.com/workload/workload-mode-for-scheduled-orders.md)

{% hint style="info" %}
For orders that go to the Waiting Room, the Start Preparing At timestamp changes to when the order is fired from the Waiting Room to the KDS.
{% endhint %}

## Station-Specific Display

In venues with multiple kitchen stations, each KDS screen will display **only the products assigned to that specific station**.&#x20;

For meals that include products from multiple stations, the KDS will still separate the items based on station assignment. In other words, each station will only see its own component of the meal.

> **Example:**
>
> Pizza station KDS will only see pizza items, while Sides station KDS will only see side items.
>
> If a customer orders a meal that includes both pizza and sides, the products will appear on their respective station screens, rather than showing the full meal in once place.

## Filtering by Service

The KDS allows filtering of orders by **service type**.

> **Example:**
>
> A venue may configure the Pizza station KDS to display only Table and Takeaway orders.


---

# 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/kitchen-display-system-kds/order-visibility-in-kds.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.
