---
sidebar_label: 'Menu content'
sidebar_position: 2
---

# Menu content

## Menu definitions

A **menu definition** controls what a compiled menu contains by listing one or more content group and price group pairs. Each pair tells the platform: _include these categories and items, priced according to this price group_. The platform resolves all pairs in order to produce the final menu instance.

Because the two concerns — what is available and how it is priced — are separate, a single content group can be reused across many menu definitions. This makes several common patterns straightforward:

- **Same content, different pricing.** Two menu definitions for eat-in and takeaway can reference the same content group but different price groups, so prices change without duplicating the product catalogue.
- **Shared base assortment.** A core content group covers items available at every store. A second content group covers store-specific items. Each menu definition combines the shared group with the relevant store-specific group.

<!-- :::warning
It is not supported to configure a menu so that an item is included more than once
The same item must not appear more than once within a single menu definition. If two content groups included in the same definition both reference the same item, the resulting menu is invalid.
::: -->

**Example:** Two menu definitions, each built from a shared and a local content group:

| Menu definition | Content & price group pairs |
|---|---|
| MD1 (Store A, eat-in) | CG-Base + PG-Standard, CG-StoreA + PG-Standard |
| MD2 (Store B, eat-in) | CG-Base + PG-Standard, CG-StoreB + PG-Premium |

## Content groups

A **content group** is a named set of categories and items. It has two roles: it determines _which_ categories and items are available in a menu, and it controls the _order_ in which root categories are displayed to the guest.