Digital Menu Sync Service in Brookshire, TX 77423

Three different things get called ‘sync’, and only one of them is a hardware problem

When somebody calls to say the menu boards are out of sync, they mean one of three unrelated things. Naming which one saves most of the visit.

• Content publishing. Artwork and playlists moving from a cloud platform down to the player behind each screen. When this breaks the board keeps showing whatever it last received, which is why old prices persist for weeks and look like a design fault.
• Data sync. Item names, prices and availability flowing from the point-of-sale or a spreadsheet into text fields inside the layout. When this breaks the board is current in every respect except the numbers on it.
• Playback sync. Multiple panels showing the same frame at the same instant — a genuine but narrow problem that only matters when artwork animates across a multi-panel board.

Most calls are the first two, and a good share of those are fixed without anyone driving out. The third needs hardware or a platform sync group and cannot be fixed remotely.

One thing a sync system will not do

It will not change your point-of-sale prices. Somebody has to decide which system holds the truth — the POS is master and the board follows, or the designer is master and the POS is updated separately. Both work; running both at once is where wrong prices come from, and that is a management decision before it is a technical one.

Publishing to a board on a 77423 connection

Brookshire’s food businesses sit in very different connectivity situations. Travel-plaza and truck-stop kitchens along the I-10 corridor generally have decent business service. The distribution buildings toward FM 359 and FM 1489 have whatever the campus provides. The cafés and taquerias in the older part of town, and anything on acreage, are often on fixed wireless or legacy copper that has a bad hour most afternoons. All three have to run boards that never go blank.

Design for the link dropping, because it will

A properly configured player caches its playlist and every asset locally and plays from that copy. Losing the internet should change nothing on screen — the board keeps running the last published version until the connection returns and it checks in again. If your board goes black or shows an error page when the line drops, the player is streaming rather than caching. That is a configuration choice, not a property of digital signage, and it is among the first things we change.

Traffic should be sized honestly too. A full-screen promotional video is tens or hundreds of megabytes; a price change is a few kilobytes. Schedule the large downloads overnight and let small data updates come through all day — on a constrained link that single distinction separates a system that works from one blamed for slow card terminals.

Practical measures for a rural site

• Cellular failover is often cheaper than upgrading the primary circuit, because after the first full sync the ongoing signage payload is small.
• Wired beats wireless in a metal building. Barndominium-style shells and steel distribution buildings are hostile to Wi-Fi; a Cat6 drop per player removes a whole category of intermittent fault.
• Static reservations and written-down addresses, so remote support begins with a device rather than a scavenger hunt.
• A health check somebody watches — last check-in and a screenshot per player — so a board that stopped receiving content is noticed by the system, not by a customer.

Where the prices come from: a POS feed, a spreadsheet, or a designer

There are three realistic pipelines, and choosing the wrong one for the size of the business is the most common reason a board goes stale.

Manual creative

A designer edits the artwork and publishes. Total control of appearance, and it only works if a designer is genuinely available whenever a price moves. For most independents there is not, so the board drifts out of date and the paper menu quietly becomes the real one.

A bound spreadsheet

The sweet spot for an independent restaurant. The layout’s text fields are bound to cells in a sheet; change a cell and the board updates at the next check-in. No design tool, no technician, no waiting. It handles prices, item names and simple availability flags, and anyone trusted with the sheet can run it.

A POS integration

For a multi-location operator, items, prices and availability come out of the point-of-sale through a connector or API feed, so the board cannot disagree with the register. The most robust arrangement, and the one with the most setup ahead of it.

Details that decide whether a data-bound board survives reality

• Character length rules. A name that fits at twelve characters overflows at twenty-four, so the layout needs a defined maximum and an explicit rule beyond it — truncate, wrap, or shrink to a stated floor. Shrinking with no floor is how type ends up unreadable.
• Availability. An eighty-sixed item should grey out automatically from the feed; nobody edits artwork at seven on a Friday.
• Tax handling and a change log, so the board presents prices the way the register charges them and who changed one is a lookup rather than an argument.

Dayparting, and the breakfast menu that flips an hour early

