12 Device network management
One dashboard connects devices, content, and events
The restaurant updates materials centrally and analyzes table actions and requests.
The guest journey
The manager creates device groups, updates materials, and receives data on views and actions. The specific report set depends on the implementation scope.
01
Always sees current content
Menus, promotions, and service buttons match the settings for each venue.
02
Gets a consistent interface
Core actions appear in the same place on every device in the selected group.
03
Interacts with content
The guest opens an offer, places an order, calls a staff member, or moves to payment.
04
Never sees the back office
Updates and technical event collection happen without complicating the guest journey.
What changes on the floor
The restaurant manages its network as one system and sees which features guests actually use.
01
Centralized changes
One piece of content can be published to a device, dining area, restaurant, or selected group.
02
Status monitoring
With monitoring enabled, the team can see device availability and the latest connection.
03
Data for decisions
Events help compare feature demand and content performance.
Analytics are built from platform-approved events
Data types, retention periods, and access rights are defined during implementation. Personal and payment information should not be mixed with advertising analytics without a separate legal basis.
Device
Potok
→
- venue and device groups
- content versions and schedules
- views, opens, and service events
- staff roles and access
→
Restaurant system
iiko / r_keeper / API
See “Content and Analytics” on a live device
We will show the guest journey and define the integration requirements.