Live price change
A current £ price reaches the digital menu flow.
Use the current Flipdish connection to bring a live price change into the relevant digital menu workflow.
Dhruv QSR platform
UK QSR / Operating use cases
From the current service moment to the right screen message.
Dhruv QSR use cases show how a controlled publishing flow can connect UK food-service operations with the menu, campaign, and priority messages shown across the estate.
UK QSR terminology Verified public claims
The QSR content flow
Service inputPrice, menu, campaign
Dhruv QSRControlled flow
Screen estateMenu and service context
A deep-dive page grounded in confirmed public capability.
The page distinguishes current features from capability that would need separate confirmation before publication.
What this page covers
A UK QSR flow that keeps the service context visible.
Menu availability
The available menu remains the on-screen conversation.
Prepare approved availability-led content and publish it to the screen groups that need the current service message.
Campaign moment
A timely offer gets a defined launch flow.
Use prepared campaign content and configured weather-aware context to make an offer relevant to the service moment.
Priority message
Urgency can become controlled intervention.
Use Screen Takeover when the QSR message needs to appear on selected screens ahead of scheduled content.
What makes the flow different
The QSR content has to belong to the operating moment.
Dhruv connects the input, approved content, decision, and screen destination in one visible flow rather than presenting a generic display page.
The use case starts with an input
A price movement, current menu context, prepared campaign, or priority event starts the flow—not a generic screen layout.
The destination stays visible
Dhruv keeps the message connected with the selected sites and screen groups so a team can publish with the physical context in view.
The operating model scales by context
The same governed foundation supports multiple service moments without implying unsupported kiosk, drive-thru, allergen, or franchise synchronisation.
Screen context
The content needs to look right where it lands.
The screen context, module, and destination remain part of one operational publishing flow.
Direct answers
The direct answers for this flow.
Which UK QSR use cases does Dhruv support?
Confirmed public use cases include Flipdish live-price updates, menu availability content, approved campaigns, configured weather-aware content, managed site publishing, and Screen Takeover.
Can Dhruv support a nationwide rollout?
Dhruv supports managed sites and screen groups. The exact scope of any rollout depends on the configured destinations, data, approval process, and deployment permissions.
Does Dhruv cover kiosk and drive-thru synchronisation?
That capability is not currently presented as a confirmed public feature. Dhruv’s published QSR flow focuses on the verified digital menu, live-price, campaign, and screen-control capabilities.
Dhruv QSR
Map the QSR content flow around the service moment.