Locations and multi-venue setup

If you operate more than one venue under the same legal entity (a food truck plus a brick-and-mortar, two bars in different cities, a coffee shop with a pop-up at events), Rowie groups them as locations under a single organisation.

Where to find locations

Locations live on the Organization page in the vendor portal, not under "Account" or "Settings". To get there:

1. Click Organization in the sidebar (under the Account group at the bottom. Sidebar group labels render in uppercase, but the underlying label is "Account").
2. The Locations card is at the top of the page, before the org-level fields. Your first location was created at signup. New ones appear here as you add them.

Each location renders as a tile showing its name, a star icon if it's the default, and a city/state subtitle (e.g. "Springfield, OR") once filled in. The tile contains two sub-cards for the auto-generated POS and Kitchen system accounts (see Staff, POS and kitchen logins). Non-default locations also get a Make default button and a delete (trash) icon next to the edit pencil.

Add a location

1. On the Organization page, in the Locations card header, click the orange + Add location pill.
2. The Add location modal opens. Fill in:
   • Name (e.g. "Downtown"). Required. The Create button stays disabled until this is filled.
   • Street address (123 Main St).
   • City, State / Region, Postal code.
   • Phone (international input with country flag dropdown plus dial code).
   • Timezone (dropdown with the standard list, e.g. America/New_York, Europe/London, Asia/Singapore).
   • Tax rate (%). Optional, with helper text "Applied to orders, sessions, and preorders settled at this location. Leave empty to use your organization's default rate." See Tax rates.
3. Click Create. The new location appears in the Locations card immediately, with its own POS and Kitchen system accounts ready to receive passwords. New locations are active by default.

Editing an existing location uses the same form but adds one extra field, Active menu (a dropdown picking which menu the POS should default to at this venue).

Why locations matter

Locations drive several behaviours:

• Menus, floor plans, and bookings are each pinned to a location at creation. The same physical menu can be reused across locations, but operational data (tables, sessions, bookings) belongs to one venue.
• Sessions and orders are tagged with the location they happened at, so analytics and reports filter cleanly by venue.
• Tax rates can be set per-location, falling back to the organisation default. See Tax rates.
• Staff scoping. Staff (User role) and POS / Kitchen accounts see only the data for the location(s) assigned to them. Owners and admins see everything aggregated org-wide.

Assign staff to locations

You pick the locations directly inside the Invite Staff Member modal:

1. Go to Staff in the sidebar (Pro plan only. See Staff, POS and kitchen logins).
2. Click Invite (top-right) or the Invite Staff button in the empty state.
3. Switch the Role tile to User ("App only access"). The Assigned locations checkbox list appears below. At least one must be ticked or the invite won't send.
4. Click Send Invite. The invitee gets an email to set their password.

Staff (User role) sign in on the mobile POS only. When they have access to more than one location, the app's Account → Location picker lets them switch between them.

Admins also need to be invited via the same modal but choose the Admin tile. They have org-wide access and no location selection appears for that role.

Per-location settings

Each location tile on the Organization page shows the POS and Kitchen system accounts inline (each with Generate password / Set manually). Clicking the pencil edit icon opens the Edit location modal. That's where you change:

• Name, address (Street address / City / State / Region / Postal code), Phone, and Timezone.
• Tax rate (%). Per-location override (see Tax rates).
• Active menu. The menu that should be active for the POS at this venue. (Only available on Edit, not on Create.)

Non-default locations also expose:

• Make default. Promotes this location to be the org default.
• A trash icon. Opens a delete confirmation modal where you have to type the location name to confirm.

Deleting a location

Locations are soft-deleted, so historical orders and sessions on that location are preserved. The portal blocks deletion when:

• It's the only active location in the organisation.
• There are open or in-progress table sessions on it.
• It still has menus, floor plans, active bookings, or booking pages attached.

Reassign or close those dependencies, then delete.

See also

• Staff, POS and kitchen logins
• Roles and permissions
• Tax rates