The architecture problem most Australian boutique wineries don't see is sitting in plain view on their own website. The cellar door booking goes through one platform — usually Bookable, Now Book It, or a custom form. The wine club lives on a second platform — usually a subscription tool tacked into WooCommerce or a standalone solution. The e-commerce shop is on a third — Shopify or WooCommerce. The cellar door POS is a fourth — Lightspeed or Square. None of them talk to each other.

The result is a winery that doesn't know its own customer. Sarah books a cellar door tasting via the website. She tastes, joins the club at the door (paper form, transcribed Monday), and buys two bottles on the way out (rung through the POS). Two months later she logs into the e-commerce site to reorder a bottle she liked. The site doesn't know who she is. There's no record she's a club member. There's no record she visited.

That fragmentation is the single biggest unforced error in Australian winery websites. The fix isn't more software. It's the right architecture.

Why this happens

Three forces pushed the industry into the fragmented stack:

Each function got built separately, by different vendors, at different times. The cellar door booking was added in 2019 when the maker decided to charge for tastings. The wine club had existed since 2012 and was on a spreadsheet, then a basic e-commerce tool, then upgraded to Vinsuite or Commerce7 in 2022. The shop was on WooCommerce because the agency knew WordPress. None of them were designed to integrate.
The Australian wine industry's tech vendors are smaller than the US/EU equivalents. Commerce7 and Vinsuite — both Canadian — have built integrated DTC platforms for wineries that handle club + e-commerce + cellar door + POS as one system. They're better than anything Australian-grown. But they're not commonly deployed in Australia because few agencies sell them, and the Australian winery market has historically built on cheaper componentry.
The cellar door manager and the e-commerce manager (often the same person, often part-time) are different mental modes. Cellar door is hospitality. E-commerce is retail. Wine club is membership. The same person manages all three but switches between three different software interfaces depending on which hat they're wearing. The integration debt accumulates because no single person is incentivised to fix it.

The case against full integration

Let me give the fragmented stack its fair hearing because there's a real argument for it.

If you're a winery doing under $400k in DTC, the integrated platform investment ($800–$2,000/month for Commerce7 or Vinsuite plus $20,000+ for the website rebuild) may not pencil. The fragmented stack at $30–80/month per platform is cheaper. The customer-knowledge problem is real but you can paper over it with manual cross-referencing once a quarter.

If you're a winery whose cellar door is the primary channel and you only sell direct online incidentally, the e-commerce site can be a brochure with a buy button and that's fine. Don't overbuild.

If your club is small (under 200 members) and growth isn't a strategic priority, the standalone club tool works. Migration costs to consolidate may exceed the benefit.

The integration thesis only really pays off at $500k+ DTC and 500+ club members. Below that, the fragmented stack is rational. Above that, it's costing you customer knowledge faster than you realise.

The three workflows that need to talk to each other

If you're going to integrate, here's where the integration matters most. The cross-flow between these is where the revenue lives.

Flow 1: Cellar door visitor becomes club member becomes online customer

The journey: Sarah books a cellar door tasting online for a Saturday in March. She arrives, tastes, loves the Pinot, joins the club on the spot, buys six bottles for the cellar. Three months later her quarterly club case ships. Six months later she logs into the e-commerce site to buy two more bottles of the Pinot because she's running out.

In the fragmented stack, every step of that journey is a separate database. The cellar door booking is in one system. The club join is in another. The bottle purchase is on the POS. The reorder is on the e-commerce shop. Sarah is four different customer IDs across four systems.

In the integrated stack, Sarah is one customer. Her booking creates the record. Her club join adds membership status. Her POS purchase appends to her order history. Her e-commerce purchase recognises her as a club member and applies club pricing automatically. By the time she's ordered three times, you know what she likes, what she's bought, when she last visited, and what to suggest next.

Flow 2: Club shipment customisation

A wine club shipment that goes out as "two bottles of Pinot, one Chardonnay, one rosé" to every member is the old model. The new model is partial customisation — members can swap one or two bottles per shipment, opt out of varietals they don't drink (no whites, no rosé), and add bonus bottles at member pricing.

In the fragmented stack, customisation is either impossible or requires the club manager to email each member individually. In an integrated platform, members log into their account, see their upcoming shipment, swap or add, and the system processes the order. The club manager's quarterly admin time drops from 40 hours to 4.

This isn't theoretical. Every US winery using Commerce7 or WineDirect does this as default. Australian wineries doing it on Vinsuite or Commerce7 run materially higher per-member revenue than their fragmented-stack peers because members buy more when they can shape their own shipment.

Flow 3: The post-visit reactivation

Sarah visited the cellar door six months ago. She bought $180 in wine, didn't join the club, hasn't been back. In the fragmented stack, she's invisible — there's no follow-up sequence because the cellar door booking system doesn't know what she bought, the POS doesn't know who she is beyond a credit card, and there's no email integration.

In the integrated stack, Sarah gets a thank-you email 24 hours after her visit. A reactivation email two months later: "You tried the Shiraz when you visited — the new vintage just dropped, here's first access." A six-month nudge: "It's been six months since you joined us. Come back for a private tasting at member rates." Many members of the club joined this way: a cellar door visitor warmed over four months by relevant, contextual email that knew what they'd already tasted.

