Your Zenoti Booking Webstore, Built Into Your Actual Website

The Zenoti booking webstore is Zenoti's customer-facing booking interface. It works, but it lives on a separate page from your main site, which limits brand match and conversion tracking. You can embed Zenoti booking directly on your own domain using a third-party widget like BookerKit.

This page explains what the Zenoti booking webstore is, where the native experience works, where it creates friction for marketing-driven med-spas, and how operators embed Zenoti booking inside their own brand.

What is the Zenoti booking webstore?

The Zenoti booking webstore is the customer-facing side of Zenoti — the interface your customers use to schedule appointments online. It comes included with every Zenoti subscription.

The booking funnel specifically covers:

• Service selection
• Provider selection
• Date and time slot
• Customer information
• Deposit or payment to hold the appointment

The broader Zenoti webstore also handles memberships, packages, gift cards, and loyalty programs. BookerKit does not touch any of those. They stay exactly where they are, managed by Zenoti.

Where the native booking webstore lives: a Zenoti-hosted page, typically on a subdomain or a Zenoti-branded URL — not on your website. That's the gap BookerKit was built to close.

Ready to connect Zenoti to BookerKit? Set up a Zenoti integration.

Where the native Zenoti booking webstore works well

The native Zenoti booking webstore is a working product. For most Zenoti customers it does the job without any additional tooling.

• Zero setup cost. It's included in your Zenoti subscription. No developer time, no third-party configuration.
• Reliable booking sync. Because it is Zenoti, there's no integration layer to break. Bookings land in your calendar immediately.
• Zero maintenance. Zenoti owns upgrades. When Zenoti releases new features, they show up automatically.

If you run a single location with straightforward booking needs and marketing is not a core growth lever, the native webstore is the right default.

What marketing-driven med-spas want on top of the native booking funnel

For multi-location operators running paid ads or investing in SEO, a few things sit outside what the native Zenoti booking webstore is designed to do.

Brand discontinuity. When a customer clicks "Book Now" on your site, they leave your domain and land on a Zenoti-hosted page. They see Zenoti's interface, not yours. That handoff adds a step between your site and the booking, which can dilute the brand continuity you spent money to build.

Brand controls scoped to the hosted page. You can add a logo and adjust colors. Matching your site's full design system — fonts, spacing, CTA language — isn't part of that setup.

Conversion-tracking gaps. Wiring clean, end-to-end attribution across a domain handoff is harder. You can do it, but it requires additional configuration to follow a customer from your ad click through to a confirmed booking on a separate domain.

No abandoned-booking signal at step one. If a customer opens the booking flow, enters their name and email, and then drops off — you need that signal to re-engage them. The native webstore isn't built to emit that partial-funnel signal into your CRM or ad platforms.

The buyer mental model — three operator profiles

Not every Zenoti customer needs a third-party booking funnel. Here's the honest breakdown.

Solo operator, one location, no marketing team. The native Zenoti booking webstore is fine. You won't use what BookerKit adds. Stick with what you have.

Multi-location operator with in-house marketing. The domain handoff is where the friction shows up. Your marketing team is running Google and Meta campaigns that drive customers to your site — and then those customers leave your domain to book. Brand match and per-step attribution matter here. This is where BookerKit fits.

Enterprise or agency-managed operator with engineering resources. Build versus buy is a real question. BookerKit removes the maintenance burden and gets you live in 5 minutes. A custom Zenoti API build gives total control but requires ongoing engineering. Neither answer is wrong — see the full build / buy / default decision guide for the comparison.

A drop-in alternative for the booking funnel

BookerKit replaces the customer-facing booking funnel — the four-step flow from service selection through deposit payment — while Zenoti continues to run everything else.

Three embed methods — iframe, button trigger, or custom element — let you place the widget anywhere on your site. The widget is white-label: customers see your brand, your colors, your domain.

See exactly how each method works.

Conversion tracking, briefly

BookerKit captures attribution at every step of the booking funnel. The booking_started webhook fires when a customer completes step one (personal information) — giving you an abandoned-booking signal before they've confirmed.

Per-step webhooks fire as customers move through the funnel, signed with HMAC-SHA256. Every step also pushes a dataLayer event so your marketing team gets clean attribution in GTM, Google Ads, Facebook Pixel, and GA4 — without any custom tagging.

For the full payload reference: webhook payload reference and full event list.

What you keep, what you replace

To be direct about scope:

You keep: Zenoti as your operations system of record — services, providers, calendar, payments, customer history, reporting. You also keep the rest of the Zenoti webstore: memberships, packages, gift card purchases, and loyalty programs all stay in Zenoti.

You replace: Only the customer-facing booking funnel. Bookings still flow into Zenoti automatically. Your staff works in Zenoti exactly as they do today.

BookerKit is not a Zenoti replacement. It's a front-end layer over the Zenoti booking API that puts the funnel on your domain instead of Zenoti's.

Setup time and pricing

FAQ

Does BookerKit replace Zenoti?

No. Zenoti remains your full operating system. BookerKit replaces only the customer-facing booking funnel — bookings still sync into Zenoti automatically.

Does BookerKit replace the entire Zenoti webstore?

No. BookerKit covers the booking funnel only: service selection, provider selection, date and time, and deposit. Memberships, packages, gift cards, and loyalty programs stay in Zenoti's webstore.

Will my customers know they're using a third-party tool?

No. The widget is white-label and loads on your domain. Customers see your brand throughout the entire booking flow.

Can I run BookerKit across multiple locations?

Yes. Multi-location support is included in Starter, Growth, and Enterprise. Starter and Growth are priced per location; Enterprise offers volume pricing.