Adding a second location
One account, one bill, one team — and what changes on your invoice the moment a second venue goes live.
A second restaurant doesn't need a second account. It joins the one you already have, shares your team, and appears on the same invoice — which is the convenience and also the part worth reading before you press the button.
The shape of it
Your account is the thing we bill. Locations hang off it. The tooltip on the button states the whole model in nine words:
Add another venue to this account, one bill, shared team.
That has three consequences, and none of them is obvious from the button:
- One subscription. You are not starting a second plan; you are adding to the one you have.
- One team. The people on your team belong to the account, so a colleague you invited for the first venue can be given the second without a new invitation.
- One invoice. Your bill is your plan price multiplied by live locations.
What it does to the bill
Pricing is per location — you'll see the price carry a /location suffix, and the account total read as "3 locations · €117".
Volume pulls the other way. Once you're running several venues a group discount applies automatically and permanently: 10% from 2 locations, 15% from 5, 20% from 10. You don't ask for it and there's no code to enter — it appears on your invoice breakdown as "10% group discount".
Counting is by live location, not by rows on your screen. A venue still in setup or waiting for approval isn't billed. That's also why the number can lag what you just did: the bill follows the location going live, not you filling in the form.
If your account is on launch pricing, the breakdown reads "Launch pricing — fees waived" and settles at zero regardless of how many locations you add. The seat count is still real and still tracked — it simply isn't charged yet.
Adding one
Settings → Locations → Add location walks the same short wizard your first venue used: identity, address, hours, tables. Nothing about it is new, which is the point — you already know how to do this.
If the button reads Upgrade to add locations, the feature is above your current plan and the account needs a plan that includes it.
Then it waits
A new venue is not instantly public. It enters a review queue and our team approves it, usually within one business day, exactly as your first location did:
Your public booking page, menu, and link-hub aren't live until our team approves your location, usually within one business day. Keep configuring everything in the meantime.
The locations list shows each venue as Live or Setup, so you can see at a glance which is earning and which is still being built. Everything you configure while it waits — menu, hub, hours, tables — is ready the moment it opens.
One field you cannot change later
Country is fixed at signup. The locations list says so on the row itself. Country decides currency, tax treatment, address format and the public URL your venue lives at, so it is set once and never edited. A venue in the wrong country is corrected by adding the right one, not by editing this.
Get this one right on the way in. Everything else on a location — name, address, hours, covers, menus — you can change any afternoon.
Working across venues
Each location has its own admin, reached by its own handle, and the switcher at the top of the admin moves between them. Settings are per-location by design: your Milan covers and your Turin covers have nothing to do with each other, and neither do their menus, hours or booking policies.
What is shared is the account: your team, your subscription, your payment method, and your guest records. A guest who books both venues is one guest to you, not two — which is the reason to add a location here rather than open a second account.
Removing one
A venue you take offline stops counting toward your bill, and the group discount recalculates on the new number. Your guest history and past bookings stay where they are — closing a location is a change to what's bookable, not an erasure of what happened.