Winery Tasting & Club Event Booking

The vertical decides the vocabulary, the questions asked at checkout, the inventory model, the door, the payout terms and the theme. This page says "seat" and "tasting" because that is what a winery says; a config whose primary call to action is generic ticketing wording fails validation rather than shipping.

Who this is not for. Excludes wholesale and DTC bottle shipping, which is separately regulated. If that is closer to your operation, the vertical you want is probably a different one — all twenty are listed here.

Saturday afternoon is a queue at the bar and a room capacity somebody is guessing at

Walk-ins do not arrive evenly. Two o'clock is a queue at the counter and a table of eight who did not say they were coming, four o'clock is three staff and an empty room, and the number of people the licence lets you seat is held in the head of whoever is on that afternoon. The cost is paid twice: the couple turned away at the busiest hour never come back, and the pourers standing about at four were paid for anyway. A booking form that sells "a tasting" with no time on it does not help — it sells the whole day into the same two hours.

What bindro does: The day is inventory rather than an opening period. Each arrival slot carries its own stock of seats per flight, and the counts move only under a row lock inside the transaction that confirms the booking, with a database constraint behind it, so two couples cannot take the last seat at three o'clock in the same second. A slot that fills stops selling by itself and says "Fully booked" in this trade's own words rather than showing a generic sold-out badge, and the remaining count per slot is live on the day-of screen while the room is running.

The age question gets asked after the money, by whoever happens to be pouring

A generic checkout collects an age tick box, which is a promise made by the person least likely to be held to it. The refusal therefore happens at the bar: a twenty-year-old who has already paid, in front of a room of other guests, refused by a part-time pourer who did not set the policy and cannot change it. Everyone involved hates that conversation, which is precisely why it is the one most often not had — and a pour served to somebody under age is the risk that costs a winery its licence rather than its afternoon.

What bindro does: The booker's date of birth is an eligibility rule evaluated on the money path, inside the same transaction that would have taken the card, so an under-21 booking is refused before payment instead of refunded afterwards. A date that cannot be parsed is refused rather than waved through, and the 21-and-over confirmation is blocking, so an order cannot complete without it. At the door the console will not admit anybody until the operator has ticked that ID was checked — bindro makes the refusal cheap and early, and leaves the looking-at-a-driving-licence part where it belongs, with a human being.

Member pricing is a conversation at the counter and a discount nobody can audit

Somebody says they are in the club. Nobody is going to challenge them over eight dollars while five people wait behind, so the discount is given on trust, and by the end of the month the tasting-room takings and the club list disagree by an amount nobody can attribute. It gets worse the better the club does: the more benefits membership carries, the more often it is claimed, and the less anyone at the counter is able to check it against a roster that lives in a different system on a laptop in the office.

What bindro does: The member rate is set on the ticket type and derived on the server. A taster types their membership number at checkout, it is matched against your winery's own roster inside the transaction that takes the money, and a current member is charged the member rate while everybody else is charged the standard one — a decision recorded on the order rather than a favour done at a counter. Two limits belong in the same breath: that roster is typed into the console by hand, one member at a time, with no import and nothing that adds a buyer to it automatically, and it prices a booking without ever gating one.

The bottles a tasting sells get rung up somewhere else, or not at all

A tasting is a sampling exercise whose actual purpose is the case that leaves with the guest. That sale lands on the card machine, the seat landed on a booking site, the cheese board went on a paper chit behind the bar, and the three of them are reconciled by hand, on a Monday, by somebody who was not there. The question a winery most wants answered — what is an hour in this room actually worth — has no answer, because the takings from one hour are split across three systems and one of them is a pad of paper.

What bindro does: Bottles, glasses and boards are published as add-ons against the tasting, each with its own stock, and a taster picks them during checkout. They are priced and their stock is moved inside the same transaction that takes the seat, so a board that has run out cannot be oversold, and the platform fee, the sales tax and any later refund treat the bottle exactly as they treat the seat. The counter is deliberately different and worth reading twice: the till page records a counter sale at your own price for your end-of-day numbers, and that money never routes through bindro. A walk-up seat sold at the door is the opposite — a genuine card sale on the ordinary checkout.

The signal dies halfway up the hill and the door falls back to a printed list

