Features

Remote menu control built for restaurant operations.

TVMenus focuses on the operational pain behind digital menu boards: stale specials, Friday rush changes, manual TV updates, device health, and screenshot proof.

TVMenus dashboard showing device health and screenshot proof beside restaurant menu boards

Live workflow

From stale special to verified screen.

  1. 1Create the menu and promo slides once.
  2. 2Assign screens by site and area.
  3. 3Schedule the menu around dayparts and rush windows.
  4. 4Publish, then verify playback with telemetry and screenshots.

Platform

Everything points at reliable TV playback.

The dashboard, database, API, and player app all support the same goal: make the right menu appear on the right screen at the right time.

UP

Menu changes without TV babysitting

Update items, prices, promos, and sold-out states from the dashboard instead of touching every screen.

FR

Friday rush scheduling

Plan lunch, dinner, happy hour, and late-night boards before staff are under queue pressure.

TV

Player-first reliability

Pair TVs, pull signed manifests, cache playback locally, and keep the TV app centered in the workflow.

OK

Device health and screenshot proof

Use health pings, current-view previews, and screenshot proof so operators know the right menu is live.

SA

Sites, areas, menus, devices

Model real restaurants with companies, sites, service areas, menus, devices, slides, and assets.

AS

Reusable screen assets

Organize menu artwork, promo slides, and fallback screens around the venues and devices that need them.

Restaurant fit

Built for counters, lobbies, bars, and multi-screen venues.

  • No USB drives, no browser refresh guessing, and no manually updating every screen.
  • Menus can be organized by site, area, and assigned device instead of generic playlists.
  • Player telemetry helps expose offline, stale, or unpaired screens before the rush.