Scheduling versus rotation: use the rules for the correct product

What this does

A schedule controls eligibility or delivery time; rotation controls how content cycles after it becomes eligible. SmartQ schedulers do not all share one time-zone, recurrence, or overlap contract.

Before you start

• Identify the object being scheduled: campaign, menu delivery, message, or notification.

Steps

1. Identify the actual scheduler rather than interpreting every timing field as a start time.
2. Check that scheduler's clock, day and time rules.
3. Check whether changes need a parent save, a picker save, or an explicit send/publish action.
4. Verify the result at a boundary without changing a production device.

Scheduling is not rotation

A TV campaign schedule decides whether the campaign is eligible now; asset duration and BevQ Rotate Every decide timing inside playback. The BevQ Schedule Daily Deliveries modal stores PDF delivery configuration, not TV-menu dayparts. No automated PDF schedule execution implementation has been identified in current authoritative source; it is excluded from implemented customer schedulers. The SMS Send At form has a separate execution path. Do not transfer campaign weekday, overnight, or time-zone rules to notification or SMS scheduling merely because the controls look similar. Visible settings alone do not prove a working delivery scheduler.

BevQ Daily PDF Delivery: configuration only

BevQ stores Daily PDF Delivery schedule configuration, but no automated delivery implementation has been identified in the current authoritative source. Do not rely on these saved settings to generate or email menu PDFs automatically. Saving configuration is not evidence that delivery is scheduled or will occur. No delivery time zone, DST handling, retry policy or delivery guarantee is established for this configuration. Use Printable Menus to preview and manually export a PDF when you need one. The schedule dialog Save updates the page draft; the notification page Save persists the selected location configuration. The parent automation-only settings surface does not expose this PDF schedule. This limitation does not disable ordinary POS-change notifications or manual Printable Menus export.

Permissions and scope

• Permissions are product-specific; a scheduling field does not grant access to another product or scope.

Mobile

• Native date/time inputs can present differently by browser; verify the stored result and intended clock.

What happens next

Verify the saved result in the correct scope and delivery path. A preview or status badge is not proof that every production Player has refreshed.

Warnings

• This source-reviewed guide describes the named paths only. Operational coverage and production visual verification are still in progress.

Related articles