Booking and Checkout for a Sauna Business

A sauna session is not an appointment. An appointment is one person and one provider for a stretch of time. A session is a room with a fixed number of seats and a fixed clock, and you are selling those seats to strangers who will sit together. Booking and checkout have to respect that, or they quietly cost you money.

Short answer

A sauna booking should claim one seat in a session, never the whole room. Shared seats and private buyouts are separate products at separate prices, the seat is held during checkout so two guests cannot pay for the last one, and the charge runs on your own Stripe account so the money lands in your bank.

What to get right first

• Give every session its own seat count, and sell seats against it, not time blocks.
• Price the private buyout as its own product, above the per-seat math.
• Hold the seat the moment checkout begins, and release it if payment does not finish.
• Show availability and the full price before any login or account wall.
• Run the charge on your own payment account, on your own payout schedule.

The unit you are actually selling

The thing on sale is a seat in a session at a time. Six seats in the 7:00pm sauna. Two of the three cold plunge slots at 8:15. When a guest books, they are not reserving the room. They are taking one seat and leaving the rest for sale. Software that treats the booking like a calendar appointment will block the whole room for one person, and you will sell out a sold-out-looking session that was three quarters empty.

Zettlor models the seat. A session carries its own capacity, fills seat by seat, and shows the rest as available until the last one goes. How that seat count is set and reset between sessions is covered in capacity and scheduling.

Operator rule: a booking should claim a seat, not the room, unless the guest bought a private session or buyout.

Shared sessions and private sessions are different products

Most rooms run two ways. In a shared session, individuals buy single seats and sit with whoever else booked. In a private session, one group buys the room and nobody else can join. These are different products with different prices, and the booking flow has to switch cleanly between them. Pricing and protecting the private side is its own discipline, covered in private rentals and buyouts.

The trap is the in-between state: a shared session that one large group quietly takes over by buying every seat. If your tool cannot tell the difference between "six individuals" and "one group of six," your staff cannot either, and the front desk improvises.

Holds during checkout, or you oversell

The window between "guest picked a seat" and "guest paid" is where overselling happens. Two people open the last seat in the 7:00pm session at the same time. Both reach checkout. Without a hold, both pay, and one of them arrives to a full room.

Zettlor places a short hold on the seat the moment checkout begins and releases it if payment does not complete. The seat is yours while you are paying and nobody else's, and it goes back on sale the instant you abandon the cart.

Payment runs on your own Stripe account

Checkout charges the card on your own Stripe account. The money lands in your bank, not in a middle account you withdraw from later. You keep your processing relationship, your payout schedule, and your dispute handling. Zettlor takes a small percentage per booking and never sits between you and the funds. When a member or a prepaid credit pays for the seat instead of a card, the draw-down rules are covered in memberships and credits.

What the guest sees

A guest should see the time, the seats left, the price for the product they picked, and a checkout that takes a card and ends. No account wall before they can see availability. No surprise on the total. The fewer steps between "I want the 7:00pm" and "I am booked," the more of your sessions fill.

Common mistakes this avoids

Blocking a whole room for a single seat. Letting two people buy the same last seat. Pricing a private buyout the same as a single share. Hiding availability behind a login. Each one is a small leak, and a busy room leaks all day.