Toast menu publishing
Toast menu publishing for websites and screens
Toast stays the operational menu source. Garnsh handles the approved, guest-facing versions of that menu and publishes them to every public surface you use.
- Charred corn ribs9.50lime crema, chili salt
- Burrata & stone fruit14.00basil oil, sourdough
- Crispy brussels10.75honey, aleppo, mint
Little Ember is a fictional demo restaurant. Menus, prices and locations shown are sample data.
What is Garnsh?
Garnsh is a menu publishing platform for restaurants using Toast. It turns one location-correct menu source into website menus, hosted pages, QR views, digital boards, and supported website integrations.
The category
What is menu publishing?
Menu publishing is the job between editing a menu and a guest reading it. A POS holds the operational menu: what the kitchen makes and what the register charges. Guests read a different set of things: a website page, a QR view at the table, a board above the counter.
Without a publishing layer, each of those is a separate copy someone retypes. With one, they are published versions of the same source, each shaped for its screen and tied to one location.
Garnsh is display-first. It does not take orders or payments. It decides which version of the menu is public, where, and for which location, and it keeps a safe version on display when something upstream fails.
The flow
Source to surface, in five moves.
- 01 · Source
The menu in Toast
Your team edits items, prices and sections where it already works. Garnsh does not write back.
- 02 · Location mapping
Tied to the right place
Each Garnsh location is linked to its own menu context during guided setup.
- 03 · Preview
Exactly what guests will see
Every surface, every location, before anything public changes.
- 04 · Publish
A deliberate step
The approved version goes public. Earlier versions are kept for rollback.
- 05 · Surfaces
Every guest-facing display
Hosted pages, website embeds, QR views, digital boards and supported integrations.
- Charred corn ribs9.50
- Burrata & stone fruit14.00
- Crispy brussels10.75
- Smash burger16.25
- Green curry noodles18.50
- Half roast chicken23.00
season.
Integration boundary
Toast runs the restaurant. Garnsh runs the display.
Connection availability depends on your Toast access and configuration. Onboarding is guided, so the team confirms what is possible before anything is promised.
What Garnsh does
- Publishes location-correct menus from the menu you manage in Toast
- Hosted, server-rendered menu pages
- Website menu embeds and supported framework-native integrations
- QR-linked menu views per location
- Digital menu boards with layouts, themes, promo areas and QR links
- Preview, deliberate publish, rollback and freshness controls
- Keeps the last-known-good menu public if an upstream issue occurs
What Garnsh does not do
- A POS or a replacement for Toast
- Ordering, cart, checkout or payments
- Delivery, reservations or loyalty
- Inventory, live stock or 86 status
- A website builder or listings manager
- Hardware installation or print services
FAQ
Straight answers.
What is Garnsh?
Garnsh is a menu publishing platform for restaurants using Toast. It turns one location-correct menu source into website menus, hosted pages, QR views, digital boards, and supported website integrations.
Does Garnsh change my menu in Toast?
No. Toast stays the operational menu source. Garnsh reads the approved menu context and publishes guest-facing versions of it.
What is location mapping?
Location mapping is the record of which source menu belongs to which Garnsh location. It is confirmed during setup so each location publishes the right menu.
Is onboarding self-serve?
No. Onboarding is guided. The Garnsh team walks through your locations, Toast access and surfaces with you.
Related
One source. Many displays.
Bring your locations and screens. We will walk through the mapping with you.