# Categories

In continuation to the previous section of architecture, we are assuming you have some fair idea of what a category or subcategory might be in a menu. A category is a combination of *related* items. In some menus, to further group the related items, restaurants use something called a Sub Category.

{% embed url="<https://www.loom.com/share/97a51f035ef04771aa724dce36e27e37>" %}
Category Section in a Menu
{% endembed %}

For example, suppose a restaurant has various Pizzas to offer - right from the Veg ones to the Non-veg ones. They also offer different Beverages, Desserts, Pastas etc. Let us assume that they have around 30 varieties of Pizzas. One way to make the menu is to make a category called "What’s New: San Francisco Style" which will have these 30 varieties listed inside it. However, notice that this might be way too "flat" in terms of presenting this in the menu to the customers. A better way might be introducing smaller groups inside "What’s New: San Francisco Style" something like – "Veg", "Non-veg", "San Francisco Style - Meals" and listing a smaller number of related pizza items. The veg, Non-veg and San Francisco Style - Meals here becomes the sub-categories in this case which is further specified grouping of the pizza items.

As you have got the context for the usage of categories and sub-categories, we believe you have realised that sub-categories are not a necessity in the menu but can be used based on scenarios as applicable.


---

# 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://api-docs.urbanpiper.com/downstream/menu/categories.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.
