Sessions and order settings

Concept

A session defines when you are trading, where customers collect, and which menu they can order from.

Order settings inside the session control intake behaviour, including cutoff timing, slot duration, orders per slot, and when ordering opens.

QueueJump also provides vendor-level defaults in Dashboard -> Settings -> Order settings. These defaults prefill new sessions for:

• When ordering opens (When published, Scheduled, or X hours before start)
• Customer edit cutoff
• Customer cancel cutoff
• Core intake defaults (cutoff, slot duration, orders per slot)

Sessions are created as drafts. You publish when setup is ready.

Why it matters

Session configuration determines whether service day feels controlled or chaotic.

• Customers get clear timing and collection expectations.
• Teams get manageable order flow in each slot.
• Publish checks catch setup issues before going live.
• Repeating sessions reduce admin overhead once defaults are stable.
• Vendor defaults make new sessions faster to configure and more consistent.

Good session settings protect throughput and reduce avoidable stress.

How to configure it

1. Go to Dashboard -> Sessions -> Create session.
2. Before building lots of sessions, set your baseline in Dashboard -> Settings -> Order settings:
   • Choose default ordering-open behaviour.
   • Set default customer edit and cancel cutoffs.
   • Set default cutoff, slot duration, and orders per slot.
3. Select outlet, location, and menu.
4. Set start and end times (including overnight sessions if needed).
5. Configure ordering rules:
   • Order cutoff
   • Slot duration
   • Orders per slot
   • Customer edit/cancel cutoffs
6. Choose when ordering opens:
   • Immediately on publish,
   • At a scheduled date/time, or
   • A set number of hours before session start.
7. Add optional access/meeting-point notes for session-specific context.
8. Save as draft, review warnings, then publish when requirements are met.
9. For repeated trading patterns, configure repeat cadence and end conditions.

Defaults apply to new sessions. You can override any value per session.

Publish readiness depends on setup quality, not just date/time completion.

How to verify it worked

• Session appears in schedule with the expected status and timing.
• A new session starts with your expected vendor defaults prefilled.
• Publish succeeds without blockers.
• Ordering open/close behaviour matches your configured rules.
• A low-value live order can be placed and appears in queue correctly.
• Repeating sessions generate as expected (if recurrence is enabled).

For deeper timing setup, see Ordering windows, Session overrides, and Service day runbook.

Common mistakes

• Publishing without testing one full customer checkout path.
• Skipping vendor defaults, then re-entering the same values on every new session.
• Setting optimistic slot capacity before observing real throughput.
• Forgetting to activate the outlet before publish.
• Using a menu with incomplete allergen declarations.
• Applying broad recurring rules before validating one successful service cycle.
• Assuming updated defaults change existing sessions automatically.