> 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/workload/impact-of-workload-values-on-eta-and-other-order-timestamps/internal-cooking-time-vs-preparation-time.md).

# Internal Cooking Time vs Preparation Time

There can be a difference between the **customer-facing cooking time** (what is communicated externally) and the **internal cooking time** (what the kitchen actually requires). This ensures the customer expectation is managed while the kitchen operates efficiently.

## Example Scenarios

### Case 1: Internal Cooking Time matches Preparation Time

For this example, let's say the current time is 15:00 and the workload values are defined as:

* Internal Cooking Time: 20 minutes
* Preparation Time: 20 minutes
* Delivery Duration: 15 minutes

Since the Internal Cooking Time matches the Preparation Time at 20 minutes, the order will show on the KDS **immediately**.

### Case 2: Internal Cooking Time is different from Preparation Time

For this example, let's say the current time is 15:00 and the workload values are defined as:

* Internal Cooking Time: 15 minutes
* Preparation Time: 20 minutes
* Delivery Duration: 15 minutes

What this means is that the customer is told that the preparation takes 20 minutes, but the kitchen only needs 15 minutes. The order will not appear on the KDS until 15:05 (i.e., the Start Preparing At timestamp is 15:05).

{% hint style="info" %}
The **Start Preparing At** timestamp controls when the order appears on the KDS.
{% endhint %}


---

# 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/workload/impact-of-workload-values-on-eta-and-other-order-timestamps/internal-cooking-time-vs-preparation-time.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.