Skip to content

Venue settings — the identity card every other screen reads

The Venue settings page is the foundational identity card of your restaurant inside the system. It’s the page that holds the name printed on every receipt, the opening hours on the public site, the phone number customers tap to call you, the currency the till charges in, and the timezone every shift report is filed under. Most other settings pages drill into one specific corner of the venue — the theme, the home-page layout, the languages — but they all draw from the values you set here.

This is an owner-and-manager page. The kitchen and floor staff rarely open it. You’ll come here when you first set up the venue, then a handful of times a year when the address changes, the hours shift for a season, or you add a new aggregator link.

What it does

Imagine you’re opening the doors of a new pizzeria. Before the till can ring a single order, before the public site can show a single dish, before the AI can write a single caption that sounds like you, the system needs a few things settled. Who are you, where are you, when are you open, what currency do you charge in, what kind of place are you. That’s what this page covers.

Name and public URL. The venue’s name appears on receipts, on the public menu, on every email that goes out, and at the top of every browser tab. The public URL (the short slug like marcos-pizzeria) is the address customers see in their browser: app.bitethemenu.com/marcos-pizzeria. Changing the slug breaks every QR code and shared link in the wild, so it has its own confirmation step — you don’t accidentally rename your URL while editing your phone number.

Currency, decimals, and timezone. Three small dropdowns that quietly drive every formatter in the app. Pick EUR and every price renders with a €; pick THB and prices render in baht with no decimal places (the local convention). Pick Europe/Rome as the timezone and every “open this ticket” timestamp, every shift report, every scheduled social post reads in Rome time. Changing the currency doesn’t convert historical prices — it just swaps the symbol going forward. Changing the timezone re-renders every historical timestamp in the new zone.

Cuisine archetype. A short list of tags — Italian, Pizzeria, Sushi, Thai, Bar, Cafe — that tells the AI what kind of kitchen you run. The AI uses this to write captions in the right register (a fine-dining osteria gets different copy than a hawker stall), to recommend the right photo style, and to bias the recipe suggestions when you’re building a menu. Pick more than one if you straddle categories — a wine bar that also serves pizza is honestly both.

Opening hours. Seven rows, one per weekday. Open time, close time, optionally a note (“kitchen closes 22:30, bar until midnight”), and a closed toggle for the day off. These hours appear on the public site, on the booking widget, and inside the AI’s mental model of when you’re alive — so the social calendar won’t schedule a “lunch is now!” post on the day you’re shut.

Contact and address. Phone, email, WhatsApp, LINE, street, city, country, latitude/longitude. The phone and email go onto receipts and into the “Contact us” block on the public site. The lat/long power the Find us on Maps link and any future driver-routing for delivery. The social handles — Instagram, Facebook, TikTok, X, YouTube, website — show up as little icons in the public footer and feed the social calendar so it knows where to publish.

Aggregator profile. If you also sell through Uber Eats, LINE MAN, Grab, foodpanda, or Deliveroo, paste your storefront URLs here. The public site shows them as “Order on…” buttons next to the in-house ordering button, so customers landing on your page can pick the channel that suits them.

Online ordering toggles. Two switches. Ordering enabled turns the whole online-ordering flow on or off — when off, the public site is a menu-only brochure, no add-to-cart. Pickup / delivery sub-switches let you offer one, both, or neither, and pick which is the default when a customer arrives without choosing.

Custom domain. If you’ve bought your own domain (marcospizza.com rather than app.bitethemenu.com/marcos-pizzeria), this card links out to the dedicated custom domain page where you wire the DNS.

The rule

Every other settings page drills into one corner of what lives here. The hours, the currency, the name, the contact — change them here once, and every receipt, every email, every public page, every cron job that fires off a scheduled post picks up the new value automatically.

How to use it

Open Admin → Settings → Venue. The page is a single long form, top to bottom. Edit any field — the input glows as you type — and hit Save changes at the bottom. The save covers most cards in one shot; a couple of cards (the slug, the about page, the aggregator) have their own dedicated save buttons because changes there cascade further than a name tweak.

You don’t need to fill everything at once. The empty-state defaults are sensible: currency falls back to USD, timezone to UTC, hours to “closed” until you set them, ordering off until you turn it on. Walk the page top-down on first setup, fill what you have, save, come back when you have the rest.

A few fields lock down to owner-only — currency, timezone, the slug, the legal name. Managers can edit hours, contact details, and the about copy without owner intervention.

Worked example

Anna has just signed up for BiteTheMenu for her pizzeria in Bangkok. She opens the Venue settings page on day one.

She types Pizzeria da Anna in the name field. The slug auto-suggests pizzeria-da-anna; she keeps it. She picks THB as the currency — the example renders ฿1,250, no decimals, exactly as a Bangkok menu should read. Timezone Asia/Bangkok; the live clock to the right shows 15:42, the correct local time, so she knows the setting took. Archetype: Pizzeria and Italian, both selected.

She fills the hours: Tuesday to Sunday 11:30 to 22:30, Monday closed, with a note on Sunday “lunch service only, closes 15:00”. The contact block: phone +66 81 234 5678, email hello@pizzeriadaanna.com, WhatsApp the same as the phone, no LINE yet. Address Sukhumvit Soi 49, Bangkok, country code TH, lat/long picked off Google Maps.

Instagram handle @pizzeriadaanna, Facebook page slug pizzeriadaanna, no TikTok yet. She skips the aggregator card — she hasn’t onboarded with Uber Eats yet. Ordering toggle off for now; she’ll flip it on once the menu is built. Save changes. A green “Saved ✓” tick appears beside the button.

Twenty minutes of admin work. The receipts that print tonight already say “Pizzeria da Anna, Sukhumvit Soi 49, +66 81 234 5678” at the top. The public site at app.bitethemenu.com/pizzeria-da-anna shows the hours, the address with a Google Maps link, the phone as a tap-to-call button, and the Instagram icon in the footer. Two weeks later when she writes her first social caption, the AI knows it’s a pizzeria in Bangkok with an Italian flair and writes accordingly — no extra setup needed.

  • Custom domain — wire your own domain so customers reach you at marcospizza.com instead of the default URL.
  • Home page builder — design the public landing page that the name, hours, and contact details from here flow into.
  • Languages — set which languages the public site speaks; the venue name and about copy from here are what get translated.
  • Tax rates and registration — the VAT and legal-entity details that ride alongside the venue identity on every invoice.
  • Members — the humans authorised to sign in and edit what’s on this page.