Skip to content
garnsh
Built for restaurants using Toast

Your Toast menu.
Every screen.

Map the right location, preview exactly what guests will see, publish to every surface, and recover to a last-known-good menu when something upstream goes wrong.

Book a demoSee the publish workflow
Source menuMission St.
Managed in Toast
Smash burger16.25
Green curry noodles18.50
Half roast chicken23.00
littleember.example/menu
Small plates
Charred corn ribsNew9.50
Burrata & stone fruit14.00
Crispy brussels10.75
Mains
Smash burger16.25
Green curry noodlesSpicy18.50
Half roast chicken23.00
Small plates
  • Charred corn ribs9.50
  • Burrata & stone fruit14.00
  • Crispy brussels10.75
Mains
  • Smash burger16.25
  • Green curry noodles18.50
  • Half roast chicken23.00
Corn rib
season.
9.50
7:425G
Mission St.
Little Ember
Small platesMains
  • Charred corn ribs9.50
    lime crema, chili salt
  • Burrata & stone fruit14.00
    basil oil, sourdough
  • Crispy brussels10.75
    honey, aleppo, mint
Menu view only
One source. Many displays.

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.

Your team keeps managing the master menu in Toast. Garnsh handles the guest-facing part: which version is public, where, and for which location. Make the update once. Keep every guest-facing menu in step.

The problem

One menu. Four versions. Zero agree.

01

The board says $14.

The website says $13. The PDF from last spring says $12. Guests notice.

02

Every screen has its own login.

Website builder, board vendor, QR tool. Same menu typed three times, by whoever had a minute.

03

Nobody owns the fix.

A price change in Toast should not become a Friday-night task list.

The menu guests see should match the menu your team is running. That is the whole job.

Surfaces

One source. Four places guests read it.

Tap through each surface. Same items, same prices, shaped for its screen.

Server-rendered

A menu page you do not have to build.

A hosted menu page is a public web page Garnsh serves for each location. It loads as plain HTML, reads well on a phone, and carries your restaurant’s styling.

  • Server-rendered HTML
  • Readable on any phone
  • One page per location
More on hosted pages
menu.littleember.example/mission
Small plates
Charred corn ribsNew9.50
Burrata & stone fruit14.00
Crispy brussels10.75
Mains
Smash burger16.25
Green curry noodlesSpicy18.50
Half roast chicken23.00

Compare the surfaces

Garnsh surfaces compared
SurfaceHosted pageWebsite embedQR menuMenu board
What it isA public menu page per locationThe menu inside your current siteA phone view opened by a printed codeA designed display for in-store screens
Best forFast setup, no web workKeeping an existing siteTables, patios, countersLines and counters
Location-specificYesYesYesYes
Ordering or paymentNo, view onlyNo, view onlyNo, view onlyNo, view only
Go deeperHosted pageWebsite embedQR menuMenu board

Reliability

Preview it. Publish it.
Roll it back when needed.

Garnsh makes going public a deliberate step, keeps every published version, and holds the last good menu on display when something upstream breaks. Press a control to see what changes.

Little Ember (demo) · all locationsPreviewing draft v15 · live v14

See it before guests do.

Preview shows each surface with the exact menu that will publish. Nothing public changes yet.

Draft v15 is open in preview. Guests still see v14.

  1. v13
    saved
  2. v14
    live
  3. v15
    draft

Bad day upstream? Keep your menu on display.

A last-known-good menu is the most recent version that published correctly. If something goes wrong before a new menu reaches Garnsh, public surfaces keep showing it. No blank boards. No error pages at the table.

Upstream: unavailableServing last-known-good v14
Small plates
  • Charred corn ribs9.50
  • Burrata & stone fruit14.00
  • Crispy brussels10.75
Mains
  • Smash burger16.25
  • Green curry noodles18.50
  • Half roast chicken23.00
Corn rib
season.
9.50

Locations

The right menu at the right location.

Location mapping ties each public surface to one location’s menu. The airport price never shows up on the flagship board.

Choose a location

Now showing

Mission St.

Smash burger 16.25
BrunchSmall platesMainsDrinks
Board · 3-panel landscape
Small plates
  • Charred corn ribs9.50
  • Burrata & stone fruit14.00
  • Crispy brussels10.75
Mains
  • Smash burger16.25
  • Green curry noodles18.50
  • Half roast chicken23.00
Corn rib
season.
9.50
7:425G
Mission St.
Little Ember
Small platesMains
  • Smash burger16.25
    double patty, house pickles
  • Green curry noodles18.50
    tofu or chicken, thai basil
  • Half roast chicken23.00
    salsa verde, potatoes
Menu view only
How multi-location publishing works

Who it is for

Built for the way your team works.

Owner-operators

One or two locations, nobody with a spare hour. Make the change in Toast, preview, publish, get back to the pass.

See the publish workflow

Multi-location groups

Central oversight with location-correct menus. The airport price never leaks onto the flagship board.

See multi-location

Agencies and developers

Keep the site you built. Drop in a hosted page, an embed or a supported framework-native integration.

Plan an integration

Straight answers

Does one job. Does it well.

Keep your POS, your ordering partners and your website. Garnsh makes sure the menu they show is the right one.

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

Guides

Practical reading for operators.

FAQ

Questions operators ask.

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 replace Toast?

No. You keep managing the master menu in Toast. Garnsh publishes approved, guest-facing versions of that menu to supported public surfaces.

Is Garnsh an official Toast partner?

No. Garnsh is an independent product built for restaurants using Toast. It is not affiliated with, endorsed by, or certified by Toast.

Can Garnsh publish different menus by location?

Yes. Location mapping ties each Garnsh location to the right menu context, so each location gets its own hosted page, QR view and board configuration.

Are updates real-time?

No. Garnsh uses preview, deliberate publish and freshness controls. It does not claim live stock, 86 status or guaranteed sync timing.

What happens if something goes wrong upstream?

Public surfaces keep showing the last-known-good menu, meaning the most recent version that published correctly, instead of a blank screen or an error page.

Can guests order or pay through Garnsh?

No. Garnsh does not provide cart, checkout, payments, ordering or delivery. It shows the right menu.

Make the update once.

Guided onboarding with the Garnsh team. Bring your locations and your screens. We will map the rest.

Book a demoStart a pilot