Cocktail bar counter with recipe documentation and bar tools

Paid recipe-spec access

Specs Bar

Venue-specific digital access for current cocktail specs, powered by passkeys, one-time checkout, and revision-aware catalog control.

See venue model Start a bar page

Entry point: bar1.specs.bar
Guest access: One-time
Identity: Passkeys

Venue subdomains

Every bar gets its own branded catalog entry point.

The platform landing page stays at specs.bar. Guests buy and return through the venue subdomain, where page copy, imagery, colors, pricing, and catalog revision come from the resolved place.

bar1.specs.bar

Current revision

bar2.specs.bar

Current revision

seasonal.specs.bar

Current revision

Operating model

Built around the rules of paid current access.

Current-menu access

Guests buy the catalog revision that is live for that venue at checkout time. Future published changes require a fresh purchase.

Central catalog control

Recipes, venue copy, imagery, colors, pricing, and publishing stay with the platform admin.

Manual settlement

Each paid order feeds a local ledger, so payable and already paid-out venue shares are easy to review.

Catalog preview

Recipe specs that feel made for a bar, not a spreadsheet.

Central-admin managed

Classic

Coupe cocktail on a bar counter with recipe notes nearby

House Martini

Specs, dilution notes, glassware, garnish, and method in one clean entry.

Build

Bar counter cocktail scene used as a recipe catalog preview

Paloma Highball

Ingredient order and service notes stay locked to the purchased revision.

Seasonal

Cocktail service station with glassware and digital menu preview

Ruby Sour

A new published menu can invalidate old access without deleting purchase history.

Low ABV

Tablet showing a cocktail menu beside bar tools

Olive Spritz

Venue-specific presentation, central-admin controlled catalog data.

Manual payouts

Track what each venue is owed before the platform admin pays out.

Orders feed a local ledger with venue share, refund state, and payout status. The platform admin handles payment externally and marks eligible orders as paid out inside the system.

Sample ledger

Bar1 payable

Eligible orders28

Venue share35%

Payout statusManual review

Access flow

Simple for guests, strict on the server.

Resolve the bar

The server reads the request host and loads the matching place from the database.

Sell the current revision

Checkout uses the venue price and current catalog revision from trusted server data.

Register a passkey

After verified payment, the buyer gets a short-lived passkey registration flow.

Check access every time

Catalog reads require passkey login plus a paid purchase for the current venue revision.

Ready when the menu is

Launch a venue page around the current specs.

Start setup