Toast digital menu boards

Keep your Toast menu and your screens in step.

ScreenFire's restaurant workflow can use Toast menu and order information for items, prices, and availability. Check how your configured menu updates reach the TV, and review prepared promotions before publishing.

Reviewed October 7, 2026

A Toast-connected menu board should reduce double entry. Source changes, menu updates, and prepared promotions need separate checks.

What connects from Toast

The current ScreenFire restaurant workflow can use Toast menu and order data for items, prices, availability, and related operating context. The Toast connection is included on the Pro and Business plans.

Check what the configured workflow receives, what reaches each screen, and whether a price or availability change requires review. ScreenFire supports review and approval before prepared promotions are published.

  • Menu items and categories
  • Current prices and availability
  • Order and operating context
  • A reviewable screen update

Why review still matters

For a prepared promotion, check the item, price, availability, target screen, and intended service window before publishing. Broader automatic policy and stop-rule capabilities remain roadmap work.

Menu updates and finished artwork need separate checks. A price or item-status change in Toast does not by itself establish what happens to a prepared poster or video.

Test three changes before service

Use an agreed test item. Check one price change, one sold-out item, and one size or modifier. Compare the information in Toast, what ScreenFire receives or prepares, and the result on the actual TV. Record whether review is required and how long your configured workflow takes; do not assume every change is instant.

Check finished posters and videos separately. A dish name or price embedded in artwork does not rewrite itself when Toast changes. ScreenFire supports review before prepared promotions are published; broader automatic stop rules remain roadmap work.

Toast's linked documentation describes Delphi-specific visibility, pricing, and stock settings. Those are not ScreenFire connection instructions. Confirm the current ScreenFire setup for your restaurant rather than enabling settings intended for another product.

Start with one location and two screens

Give each display a clear job, such as meals on the left and drinks on the right. Check the intended categories and prices on both TVs, then publish an agreed change to the selected display and verify the other display still shows its intended content.

Before adding locations, repeat that check with each location's menu. Selected-screen publishing is not the same as franchise permissions or fleet-wide governance; ask for a demonstration of the controls you need today.

What you need at the screen

Use a compatible Fire TV or Google TV display, or connect a separately purchased compatible streaming device to a screen with an available HDMI input. The location also needs nearby power and Wi-Fi.

  • A supported display or HDMI screen
  • A compatible streaming device when needed
  • Power and Wi-Fi
  • A ScreenFire Pro or Business plan for the Toast connection
Common questions

Clear answers before you choose.

Does ScreenFire connect with Toast?

Yes. ScreenFire's current restaurant workflow can use Toast menu and order data for items, prices, availability, and related operating context. The Toast connection is included on the Pro and Business plans.

Does every Toast change publish automatically?

Menu updates depend on your configured workflow. Test a price change, a sold-out item, and a size or modifier; check whether review is required and how long the update takes to reach the TV. Prepared promotions support review before publishing. Broader automatic policy and stop rules remain roadmap work.

Can one publish update several screens?

Yes. One confirmed publish operation can target several selected screens and costs one ScreenFire credit.

Is the screen hardware included?

No. Hardware, installation, retailer pricing, taxes, and custom integration work are separate unless explicitly quoted.

Sources and further reading

Official documentation for the hardware, menu data, or design guidance discussed here.