Outlets

Concept

An outlet is the operational unit you trade from in QueueJump.

In practice, each outlet holds your service identity for scheduling: name, outlet type, notes, status, and optional banner image. Every session is then attached to one outlet.

If you run more than one operation (for example a truck and a pop-up stall), create separate outlets so sessions, reporting, and ownership stay unambiguous.

Why it matters

A clean outlet structure makes event-day operations easier to run.

• Schedules are clearer because each session is assigned to the correct service unit.
• Team handover is simpler because everyone knows which outlet owns each service window.
• Operational reporting stays accurate when orders and sessions map to the right outlet.
• Growth is easier to manage as you add additional trading units.

Done well, outlet setup reduces avoidable mistakes on busy service days.

How to configure it

1. Go to Dashboard -> Outlets and select Add outlet.
2. Add a clear outlet name that your team will recognise quickly during service.
3. Select the closest outlet type (Truck, Pop-up, Restaurant, Café, Catering, or Other).
4. Add internal notes where useful (handover context, setup constraints, or operating details).
5. Save the outlet, then assign new sessions to that outlet when planning dates and collection windows.
6. Repeat only where you have genuinely separate operations.

Use one outlet per real service unit, not per menu or per event theme.

How to verify it worked

• The outlet appears in your outlet list with the expected name and type.
• New sessions can be assigned to the outlet without confusion.
• The outlet detail page shows the expected number of draft or published sessions.
• Team members can identify which outlet owns each live service window.

For a full setup sequence, continue with Locations, Team and permissions, and Service day runbook.

Common mistakes

• Creating outlets for temporary campaigns instead of real operational units.
• Using vague names that are hard to identify during service.
• Leaving all outlets active even when they are no longer used.
• Deleting an outlet before checking whether future sessions are linked to it.
• Mixing multiple service models inside one outlet when separate outlets are clearer.