Deploying SevenRooms for a brand present in several cities is not simply a matter of creating one more account. You have to decide what is shared across all venues and what stays specific to each one. This case study looks back at the SevenRooms deployment māhie carried out for Nammos, in Dubai and London, then explains in plain terms what it involves for a group operating across several markets.
What this article covers, and what it does not. It relies only on public information: the presentation of Nammos and of the project on mahie.io, and the nammos.com website. We do not detail Nammos's actual configuration, results or data. The educational part draws on SevenRooms' official documentation and describes what exists in general, not what was enabled for this client.
Nammos in Dubai and London: context and deployment
Born in Mykonos, Nammos took its Mediterranean way of life to the beaches of Dubai and to a two-storey address in Mayfair, in the heart of London. The brand combines the world of the beach club and that of the restaurant, with an international dimension.
On mahie.io, Nammos appears among the venues where māhie deployed SevenRooms, alongside Manko, L'Arc and Rural by Marc Veyrat. That is the only public information about the nature of the assignment: a SevenRooms deployment for a brand present in Dubai and London. The detail of the initial brief is not published, so we do not invent it.
The situation is nonetheless a classic one for an international group: several venues, different clienteles, and languages, currencies and booking habits that vary from one market to another, yet a brand that must stay consistent.
What does deploying SevenRooms for a multi-market brand mean?
Deploying SevenRooms across several markets means configuring each venue for its local context while keeping a shared structure for the brand. In practice, three questions come up.
- What must be identical everywhere? The tone, how a guest is qualified, the tag categories, the indicators management follows.
- What must be local? Floor plans, service hours, booking conditions, payment policies, the language of communications.
- Who has access to what? A group director, a regional manager and a host at the door do not have the same needs.
A good setup answers these three questions before changing a single setting. Otherwise each venue ends up working its own way, and it becomes impossible to compare or steer at brand level.
This thinking applies to a brand with two venues as much as to a group of twenty. The more markets you add, the more the lack of a shared foundation costs: each new opening starts from scratch instead of reusing a proven base. Conversely, a foundation that is too rigid stops local teams from adapting to their clientele. The work of a deployment is to find the right balance, venue by venue.
Structuring the group: venues, Pods and access
For groups, SevenRooms offers a Group Portal, which lets you manage settings, access and performance across an entire venue group. It is available on select SevenRooms packages, so check what yours includes.
Three notions are worth knowing.
- Pods: groupings of venues based on a shared characteristic. Common Pod Categories include cuisine, service type, brand, region, country or property. For a brand present in Dubai and London, one could for example imagine a "Country" category. That is only an example of use, not Nammos's configuration. Pod management is reserved for customers on the Premium package, according to the documentation.
- Group Users and Roles: a user can have access to the whole group, to selected venues or to selected Pods, with different roles depending on the venue. Updating a role once applies it to everyone who holds it.
- Global Tags or Tags limited to selected Pods: client and reservation tags can be standardised for the whole group, or reserved for the venues concerned.
The point is simple: teams see only what concerns them, and management keeps an overall view.
Fictional example, for illustration: a brand opens a second venue in another country. If each team invents its own labels ("VIP", "Important guest", "Big spender"), group reports stop meaning anything. If the brand defines three shared categories from the start and leaves two free labels per venue, teams keep their flexibility and management keeps its reading. This method choice costs half a day of framing and avoids months of cleanup.
Language, payments and booking rules: what varies by market
Each market has its own habits. Here is what SevenRooms lets you adapt, according to the documentation.
Guest language. The Guest-Facing Language setting lets you customise the text shown to guests (reservation widgets, confirmation pages, emails, SMS, policies) and enable several languages. SevenRooms states that every customisation must be translated manually into each enabled language. If you change a term, for example, you must update the translation in every language. This feature also depends on your package.
Booking and payment rules. Each venue has its own availability and payment settings. A seasonal venue and a highly sought-after one will not have the same rules. On deposits, see our article on deposits, card imprints and prepayment.
Moving guests between venues. With the Cross-Promotion feature, a guest who cannot find a table at one venue can be offered the group's other venues. According to the documentation, the Cross-Promotion and Group widgets are only available to customers on the Growth or Premium packages.
Personal data. Data protection rules vary by country. Before configuring consent, emails and marketing, have your approach validated by your legal counsel for each market. For the European framework, our article on emailing and GDPR with SevenRooms covers the basics.
Tracking performance and unifying guest knowledge
A multi-market deployment is only worth something if management can compare. The Group Portal offers consolidated reports (Group Reporting). According to the documentation, they let you in particular:
- review past and future reservations, and track covers;
- compare venues and spot the top performers;
- analyse cancellations and no-shows;
- follow returning guests;
- review payments and refunds, with amounts in local currency.
Pods act as filters in these reports: you can, for example, compare the venues of a single region.
On the guest knowledge side, the stake is consistency. Auto-tags and Reservation Tags defined the same way across all venues let you segment the clientele in a comparable manner. Our article on Auto-tags explains how to build them.
Good to know. SevenRooms features, packages and labels change over time. Before building a deployment plan, confirm with SevenRooms what your plan includes today, in particular the Group Portal, Pod management, Guest-Facing Language and Cross-Promotion. A plan built on a feature your package does not include costs time at every later step.
How to approach a multi-venue SevenRooms deployment
Here is the method we recommend to a group expanding across several markets.
- Map the venues: service types, languages, currencies, teams, tools already in use (POS, website, newsletter).
- Define the shared foundation: tag categories, user roles, tracking indicators, tone of communications.
- Define local variations: hours, payment policies, enabled languages, booking access rules.
- Configure a pilot venue, test it with real bookings, then replicate the logic across the other venues.
- Connect SevenRooms to the rest of the ecosystem: website, CRM, newsletter, forms. Our SevenRooms service includes these connections up to the API.
- Train each local team, taking language and role differences into account.
- Follow up after launch: check the group reports, fix discrepancies, adjust the rules.
A few common mistakes to avoid:
- configuring each venue separately, without a shared foundation;
- multiplying tags without a shared definition;
- forgetting to translate each customisation into every enabled language;
- giving everyone full access "to go faster";
- postponing training of local teams until after opening.
Multi-market SevenRooms deployment: frequently asked questions
Do you need one SevenRooms account per venue?
Each venue is configured as its own venue with its own settings. To manage several venues together, SevenRooms offers the Group Portal, available on select packages. Check with SevenRooms what your plan includes.
Can SevenRooms be used in several languages?
Yes, with the Guest-Facing Language setting, depending on your package. You enable the languages you want, then manually translate customised text into each one. SevenRooms lists English, French, German, Italian, Spanish and several other languages.
How do you compare the performance of several venues?
Group Reporting in the Group Portal consolidates reservations, covers, cancellations, returning guests and payments, with filters by Pods. For the comparison to be reliable, tags and rules must be defined the same way everywhere.
What does this article contain about the Nammos project?
It uses the public presentation: Nammos took its Mediterranean way of life to Dubai and London, and māhie deployed SevenRooms for the brand. It gives no detailed configuration or results, and the educational part describes general SevenRooms features.
Need help deploying SevenRooms across several venues?
A growing group needs a clear structure from the start. māhie has deployed SevenRooms more than 60 times for restaurants, hotels and groups, and supports more than 90 venues.
- Setup and migration from your previous tool, without losing your guests.
- Tailored audit of your current configuration.
- Guest segmentation: VIPs, regulars, companies, first visit.
- API connections with your website, CRM, newsletter and internal tools.
- Team training: floor, reservations and management.
Explore our SevenRooms offer and our projects, then Contact māhie.
