Menu v2 Concept
Menu v2 is the menu model behind every ordering channel on PAR Ordering — the web app, the native apps, kiosks, and the marketplaces connected through PAR Link. This page explains the shape of the model, so that the responses from the Menu v2 API make sense before you read them field by field.
Four entities in a tree
A menu is built from four kinds of entity:
- A Menu is the top of the tree — "Lunch", "Breakfast", "Catering". A brand can have several, and each store is served the ones assigned to it.
- A Category groups products — "Burgers", "Sides", "Drinks". Categories can nest.
- A Product is anything a customer can pick: a burger, a side, a sauce, a combo. The same entity type serves as a main item and as a modifier.
- A Product Group is a set of products attached to a product — "Choose a side", "Add a sauce" — with rules on how many must or may be chosen. A product inside a group can carry groups of its own, which is how nested modifiers work.

Entities are reused rather than copied. "Add a sauce" is defined once and attached to every burger, every side, and every wrap that offers sauces; adding a sauce to the group adds it everywhere the group appears. When one product should not offer one of the options, the brand hides that option for that product only — the group stays shared.

A price belongs to a placement, not a product
Because a product can appear in many places — on its own in a category, as a modifier under one product, as a modifier under another — it needs a price for each of those placements. French fries might be $2.00 as a side and $1.00 inside a combo.
That is why every product node in a Menu v2 response carries its own price_id, and why the cart is built from price_id values rather than product ids. The price_id identifies this product, at this place in this menu, at this store, and the same product has a different price_id under every parent it appears under. Prices come from the POS, so they match what the store charges. See Display Nested Menus for how the ids line up in a response, and the price_id warning in Server Side Cart for what goes wrong when the wrong one is sent.

One template, many stores
A brand defines a menu once, as a template, and assigns it to stores or store groups. Each store then gets its own copy with local prices and stock. Updating the template updates every store; marking an item out of stock at one store leaves it available everywhere else.
For an integration this means a menu is always read for a store: every Menu v2 call takes a venue_uuid, and Get Menus returns the menus that store serves, already resolved to its prices and availability. There is no brand-level menu to fetch.
Where to go next
- Display Nested Menus walks through the responses, including nested product groups and
included_ingredients. - Limited Time Products and Pre-Ordering cover products that are only available for a period.
- Secret Menus covers products that only some customers can see.
