> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dishink.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Kitchen Analytics

> Prep time, station throughput, bottlenecks, and dish-level kitchen timing.

Kitchen Analytics measures how fast your kitchen serves orders. Prep time, station throughput, bottlenecks, and dish-level timings all live here.

## Overview

Core metrics:

* Average prep time per item
* Time-in-status (new → preparing → ready → completed)
* Station throughput (grill, fry, bar, prep)
* Peak-hour heatmap
* Void reasons attributed to kitchen

## View kitchen analytics

<Frame caption="Kitchen analytics">
  <img src="https://mintlify.s3.us-west-1.amazonaws.com/dishink/images/reports/kitchen.png" alt="Kitchen analytics" />
</Frame>

<Note>
  Kitchen Analytics excludes voids and refunds from timing metrics — cancellations don't distort throughput.
</Note>

## Tips & best practices

<Tip>
  Set realistic prep targets. Aspirational targets colour every ticket red and nobody trusts the colour codes.
</Tip>

## Common mistakes

<Warning>
  Do not compare kitchen throughput between branches without matching menu complexity. A café with 10 items will always be faster than a full-service kitchen with 100.
</Warning>

## Related pages

* [KDS: Kitchen Statuses](/kds/kitchen-statuses)
* [Menu Items](/menu/menu-items)
* [Revenue Reports](/reports/revenue-reports)