Your booking address

Every venue has a public web address diners book at. It looks like this:

tablestack.ca/avacorp/hyatt-breakfast/book
             └─ group ─┘└─── venue ───┘

The first part is your group — the organization the venue belongs to. The second is the venue itself.

Why there are two parts

Because venue names repeat. Plenty of restaurants have a "patio", a "downtown" or a "main dining room", and two different businesses must be able to use the same word without one of them losing. The group segment is what keeps them apart, so your venue names are yours alone rather than first-come-first-served across every restaurant on TableStack.

It also groups a multi-venue business under one recognisable name, which is what guests see in the address bar when they book.

Changing it

An Owner can change either part, in Venue settings → Booking address. Type what you want in plain language — "The Patio" becomes the-patio automatically. Both halves save together, so you're never left with a half-applied address.

A few addresses are refused:

• Words TableStack reserves for its own pages, like admin, settings, pricing or help. A group called settings wouldn't break anything — it would just become unreachable, which is worse, so it's blocked outright.
• Addresses already in use by another group, or by another venue in your group.
• Addresses somebody has retired. If another business used to be avacorp and renamed, that word stays reserved to them, so their old links can't be quietly hijacked. You can always reclaim your own old address.

Dropping the group entirely

If you'd rather not show the group at all, a venue can claim a short address:

tablestack.ca/hyatt-breakfast/book

It's optional, Owner-only, and set in the same place. Once claimed it becomes your real address — it's what your booking page, embed snippet, QR posters, search listing and Google feed all publish, and the longer form redirects to it. Clear the field to go back to the long form.

The trade is worth understanding before you claim one. Your venue slug only has to be unique inside your group, which is why you can call a room "patio" even though hundreds of other restaurants have one. A short address competes with every group name on TableStack, so it is first come, first served — common words are likely already gone, and you'll need something more specific.

If you release a short address, TableStack keeps it pointed at you rather than handing it to the next person who asks. Links you have already given out don't suddenly lead somewhere else.

Old links keep working

This is the important part. Your booking address ends up in places you can't edit afterwards: printed QR posters on the host stand, confirmation emails already in guests' inboxes, your Google listing, links shared on social.

So renaming never breaks them. TableStack remembers every address a venue has ever had and permanently redirects the old ones to the current address — the guest lands on the right booking page and never sees an error. This holds even if you rename both parts, or rename the same venue several times over the years.

Any styling on the link — the accent colour and corner radius from your embedded booking widget, or a language parameter — carries across the redirect too.

What this affects

• Your booking page and the waitlist QR — both sit at this address.
• Your search listing and Reserve with Google feed — they publish the current address.

What affects this

• Your role — only an Owner can change it.
• Archiving a venue — an archived venue stops taking bookings, and its address stops resolving.

Related: venue settings, QR codes.