QSmartQ Support

BevQ · Integrations

BevQ POS synchronization

Connect and monitor supported POS menu data for a location.

Verified 2026-09-04 · Source da3f301

What this does

Connect and monitor supported POS menu data for a location.

Steps

  1. Open BevQ and select the location.
  2. Open POS or Integrations.
  3. Complete the supported provider connection.
  4. Review mapped items and the latest synchronization state.
  5. Use History when data is delayed or unexpected.

Connection and sync status

This control is covered by the BevQ POS synchronization workflow.

Applies to /admin/bevq/pos/:groupId/:locationId

Map and ignore items

This control is covered by the BevQ POS synchronization workflow.

Applies to /admin/bevq/pos/:groupId/:locationId

Refresh/retry and provider errors

This control is covered by the BevQ POS synchronization workflow.

Applies to /admin/bevq/pos/:groupId/:locationId

Date/status filters

This control is covered by the BevQ POS synchronization workflow.

Applies to /admin/bevq/history

Added, removed, matched, and failed events

This control is covered by the BevQ POS synchronization workflow.

Applies to /admin/bevq/history

Retryable versus informational states

This control is covered by the BevQ POS synchronization workflow.

Applies to /admin/bevq/history

What happens next

Your change is available within the scope you selected.

Troubleshooting

  • For refresh/retry and provider errors, 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 added, removed, matched, and failed events, 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 retryable versus informational 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.

Was this helpful?