> 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/kds-settings/enforce-cooking-stage-flow-for-table-service.md).

# Enforce Cooking Stage Flow (For Table Service)

When "Enforce cooking stage flow" is enabled, the system controls the timing of when different courses are prepared to ensure proper service flow.

## Starters

Starter items can be cooked immediately upon order. Starters stations has full access to begin cooking.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2FgKirhmPuICh0Vwwhpk9y%2Fimage.png?alt=media&amp;token=51305d30-ad13-49f6-b4d6-d0caae8028ef" alt=""><figcaption></figcaption></figure>

## Mains

Main course items are held and cannot be cooked initially. They appear on appropriate kitchen screens but are blocked from preparation until staff manually releases the hold.

<figure><img src="https://1925381409-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F5cJdZdmiiIn3u107Grmv%2Fuploads%2F2xpu1tH2amdESogwUC0D%2Fimage.png?alt=media&amp;token=c56f11ee-5403-43a1-962b-e1f561f6e85a" alt=""><figcaption></figcaption></figure>

## Desserts

Because desserts are ordered after the main course is underway or finished, there's no need to put a hold on them—their natural ordering timing already provides the proper service flow.

Since desserts are typically ordered later, these products can be cooked immediately when they appear.


---

# 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/kds-settings/enforce-cooking-stage-flow-for-table-service.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.
