Digital Menu Sync Service in Stafford, TX 77477

The chain a price change travels before it reaches the glass

When a manager raises a price, five things happen in sequence. Knowing the sequence is what turns a two-hour problem into a two-minute one.

1. The edit is saved in the content platform, or read out of the register by it.
2. The platform builds a new version of the layout and marks it for publication.
3. Each player checks in on its schedule and learns there is something new.
4. The player downloads the change and writes it to its own storage.
5. The player swaps it onto the screen, either immediately or at the next loop.

Every complaint about a board that will not update lands on one of those five steps, and each has its own fix. We document the platform, the check-in interval and the network path for your site, so troubleshooting is a checklist rather than guesswork.

Keeping the boards off the network your card readers use

Plugging a media player into the first open port beside the point-of-sale terminals is quick, common and a bad idea.

Menu players are internet-connected devices running vendor software that updates itself; payment terminals sit in a far more controlled world. The sensible arrangement is a separate segment for signage, with rules letting players reach their content platform and nothing else – no path from a player into the segment carrying payment traffic.

Two rules go with it. Players need outbound connections only – nobody should open an inbound port to a media player for remote access, and if a vendor asks for one, ask why. And each player gets a reserved address rather than whatever the router hands out that week, so labels, monitoring and firewall rules still point at the right device six months later.

To be clear about scope: how your payment environment is defined and assessed is a matter for your processor and assessor. We build the signage side so it stays out of that conversation.

Two small settings that make screens disagree with each other

Clocks. Scheduled content only looks professional if it changes everywhere at once, and players holding their own drifting clocks switch a minute or more apart. Every player takes its time from a common network source, sits in the same zone, and is checked against the daylight-saving change rather than discovered by it in March.

Power. Displays have a setting that decides what happens when power returns after an interruption. On the factory default many panels return to standby and wait for a remote. Set to resume their previous state, they come back to the menu with nobody present. Where the panels support control over the network or a serial link, we also set a daily on and off schedule so nothing depends on a staff member remembering.

The network gear deserves a small uninterruptible supply. A sag that reboots the router costs minutes of reconnection on every player; a modest UPS removes that.

What the screens show when the circuit goes down at noon

This should be asked before the hardware is chosen, and it usually is not. A properly configured player stores its content locally, so when the connection fails it keeps playing the last version it downloaded. The room does not go blank and most staff will not notice for hours.

The nuance matters more. An offline board is not a broken board, it is a frozen one. A price changed while the circuit is down will not appear until the player reconnects, and a sold-out item flipped at eleven will still be advertised at noon. So the failure to plan for is not a black screen, it is a screen confidently displaying something that is no longer true.

Two things reduce the exposure: monitoring that tells you a site went offline rather than leaving you to discover it, and where stale pricing is intolerable, a cellular backup path carrying the small amount of traffic signage needs.

Pushing one change to several locations without breaking one of them

Plenty of operators based around 90A run more than one storefront. Get the structure right on day one – retrofitting it later means rebuilding every layout.

• Group by site. Screens are tagged by location and by role – order queue, drive lane, dining room – so a change can target a group instead of being pasted screen by screen.
• Separate what is corporate from what is local. The template, the brand and the core price list belong to one central account. Sold-out flags, local specials and store hours belong to the store.
• Publish in stages. A menu change goes to one location first, gets looked at by a human, and then rolls to the rest. A layout error that reaches nine stores at once is a very long afternoon.
• Handle the exceptions deliberately. If one site prices differently, that has to be a defined exception in the system rather than a manager who remembers to undo the corporate push.

Finding a dark screen before a customer mentions it

The worst outcome is not a failure but a failure nobody notices until a customer points at a black rectangle above the counter.

Content platforms report when each player last checked in, and an alert on a missed window catches most cases – a failed player, a dead switch port, a site that lost its circuit. What it misses is the player that is happily online while the display in front of it is off or on the wrong input, which looks healthy from a dashboard.

Two additions close that gap. Where a panel can be queried over the network or a serial link, its actual power state is monitored rather than assumed. And where the platform captures a periodic frame from the player, somebody can see what is genuinely on the glass without driving out. We configure whichever your platform supports.

Boards in Stafford flex space: cafeterias, breakrooms and shop floors

Not every board in this ZIP code sells food to the public. A good share of them sit in employee cafeterias, warehouse breakrooms and on shop floors in the business parks here, running a daily menu alongside shift information.

The engineering changes. Light from open dock doors is harsher than restaurant lighting, so brightness and a matte finish beat resolution. Viewing distances are longer, pushing type size up and item counts down. Dust is constant, which argues for sealed, fanless panels. And temperature is a real limit: commercial displays carry a stated operating range, and an unconditioned warehouse in August exceeds it. There we either keep the screen inside the conditioned envelope or specify hardware rated for the conditions.

Where an in-house IT person is already enough

If you have competent IT, a managed switch, a spare VLAN and one or two screens, they can do this. We will happily give them the configuration notes rather than sell a truck roll.

Where we get called instead: cable that has to cross a building nobody wants to core-drill; displays going onto tilt-wall concrete; several sites that must behave identically with nobody free to build them one at a time; a payment network whose isolation has to be demonstrably true; and operators who want one company responsible for the screen, the cable, the player and the platform, so a fault does not become three vendors pointing at each other.

How EVOTECH commissions and documents the system

1. Design the segment. Address plan, reserved addresses, firewall rules, switch ports labelled to the screen they serve.
2. Bench-build the players. Named, updated, joined to the account and tested before they leave our shop.
3. Install and cable. A run per screen, mounts anchored to real structure, player and display on the same protected supply.
4. Set clocks, schedules and resume behaviour. Verified screen by screen, not assumed from a default.
5. Prove the path. One real price change, timed from edit to glass, on every screen.
6. Simulate the failures. We pull the internet and watch what the boards do, then restore it and confirm they catch up.
7. Hand over documentation. Address list, port map, platform roles, alert recipients and measured update time, in writing.

Six failures we are called in to clean up

• A port forwarded to a player. Opened once for convenience, left open for years, facing the internet.
• Addresses handed out fresh each week. Monitoring and firewall rules quietly stop matching the devices they were written for.
• A player sealed behind a panel with no airflow. It runs all winter and starts rebooting itself in July.
• A corporate push that overwrote a local price. One store had an exception that lived only in a manager’s memory.
• A display on the wrong input. The player is online, the dashboard is green, and the screen shows a blue box.
• Nobody receives the alerts. The platform sent them to an address belonging to somebody who left.

What moves the number on a Stafford quote

On this kind of project the screens are often the smaller half. What we price against:

• Screen and site count, and how much usable network already exists.
• Whether a separate segment and firewall policy have to be built or only configured.
• Cable distances in flex and warehouse buildings, far longer than a retail suite and sometimes needing an intermediate equipment location.
• Mounting surface – drywall, block and tilt-wall concrete are three different jobs.
• Panels specified for brightness, dust or temperature rather than standard indoor units.
• Backup power, and whether a cellular failover path is wanted.
• How the register exposes menu data, and how many exceptions the multi-site structure has to carry.
• Whether monitoring and alerting are configured and tested, or the screens are simply hung.

It arrives itemized. Nothing is quoted over the phone, because the network half cannot be assessed from a description.

Related services

Frequently asked questions