Zenoti, connected to the rest of your business.

Production Zenoti integrations live across 180+ locations. Booking, retail, inventory, and accounting data flowing in real time through Nexus middleware.

The case for proper Zenoti integration

Zenoti is the dominant platform for multi-site spa, salon, beauty, and wellness businesses in Australia and globally. It does the operational core (booking, POS, staff, services, memberships) better than almost anything else in its category. If your operational core is run on Zenoti, you have made a sound platform choice.

What Zenoti does not do well is be the only system in your stack. The moment you also have a Shopify store for retail, or a Xero account for the books, or a Dear instance for inventory, you have an integration problem. Zenoti has APIs, but they require careful handling. Common shortcuts (CSV exports, nightly batch jobs, manual reconciliation) create exactly the operational pain that running Zenoti was supposed to remove. The platform is doing its job. The integration layer is not.

We have built Zenoti integrations across multi-site beauty, wellness, and dental businesses, including the largest deployment we know of in this market (180+ locations across multiple brands, with full inventory parity, retail commerce, and accounting integration). The patterns repeat. The edge cases repeat. Knowing where the edge cases are before discovery starts is the difference between a clean six-week build and a six-month nightmare.

The honest moment most agencies skip: some Zenoti integrations are better handled by Zenoti’s native integration partners. For straightforward Xero or QuickBooks accounting sync at small scale, the partner ecosystem usually covers it adequately. We will tell you that directly. About one in five Zenoti discoveries we run ends with our recommendation to use a native Zenoti integration rather than building custom middleware. The middleware case starts with multi-brand groups, multi-region rollouts, custom commission structures, retail commerce integration, or any workflow where the off-the-shelf integrations stop being enough.

If your Zenoti rollout has stalled at the integration layer, call 0431 000 062.

Symptoms to look for

You probably need proper Zenoti integration when one or more of the following are true.

• Inventory parity between Zenoti and your retail channel is unreliable. The same product is in stock on Zenoti and out of stock on Shopify, or vice versa. Customers buy what cannot be fulfilled. The customer service team has a standard apology script for it.
• Sales from Zenoti do not flow to accounting cleanly. Daily exports are running, but reconciliation is a manual process at month-end. Tips, gift cards, store credit, and refunds all post in ways the accountant has to manually correct.
• Membership data is trapped in Zenoti. Marketing and reporting need access to customer and membership data that Zenoti holds but does not surface easily. Campaign segmentation requires CSV exports and manual joining.
• Multi-brand or multi-location reporting is impossible. Each brand or location has its own Zenoti centre, and rolling up data across them requires manual work. The CFO asks for group-level revenue and the answer takes three days.
• You have a custom workflow Zenoti does not support natively. A specific commission structure, a specific gift card flow, a specific membership rule, that Zenoti configuration cannot handle but middleware can. The franchise has been waiting six months for the feature request.
• Centre-level reporting works; group-level reporting does not. Each centre manager can see their own numbers in real time. The CEO, the CFO, and the marketing team are all working from a spreadsheet that lags 48 hours behind reality.
• Loyalty or gift card balances do not survive crossing systems. A customer earns loyalty points or buys a gift card at one centre; the balance is invisible at another centre, or invisible online. The customer is told the balance does not exist; the customer is correct that it should.

DIAGNOSTIC

If three or more describe your situation, the integration layer is now the bottleneck on your Zenoti investment. Proper middleware turns Zenoti from an island into a connected platform.

The architecture we deploy

Every Zenoti integration we build on Nexus uses the same pattern. The components are deliberately boring. Boring is the point.

Zenoti API consumption

Nexus reads from Zenoti through the official Zenoti APIs. Centre data, customer data, appointment data, sales data, membership data, and inventory data are pulled at the right cadence: real-time where the APIs support it, polled where they do not. We know which Zenoti endpoints are rate-limited, which ones return partial data on first call, and which ones need polling adjustment for multi-region deployments. That knowledge is the difference between an integration that scales to 180 locations and one that falls over at 30.

Event normalisation

Zenoti data is transformed into clean, normalised events that the rest of your stack can consume. A sale is a sale, regardless of which centre it happened in. A customer is a customer, regardless of which brand they bought from. The normalisation layer is the difference between a stack where each downstream system needs its own custom field mappings, and a stack where the integration logic lives in one place.

Routing to downstream systems

Sales flow to Xero or MYOB in the right form (revenue, GST, tips, gift cards, store credit, all mapped correctly). Inventory adjustments flow to your inventory system. Customer updates flow to your CRM. Each downstream system gets exactly what it needs. The accounting team stops finding tip income posted to revenue accounts. The inventory team stops seeing service consumption recorded as customer purchases.

