Zuzu · Pro early access

Restaurant work, in plain language.

Ask how service went, change a menu item, prepare table setup, or turn a menu photo into a draft. Zuzu works through restricted MenuBeacon tools, with your role and restaurant boundaries still in force.

See Pro pricing Ask about early access

Availability is staged and is not guaranteed for every Pro restaurant yet. The public demo does not enable Zuzu.

Zuzu, MenuBeacon's restaurant AI assistant, waving Built into MenuBeacon

What Zuzu can do

A restaurant operator, not a general chatbot.

Every capability maps to a purpose-built MenuBeacon operation. What you can ask for still depends on your plan, market, account role, and restaurant configuration.

Set up the restaurant

Check setup status and help update the restaurant profile using the authenticated restaurant context.

Work on menus

List and create menus, add categories and items, edit items, change availability, and prepare bulk price updates.

Turn a menu into a draft

Use the existing MenuBeacon import flow to extract a reviewable menu draft from supported uploads, images, and PDFs.

Prepare table setup

Explain table QR setup, list existing tables, and prepare creation of new table records within plan limits.

Answer order questions

Find recent orders, open a specific order, and summarize order status without changing the order itself.

Explain performance

Summarize sales, top items, orders, tables, and customer counts when the account, role, and market allow it.

Zuzu pointing toward example restaurant questions

Start with the question you already have

Talk like a restaurant owner, not a software manual.

“How did we do today?”
“Which orders are still unpaid?”
“What sold best this week?”
“Make the pasta unavailable.”
“Raise drinks by 5%.”
“Set up my menu from this photo.”
“Create QR codes for ten tables.”
“What should I set up first?”

How an action happens

The model suggests. MenuBeacon decides what is allowed.

  1. 1

    You ask in plain language

    Zuzu reads only the conversation context needed to understand the restaurant task.

  2. 2

    MenuBeacon checks access

    Authentication, restaurant ownership, role permission, plan, market capability, rollout, and usage limits are checked on the server.

  3. 3

    Zuzu uses a specific tool

    There is no general HTTP, SQL, shell, code, or open-ended admin tool. Every action uses an allowlisted MenuBeacon operation.

  4. 4

    You confirm high-impact work

    Bulk prices, menu import, and table creation are stored as reviewable pending actions. A chat “yes” does not execute them.

Zuzu thinking about a request

Deliberate boundaries

Some answers should always be “I can’t do that.”

Zuzu holds no payment credentials or cross-restaurant data. Prompt screening, output screening, tenant scoping, permission checks, plan and market checks, validation, confirmation, budgets, and audit logs sit around the model.

  • Access another restaurant or accept a restaurant ID from the chat
  • Delete menus or restaurant data
  • Issue refunds or change payments and payouts
  • Change staff roles, permissions, passwords, or security settings
  • Modify orders, regenerate QR codes, or change delivery configuration
  • Send marketing campaigns or browse the open internet

See the broader MenuBeacon security overview →

Availability

Pro entitlement, staged rollout, normal MenuBeacon underneath.

Zuzu is designed for active Pro restaurants in Pakistan, the UK, the US, and the EU. Access also depends on rollout enablement and operational safeguards. If Zuzu is paused, unavailable, or reaches its allowance, the menu, orders, kitchen, and every standard MenuBeacon screen continue to work.

Pro

Required plan

4 markets

PK · UK · US · EU launch scope

Independent

Core product does not rely on AI

Zuzu giving a thumbs up

Zuzu questions

Who can use Zuzu?

Zuzu is for active Pro restaurants in supported launch markets (Pakistan, the UK, the US, and the EU), subject to the staged rollout, restaurant-level enablement, provider availability, and usage safeguards. Free accounts see a product teaser rather than an active assistant.

Can I try Zuzu in the public demo?

Not currently. Zuzu is disabled for the shared public demo account so demo visitors cannot consume the restaurant assistant allowance or create actions for one another.

Does Zuzu make changes without asking?

Explicit, lower-risk menu writes may run after the normal permission and validation checks. High-impact actions such as bulk price changes, menu import, and table creation require a separate confirmation card tied to the same user and restaurant.

Can Zuzu see other restaurants?

No. The server binds tools to the authenticated restaurant and re-scopes every menu, item, table, order, and other resource before returning data or making a change.

What happens when the AI service is unavailable?

The rest of MenuBeacon keeps working. Zuzu has independent feature flags, rollout controls, budgets, and circuit breakers and is not required for menus, orders, the kitchen, or any standard workflow.

Build the restaurant first. Let Zuzu make it easier to run.

Start with MenuBeacon Free, then move to Pro when the workflow and staged Zuzu access fit your restaurant.

Create your free menu

Zuzu requires active Pro and rollout eligibility · Core MenuBeacon works without AI