> 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/services/filtering-by-service.md).
# Filtering by Service
On various screens across the POS system, you can filter orders based on their service type.
## Order History Screen
You can filter the list of orders by service type to quickly locate specific transactions.
### How to Filter Orders on the Order History Screen
1. On the POS, open the **Order History screen**.
2. Click on **Service**.
3. Select which **Service** you want to display.
## Kitchen Display Screen (KDS)
You can filter each screen to display only the orders relevant to the services configured for it. For example, one kitchen KDS may show only Table and Takeaway orders, while another displays only Delivery. This helps staff reduce distractions and prioritise orders
### How to Filter Orders on the KDS
1. On the POS, open the **KDS screen**.
2. Click on the **Settings** icon.
3. Under **General Settings**, click on **Services**.
4. Select which **Service(s)** you want to display.
## Packing Screen
You can filter by service to split cooking flows by screens so that the venue can prioritise specific orders on a specific screen.
### How to Filter Orders on the Packing Screen
1. On the POS, open the **KDS screen**.
2. Click on the **Settings** icon.
3. Under **General Settings**, click on **Services**.
4. Select which **Service(s)** you want to display.
---
# 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/services/filtering-by-service.md?ask=&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.
