Imagine a restaurant that installs digital menu boards and discovers two things in the first month. Prices are wrong on one screen because somebody edited the artwork file instead of the source list. And at 10:58, halfway through the breakfast-to-lunch changeover, one board is showing breakfast while the other has already switched.
Both problems were decided long before the screens were mounted. This guide is how to plan the menu structure, the dayparts and the failure behavior so that service does not depend on somebody noticing.
Start with the ordering decision
A menu board is not a poster of the menu. It is the thing a customer reads while deciding what to order, in a queue, with other people behind them.
Split the menu into two kinds of information, because they are maintained differently.
Stable structure. Categories, the order they appear in, the arrangement of the board. This changes rarely and should be controlled centrally.
Changing values. Prices, availability, promotions, dayparts. These change often, sometimes daily, and they need a controlled source.
The rule that saves the most time: every changing value has one source of truth, and it is not the artwork file. If the price exists only inside a designer's file, then every price change costs a design job, and the screen will be wrong in between.
Then decide what has to be visible at the same time. If customers compare two options, splitting them across two slides makes the comparison harder. A board that shows less but shows it together is usually better than a board that shows everything in rotation.
Use the real menu in the mockup. Placeholder text does not crowd the way real descriptions, prices and conditions do, and the crowding is what you are testing for.
Give every field an owner
The expensive menu errors tend to be ownership errors. Somebody changes a price in the point-of-sale system, somebody else maintains a spreadsheet, and a third person updates the artwork.
| Content | Where the value comes from | Who checks it before publishing |
|---|---|---|
| Item name | The approved menu list | Menu owner |
| Price | The point-of-sale price list | Menu owner |
| Availability | Kitchen or supply status | Shift manager |
| Promotion and its dates | The campaign record | Marketing |
| Allergen and dietary information | The approved menu list | Menu owner |
| Daypart schedule | Opening hours and the service plan | General manager |
Two rows carry more risk than the rest. Price and allergen information are the two things a customer will act on and complain about, so both need a named checker and a way to verify the screen against the source.
Plan the dayparts and the leftovers together
Dayparts are where menu boards fail most visibly, because the failure happens at the busiest moment.
Write the schedule as a table before configuring anything. For each daypart: the start and end time, the items that change, and who is responsible if the change does not happen. Then add the two cases that schedules usually ignore.
The overlap. A board that switches at 11:00 exactly is fine. A board that takes four minutes to update is showing breakfast at 11:02. Decide whether that matters, and if it does, switch earlier rather than later.
The exception. A public holiday, a delivery that did not arrive, an item that sold out at noon. For each exception decide what the board shows, and make sure somebody in the building can act on it without calling head office.
Offline behavior is part of the plan. Decide what the board shows when it loses the network or the player restarts: the last known menu, a generic approved menu, or nothing. Test it on a controlled endpoint, or during an agreed maintenance window, rather than by interrupting a live service at the counter. A single spare player, or one board that is not taking orders, is enough to answer the question. Which fallback is right is your decision, and it depends on what the board sells: a price that is out of date is a pricing decision, and some operators would rather show nothing than show a figure they cannot stand behind. Decide it in advance and write it down, rather than discovering the answer at 12:30. The retail content guide covers the same decisions for the rest of the store's screens.
Check the view from where the order is placed
Menu boards are usually reviewed on a laptop and then installed above a counter, and the two views have almost nothing in common.
Stand at the ordering position, at the distance a customer stands, and read the board. Then check three things.
The smallest text. Allergen notes, portion sizes and conditions are usually the smallest items and the ones that must not be misread.
The light. A board behind a counter faces whatever light the seating area has, and a board near a window faces daylight for part of the day. Look at it in the worst conditions, not at opening time.
The queue. People read the board while a queue moves. Check that the key information is visible at a glance from several meters back, not only from the front.
Then test with actual content, not a test pattern, and get somebody who did not design it to tell you what they would order.
If guests place their own orders at a separate terminal, add the self-ordering kiosk menu and POS rule check. A display menu and an accepted kitchen order have different roles; verify modifiers, availability, and channel assignments in the ordering application.
What to hand over to the site
Before opening day, put the following in one document and give it to the store:
- The daypart schedule, with the exception behavior.
- The source of truth for every changing value, and how to check the board against it.
- Who can change what, including what a shift manager can do without calling head office.
- The offline behavior, and what to do if the board does not recover.
- The recovery procedure, written for a person who did not install the system.
- A photograph of a correct board, so a wrong one is obvious.
Point five is the one that gets skipped. Test it by handing the notes to a member of staff who was not involved and watching them follow it during a quiet period.
For the placement of the boards, see the retail placement guide. For drive-through and window-facing positions, the drive-through planning guide covers the site differences.
When the menu travels with a food truck
A mobile service changes the location as well as the menu. Confirm the stop, service period, viewing position, power arrangement, and approved fallback before opening; yesterday's successful playback does not approve today's pitch. Use the food-truck menu display daily setup record for that location-by-location handoff.
What this guide does not cover
It gives no allergen or labelling guidance, which varies by market and needs the responsible specialists, and no brightness, distance or mounting figure. Menu-board law and local regulation are beyond its scope, and it makes no claim about sales. The placement guide covers where the boards should hang relative to the ordering position.
Send the menu and the counter layout
Tell us the menu structure, the dayparts, where the boards will hang and what the light is like there. We will tell you which configurations suit the position, what the installation and servicing need, and what has to be confirmed for the specific model.
Send the menu and the counter layout →
Request a Quote