Tasting rooms are in barns, in cellars, at the end of a track, in a marquee at the top of a vineyard. One bar of reception is the normal condition rather than the bad day, and the usual fallback is a list printed at nine in the morning and a pen. That list is out of date by eleven, it cannot tell a real booking from a screenshot of one somebody sent a friend, and the record of who actually turned up ends the afternoon as a column of ticks that nobody types back in. The following week the no-show rate is a guess.

What bindro does: The door downloads a manifest for the session before it loses connectivity, scans against it with no network at all, and replays what it recorded when it reconnects. First scan wins, and anything that looks like a double admission goes into a conflict queue for a person to settle rather than being silently resolved. Pass holders are written onto every covered session's manifest, so they are admitted offline too. One number to size for while you are planning the room: a pass consumes no seat in the slots it admits at, so a licensed capacity has to leave room for the pass holders you expect on top of the seats you sell.

A day cut into arrival slots, each slot holding its own seats per flight

This is the shape of the vertical and everything else hangs off it. You publish a tasting, give it the times you open, and give each time its own stock — which can differ per flight, so eight reserve seats and twenty estate seats at two o'clock is an ordinary configuration rather than a workaround. Tiers open and close on the dates you set, whether or not anybody is watching the console that evening.

• Seats are held under a row lock while a taster pays, and released again if they abandon the page.
• Each flight is its own ticket type with its own price, its own stock and its own on-sale window.
• A filled slot stops selling itself and shows "Fully booked" — the label this config chose, not a generic one.
• Remaining seats per slot are live on the day-of screen, so the person on the floor sees what the website sees.
• The registration form already asks the six things this trade asks: party size, the 21-and-over confirmation, the booker's date of birth, a membership number, dietary needs and access needs.

Member prices decided by the server, against a roster you control

A ticket type can carry a member price beside its standard one. The number a taster types is checked against your organisation's roster in the same transaction that takes the money, so the discount is a server-side derivation rather than a claim made at a counter. Comps and promo codes sit alongside it for the cases membership does not cover — a trade visit, a journalist, a voucher printed for a wine fair.

• The roster is maintained in the console by hand, one member at a time: a name, a reference and an expiry.
• An expired member pays the standard price rather than being refused — membership is a price, never a permission.
• Nothing adds a buyer to the roster automatically, including buying a pass, so your club platform stays the system of record.
• A comped seat is a real credential with a real scan and no money attached, which is what a trade visit needs.
• Promo codes discount the sale before the platform fee is computed, so a discount costs you less fee as well as less revenue.

Bottles charged with the seat, and a till that records what it will not charge

Two things share the phrase "cellar door POS" and only one of them takes money. Add-ons are part of the order: the bottle is charged by bindro, taxed with the seat, stock-moved inside the confirming transaction and refunded through the same path. The till page is a record of counter trade at prices you set — useful for your end-of-day numbers, invisible to the ledger. Sales tax is applied server-side in the single derivation the quote and the confirmation share.

• Add-on stock cannot be oversold, because it moves under the same lock as the seat it was bought with.
• One tax rate is set on the event, itemised on the checkout summary rather than buried in the total.
• A refund reverses in a fixed order — your proceeds, then the tax, then the platform fee — so a refund never leaves you charged for an undone sale.
• Counter sales rung up on the till never reach a payout and cannot be refunded here; your own card machine took that money.
• There is no way to record a tasting seat paid for in cash, because crediting you for money the platform never held would pay you for the same seat twice.

A door that works with no signal, and a walk-up that is a real card sale

The check-in device is built for a vineyard rather than for a foyer with fibre. It syncs a manifest, scans offline, and reconciles later. Where somebody arrives without a booking, the day-of page shows live availability per flight and per slot and hands you into the ordinary checkout with a genuine hold on those seats — there is deliberately no second money path at the door.

• Offline scanning validates against the synced manifest; a replayed duplicate is queued for a human rather than resolved silently.
• A door sale derives its price the same way, applies the same registration rules, captures the card the same way and issues a credential that scans.
• Check-in refuses to admit until the operator confirms ID was checked, which is where an age rule stops being a checkbox.
• Manual check-in covers the phone that will not light up and the guest who deleted the email.
• Staff roles are enforced in the handler: a door login sees a name and whether the code admits, not what anybody paid.

Passes and gift cards, sold on your own page or inside the site you already have

A pass is a ticket type whose holder is admitted at every session of the event it covers, which is the natural shape for a release weekend or a season of Saturday flights. A gift card is bought against the winery rather than against one tasting, and it is carried as a liability until it is redeemed rather than booked as revenue on the day it was sold — which is the correct treatment and the reason the figure in your reports is worth trusting.

