MenuPulse
One menu, every surface, always current
The structured menu of the restaurant: dishes, modifiers, prices, allergens, 86-ed items. Read by every surface that needs to talk about food — chat, voice, website, print.
- 1 Canonical menu, every channel
- Live 86-ed propagation
- Typed Allergens and modifiers as data
MenuPulse replaces the scattered PDFs and spreadsheets with a structured menu. Each dish has allergens, modifiers, price tiers, and a description; each section has availability windows; the whole thing is versioned so nothing goes out of sync.
When a dish is 86-ed for the night, the update flows to every channel at once — the website, the voice host, the chat, the printed tablet menus. No more "sorry, we ran out of that an hour ago" surprises.
Everything MenuPulse handles for you
-
Structured dishes
Allergens, modifiers, and price tiers on every dish — not just a wall of text.
-
Live 86-ed status
One toggle propagates to every channel so no one orders a dish that ran out.
-
Availability windows
Brunch, lunch, dinner, seasonal specials — availability handled as first-class data.
-
Everywhere rendered
The same canonical menu drives chat, voice, website, and printed QR pages.
How MenuPulse plugs into the restaurant stack
MenuPulse is a shared data source. Every conversational and print surface reads from it; the kitchen and managers update it.
- VoiceHost answers phone callers from the structured menu with current prices and 86-ed flags.
- ChatBuilder renders live menu cards in chat, including out-of-stock states.
- PrepLine reads dishes and modifiers to compute kitchen load forecasts.
- ReviewLoop cross-references reviews with the menu to learn which dishes drive reactions.
Wire MenuPulse into your product today
Book a consultation with our founders and we'll walk you through the whole microservice stack — not just this one — live on your domain.