How it works
From the menu in Toast to every guest-facing display
Five steps, guided by the Garnsh team. The first three happen once. The last two become a short habit.
- 1
Confirm the restaurant and location.
We start with what exists: your locations, the surfaces guests use today, and who on your team will own publishing. Nothing is connected yet.
- Location list and addresses
- Current website, QR and screens
- Named publishing owner
7:425GMission St.Little EmberSmall platesMains- Charred corn ribs9.50lime crema, chili salt
- Burrata & stone fruit14.00basil oil, sourdough
- Crispy brussels10.75honey, aleppo, mint
Menu view only - 2
Connect the menu source through the approved setup.
Garnsh connects to the menu context your Toast access allows. Location mapping then ties each Garnsh location to its own menu.
- Guided, not self-serve
- Depends on your Toast access
- One mapped menu per location
Source menuMission St.Managed in ToastSmash burger16.25Green curry noodles18.50Half roast chicken23.00 - 3
Shape the right display for the right surface.
Choose layouts, themes, sections and promo areas for each hosted page, embed, QR view and board.
- Board layouts and orientation
- Focused QR selections
- Brand styling
Small plates- Charred corn ribs9.50
- Burrata & stone fruit14.00
Mains- Smash burger16.25
- Green curry noodles18.50
Drinks- Yuzu spritz7.00
- Cold brew tonic5.50
- 4
Preview and publish the public version.
Preview shows each surface exactly as guests will see it. Publishing is a deliberate action, and earlier versions are kept.
- Preview per surface and location
- Deliberate publish
- Version history
menu.littleember.example/missionSmall platesCharred corn ribsNew9.50Burrata & stone fruit14.00Crispy brussels10.75MainsSmash burger16.25Green curry noodlesSpicy18.50Half roast chicken23.00 - 5
Monitor the published state and recover safely when needed.
Freshness shows when the source was last read and when each version went live. Rollback restores the previous version. Last-known-good keeps a correct menu up if something upstream fails.
- Freshness information
- One-move rollback
- Last-known-good behavior
Upstream: unavailableServing last-known-goodSmall plates- Charred corn ribs9.50
- Burrata & stone fruit14.00
Mains- Smash burger16.25
- Green curry noodles18.50
Corn rib
season.9.50
Try steps four and five
Press a control. Read what changed.
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.
- v13
saved - v14
live - v15
draft
What Garnsh does not do
Garnsh is not a POS, website builder, checkout, payment processor, delivery service, loyalty platform, inventory system, print vendor, listings manager or hardware installer. It does not claim live stock, 86 status, daypart automation or guaranteed sync timing.
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.
How long does setup take?
It depends on your Toast access, number of locations and surfaces. Onboarding is guided, and timing is planned with you.
What is a last-known-good menu?
The most recent menu version that was published successfully. Garnsh keeps it public if an upstream issue occurs.
Are updates instant?
No. Garnsh uses a preview and deliberate publish step and does not claim guaranteed sync timing.
Keep reading
See it with your menu.
A guided demo walks these five steps with your locations.