• The hosted tasting page speaks this trade's vocabulary: seats, flights, tastings and tasters, not tickets and events.
• The same booking flow embeds into your existing winery site, so the fee, the age rule and the roster check follow it there.
• A back-office booking records the party who rang up, and cannot be refunded through bindro because no card was charged here.
• Gift card value is applied as a tender line and drawn down inside the transaction that takes the booking.
• How many passes exist is bounded by the pass tier's own stock — and a pass takes no seat in the slots it admits at.

Your tasters and your rows, exportable on the day you decide to leave

The people who booked are your contacts, held per organisation, and they come out as CSV whenever you want them behind a one-time code — no export fee, no notice period and no contract to leave. Money reports read off the same ledger the payouts reconcile against, so what the console shows and what reaches the bank are the same arithmetic rather than two systems that agree most of the time.

• Gross, platform fees and refunds per tasting, from the ledger rather than from a summary table.
• Seats sold against tasters checked in, with a no-show percentage per session.
• A post-event email to the people who came, which is how a release weekend sells the next one.
• Sensitive answers — dietary needs, access needs — are classified on the field rather than by convention, and are excluded from AI context absolutely.

Who pays the booking fee?

The taster, unless you say otherwise. Every tasting carries its own setting — the taster pays, you absorb it, or you split it — and the fee itself does not change with the choice, only which side of the sale it comes from. On a ten-seat $25.00 tasting that is $16.20 either added to what tasters pay or taken out of what you keep.

Because the default is the taster, a winery can go from signing up to a sold-out tasting without paying bindro anything up front, at any point, ever. We are paid out of sales that happened or we are not paid.

The word "event" is load-bearing and worth reading twice. The scheduler groups by tasting, admits one only once its LAST session has ended, and pays it once. A tasting sold as a run of dates therefore pays after the final date, not after each one — a season's float is not something an operator should discover halfway through the season.

Bindro never pays before delivery, in any vertical. A pre-event advance is a configuration violation platform-wide rather than a policy someone can be talked out of, because paying out on tastings that have not happened is exactly how a cancellation becomes tasters with no refund. "Paid" also means the money moved: a payout only reaches its paid state with a real transfer reference attached, enforced by the database rather than by a status field someone can set.

• One payout per tasting, after its last session ends, one in flight at a time.
• T+2 for this vertical (low risk tier), no reserve.
• Refunds reverse in a fixed order — your proceeds first, then tax, then our fee — so a refund never leaves you charged for a sale that was undone.
• Sales tax, where it applies, is held as a liability rather than mixed into your balance, so the payout figure is proceeds rather than a number you still have to do subtraction on.

The argument worth having before you read any figure is which seats go on the bottom. A Saturday published as 6 slots of 12 offers 72 seats; sell 58 of them at $35.00 and the day takes $2,030.00 on seats. Divide by what you sold and every Saturday returns $35.00, which measures nothing. Divide by what you offered and you get $28.19 — a number that moves when a slot fails to fill, which is the thing a tasting room is actually managing. Both counts are on the same screen; the choice of denominator is yours and it is the whole meaning of the metric.

Bottle attach is where this vertical differs from the rest of the platform and where the number is most nearly free. Because an add-on is part of the order rather than a counter sale, add-on revenue sits in the same export as the seat that carried it, and attach rate is add-on lines over orders on a single sheet. The honest caveat is the one the till section makes: bottles rung up at the counter are outside that export entirely, so a winery that sells most of its wine at the till is measuring the smaller half here and should say so to itself before comparing months.

Club conversion is the one bindro genuinely cannot give you, and it would be easy to imply otherwise. Nothing in this product enrols a member: the roster is typed in by hand, buying a pass adds nobody to it, and there is no dues charge to observe. What you can measure here is the half that touches the booking — how many seats were sold at the member rate against the standard one, and which tastings those were — and the conversion itself is a join against whatever runs your club, on two exports.

Repeat visit rate falls out of the contact list rather than out of a report. Tasters are retained per organisation with the tastings they attended, so a second visit is a duplicate email address across two events. It is worth reading against check-ins rather than bookings: a repeat booker who did not turn up is a different problem from a repeat guest, and the no-show percentage per session is the column that separates them.

