Ordering windows

Concept

An ordering window controls when customers can place orders for a session.

In QueueJump, ordering opens at your configured open time and closes before session end based on your cutoff minutes. Collection flow is then shaped by slot duration and orders per slot.

Why it matters

Good ordering windows protect prep capacity and smooth collection demand.

• Customers get a clear and consistent ordering period.
• Teams avoid late intake that cannot be fulfilled properly.
• Slot pacing reduces last-minute queue spikes.
• Session performance becomes easier to review and improve.

Poor window settings usually lead to late prep pressure, frustrated customers, and avoidable refunds.

How to configure it

1. Go to Dashboard -> Sessions and create or edit a session.
2. Set the service start and end times.
3. Choose when ordering opens:
   • Immediately when you publish,
   • At a scheduled date/time, or
   • A set number of hours before session start.
4. Set order cutoff minutes (how long before session end new orders stop).
5. Set slot duration and orders per slot to match real throughput.
6. Save, then place a low-value live order before full launch.
7. During live service, use Orders -> Pause ordering only for temporary control, then resume when ready.

How to verify it worked

• Session status copy shows expected open/close behaviour in schedule.
• Orders begin appearing only when ordering opens.
• New orders stop at the expected cutoff.
• Collection slots align with what your team can fulfil.
• The orders queue stays manageable through peak service.

Related guides: Sessions and order settings and Service day runbook.

Common mistakes

• Opening ordering too late to build useful pre-order volume.
• Setting cutoff too close to end of service.
• Overestimating orders per slot on first launch.
• Changing time windows without checking active order impact.
• Leaving ordering paused after a temporary hold.