Venue settings

Finding your way around

Settings save when you press Save changes — nothing is written while you type. The moment the page holds edits the server hasn't seen, a floating "You have unsaved changes" bar appears at the bottom of the screen with the save button right in it, so you can never scroll away and lose work silently.

On a desktop screen the page shows a section rail on the left — tap any entry (Hours, Deposits, Guest book…) to jump straight there; the rail highlights the section you're reading as you scroll.

Settings save explicitly: edits collect on the page and a floating Unsaved changes bar appears the moment anything differs from what's stored, with a Save button right in it. Nothing takes effect until you save — a half-entered scheduling rule can't disturb live availability.

Venue settings is the control room for one location. Almost everything TableStack does for a venue — what the booking page offers, how service flows, how the room is branded — is configured here. This is a tour of what you'll find; several sections have their own detailed guides linked below.

The basics

• Name, timezone and address. Your venue's identity. The timezone matters more than it looks: all your times — service hours, reports, reminders — are shown in it.
• Booking-page logo. Upload a logo (PNG, JPG or WebP) that appears at the top of your public booking page. It's separate from the embedded widget's styling.
• Booking-page language. Set the language diners see on your public page.

Service hours and booking rules

This is the heart of what your booking page offers — service periods, slot interval, buffer, pacing cap, turn times by party size, slot rules and the overbook passcode. Each of these is covered in depth in scheduling and turn times and overbooking and holds.

Service flow

Define the meal steps your team taps through — turn courses on or off and rename them to your language. See course sequences. You can also set custom table status names so the floor speaks in your terms.

Ticketed experiences

Create prepaid, capacity-capped special seatings — wine dinners, prix-fixe menus — offered on the booking page within their dates. See creating an experience.

Closures and special dates

Mark days you're closed, or set special hours for a single date that override the weekly schedule — a shorter holiday service, for example. Closures show grey on the reservation calendar.

Integrations

Deposits, AI features and future partner integrations moved to their own Integrations page under Manage — see below.

Guest communications

Guest notifications (confirmations, waitlist and reminder toggles), post-visit feedback requests, branded email content, promo codes and marketing automations all moved to their own Guest communications page under Manage. See notifications & reminders.

Your booking address

The public web address diners book at is set here too. See your booking address for what the two parts mean and how renaming keeps old links alive.

Closing a venue

When a location closes — for a season, a renovation, or for good — archive it rather than deleting anything. Archiving takes the venue out of your venue switcher, hides it from TableStack's public directory, stops its booking page taking reservations, and drops it from your bill. Everything else is kept exactly as it was: the floor plan, past visits, reservations and every figure in your reports. Restoring puts it all back.

TableStack won't archive a venue while there's a party still on the floor, while guests hold upcoming bookings (they'd be stranded), or if it's your only venue. Clear or move those first.

Permanently deleting a venue is a separate, Owner-only step, available once it's archived and only for a venue that never took a booking or hosted a visit — usually one created by mistake. You have to retype the venue's name to confirm. Anything with real history stays archived instead, because your reports read that history.

What this affects

• Your booking page and availability — most rules here shape what diners can book.
• Service — the flow and status names your team uses.
• Reports — turn-time targets and feedback collection are set here.

What affects this

• Your role — changing venue settings is permission-gated.
• Your plan — deposits and AI features are Pro.