Club integrations (CSI)
The CSI Software integration connects your CSI club management system with Zenoti, providing bidirectional member synchronization. Club members managed in CSI become guest profiles in Zenoti; guest profile updates in Zenoti can flow back to CSI. This article covers the configuration model and operational concepts for the CSI integration.
Audience: Organization administrators who configure and maintain the CSI Software integration.
On this page
- Before you begin
- Deployment model
- External-system prerequisites (CSI side)
- Network requirements
- Connect CSI Software
- How member fields are mapped
- How membership types are matched
- Run the initial sync
- Sync direction
- Migrate stored accounts between processors
- Handle CSI sync failures
- Reconciliation
- Tips
- Troubleshooting
Before you begin
Permission: You need organization administrator access to configure the CSI integration.
- Your organization must have an active CSI Software contract with API access.
- You need CSI API credentials obtained from your CSI Software account representative.
- The CSI integration must be active for the center before sync operations can run.
- Complete the CSI-side prerequisites before connecting.
Deployment model
CSI Software is typically self-hosted at the club's premises, with a CSI-provided connector that exposes the API to Zenoti. Zenoti uses a provider pattern to communicate with CSI Software, selecting the appropriate processor based on the country code configured for the center.
The integration supports two sync directions:
- Inbound (CSI β Zenoti): Zenoti retrieves member data from CSI and creates or updates guest profiles. For main members, Zenoti automatically creates a membership invoice. For dependent members, Zenoti links the record to the main member.
- Outbound (Zenoti β CSI): Zenoti identifies guest profiles modified since the last sync and pushes those changes to CSI Software.
Each sync run is logged with success and failure counts, the sync date, and the method used. You can review these logs to monitor integration health.
Document the topology that applies to your site before starting β the network requirements below differ slightly between self-hosted and CSI-hosted models.
External-system prerequisites (CSI side)
| Prerequisite | Owner | Where it is done |
|---|---|---|
| Active CSI Software contract with API access enabled | CSI account representative | CSI customer account |
| API credentials (service account) provisioned for Zenoti | CSI account representative | CSI admin portal |
| CSI-side member field schema confirmed (which fields exist and which are required) | Club's CSI administrator | CSI admin portal |
| If self-hosted: the CSI bridge or connector installed and reachable from the internet | Club IT (with CSI guidance) | Club network |
If your CSI installation is self-hosted and you do not have a point of contact for the CSI bridge, open a ticket with CSI Support first; Zenoti cannot provision CSI-side infrastructure on your behalf.
Network requirements
| Direction | Protocol / port | Purpose | Who whitelists |
|---|---|---|---|
| Outbound from Zenoti to CSI API | HTTPS (port 443) | Sync requests from Zenoti | Managed by Zenoti |
| Outbound from CSI bridge (if self-hosted) to Zenoti | HTTPS (port 443) | Event or change notifications, if configured | Club IT team, per CSI guidance |
Plain HTTP is not supported. If CSI is self-hosted, work with your CSI contact and club IT to confirm both directions of traffic are allowed.
Connect CSI Software
Note: CSI is a center-to-center integration. Its accordion appears only at center scope β select the center in the scope selector first; at organization scope the Integration Settings page does not list it.
At center scope, navigate to Configuration > Integrations > Integration Settings. The CSI accordion is the first on the page and opens expanded.
Turn on Enable CSI. If Zenoti reports
Please turn off auto guest code generation to enable CSI., turn off automatic guest code generation for the center first and try again.Enter the connection details. Every value comes from your CSI Software account representative or club IT; Zenoti supplies no defaults.
Field Source Notes Club Name CSI account representative The club as it is known in CSI. Consumer Name, Consumer Password CSI account representative The service-account credential CSI issued for this club. Rotate on staff changes. Api Service URL CSI account representative / club IT The URL where CSI exposes its API. Do not reuse a URL from another CSI-integrated product. Data Sync Service URL CSI account representative / club IT The URL of the CSI data-sync service used for member synchronization. Site Id CSI account representative Identifies which CSI-managed club (site) corresponds to this Zenoti center. Sync System CSI account representative The CSI system the member sync runs against. Tips Csi Item Code, Ssg Csi Item Code, Tax Csi Item Code Club finance team The CSI item codes Zenoti posts tips, service charges, and tax against. Tips Pay Code, Tips Pay Code Description Club finance team The CSI pay code (and its description) used for tips. Select Save at the bottom of the page.
Member sync runs on Zenoti's scheduler for every center whose CSI integration is active; there is no direction switch or manual sync control on the accordion (see Sync direction). Repeat the steps for each center that CSI manages.
How member fields are mapped
The mapping between CSI member records and Zenoti guest profiles is fixed by the integration; there is nothing to configure on the accordion. When a member arrives from CSI, Zenoti creates or updates the guest profile with the member's identity and contact details, keeps the CSI member reference on the record, and records the sync result for that guest. For a main member Zenoti also creates the membership invoice; for a dependent member it links the record to the main member.
Before the first sync, review a sample of members in CSI for incomplete or duplicated contact details. Mis-keyed data is easier to correct in CSI before it is synced than to merge in Zenoti afterwards.
How membership types are matched
When a main member is created from CSI, Zenoti retrieves the member's CSI membership type and resolves it to a Zenoti membership so that the membership invoice can be created. The resolution is performed by the integration during the sync; there is no mapping grid on the accordion.
Note: If members sync but their membership invoices are not created, confirm with your CSI account representative that the membership type is active in CSI and that the service account can read membership types, and make sure a Zenoti membership exists for each CSI membership type your club sells.
Worked example: A club sells three CSI membership types: "Gold Annual", "Silver Monthly", and "Family Plan", and has matching Zenoti memberships. When a new Gold Annual member syncs from CSI, Zenoti creates the guest profile and a membership invoice for the matching Zenoti membership.
Run the initial sync
- After configuring field mapping and membership type mapping, run a full member sync to import existing CSI members into Zenoti.
- The sync identifies all members in CSI and creates or updates corresponding guest profiles in Zenoti.
- For each guest, Zenoti records whether the sync succeeded or failed.
- Review the sync log after the initial run to confirm member counts match expectations.
Run the initial full sync outside business hours to avoid performance impact on both systems.
Sync direction
The sync is bidirectional and is not configurable per direction.
| Direction | What moves | When |
|---|---|---|
| CSI β Zenoti | Members are created or updated as Zenoti guest profiles; main members receive a membership invoice, dependents are linked to their main member. | Every scheduled run for a center whose CSI integration is active. |
| Zenoti β CSI | Guest profiles modified in Zenoti since the last run are pushed to CSI. | The same scheduled run. |
Treat CSI as the system of record for membership data and Zenoti as the system of record for what happens at the center; changing the same member's contact details on both sides between two runs is the usual cause of an unexpected overwrite.
Migrate stored accounts between processors
If your organization changes payment processors, you can migrate stored accounts (tokenized card data) from the source processor to the target processor without requiring guests to re-enter their card details.
Important: Card migration is a batch operation. Review migration results carefully before deactivating the source processor. Stored accounts that fail migration must be re-collected from guests.
Before you begin a card migration
- Confirm both the source and target processors are configured and active in Zenoti.
- Confirm that stored accounts exist on the source processor for the center or organization you are migrating.
- Schedule the migration outside business hours to minimize impact on recurring membership collections.
Steps
The card migration console (Card migration under Process payments) is available only in a Zenoti support session; it does not appear for a customer login. Zenoti Support runs the migration with you.
- Contact Zenoti Support with the source processor, the target processor, and the scope (the organization or specific centers), and agree a low-activity window.
- Support creates the migration batch (New Card Migration) and starts it (Start Migration). Each stored account is re-tokenized with the target processor.
- Support monitors the batch through Migration Reports and shares how many stored accounts were processed, succeeded, or failed.
- After the batch completes, review the results Support provides to identify stored accounts that could not be re-tokenized with the target processor.
- For failed stored accounts, contact the affected guests to collect updated card details.
See Card migration for the batch statuses and follow-up steps.
Note: Card migration re-tokenizes stored accounts with the new processor. The guest's card number, expiry, and card network are preserved where the target processor supports the same card networks. Cards that the target processor does not support cannot be migrated and will appear as failures in the migration results.
Handle CSI sync failures
| Failure mode | User-visible symptom | Resolution |
|---|---|---|
| CSI API unreachable | Sync attempt reports Failed β endpoint unreachable. | Confirm outbound HTTPS from Zenoti to the CSI endpoint is allowed; for self-hosted CSI, confirm the bridge is running. Retry after CSI confirms availability. |
| Authentication error | Sync attempt reports Unauthorized. | Regenerate the CSI API credentials and update them in Zenoti's CSI integration page. |
| Field mapping error | Individual member records fail with Invalid field value. | Review the field mapping; confirm the CSI field type matches the Zenoti field type. |
| Duplicate member matching fails | New member appears twice in Zenoti. | Merge duplicates in Zenoti and adjust the unique-match key used for upsert. |
| CSI member already closed | Update fails with Inactive member. | Reactivate the member in CSI if appropriate, or mark the guest inactive in Zenoti. |
| Rate limit hit | Batch sync pauses with a rate-limit warning. | Reduce batch size, or schedule the sync outside business hours. |
| Membership type not mapped | Member imports without a membership invoice. | Add the missing CSI membership type to the membership type mapping and re-run the sync for affected members. |
Reconciliation
| Source | Report / view | Match key | Cadence |
|---|---|---|---|
| Zenoti | Guest export filtered to CSI-sourced guests | CSI Member ID (custom field) | Monthly for member counts; weekly if operationally active |
| CSI | Active member export from the CSI admin portal | CSI Member ID | Matches Zenoti cadence |
The match key is the CSI Member ID stored as a custom field on the Zenoti guest. Investigate members present on one side but missing on the other β these usually indicate failed upserts or manual deletions that bypassed the sync.
The sync log records success and failure counts for each run. Review the log regularly to identify patterns in failures before they accumulate.
Tips
- Run the initial full sync outside business hours to avoid performance impact on both sides.
- Review the field mapping carefully before running the first sync β mis-mapped data is expensive to reverse.
- If a member exists in both systems with conflicting data, decide which system is authoritative before switching to bidirectional sync.
- CSI and Zenoti use different identifiers for centers and clubs; confirm the club/site identifier maps to exactly one Zenoti center before going live.
- Complete the membership type mapping before the initial sync so that main members receive the correct membership invoice automatically.
- Rotate CSI API credentials whenever a staff member with access to those credentials leaves your organization.
- When migrating stored accounts between processors, always run the migration in a test batch for a small subset of guests before processing the full organization.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
| Sync runs but no members appear in Zenoti | The CSI processor is not active for the center, or the club/site identifier is incorrect. | Confirm the integration is active for the center and that the club/site identifier matches exactly what CSI has on file. Contact Zenoti Support if the setting is not visible. |
| Main members import but dependent members are missing | Dependent members are linked to the main member in CSI; if the main member failed to sync, dependents are skipped. | Resolve the main member sync failure first, then re-run the sync. |
| Membership invoices are not created for imported members | The CSI membership type is not mapped to a Zenoti membership. | Add the mapping in the membership type mapping section and re-run the sync for affected members. |
| Outbound sync sends no updates to CSI | The last sync timestamp is not advancing, or no guests have been modified since the last run. | Confirm the sync direction is set to include outbound. Check whether any guest profiles have been updated since the last sync timestamp. |
| Sync log shows repeated failures for the same member | A persistent field mapping conflict or a data validation error in CSI. | Inspect the failure reason in the sync log, correct the underlying data in the authoritative system, and retry. |
| Card migration batch shows failures | The target processor does not support the card network, or the source token has expired. | Review the migration results for failure reasons. Contact affected guests to collect updated card details for failed stored accounts. |