What the console shows today, without an integration or a spreadsheet:

• Gross, platform fees and refunds per tasting, read from the ledger the payouts reconcile against.
• Seats sold against tasters checked in, with a no-show percentage per session.
• Live remaining capacity while the tasting is running, per pool, on the day-of screen.
• This winery's own funnel — view → slot selected → checkout → paid → attended → club joined — stage by stage with the drop-off between them, and any step the platform cannot see said so rather than shown as a zero.
• Refunds, transfers, turnout, no-shows, add-on attach and repeat buyers, each printed with the two numbers it was divided from.
• Orders and tasters as CSV, so anything not on the screen is one export away.

Two more that are worth stating plainly. Sensitive answers are classified on the field rather than by convention, and health data is excluded from analytics exports and from AI context absolutely, with no override in any vertical. And a winery's own people see only what their role allows — a door login sees a name and whether the code admits, not what anyone paid — which is checked in the handler rather than by hiding a button.

• bindro does not run your wine club. There is no recurring charge anywhere in the product: no dues, no renewal, no club sign-up, no allocation and no shipping. Member pricing is a check made at checkout against a roster you type into the console by hand, one member at a time, with no CSV import — and nothing adds a buyer to it, not even buying a club pass. Whatever bills and ships your club today keeps doing it.
• A member price is not a members-only door. The roster decides what a taster PAYS, never whether they may book: once a tasting is on sale, anyone with the link can take a seat at the non-member price, and there is no invitation-only listing, no access code and no rule you can point at a membership number. A club-only release is protected by who you send the link to and by the person on the door, not by the software.
• The till writes bottle and food sales down; it does not take the money, and there is no way to record a seat paid for in cash. A counter sale rung up on the POS page is recorded at the price you set for your own end-of-day numbers, and that money never enters the platform ledger, never reaches a payout and cannot be refunded here. A walk-up seat sold at the door is a real card sale on the ordinary checkout, but crediting a winery for cash the platform never held would pay you for the same seat twice, so bindro refuses to pretend. Bottles a taster adds to a booking ARE charged by bindro, because an add-on is part of the order.
• No deposits and no payment plans. A winemaker dinner is charged in full at the moment of booking or not at all: this vertical does not resolve instalments, so there is no deposit-now-balance-later, no scheduled second charge and no card held for the rest. The nearest instrument is a gift card, and a gift card is something a guest chooses to buy rather than something you can bill them for.
• No waiting list, and a refunded seat does not come back on sale. When a slot fills the page says fully booked and stops: nobody joins a list and nobody is emailed when a seat frees up. Refunding a booking returns the money and leaves the seat counted as sold, so if you want one more couple at two o'clock, raise that slot's capacity by one rather than waiting for a cancellation to reopen it.
• No transfers and no date changes. A taster who cannot come on Saturday cannot hand the seat to a friend and cannot move it to Sunday — this vertical resolves neither ticket transfer nor deferral, and there is no credit note to issue. The only lever is a refund, after which they book again at whatever is still on sale. A gift card is the giftable instrument; a tasting seat is not.
• No group product and no invoicing on terms. A booking takes up to twelve guests on one card payment and that is the whole of it: there is no group rate to set, no roster for a coach party to fill in guest by guest, and no purchase order or invoice. A tour operator or a corporate visit is either an ordinary booking at the ordinary price or an arrangement you make with them off the platform.
• A club pass takes no seat in the slot it admits at. A pass tier is bounded only by its own stock, and its holder is admitted at every session of the event it covers while consuming none of those slots' seats. A tasting room with a licence-limited capacity therefore has to size its slots for the pass holders it expects as well as for the seats it sells; nothing warns the door that a busy slot is fuller than the screen says.

If one of those is the thing you need, say so — the answer is a capability declared, built and gated properly, or a straight no. It is never a feature flag that collects the request and does nothing.

This is the first thing to settle, because it decides whether the rest of the page is relevant to you. Two of the four tools wineries usually weigh against us are club and DTC platforms whose centre of gravity is the shipment, not the room. Bindro is the other half: it is configured for the afternoon, the licence, the flight and the door. Most wineries that use it keep both, which is a sentence a page selling you something is not supposed to write.

The integration between the halves is deliberately thin, and thin is honest. You type your members into the console — a name, a reference, an expiry — and that roster decides who is charged the member rate. There is no import, no sync and no webhook from your club platform, so a club of four hundred is four hundred rows entered by somebody, and a club of forty is an afternoon. Knowing that before you sign up is worth more to you than a signup is to us.

