If your data changes, the screen already knows.

Connect any type of structured data and use it twice: display the values inside your content (prices, timetables, KPIs) and filter which items appear at all (only products in stock, only today's departures). One feed, and the screens keep themselves current.

Display it: live values inside the design.

Menu prices from the ERP, wait times from the queue system, dashboards from your BI stack. The value on screen is the value in your system, updated without anyone re-exporting a slide.

  • Prices, timetables, and KPIs rendered live
  • Values styled in Scene Designer like any element
  • No re-rendering when the source changes

Filter with it: only the relevant items appear.

Data does not just fill placeholders, it selects content. Show only items flagged available, only campaigns for this store's region, only sessions happening today. Sold out disappears from the menu board by itself.

One feed, three jobs.

The same source that displays values and filters items also drives display rules. A stock feed can print the price, hide the sold-out item, and pull the whole campaign when the last unit goes, all from one connection.

From feed to screen.

  1. 1

    Connect the source

    Point OmmaSign at your structured data, whatever system it lives in.

  2. 2

    Bind it in content

    Place values in scenes and set which items the data should filter.

  3. 3

    Let it run

    Screens follow the feed from then on. Change the data, the fleet updates.

Data source questions, answered.

Any structured data: product and price feeds, timetables, queue systems, spreadsheets, or JSON from a URL. If your system can expose it, the screens can use it.

Retire the weekly export.

Show us the spreadsheet someone updates by hand every Monday. We will connect it once and let the screens do the updating.