Introduction
This article is for clients who have or are considering having multiple clubs in two or more different countries. We present how these clubs may work if they are run under separate branding. You will find the best practices, recommendations, possible workarounds and system no-go's presented. These are the questions and answers about the major technical and operational issues.
Mind that Perfect Gym (Software-as-a-Service) software architecture is designed to be country-oriented to address various aspects specific to different countries. As so, we recommend that separate databases be created for each of the clubs when they operate in two different countries.
- This article will be helpful to prospective or new clients during the onboarding phase.
FAQ
Q#1: Is the client able to operate on PGM when they have clubs in two different countries or several clubs on one database/PGM instance?
A: It is possible for the client to have many clubs in one database/PGM instance. However, if these clubs are in different countries, we recommend that separate databases should be created for each of them. This solution is the most convenient from the technical and operational point of view and provides seamless operation of each club. There is a technical possibility to create clubs operating in different countries in one database/PGM instance if the client agrees to create all of them in one culture. Nevertheless, the client should be prepared for the need to include further custom solutions, which are extra paid and out-of-the-box, or various issues and system hiccups as this is just a workaround, not the PGM feature.
Q#2: Is it possible to synchronize reports for the clubs in two different countries or several clubs on one database/PGM instance?
A: In such a case, you may use API to build your custom report combining the data from two separate databases.
Q#3: How should Access control work when the client has several clubs on one database/PGM instance?
A: If two or more clubs are on one database/PGM instance, a custom Access Logic should be created.
Q#4: How should Access control work when the client has clubs in two different countries?
A: Access rules cannot be linked between two different databases, which is the case for clubs operating in different countries.
Q#5: How is someone in country A supposed to know that member X has paid for a contract in the club in country B?
A: It is impossible to know it as long as these two clubs operate on two different databases. You may though offer a special payment plan to such members and add them to your database under dedicated conditions. However, the process of verifying if these members actually have paid for an active contract in another club in another country would have to be established outside the PGM.
Q#6: What should the User agreements and terms of service look like in the case of several clubs in different countries?
A: For the User Agreements to work properly, the cubs in different countries should have the same GDPR policy, club regulations and User agreements. Otherwise, two databases for each country should be created.
Q#7: How should the synchronization of members look to enable them to log in to the Client Portal in the case of several clubs in different countries on one database/PGM instance?
A: It is not possible to enable logging into the Client Portal in the case of several clubs in different countries. One database corresponds to one Client Portal instance only.