Why this exists

Most restaurants update menus more often than they admit and have less software than they need. Seasonal changes turn into weekend projects across three tools: a generic design app, a spreadsheet of items and prices, and an email thread to the printer. The QR code on the table goes stale because nobody wanted to ship the changes through every channel by hand.

We built Menu Author so that a menu lives in one place. Edit it on a real canvas, publish once, and the public URL, embedded version, kiosk display, QR-coded version, and print PDF all reflect the new state. The tool understands what a menu is (sections, items, modifiers, dietary tags, price variants, currencies) instead of treating every change as a generic shape on a page.

What we focus on

  • Restaurant specific structure. Dishes, add-ons, sizes, dietary tags, and sections are proper fields you fill in, not just free text.
  • Print as a real output. Print-ready files set up correctly for wherever they're going, not a browser "save as PDF."
  • Honest analytics. Anonymized view counts split by source. No tracking cookies on guests.
  • Multi-location, multi-role. Group owners run multiple brands under one account with admin and staff roles.
  • AI that respects your input. Upload a PDF or photograph an existing menu; you get a structured, fully editable layout, not a one-way trap.

The team

Menu Author is built by a small team that has spent years working with restaurants and software in roughly equal measure. We use the product ourselves: the same canvas, the same publish button, the same six print profiles.