> 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/products/product-types.md).

# Product Types

{% hint style="warning" %}
The distinction between **Regular** and **Detailed** products applies only within the POS. Regular products are added directly to the basket, while Detailed products trigger a customisation screen. Outside of the POS, they function in the same way.
{% endhint %}

## Regular

A Regular Product is a standard item that is added directly to the basket when selected. It does not trigger a customisation pop-up. (e.g., Coca-Cola)

## Detailed

A Detailed Product opens a customisation pop-up when selected. This allows the item to be modified with options such as toppings or add-ons. (e.g., Burger, Pizza)

## Meal/Combo

A Meal or Combo is made up of a combination of Regular and/or Detailed Products. A Meal/Combo must consist only of Regular and/or Detailed Products, and cannot include another Meal or Combo. The only difference between them is that a Combo displays the product names in brackets on the KDS.

## Splittable

Splittable products allow you to combine existing products into a single item that's divided into parts.&#x20;


---

# 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/menu/products/product-types.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.