Dayparting is just a schedule: breakfast layout until the changeover, lunch after, a late-night board if you run one. The mechanism is trivial. The failures are all about time being wrong, and they are remarkably consistent.

• Timezone never set. A player shipped configured to UTC and never corrected changes the menu five or six hours off. It presents as a broken schedule and it is a broken clock.
• Time server unreachable. Block outbound time synchronisation at the firewall and the clock drifts: nothing looks wrong for weeks, then the changeover starts happening a few minutes early, then more.
• A fixed offset instead of a named zone. Minus six hours rather than America/Chicago is correct for about half the year; daylight saving should be the timezone database’s job.
• Two schedulers disagreeing. A schedule in the content platform plus a second in the display’s own timer will eventually contradict each other. Pick one and switch the other off.
• No default playlist. When no rule matches — a gap between dayparts, a holiday, a schedule that ended — the screen needs somewhere to fall back to. Without one it falls to black, and a black screen over a counter reads as a dead business.

Configured properly it is a named timezone, a reachable time server, scheduling in exactly one place and an explicit fallback. Boring, and it stays right.

The diagnostic ladder: symptom, likely cause, first checks

Nearly every menu board fault sorts into a short list. This is roughly the order we work through, and much of the top half is done remotely before anyone is dispatched.

Running Brookshire and the Houston stores from one console — and who owns the login

The moment there is more than one location, publishing becomes a governance problem rather than a technical one.

• Tags and site groups. Content identical everywhere publishes once to a group; a Brookshire-only special targets one tag. Without that structure somebody eventually publishes one store’s pricing to every store, and nobody notices before a customer does.
• Per-site overrides for local pricing, clearly visible so they do not become a mystery six months later.
• An approval step on price changes, because one person reviewing before publish catches the decimal point.
• A naming convention that survives staff turnover. A player named for its site and position beats “Player 4” every time.

The account belongs to the restaurant

We configure the platform under the owner’s account, the owner holds the master credential, and EVOTECH is added as a user the owner can remove at any moment without asking us. An installer holding the only login to your menu system has made you dependent on them for every price change, and we will not set a client up that way. At handover you get the player addresses, the platform structure, the layout’s data source and a written record of what runs where.

What EVOTECH actually does on a menu sync call

1. Establish when it broke. A board wrong since Tuesday is a publishing or network problem; one that went wrong during lunch is a schedule, a clock or a power event. That question redirects the whole visit.
2. Look before driving. Where remote access exists we read each player’s last check-in, content version and screenshot first; a meaningful share are resolved from the office, faster for you than a truck roll.
3. On site, work outward from the screen: panel power and input, player lights, cable and connector, then the network path, then the platform. Working inward from the cloud wastes the visit.
4. Prove the clock. Named timezone, time server reachability, daylight saving behaviour, and confirmation that only one system is scheduling.
5. Prove the data path end to end. Change one price at the source, watch it land on the glass, note how long it took. Until that round trip is observed nothing has been verified.
6. Make the next outage invisible. Local caching, large downloads moved to an overnight window, failover where the primary link justifies it.
7. Leave it documented and leave you in control: labels, addresses, a one-page how-to, and you making a change yourself before we pack up.

We also take on boards other companies installed. There is no expectation that you started with us.

What affects the cost of sync work

We do not quote a figure before seeing the system, and this work varies more than installation does because it depends on what already exists.

• Repair or design. Fixing a pipeline someone else built is a different job from designing one.
• Whether the layouts are already data-bound. Artwork with prices baked into images has to be rebuilt as templates before any feed can drive it, and that is design work.
• The data source. A bound spreadsheet is quick; a point-of-sale integration involves the POS vendor and takes longer.
• Screens and sites, though sites scale the effort faster than screens do.
• Connectivity work, where the fix involves cabling, a switch or a failover device.
• Whether remote access exists. Sites we can see into cost less to support for the rest of their life.

Platform subscriptions are billed by the content platform directly to the owner. The on-site estimate is free and the quote is itemized. EVOTECH IT LLC is a licensed and insured low-voltage contractor serving Brookshire, Katy, Houston, Sugar Land, Richmond, Fulshear and Cypress, and has been doing this since 2004.

Related services

Frequently asked questions