Bidirectional sync where it matters

For inventory, the sync is bidirectional. Stock movements in Zenoti update the inventory system. Stock receipts in the inventory system update Zenoti. The result is true inventory parity, not approximate parity. Loyalty and gift card balances also flow both ways where the business requires unified balances across centres and online retail.

Full audit trail

Every event from Zenoti, every transformation, every write to a downstream system is logged. When a sale does not appear in Xero, you trace it in the audit log within minutes. When the auditor asks how franchise commission was calculated for a specific transaction in March, you hand them the calculation log. The “phone Zenoti support and wait three days for an answer” pattern disappears.

Three engagement shapes

We structure Zenoti integration engagements one of three ways. All three start with discovery.

• Single integration. From $15,000. Zenoti to one downstream system. Examples: Zenoti to Xero, Zenoti to Shopify inventory. 4 to 6 weeks. Best when one specific integration is the source of most of the pain.
• Full middleware deployment. From $50,000. Zenoti as operational core, Nexus as middleware, multiple downstream systems connected. 8 to 12 weeks. Best for multi-brand or multi-region groups where the integration layer is the bottleneck on the platform investment.
• Run With Us retainer. From $6,500 per month. Ongoing monitoring, continuous additions, security patching, quarterly review. Best for groups whose Zenoti rollout is continuing and who want a team that knows the stack on standby.

Call 0431 000 062 to talk through which fits.

Zenoti integrations we have built

Three Zenoti integration programmes. Two named clients, one confidential at client request. Reference calls available.

WHMA group, 180+ locations

• Problem: Major beauty group running Zenoti across 180+ locations, with Shopify Plus for online retail, and a need for inventory parity across both. Existing CSV-based sync was unreliable. Inventory drift was costing sales and creating customer complaints. Group-level reporting required a four-day month-end process.
• Built: Event-driven middleware on Nexus connecting Zenoti and Shopify Plus. Real-time inventory sync in both directions. Sales unified into a single reporting layer. Customer data joined across both systems. Built over 14 weeks.
• Result: Inventory parity across three systems achieved in production. Online and in-store stock now reflect reality. Booking and retail data join in the same reporting layer for the first time. Operational reporting that previously required manual data joining is now available daily.
• Stack: Zenoti API, Shopify Plus, Nexus middleware, PostgreSQL, AWS Sydney, event sourcing architecture.

WesHealth medical group

• Problem: Multi-site medical and wellness business with Zenoti for booking and POS, Dear for inventory, and a WordPress site for content and intake forms. Three systems, three customer databases, three sources of truth. Patient intake required staff re-keying data, costing roughly 15 minutes per new customer.
• Built: Nexus middleware connecting Zenoti, Dear, and WordPress. Customer records unified across the stack. Inventory sync bidirectional between Zenoti and Dear. Intake forms flowing into Zenoti customer profiles automatically. Built over nine weeks.
• Result: Single customer record across the stack. Inventory variance reduced from weekly to negligible. Intake-to-appointment time reduced from approximately 15 minutes per customer to under 2 minutes. 100% inventory parity between Zenoti and Dear.
• Stack: Zenoti API, Dear Systems API, WordPress REST API, Nexus middleware, PostgreSQL, AWS Sydney.

A multi-brand wellness group, name confidential

• Problem: Group running three brands across two Zenoti centres each, with separate Xero files per brand and a unified marketing platform. Group-level reporting required combining six Zenoti centres, three Xero files, and the marketing database. The CFO had a private spreadsheet that took two days to update each Monday morning.
• Built: Nexus middleware as the unifying reporting layer. Zenoti centres rolled up to brand level, brands rolled up to group level. Xero data joined via API. Marketing platform fed real-time customer segments. Custom commission engine to handle inter-brand referrals.
• Result: CFO’s Monday spreadsheet retired. Group-level reporting now available in real time. Inter-brand referral commission auditable and provable. Marketing campaign performance now measurable across all three brands in one dashboard.
• Stack: Zenoti API (multi-centre), Xero API (multi-file), Nexus middleware, PostgreSQL, AWS Sydney, custom commission engine.

Who you will work with

No account managers, no offshore teams, no juniors learning on your project. The two engineers below scope, build, and ship the work. Both have built Zenoti at scale and know the API edge cases by name. The person who hears your edge cases is the person who handles them in production.

How we ship it

Zenoti integration projects run in three phases. Each phase is fixed scope and fixed price.

For single-brand single-region deployments, total project time is 4 to 8 weeks. Multi-brand or multi-region deployments extend timelines.

Zenoti integration FAQs