Why a Clover digital menu board beats a manual one
If you run Clover, your item names, prices, categories and availability already live in one place and are already kept current, because the till will not take money otherwise. A Clover digital menu board reads from that same source instead of asking someone to retype it.
That is the whole value. Not the animation, not the photos. One place where a price is true. The alternative is two menus that will disagree within a fortnight, and the board is always the one that is wrong, because the till is the one that gets corrected in the moment.
What actually syncs from Clover
Clover organises inventory as items, with categories, modifier groups, tags and item stock hanging off them. Clover documents this model in its Inventory API, and it maps to a menu board more cleanly than most POS systems do.
| Clover object | Reaches the board | Notes |
|---|---|---|
| Item name | Yes | Use alternateName for a customer-friendly board label |
| Price | Yes | Stored in cents; VAT-inclusive for VAT merchants |
| Categories | Yes | Becomes your board's panel grouping |
| Item stock / availability | Yes | Drives sold-out and 86'd behaviour |
| Tags / labels | Yes | Useful for vegan, spicy, new flags |
| Modifier groups | Partially | Group names sync; per-modifier pricing rarely belongs on a board |
| Item photos | Usually not | Clover's image handling is inconsistent, generate board art instead |
| Online-ordering descriptions | No | These live in Clover's OLO system, not standard inventory |
That last row is the one that catches people. Clover's online-ordering fields, including online status and item description, are part of a separate system and are not returned by the standard inventory response. If your board plan depends on long item descriptions you keep in online ordering, plan to maintain those in the board software instead.
Setting it up, step by step
Budget about twenty minutes for the first screen.
- Tidy your Clover categories first. Your board's panel structure will mirror them, so a category called "Misc" with nineteen items in it becomes a bad panel. Fix it in Clover, not in the board.
- Set customer-facing labels. Clover's
alternateNamefield exists for exactly this. "CHK SNDWCH LG" is fine on a till; it is not fine on a wall. - Connect the integration. Authorise the menu board software against your Clover merchant account. You are granting read access to inventory, not write access.
- Map categories to panels. Decide which Clover categories appear on which screen. Six to eight items per panel is the ceiling.
- Choose your sold-out behaviour. Hide the item, or grey it with a SOLD OUT flag. Hiding reflows the layout; greying keeps it stable. Greying is usually better on a fixed-height panel.
- Set dayparts. Breakfast categories off at 11, evening menu on at 4. This is where the setup starts saving real labour.
- Pair the screen and go read it from the queue. You will change one font size.
What to leave off the board
A Clover catalogue holds far more than belongs on a wall. Do not push everything across.
Leave off modifier pricing (a wall of "+$0.50 extra cheese" is visual noise), single-ingredient items that only exist for kitchen accuracy, anything with zero sales, and items that only make sense as an upsell at the register. Customers read a board for around eight seconds. A complete catalogue is the enemy of a readable menu.
The honest limits
Three things to know before you commit.
Sync is polled, not instant-magic. Clover exposes webhooks for inventory changes and a REST API for reads, so a well-built integration lands changes in well under a minute. Anyone promising literally instantaneous is describing a cache, not a certainty.
Item pagination is real. The Clover items endpoint returns a limited page by default, and large catalogues need paging. If a rollout shows a board that is missing exactly some of your items, this is usually why, not a mysterious integration bug.
Multi-merchant groups need mapping. If each location is its own Clover merchant with its own item IDs, matching them into a single brand menu is real work. Do it deliberately at the start rather than discovering it at store four. Our multi-location rollout playbook covers the pattern.
How it compares to Square and Toast
All three are viable. Clover's catalogue is closer to retail inventory in shape, which means item groups and variants are strong but restaurant-specific concepts like courses are looser. Square is the simplest to connect and the most limited in modifier depth. Toast has the richest restaurant model and the most fields you have to decide about.
If you already run one, that is the answer. Nobody should switch POS to get a nicer menu board.
Frequently asked questions
Does Clover have a built-in digital menu board?
Clover offers customer-facing display functionality on its hardware, but that is a transaction-side screen, not a wall-mounted menu board. For counter and drive-thru boards you connect third-party signage software to Clover's inventory.
How fast do Clover price changes reach the screen?
With a properly built integration using inventory webhooks, under a minute. Poll-only integrations may take a few minutes. Ask a vendor which mechanism they use before you buy.
Do Clover modifiers show on a digital menu board?
Modifier group names can, and sometimes should for a build-your-own item. Individual modifier prices generally should not: they turn a menu into a price list and cost you legibility.
Can one Clover account drive several menu screens?
Yes. One merchant account feeds as many screens as you like, with different categories on each panel. That is the standard three-panel QSR setup, covered in the multi-screen sync guide.
What happens to the board if Clover goes down?
A well-built player caches the last known good menu and keeps displaying it. Prices simply stop updating until the connection returns. A board that goes blank when the POS hiccups is a badly built board.
Start with one screen and one category
Connect Clover, push a single category to a single screen, and watch a price change land. That five-minute test tells you more than any demo, because it proves the one thing that matters: the board reads from the till, not from someone's memory.
MenuPi is free on one screen and connects to Clover natively. Get the first panel right and the rest are clones.