Configure a custom domain for the Webstore
Replace the default Zenoti subdomain (for example, orgname.zenoti.com/webstoreNew) with a branded domain (for example, booking.orgname.com) for your Webstore.
Note: For conceptual background on the Webstore and its configuration layers, see Webstore overview.
Audience: Zenoti administrators who manage Webstore configuration for their organization.
On this page
- Before you begin
- Steps
- Compatibility note: bot-verification challenges
- Tips
- Troubleshooting
- Related articles
Before you begin
- You need configuration access in the Zenoti admin portal.
- You must own the domain you want to use and have access to its DNS management console.
- Decide whether to use automatic SSL certificate provisioning (via Let's Encrypt) or to upload your own SSL certificate in PEM format.
Steps
Follow the steps below to register a custom domain, verify DNS ownership, and configure SSL certificates for your Webstore.
Register a custom domain
- Navigate to Configuration > Online booking > Custom domains.
- Select Add New Domain.
- In the Domain and User Details step, complete the following fields:
- Custom Domain Name β Enter your branded domain (for example,
booking.yourbrand.com). - User Email Address β Enter the email address of the point of contact for this domain.
- Custom Domain Name β Enter your branded domain (for example,
- Select Save and Continue.
Verify DNS ownership
Before the custom domain can be activated, you must verify ownership by creating DNS records.
- After registering the domain, the system displays the required DNS records:
- A CNAME record pointing your custom domain to the Zenoti Webstore.
- A TXT record for domain ownership verification.
- In your domain's DNS management console, create both records with the values shown.
- Return to Configuration > Online booking > Custom domains, locate the domain in the Custom Domains Added list, and select Verify to trigger an immediate DNS verification check rather than waiting for the next automatic poll. This is useful for time-sensitive launches.
Note: DNS propagation can take up to 48 hours depending on your DNS provider. Refer to your DNS provider's documentation for instructions on creating CNAME and TXT records.
Cloudflare users: If your domain is managed by Cloudflare, the CNAME record for your Webstore subdomain MUST be set to DNS only (grey-cloud icon) β not Proxied (orange-cloud). Cloudflare's proxy intercepts SSL handshakes and prevents Let's Encrypt from issuing the Webstore's certificate. Setting the proxy to "Proxied" is the most common cause of SSL Renewal Failed status when Cloudflare sits in front of the tenant's main domain.
SSL certificate provisioning
In the Choose type of SSL Management step, select one of the following options:
Automated SSL Management (Recommended)
After DNS verification, the system automatically provisions an SSL certificate via Let's Encrypt. The certificate renews automatically before expiration. No further action is required after selecting this option.
Manual SSL Management
If your organization manages its own certificates:
- Select Manual SSL Management.
- In the Add DNS Records step, upload the following files in PEM format:
- SSL Certificate β The SSL certificate file.
- Private Key β The certificate's private key.
- Certificate Chain β The intermediate certificate chain.
- Select Save.
Worked example: An organization using an enterprise certificate authority uploads three PEM files:
booking-yourbrand-com.crt(SSL Certificate),booking-yourbrand-com.key(Private Key), andintermediate-chain.pem(Certificate Chain). After selecting Save, the domain status moves to Uploaded and then to Active once the system validates the certificate.
Certificate status lifecycle
The domain moves through the following statuses from registration to activation. The current status for each domain appears in the Certificate Status column of the Custom Domains Added list.
| Status | Description | Required action |
|---|---|---|
| Pending Verification | DNS records have not been verified yet. | Wait for DNS propagation, then select Verify. SSL provisioning typically completes 15β30 minutes after successful verification. |
| Created | Domain is registered; awaiting certificate provisioning. | None β the system provisions the certificate automatically. |
| Uploaded | Manual certificate has been uploaded; awaiting activation. | Wait for activation. |
| Active | Domain is live with a valid SSL certificate. | None. |
| Renewing | Automated SSL renewal is in progress. | None β automatic renewal is handled by the system. |
| Expired | The SSL certificate or domain registration has expired. | Renew the domain or replace the SSL certificate. The Webstore is not accessible via the custom domain while expired. |
| SSL Renewal Failed | Automated SSL renewal failed. | Check that DNS records still point correctly and that Cloudflare proxy is set to DNS-only. After correcting, select Verify and trigger renewal. The Webstore is inaccessible via the custom domain while in this state. |
| Verification Failed | DNS records did not match the expected values. | Re-check the DNS records (CNAME and TXT) against the values shown in the admin, correct any typos, and select Verify. |
SSL provisioning timeline
SSL certificate provisioning typically completes within 15β30 minutes after successful DNS verification. If the status remains Pending Verification after 30 minutes, proceed to the troubleshooting section below.
Manage an existing domain
The Custom Domains Added list displays all registered domains with the following columns: Domain Name, Point of Contact, SSL Management, Certificate Status, and Expires On. Available row actions depend on the domain's current status:
- Verify β Trigger an immediate DNS verification check. Available when the domain is pending verification.
- Edit β Upload a new SSL certificate for an existing custom domain. Available after the domain has been verified.
- Delete β Remove the domain and mark it as void. This action cannot be undone.
- Deferred verification β If DNS verification is not complete, you can request a 1-week extension.
Important: Deleting a custom domain removes it from the system and marks it as void. Guests who navigate to the custom domain URL will no longer reach your Webstore. Perform this action only when you intend to permanently retire the domain.
Compatibility note: bot-verification challenges
Important: When your Webstore is served from a custom or masked domain, bot-verification challenges are incompatible with several guest-facing flows. The following flows fail domain validation when a challenge is active on a custom domain:
- Guest registration (sign up)
- Pre-assessment forms
- Feedback and confirmation links
- Guest sign-in
Because the challenge applies at the domain level, all guests are affected simultaneously β this presents as a total Webstore outage rather than an isolated guest issue. If you observe these symptoms after activating a custom domain, disable the bot-verification challenge for that domain to restore access.
Tips
- Test DNS records before going live. Use a DNS lookup tool (such as your DNS provider's built-in checker or a public DNS lookup service) to confirm that your CNAME and TXT records have propagated before selecting Verify in the admin. This avoids unnecessary failed verification attempts.
- Use automated SSL management when possible. Let's Encrypt certificates renew automatically, reducing the operational overhead of tracking certificate expiry dates. Reserve manual certificate upload for organizations with specific compliance or certificate authority requirements.
- Request a deferred verification extension early. If your DNS team needs more than the standard verification window, request the 1-week extension as soon as you register the domain β do not wait until the deadline. Navigate to Configuration > Online booking > Custom domains, locate the domain, and select the option to defer verification.
- Keep DNS records in place after activation. Removing the CNAME or TXT records after the domain is Active can cause SSL renewal to fail at the next renewal cycle. Leave both records in place permanently.
- Communicate the domain change to guests. After the custom domain is Active, update any marketing materials, email templates, and booking links that reference the old Zenoti subdomain. Changes to the Webstore configuration may take up to 30 minutes to propagate due to cache invalidation.
Troubleshooting
| Problem | Likely cause | Resolution |
|---|---|---|
| Status remains Pending Verification after 30 minutes | DNS records have not propagated, or the records contain a typo. | Verify the CNAME and TXT record values in your DNS console match exactly what is shown in Configuration > Online booking > Custom domains. DNS propagation can take up to 48 hours. Select Verify again once records are confirmed correct. |
| Verification Failed status after selecting Verify | CNAME or TXT record values are incorrect or missing. | Re-enter the DNS records using the exact values displayed in the admin. Check for trailing spaces, incorrect subdomains, or missing record types. After correcting, select Verify. |
| SSL Renewal Failed status | Cloudflare proxy is set to Proxied instead of DNS only, or DNS records were removed after initial activation. | Set the Cloudflare CNAME record to DNS only (grey-cloud). Confirm both CNAME and TXT records are still present. Select Verify to trigger a new renewal attempt. |
| Custom domain shows a certificate error in the browser | Manual certificate upload used an incorrect file or the certificate has expired. | Navigate to Configuration > Online booking > Custom domains, select Edit for the domain, and upload a valid PEM-format SSL Certificate, Private Key, and Certificate Chain. |
| Guests reach the old Zenoti subdomain after the custom domain is Active | Cached DNS responses or outdated bookmarks. | Advise guests to clear their browser cache or try an incognito window. DNS caching at the ISP level can persist for up to the TTL set on the old records. No admin action is required β this resolves automatically as caches expire. |
| Guest registration, sign-in, feedback links, or pre-assessment forms fail for all guests at once | A bot-verification challenge is active on the custom domain. | Disable the bot-verification challenge for the custom domain. See Compatibility note: bot-verification challenges above. |