The second half of the same honesty is what membership does NOT do here. It cannot gate a listing. Once a tasting is on sale, anyone holding the link books it at the standard price, and there is no invitation-only listing, no access code and no eligibility rule that can point at the roster. A members-only release is protected the old way: publish it as its own tasting, send the link to members, and let the person on the door turn away anybody who should not be in the room.

• Bindro: timed slots, flights, the under-21 refusal, member prices, add-ons, tax, the door, the payout.
• Not bindro: dues, renewals, allocations, shipping compliance, and the club roster as a system of record.
• The seam between them is one number typed at checkout, and one roster maintained by hand.

Take the payout first, because it is the part that cannot be changed later. One payout covers one event and is released two days after that event's final session ends, never before delivery, in this vertical and every other. A Friday-to-Sunday release published as a single event with thirty slots therefore settles once, after Sunday's last pour. Wineries sit in the low risk tier, so nothing is held back as a reserve — the whole of your proceeds moves on that schedule.

A pass is the argument for the single-event shape. Its holder is admitted at every session of the event it covers, which is exactly a release-weekend wristband, and it is written onto every covered session's offline manifest so the door honours it up the hill with no signal. Across three separate events, a pass would have to be three passes. Size the room for it: a pass holder takes no seat in the slot they walk into, so the licensed capacity has to cover the passes you expect as well as the seats on sale.

The counter-argument is float and blast radius. A weekend published as one event holds the whole weekend's takings until Sunday has happened; three events pay three times, and a cancelled Sunday does not sit in front of Friday's money. For a winemaker dinner — one night, a high seat price, its own economics — its own event is nearly always right. The middle path most wineries land on is one event per day, with a pass only where they genuinely want a multi-day ticket.

• One event, many slots: one payout, one pass that admits all weekend, one thing to cancel.
• One event per day: money on each day's own schedule, and no pass that spans the weekend.
• Either way, seats are per session and the door list is per session — this is about the payout and the pass, not the inventory.

This is stated on the page that sells rather than in a support article, because it is the single operational habit a winery has to change when moving here. The workaround is one click and it is not a bug you are routing around: capacity is a number you set per slot, and adjusting it after a cancellation is exactly as valid as setting it the first time. What you must not do is assume the number on the screen self-heals, because on a busy Saturday it will quietly cost you the seat.

Refunds otherwise behave the way the money did on the way in. They run from the console, or from the signed link in the taster's own confirmation where your policy allows it, and they reverse in a fixed order — your proceeds first, then the sales tax, then the platform fee — so a refund never leaves you charged for a sale that was undone. An add-on refunds with the seat it rode in on. A counter sale rung up on the till cannot be refunded here at all, because bindro never held that money.

The things this vertical genuinely does not give you are worth naming in the same breath, since a cancellation is when a host reaches for all three. There is no waiting list, so nobody is emailed when a place frees. There is no transfer, so a seat cannot be handed to a friend, and no deferral, so it cannot be moved to Sunday. A gift card is the giftable instrument here; a tasting seat is not. The lever is a refund and a rebooking, and everything else is a conversation you have with the guest.

The per-order detail is worth a paragraph because a cellar door books in parties and the arithmetic favours that. The fee is computed on the order's discounted subtotal, so a table of 6 taking $35.00 seats together is a $210.00 booking carrying $6.24 of platform fee, where the same 6 people booking one at a time would carry $11.22 — the fixed part is paid once by the party and once each by the individuals. The fee table further up this page prices a single seat, which is the right way to read a rate and the wrong way to budget a Saturday of tables.

Who pays it is a per-tasting setting: the taster pays, you absorb it, or you split it. The fee itself does not change with the choice — only which side of the sale it comes from. Because the default is the taster, a winery can go from signing up to a fully booked release weekend without paying bindro anything up front at any point. We are paid out of sales that happened, or we are not paid.

Two things that are not fees and are sometimes mistaken for them. Sales tax is not ours: you set the rate, the server applies it, it is itemised rather than netted, and it is held as a liability rather than mixed into your balance, so the payout figure is proceeds rather than a number you still have to do subtraction on. And gift card value is not revenue on the day it is sold; it is carried until it is redeemed, which is why the number in your reports is one you can plan against.