I get asked about the age gate at least once a month. A winery is rebuilding their site. The agency mentions, sometime in week two, "we'll need to put an age verification gate up." The winery owner pushes back: "every site I visit with one of those, I bounce off immediately."

They're both right. Full-screen modal age gates are conversion killers. They also exist for legitimate legal reasons. The trick is implementing the right kind, in the right place, at the right moment — and a startling number of Australian winery websites get this wrong in both directions. Some have aggressive gates that destroy mobile conversion; others have nothing at all and are sitting on legal exposure they don't know about.

Here's the honest opinion: a full-screen age gate on the homepage is the wrong answer in 95% of cases. So is no age verification at all. The right answer is a tiered approach that checks age where the legal requirement actually attaches — at purchase, at delivery — not at the moment of arrival.

What the law actually requires

Let me start with what the law says, because most of the panic on this topic comes from misunderstanding the regulation.

Australian liquor law is state-based. The relevant acts:

Victoria: Liquor Control Reform Act 1998, administered by the Victorian Liquor Commission.
NSW: Liquor Act 2007, administered by Liquor & Gaming NSW.
South Australia: Liquor Licensing Act 1997.
Western Australia: Liquor Control Act 1988.
Queensland: Liquor Act 1992.

Each requires that liquor sales are not made to anyone under 18. The shared regulatory expectations across states for online wine sales:

The seller must hold an appropriate licence (typically a packaged liquor licence or a producer's licence).
The site must not market alcohol to minors.
Age must be verified at the point of sale.
Identification must be checked at delivery, by the delivery driver, before the goods are handed over.
Delivery to obviously intoxicated or underage persons must be refused.

What the law does not require: a homepage age gate that blocks all visitors from entering the site. The legal verification attaches at purchase and delivery, not at arrival. Many of the most aggressive winery age gates exist not because the law requires them but because the agency that built the site copied the pattern from a US alcohol brand (where state-level marketing rules are stricter) or from a spirits brand (where industry voluntary codes are tighter than wine).

The case for the homepage age gate

I want to give the homepage gate a fair hearing because it's not entirely irrational.

The argument for it: alcohol marketing should not target minors. A user-facing splash that asks "Are you over 18?" creates a clear record that the visitor self-declared age before viewing alcohol content. If a regulator or a parent ever raises a concern, the gate is evidence of a good-faith attempt at compliance.

The Alcohol Beverages Advertising Code (ABAC) — the industry self-regulatory framework most Australian wineries voluntarily commit to — does explicitly recommend that "websites that promote alcohol beverages should take reasonable steps to ensure they are not targeted at or appealing to minors." A reasonable step is interpretable, but a visible age gate is one reasonable step.

For wineries selling spirits in addition to wine, where the marketing rules are tighter, the gate has stronger justification. For wineries whose audience overlaps with younger demographics (RTD products, some craft segments), the gate is more defensible.

That's the case for. It's narrow. For most boutique wineries selling table wine to an over-30 audience, the homepage gate creates compliance theatre without commensurate legal protection — and costs significant conversion.

The cost of the wrong gate

Real numbers from the industry. Full-screen blocking age gates that interrupt the homepage before the user has seen the brand:

Increase bounce rate by up to 63% on mobile.
Reduce return-visit rates by ~25% (users associate the site with friction).
Disproportionately affect new visitors who haven't yet decided whether the site is worth their time.
Are often clicked through dishonestly (a 12-year-old clicks "Yes I'm 18" — the gate provides effectively zero protection beyond legal paperwork).

For a winery doing 50,000 monthly visits, a 30% increase in bounce rate translates to roughly 15,000 lost sessions per month — and, at typical conversion rates, around 30–60 lost e-commerce orders and a similar number of lost cellar door bookings. Annualised: $80,000–$200,000 in revenue impact, depending on AOV.

This is the cost of doing the wrong kind of age check at the wrong moment.

The right approach: tiered verification

The defensible legal and conversion-friendly approach is to tier verification based on the user's actual action.

Tier 1: The homepage — no gate

The user lands on the homepage. They see the brand, the wines, the cellar door, the story. No interruption. The site is doing its job of warming the user up.

The site footer carries the standard disclaimers: "Wine is for adults of legal drinking age. Please drink responsibly." Plus a link to DrinkWise Australia, the industry's responsible drinking body. These are passive responsible-drinking signals that ABAC and state regulators recognise.

Tier 2: Browsing the shop — soft check at first product

When the user navigates to the shop or first product page, a small inline banner or modal appears: "To browse our wines, please confirm you're over 18." Single button. One click. The check is recorded as a cookie so the user doesn't see it on subsequent visits within 30 days.

This is the moment where the user has indicated they want to engage with alcohol content. The check is contextual and minimal.

Tier 3: Adding to cart — formal age declaration

At the checkout step, before payment, a clear declaration: "I confirm I am over 18 years of age, and the recipient of this delivery is also over 18." Checkbox. Required to proceed.

The user provides date of birth at checkout (some platforms require this for tax / shipping reasons anyway). This is the legally meaningful verification.

Tier 4: Delivery — physical verification

The delivery driver checks ID at handover. This is the only verification that actually works in practice — a face-to-face check by a trained person who can refuse delivery. Required by every state liquor act for alcohol delivery.

The shipping label and the delivery instructions are tagged for ID-check. The delivery courier (Australia Post StarTrack, DHL, or specialist wine couriers like Pack & Send or Toll Express) has its own ID-check workflow.

This tiered structure satisfies:

The law: verification happens at purchase and delivery, with explicit declaration and physical ID check.
The ABAC code: "reasonable steps" are taken — the responsible drinking link, the soft check on alcohol content, the formal declaration at purchase.
The conversion funnel: the homepage and brand pages are unimpeded; friction only appears when the user has already engaged with the buying intent.

The technical implementation

If you're rebuilding or auditing your winery site, here's what to actually do at the code level.

Pass-through cookie for return visitors

Once the user has confirmed age at any tier, set a wine_age_confirmed=true cookie with a 30-day expiry. Suppress further age checks until the cookie expires. This eliminates repeated friction for returning customers.

Geolocation logic

If you ship interstate or internationally, the gate logic varies by destination. A NSW customer buying for delivery to Victoria must satisfy Victorian receiving requirements. A US customer might fall under different rules. Modern platforms (Commerce7, Vinsuite, Shopify with Drinks.com Assure) handle this automatically; custom builds need it implemented.

Reasonable mobile-first design

The Tier 2 check on the shop page should not be a full-screen blocker. It should be a 100–150px banner at the top of the viewport, dismissible with a single tap, that updates the state. Full-screen modals on mobile cause the disproportionate bounce loss.

Audit trail

For Tier 3 (the formal declaration), log the timestamp, IP address, and the explicit checkbox event into your customer record. This is the audit trail you'd want if a regulator ever asks how you verified an age claim.

Server-side, not just client-side

The age check at checkout needs to be enforced server-side. A user can disable JavaScript and bypass a client-only check. The form submission to checkout should fail without the age confirmation field set.

Common mistakes I see in audits

When I run a winery site audit, I see the same age-gate failures over and over:

Mistake 1: Aggressive homepage gate on a brand-only site

The winery doesn't even sell wine online. The site exists purely for cellar door bookings and wine club acquisition. There's no e-commerce. And yet a full-screen "Are you over 18?" interrupts the homepage. There's literally nothing on the site to gate. The agency installed it as a checkbox.

Fix: remove it. There's no legal requirement for a brochure site to gate access to brand content. The responsible drinking footer link is sufficient.

Mistake 2: A gate that pops up on every page reload

The cookie isn't being set. The user lands, confirms age, navigates to the wines page, and gets gated again. Then navigates to the cellar door page and gets gated again. Then comes back next week and gets gated again on the homepage they've already entered three times.

Fix: set the cookie properly with a sensible expiry. 30 days is industry standard.

Mistake 3: An age gate but no checkout verification

The homepage has an aggressive gate. The checkout has no age declaration field at all. This is the worst of both worlds — friction at the wrong moment, no protection at the right moment.

Fix: invert. Remove the homepage gate (or soften it). Add proper declaration at checkout.

Mistake 4: No delivery ID-check workflow

The website handles age verification well. But the delivery is shipped via a generic courier with no ID-check flag. The driver leaves the wine at the door if no one's home. This violates the delivery requirements under most state acts — particularly section 119A of the Victorian Liquor Control Reform Act, which requires drivers to refuse delivery if they have reasonable grounds to suspect the recipient is underage.

Fix: use a courier that has an alcohol delivery workflow, tag the parcel as restricted-item, and require ID check at handover.

What the regulator actually cares about

I had a conversation with a compliance lawyer last year who specialises in liquor licensing. The summary of what regulators look at if a complaint is escalated:

Does the site have a valid liquor licence number visible (typically in the footer)?
Does the site take reasonable steps to ensure marketing isn't targeted at minors? (Imagery, language, sponsorships, etc.)
Does the checkout require explicit age declaration?
Is delivery handled by a courier with ID-check capability?
Is there a record of age verification events tied to customer accounts?

Notice what's not on this list: a full-screen homepage age gate. Regulators care about the actual sale moment, not the moment of arrival. Wineries that focus their compliance effort on the splash gate are over-investing in the wrong control.

What to do this week

If you're a winery operator and you don't know whether your current site is in the right configuration, the 30-minute check:

Open your site in an incognito window. Is there a homepage gate? If yes, can you skip it without confirming age? (If you can — you're paying the conversion cost for nothing.)
Navigate to your shop. Is there a softer age check when you start browsing alcohol products?
Add a product to cart. At checkout, is there an explicit "I confirm I'm over 18" declaration?
Is your liquor licence number visible in the site footer?
Is your delivery method ID-check-capable?

If the answer is "no" to 3 or 4, you have a compliance gap regardless of how aggressive your homepage gate is. If the answer is "yes, homepage gate" to 1, you're losing conversion for compliance theatre.

The right answer is no gate at the homepage, a soft check on shop pages, an explicit declaration at checkout, an ID-check delivery method, and a licence number in the footer. That configuration is legally defensible, ABAC-compliant, and stops costing you mobile conversion.

If you want a second opinion on whether your current age verification is in the right place — and what fixing it might be worth in recovered conversion — run a free audit. I'll go through the funnel on mobile, identify the friction points, and send back a written report with the priority fixes.

Wine Website Age Gates: The 63% Bounce Trap (2026)