Markets · St. Louis · Remote from Houston

For St. Louis restaurants whose menu lives in a PDF

A PDF menu is easy to upload and hard to read on a phone, and it is often out of date. A readable HTML menu loads quickly and works better on small screens, but only if someone owns updates. This guide helps you decide what the menu page should contain, how it relates to any ordering platform you already use, and who changes it when prices or dishes do.

Houston-based, with remote delivery for St. Louis businesses. Work directly with Robert through email, video and shared reviews, from the initial brief to handoff.

The menu question

  1. 01 How often do dishes or prices change?
  2. 02 Does an ordering platform already show the menu?
  3. 03 Who will send changes, and to whom?
Skyline of St. Louis, Missouri
St. Louis, Missouri · Remote delivery from HoustonPhoto: Panini! · Source · CC0. Cropped and optimized.

St. Louis · Restaurants and private-dining businesses

A group-dining visitor should not have to decode the menu PDF

A public local resource, then our website recommendation. The source does not endorse Hyper Solutions.

Observedfrom a public source

Explore St. Louis publishes a group-dining directory alongside its restaurant resources. A visitor choosing a meal and a planner arranging a group have related but different questions.

Source, worth reading yourself

HSC adviceour recommendation, not the source's

Provide a readable HTML menu and a distinct group inquiry where the restaurant actually offers one. Use owner-confirmed capacity and policy information, not inferred availability from a directory.

A possible website implication for owners in this segment. Whether it applies to you is settled in your brief and written quote.

Illustrative only

A planning scenario

A fictional restaurant lets a diner browse current dishes on a phone while a group planner asks about a tentative date and format. Neither action confirms a table or event.

Invented to show the decision. Not a client, not a result.

Before you ask for a price

Three checks before you decide

  1. Is the menu usable as text without downloading or zooming a PDF?
  2. Are group requests distinguishable from ordinary dining and takeaway?
  3. Who keeps dishes, dietary wording and event conditions current?
Fictional demo

Kettle & Clove

Explore the fictional HTML menu and practical visit information.

Open the demo

Buyer decisions

Settle these before asking anyone to price the site.

Each decision ends with what it means for the written quote.

01HTML menu, PDF, or both?

An HTML menu reads well on a phone and can be searched. A PDF can remain as a printable copy if you keep it current. Two versions that disagree is the outcome to avoid.

In the quoteA readable menu built from the menu you supply, up to 30 items as agreed, can be included. Larger menus are scoped separately.

02How does it relate to ordering?

If you already use an ordering or reservation service, it may hold its own menu. Linking to it, and deciding which version is the reference, prevents conflicting prices.

In the quoteNormal links to existing ordering or reservation services can be agreed; we do not set them up or manage transactions.

03Who updates the menu?

There is no automatic menu editor in standard scope. Decide whether changes go out as quoted requests or within optional upkeep, and who sends them.

In the quoteOptional Website & Profile Upkeep is $149/month with one supplied update batch; whole-menu retyping is separate.

Illustrative buyers

How the decision plays out for different businesses.

Illustrative website briefs, not actual clients. The pages below are planning examples; your written quote defines the agreed scope.

  1. Example 01

    A neighbourhood restaurant with a stable core menu

    HTML menu by section, a printable PDF kept in sync, hours and directions up front.

    Home, Menu, Visit, About

  2. Example 02

    A two-location group using an ordering platform

    Location pages with hours, a shared menu page, and clear order links per location.

    Home, Menu, Locations, Order (link)

Scope line

What to bring to the quote, and what gets scoped separately.

Belongs in your brief

  • Your current menu text and prices
  • Section structure for the menu
  • Dietary or allergen wording you supply
  • Links to existing ordering or reservations
  • A named person who sends menu changes
  • Hours, address and a directions link

Reviewed and quoted separately

  • An automatic menu editor or CMS
  • Online ordering, payments or POS setup
  • Menus beyond the agreed item count
  • Retyping a whole new menu after launch
  • Food photography

Standard work fitting an approved brief starts at $4,250 one time for an informational rebuild, with one consolidated revision round. Complex or unknown work needs technical review and a separate fixed written quote. Domain and hosting are purchased in your own accounts. Optional upkeep after launch is never required. See pricing.

Menu handover

Menu content and update ownership

Tick what you already have. Ticks stay in this browser tab only; nothing is saved or sent. Print it, or bring the gaps to your quote conversation.

0 of 6 ticked

Content
Ownership