ShiftQ and Order Board operations and playback

What this does

Use ShiftQ for live sales/labor signals and Order Board for location queue state and display output.

Steps

1. Confirm group or location scope.
2. Open ShiftQ for sales, labor, and source freshness.
3. Open Order Board for open, ready, and completed ticket flow.
4. Refresh or filter to the intended location/date.
5. Verify the TV preview or display and Toast connection when data is missing.

ShiftQ

Metrics reflect the selected scope and source timestamp. Group scope rolls up eligible locations; location scope shows a single venue.

Order Board

Open and Ready are operational queues; completion removes a ticket from active playback according to the configured flow.

TV playback

Preview checks presentation. Live output also depends on published assignment, Player health, and location connectivity.

Permissions and scope

• No Access hides or blocks the module. Read Only permits viewing but disables changes. Editor permits the documented create, edit, publish, or administrative actions within the user's assigned scope.

Mobile

• On narrow screens, open the sidebar or overflow menu to reach the same actions; labels and save behavior are unchanged unless this article says otherwise.

Customer-visible states

• loading
• no data
• open
• ready
• completed
• stale sync
• disconnected

Queue playback

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /android/orderboard/:deviceId/:groupId/:locationId

Ready and completed states

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /android/orderboard/:deviceId/:groupId/:locationId

Disconnected or empty queue

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /android/orderboard/:deviceId/:groupId/:locationId

Preview queue presentation

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/shiftq/preview/:id

Empty, stale, and disconnected preview states

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/shiftq/preview/:id

Queue columns and ticket states

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/order-board

Location filters and refresh

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/order-board

Display preview and empty/disconnected states

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/order-board

Sales and labor dashboard

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/shiftq

Date and location scope

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/shiftq

Toast sync and no-data states

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/shiftq

TV preview

This control is covered by the ShiftQ and Order Board operations and playback workflow.

Applies to /admin/shiftq

What happens next

Your change is available within the scope you selected.

Troubleshooting

• No data can mean the selected date/location has no records, Toast is disconnected, or the sync is stale.
• A display can be empty while Admin has data if its assignment, published campaign, or Player connection differs.
• For ready and completed states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
• For disconnected or empty queue, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
• For empty, stale, and disconnected preview states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
• For queue columns and ticket states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
• For display preview and empty/disconnected states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.
• For toast sync and no-data states, verify the selected scope, access level, required connection, and displayed validation or freshness status; retry once after correcting the cause, then create a context-rich Support case if it continues.