Skip to content
garnsh

Agencies and developers

Menu publishing built for restaurant websites and the teams behind them

Keep the site you designed. Garnsh supplies the location-correct menu, published from Toast, through a delivery pattern that fits the stack.

Plan an integrationSee website menus

Who it is for

You own the site. The menu takes care of itself.

Website studios

You built the site. You should not be retyping prices every time the kitchen changes them.

Agency partners

Offer clients a menu that stays in step with Toast, without owning their menu operations.

WordPress teams

Link a hosted menu page or place a website embed on the existing menu page.

Next.js and developer-led sites

Use a supported framework-native integration so the site renders the menu itself.

Delivery patterns

Three supported ways in.

High level by design. Specifics depend on the stack and are confirmed during onboarding. No unrestricted API is promised.

  1. 01No code

    Hosted page

    Garnsh serves a public, server-rendered menu page per location. Your site links to it. Lowest effort.

  2. 02Low code

    Website embed

    A small embed placed once on an existing page. The menu appears inside the site’s own layout.

  3. 03Developer

    Framework-native

    For supported frameworks, the site renders published menu data in its own components and styles.

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

Sample: published menu inside a studio-built site. Little Ember is fictional.

Guided implementation

A path you can put in a proposal.

  1. 1

    Scope

    List locations, surfaces and the current site stack. Confirm the restaurant’s Toast access.

  2. 2

    Choose a pattern

    Hosted page, embed or supported framework-native integration, per site.

  3. 3

    Map and style

    Map each location. Match type, color and spacing to the site.

  4. 4

    Preview together

    Review every page as guests will see it, with the restaurant team.

  5. 5

    Publish and hand off

    Go live. The restaurant owns publishing from then on.

FAQ

Straight answers.

Is there an open public API?

Garnsh does not promise unrestricted API access. Supported delivery patterns are hosted pages, website embeds and supported framework-native integrations.

Does Garnsh work with WordPress?

A hosted menu page or a website embed can be used with existing WordPress sites. Plan the specifics with the Garnsh team.

Who owns the website?

You and your client do. Garnsh publishes the menu. It is not a website builder.

Keep reading

Plan an integration.

Tell us the stack, the locations and the client. We will scope a pattern with you.

Plan an integrationSee the publish workflow