Menus

Concept

A menu is the product set customers order from during a session.

You can create multiple menus for different service contexts, for example a regular weekday offer, a festival menu, or a reduced high-volume menu.

In QueueJump, sessions are linked to a specific menu. You can also mark one menu as your default so it is preselected when scheduling.

Why it matters

Good menu structure improves both conversion and service operations.

• Customers decide faster when the menu is focused and easy to scan.
• Teams prep faster when sections and item naming are consistent.
• Session setup is quicker when reusable menus are already organised.
• Operational risk is lower when launch menus are tight and predictable.

If menus are unclear or over-complex, errors usually show up during peak service.

How to configure it

1. Go to Dashboard -> Menus and select Create menu.
2. Give the menu a clear internal title your team will recognise.
3. Set it as default if this is your main trading menu.
4. Add sections first, then add your first menu items.
5. Keep launch menus focused, then expand once service flow is stable.
6. Assign the correct menu when scheduling each session.
7. For seasonal or event variants, duplicate or copy from an existing menu rather than rebuilding from scratch.

A menu without items is not service-ready.

How to verify it worked

• The menu appears in your menu list and can be selected in session setup.
• Item count is greater than zero.
• No item in the menu is flagged as needing setup.
• A low-value live order shows the expected items and prices.

For onboarding sequence, continue with Menu items and modifiers, then Sessions and order settings.

Common mistakes

• Creating too many menus before running one stable live service.
• Leaving a menu empty and assuming it is ready for publish.
• Using unclear menu names that make session setup slower.
• Making large changes to a live menu without placing a low-value live order.
• Forgetting which menu is marked as default.