This is the difference between a database of customers and a list of past transactions. The first compounds. The second decays.

What stack actually works

If I'm advising an Australian winery doing $500k–$5m DTC and ready to consolidate, here's the stack I'd recommend in 2026.

The integrated platform: Commerce7 or Vinsuite

For mid-tier and above, the choice is between these two. They handle e-commerce + wine club + cellar door bookings + customer database + email integration as one platform. Commerce7 is more design-flexible but pricier ($800–$2,400/month depending on features and order volume). Vinsuite is slightly cheaper and more opinionated about workflow ($400–$1,200/month).

Both integrate with vintrace for production data, Lightspeed for in-cellar-door POS, and Klaviyo or Mailchimp for email. Both handle WET reporting via export to Xero or MYOB.

For a smaller winery (under $500k DTC), Shopify with Winehub for the club layer is the lower-cost integrated alternative. Cheaper, less wine-specific, but workable.

The custom front-end

The Commerce7 / Vinsuite default storefront templates are functional but generic. The wineries with the strongest brand presence consume the integrated platform via API and build a custom front-end on top.

That's where a build like ours fits in. Next.js or Astro on the front, Commerce7 or Vinsuite on the back. The maker's voice shows through the design. The integrated data flows underneath. The customer sees a beautifully-branded winery site; the back office sees a unified customer database.

This is the architecture I shipped late last year for a McLaren Vale winery. The Commerce7 instance handles 1,800 club members, 30,000 e-commerce orders/year, and 12,000 cellar door bookings. The Next.js front-end carries the brand. The two are stitched together via API. The customer experience is continuous from cellar door to club to e-commerce; the back office reporting is unified.

The cellar door booking

If you're on Commerce7, use Commerce7's native booking module — it's good. If you're on Vinsuite, the native booking module is decent but slightly less polished. If you're staying on Shopify or WooCommerce, Bookable is the Australian default.

The crucial integration point: the cellar door booking must create a customer record that ties to the same customer database as the e-commerce orders. Otherwise the fragmentation persists even within an "integrated" platform.

The POS

Lightspeed Wine is the Australian default and integrates well with Commerce7. The transactions at the cellar door immediately update the customer record online. Sarah's $180 in-person purchase shows up in her account when she logs into the website that evening.

Email and post-visit sequences

Klaviyo is the strongest choice for winery email. It integrates natively with Commerce7 and Vinsuite. The sequences write themselves once the data flows are right: post-visit follow-up, club shipment notifications, reactivation, win-back, vintage release pre-launch to members. Each can be automated, segmented by past purchase, and personalised.

The unsexy truth is that Klaviyo will drive 20–35% of total DTC revenue at a properly-built winery. The website builds the database. Klaviyo monetises it.

The maths on integration

Real numbers for an Australian winery doing $2m DTC, currently fragmented:

Club retention: 60% annual (industry typical for fragmented stacks). On 800 members at $480/year average, that's $230k lost retention annually.
After integration with customisation: club retention 78–85%. Lost retention drops to $80–110k. Recovered annual revenue: $120k–$150k.
Post-visit conversion to club: 5% in fragmented stack (no follow-up). 12–18% in integrated stack with sequence. On 8,000 visitors/year, that's an additional 560–1,040 new members at $480 ARPU. New annual revenue: $270k–$500k.
E-commerce order frequency: 1.4 orders/year/customer fragmented. 2.1 in integrated stack with personalisation. On 6,000 customers, additional $250k in repeat orders.

Total annual incremental revenue from integration: $640k–$900k.

Cost of integration: $25k–$60k for the website build, $400–$2,400/month for the platform, plus ongoing maintenance.

Payback: usually inside year one. Sometimes inside six months.

What to do this quarter

If you're a winery currently running a fragmented stack and the maths above feel like they apply, the order:

Audit the current systems. Where does each customer record live? How many separate databases? What's the data flow (or lack of)?
Decide on the integrated platform. Commerce7 vs Vinsuite vs Shopify+Winehub. The decision is mostly about budget and how custom the brand needs to feel.
Plan migration of existing customers, club members, and order history. The data import is non-trivial. Budget 4–8 weeks.
Build the custom front-end or use the platform default. Custom for the brand-driven wineries. Default for the workflow-driven ones.
Build the email automation sequences in Klaviyo. This is where the post-launch revenue comes from.
Train the cellar door team on the new system. The change management piece is often underestimated.

The whole project — discovery, migration, build, launch — typically runs 4–6 months for a mid-tier Australian winery.

The bottom line

A winery website that treats the cellar door booking, the wine club, and the e-commerce shop as three separate features is leaving real money on the table — not because each individual feature is broken, but because the customer is invisible across them. Integration turns four databases into one customer profile that compounds value over years.

A useful first data point: run a free audit on your current site. The report shows you mobile and desktop performance on the cellar door booking page, the wine club page, and the shop — three URLs that should be hitting the same customer. If they're each slow and disconnected in different ways, you'll see it. The audit doesn't tell you whether your databases talk to each other. It tells you what your customer experiences when they try to use all three.

Why Wineries Need a 4-in-1 Site: Cellar, Club, Shop (2026)