Menu items and modifiers

Concept

Menu items are the products customers purchase. Modifiers and variants define how those items can be customised.

Each item should have:

• Clear pricing
• Predictable availability
• Defined option logic

The goal is to keep both checkout and kitchen preparation unambiguous.

QueueJump supports three common modifier patterns:

• Required choices: the customer must select within defined minimum and maximum rules.
• Optional add-ons: the customer may select none or multiple extras.
• Removals: the customer can remove components, typically without additional charge.

If required choices are incomplete, or variant pricing is missing, the item may not be orderable.

Why it matters

Strong item configuration improves both conversion quality and service flow.

• Customers place more accurate orders.
• Teams spend less time clarifying tickets.
• Refund and support friction is reduced.
• Sessions are easier to publish without validation errors.

The item model is where operational detail becomes customer behaviour. Small setup decisions have visible impact during service.

How to configure it

1. Open the relevant menu and select Add item.
2. Enter a clear item name and short, practical description.
3. Choose a pricing mode:
   • Single price, or
   • Variants (for example size-based pricing).
4. If using variants, ensure each variant has both a label and a price.
5. Add modifier groups and define their behaviour:
   • Required choices (for example size, heat level, bread type).
   • Optional add-ons (for example extra cheese, toppings).
   • Removals (for example no onion, no mayo).
6. Configure minimum and maximum selection rules so customer behaviour matches real service constraints.
7. Set pricing adjustments where relevant:
   • Positive adjustment for paid extras (for example +£1.00).
   • Negative adjustment where intentionally discounted.
   • Zero adjustment where no price change applies.
8. Set availability rules and apply temporary pauses where needed.
9. Confirm allergen declarations and dietary tags.
10. Save and verify any high-customisation item with a low-value live order.

Keep modifier structures practical. Complexity should reflect real service needs, not theoretical choice depth.

Customers will see required and optional choice prompts on item pages. Selected modifiers, including +/- pricing, carry through into basket and order detail.

How to verify it worked

After saving:

• The item appears in the correct menu section.
• Required choices cannot be bypassed at checkout.
• Price adjustments display correctly in the basket.
• Modifiers are clearly shown in order detail and kitchen workflow.
• Allergen declarations are present where required.

Before publishing a session, place a low-value live order for any item with multiple modifier groups.

Compliance

Food items must have allergen declarations confirmed before related sessions can be published.

QueueJump enforces this to reduce compliance risk and prevent incomplete menu publication.

Common mistakes

• Creating overly complex modifier trees that slow customer decision-making.
• Forgetting to set minimum rules on required choices.
• Missing variant pricing, causing items to be unorderable.
• Leaving seasonal or paused options active.
• Using unclear internal naming for modifier groups.