> 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/menu/menu-structure/significant-products.md).

# Significant Products

A **significant product** is any tangible item that will be produced as a unit of output in the kitchen. These are the **actual products** that customers receive, regardless of how they're priced or packaged. Essentially, these are products that kitchen staff need to prepare.

## Examples of Significant Products

Let's take this meal deal:

* **Level 1**: Quarter Pounder Meal (Quarter Pounder Burger with Chips and Drink)
  * **Level 2**: Quarter Pounder Burger
    * **Level 3**: Lettuce, Tomato, Cheese
  * **Level 2**: Chips
    * **Level 3**: Regular, Large
  * **Level 2**: Drink

The significant products are: **Quarter Pounder Burger, Regular Chips,** and **Drink.**

## Why This Matters

Significant products are what **appear on kitchen screens**. The meal deal is simply a pricing engine that groups significant products together at a different price point, but doesn't change what the customer physically receives. This means that if we have a meal deal, we need to have all of the significant products that are actually cooked within a meal to be present within Level 2 as in as customisations.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bossithq.com/menu/menu-structure/significant-products.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.