How to keep a Toast menu updated on your website

Why website menus drift away from the POS

Most restaurant websites were built once, by someone who has since moved on. The menu page was typed into the website builder, or uploaded as a PDF, on launch day. Since then the kitchen has changed prices, swapped a seasonal plate and dropped two items that never sold. The menu in Toast reflects all of that. The website reflects none of it.

The drift is not anyone’s fault. Updating the website is a separate task, in a separate tool, with a separate login. On a busy week it waits. On a busy month it is forgotten. Guests then read one price online and pay another at the counter, and the team hears about it at the worst moment.

Step one: decide which menu is the source

Before you change any tooling, agree on one rule: the menu your team runs in Toast is the source. Prices, item names, descriptions and sections are changed there first. Every guest-facing copy of the menu is then a published version of that source, not an independent document someone edits on the side.

This sounds obvious, but many teams quietly run two masters. The marketing person edits the website copy to sound nicer. The manager edits the board to fit the screen. Both versions slowly become their own menus. Pick the source, write it down, and tell everyone.

Step two: choose how the menu reaches your site

There are three common ways to put a published menu on a restaurant website. Which one fits depends on the site you already have and who maintains it.

• Hosted menu page. A separate public page, served for you, that holds the menu for one location. Your website links to it from the main navigation. This is the fastest option and needs almost no website work.
• Website embed. A small piece of code placed on your existing menu page that shows the published menu inside your design. Your web person adds it once.
• Framework-native integration. For developer-led sites, the menu is rendered by the site itself using a supported integration, so it matches the rest of the code and styling.

Step three: make publishing a deliberate step

Automatic copying sounds ideal until a half-finished edit shows up on the public site at 6 p.m. A safer pattern is to separate editing from publishing. Changes are made in the source, then previewed as guests would see them, then published on purpose.

Preview lets you catch the boring mistakes: a missing price, a description that runs too long on a phone, a section in the wrong order. Publishing is the moment the public version changes. If something still slips through, rollback returns the site to the previous published version while you fix it.

Garnsh is built around this pattern. It reads the location-correct menu from the approved Toast setup, lets you preview each surface, and publishes only when you choose. It does not claim instant or guaranteed sync timing, and it does not show live stock or 86 status.

Step four: get the location right

If you run more than one location, the website needs to show the right menu for the right place. A guest planning a visit to your second site should not see prices from your first. Give each location its own menu page or its own embed, and make sure each one is mapped to the right location menu in the source.

Location mapping is simply the record of which source menu belongs to which public location. Check it when you open a location, close one, or change how menus are organized in Toast.

Step five: keep the page readable

A correct menu that nobody can read is still a problem. Menu pages are mostly read on phones, often outside, often in a hurry. Use real text rather than images of text. Keep sections short and clearly labeled. Show prices plainly next to item names.

Real HTML text also helps search engines and assistive technology read the page. Garnsh hosted pages are designed for crawlable, accessible HTML. That is a sound starting point, not a promise of any search ranking, and it is not a substitute for your own accessibility review.

A simple weekly routine

Once the setup is in place, the routine is short. When the menu changes in Toast, the person responsible opens the preview, checks the website version for each affected location, and publishes. Once a week, someone glances at the freshness information to confirm when each location was last published. That is the whole habit.