Skip to main content
↓ Download as Markdown

Menu content

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.

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

Menu definitionContent & 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.