innkept

Menus & menu items

Build food and drink offerings. Mark items as default, attach allergens, set sort order.

A menu is a named collection of menu items — usually a coherent food & drink offering. "Wedding feast 2026", "Canapé reception", "Three-course corporate". Guests pick from the items inside the menu they choose.

The two-level structure

Menus aren't a category for individual dishes — they're whole offerings. A guest planning a wedding picks one menu, then ticks the items they want from inside it. If you want to offer guests a choice between a sit-down meal and a buffet, that's two menus.

Adding a menu

Open Menus → New menu. Fields:

  • Location — leave blank to apply across all locations, or scope to a venue.
  • Name — what guests see, e.g. "Wedding feast 2026".
  • Description — context: what's this menu for, when does it apply.
  • Event types — restrict which event types it shows up for.
  • Active — uncheck to hide without deleting.

Adding items to a menu

Open the menu, then Add item. Each item has:

FieldNotes
CategoryFree-text — e.g. starter, main, dessert, drinks. Items are grouped by category in the configurator.
NameRequired.
DescriptionUp to 2,000 characters. Show off — this is what sells the item.
PriceIn pounds. Stored as pence internally.
Price unitflat, per_guest, or per_hour. Almost always per_guest for menu items.
DietaryTags like vegan, vegetarian, gluten-free. Shown as small chips on the item.
AllergensTags like nuts, dairy, shellfish. Worth taking seriously.
DefaultPre-selects this item in the configurator. Use for items most guests pick.
Sort orderInteger, ascending. Drives display order within the category.
ActiveUncheck to hide without deleting.

How items appear in the configurator

  1. The guest picks a menu (skipped if you only have one matching their location + event type).
  2. Items appear grouped by category, sorted by sort_order.
  3. Items marked default start ticked. The guest can untick them.
  4. The total updates as items toggle.

Allergens & dietary tags

Allergens appear as small red chips next to the item name. Dietary tags appear as neutral chips. Both are stored as arrays on the menu item — add as many as apply.

The configurator is not your allergen disclosure. Treat allergen tags as guest-facing context, not as a substitute for the legal allergen statement on your menu and at the point of service.

Multiple menus per event type

You can have several active menus tagged for the same event type — the guest will see all of them and pick one. Useful for offering "early bird" vs "premium" options, or seasonal menus.

Something missing or wrong? Tell us.

Updated regularly. UK English. No AI slop.