Why connect Toast to your menu boards at all
If you run Toast and a screen menu, you currently maintain two menus. Most operators do not think of it that way, but that is what it is.
Toast POS digital menu boards fix that by making the point of sale the single source of truth. You change a price once, at the till, and the board follows.
The payoff is not convenience. It is that the two stop disagreeing. Every restaurant with manual boards has, at some point, sold something at last month's price because nobody updated the screen.
What actually syncs from Toast
A proper integration pulls live data from your Toast menu, not a one-time import. Here is what typically flows through.
| Data | Syncs | Notes |
|---|---|---|
| Item names | Yes | Uses your Toast item name unless you override the display name |
| Prices | Yes | Including price levels per location |
| Sold-out / 86'd status | Yes | Item hides from the board automatically |
| Menu groups and categories | Yes | Maps to board sections |
| Modifiers | Partly | Usually summarised, not listed in full |
| Item descriptions | Yes | Often trimmed for screen readability |
| Item images | Sometimes | Depends on whether you upload them in Toast |
| Dayparts | Via schedules | Your Toast menu schedules can drive board switching |
The important line in that table is sold-out status. That is the one that saves you real time during a rush.
What does not sync, and why
Be clear on the limits before you assume the board runs itself.
Layout and design. Toast has no concept of how your board looks. Fonts, colours, columns, and zones live in your signage software.
Full modifier lists. A board showing every modifier for every item is unreadable. Most platforms deliberately summarise, and you should let them.
Promotional content. LTO graphics, video loops, and combo callouts are signage content, not POS data. You build those separately.
Marketing copy. Your Toast item description is written for a receipt and an online ordering page. It usually needs shortening for a screen.
Deleted items. Removing an item in Toast hides it from the board, but any custom layout you built around it may need adjusting.
How the connection works technically
You authorise the signage platform against your Toast account through Toast's partner integration flow. No credentials get shared and no one touches your terminals.
From there the platform reads your menu through Toast's API. Changes propagate on a polling interval, typically under a minute, so a price edited at the till reaches every screen before the next order.
Content is then cached on the player behind each screen. That matters: if your internet drops, the board keeps showing the last good menu instead of going black. It resyncs when the connection returns.
MenuPi's Toast integration works exactly this way, alongside native connections to Square, Clover, Lightspeed, Aloha, and 35+ other systems.
Setting it up without breaking your live menu
Do this in the order below. It takes about 15 minutes and avoids the one mistake that causes trouble.
- Tidy your Toast menu first. Fix any item names you would not want a customer reading in 60-point type. This is the step people skip and regret.
- Authorise the integration from your signage platform. You will log into Toast and approve access.
- Pick which Toast menus map to which screens. A drive-thru board and a counter board usually pull different menu groups.
- Build the layout in your signage tool, not in Toast. Choose your zones, columns, and type sizes.
- Override display names where needed. "CHK SAND LG" is fine on a receipt and terrible on a board.
- Test one price change. Edit a price in Toast and watch the board. Confirm the round trip before you trust it.
- Test an 86. Mark an item sold out in Toast and confirm it disappears from the screen.
Only after steps six and seven should you stop maintaining the board manually.
Multi-location Toast setups
If you run several venues on Toast, the integration gets more valuable, not less.
Each location's screens pull that location's Toast pricing. Regional price differences are handled automatically, which removes the most tedious part of multi-site signage.
You still push brand-level content, like a new LTO graphic, from one place to every screen. The split is clean: pricing and availability come from Toast per location, design and promotions come from your signage platform centrally.
That is the same model described in our multi-location rollout guide, and it is what keeps twenty venues consistent without twenty separate workflows.
Frequently asked questions
Does Toast have its own digital menu board product?
Toast offers screen products aimed at its own hardware ecosystem. Third-party signage platforms connect via Toast's API and generally give you more flexibility on layout, hardware choice, and per-screen cost. Which is right depends on whether you want everything on one invoice or want more control over the display side.
How fast do price changes reach the screen?
Under a minute on most platforms. If a vendor cannot tell you the sync interval, treat that as a warning sign.
Will my menu board go blank if Toast is down?
It should not. The player caches the last good menu locally, so the board keeps showing correct content and simply stops receiving updates until Toast is reachable again.
Do I need a Toast API key?
No. You authorise through Toast's standard partner flow, which handles access without you handling keys.
Can I show different prices on the board than in Toast?
You can override display values, but you generally should not. Two different prices for the same item is the exact problem the integration exists to eliminate.
Does this work with Toast Online Ordering?
Yes. Both pull from the same Toast menu, so your board, your online ordering page, and your till stay consistent by default.
Get it connected
If you already run Toast, this is the highest-value hour of setup available to you. One menu, one price, every surface.
Start MenuPi free on one screen, connect Toast, and change a price at the till. Watching the board follow within a minute tends to settle the question.