# Meal Deal Design Best Practice

A frequent mistake occurs when designing meal deals by creating separate sections for each component without including the primary significant product.

## Incorrect Approach Example

**Quarter Pounder Burger Meal**

* Choose your Burger Toppings:
  * Lettuce
  * Tomato
  * Cheese
* Choose your Burger Sauce:
  * Ketchup
  * Mayo
  * BBQ Sauce
* Choose your Chips:
  * Regular Chips
  * Large Chips
* Choose your Drink:
  * Coca-Cola
  * Sprite
  * Fanta

### In POS

While it would allow you to choose the sauce and the toppings, the actual burger is missing.

<figure><img src="/files/ddIMPZKP6SSaSjNYjoPU" alt=""><figcaption></figcaption></figure>

### In KDS

Since the burger is missing from the order, it will not show up in the KDS.

<figure><img src="/files/GFokWheYVRWJShrBPmaQ" alt=""><figcaption></figcaption></figure>

## The Problem

When a customer selects BBQ, Cheese, Lettuce, Regular Chips, and Fanta the kitchen screens display:

* BBQ
* Cheese
* Lettuce
* Regular Chips
* Fanta

**Missing:** The actual **Quarter Pounder Burger** that the toppings belong to. And because the significant product is missing, kitchen staff only see toppings but don't know what to put them on.&#x20;

**Routing Issue:** More often than not, these toppings are not even assigned to a specific station. Therefore, these toppings won't show at any kitchen screen.

## The Solution

To properly configure meal deals, you must **include the significant product** within the meal.  We need to set it as a default product (i.e., set the default quantity value of 1 or however many of that product is in the meal deal).

## Correct Approach Example

**Quarter Pounder Burger Meal**

* Choose your Burger:
  * Quarter Pounder Burger (default quantity is 1)
* Choose your Chips:
  * Regular Chips
  * Large Chips
* Choose your Drink:
  * Coca-Cola
  * Sprite
  * Fanta

Ensure that the Quarter Pounder Burger exists as a standalone product, with all its customisation options configured. The meal will automatically pull the customisations of the product.

You can use a pre-existing **Burgers** customisation and set the default quantity and limit of the Quarter Pounder Burger to 1. Hide the other products if necessary.

### In POS

Now that we've added the Quarter Pounder Burger and set it as the default and only available product, it will be shown as part of the meal deal.

<figure><img src="/files/HguzMHfUQgETlRBDTBMc" alt=""><figcaption></figcaption></figure>

The customisations within the product carry over, allowing us to still make modifications to it.

<figure><img src="/files/yRObFp2b98H1iKyXCR0m" alt=""><figcaption></figcaption></figure>

### In KDS

The burger will then be routed to its assigned station, showing in KDS.

<figure><img src="/files/xWMtpJpE1lhMWxxU36mX" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.bossithq.com/menu/menu-structure/meal-deal-design-best-practice.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.