🍾 BottleCount

Plan your party like an engineer. Configure drinks, cocktail recipes, and headcount — get a precise shopping list, cost range, break-even point, and a QR-based ticket workflow.

Run it free in your browser with no account, pay once for the hosted version, or deploy it to your own Cloudflare account for nothing. See Pricing.

App: https://bottlecount-epj.pages.dev — the product, free and paid tiers alike Docs: https://fre0grella.github.io/BottleCount — documentation only, no app

---

What It Does

BottleCount helps you plan ticketed parties without spreadsheets or guesswork. You define who's coming, what they're drinking, how strong the event should be, and what things cost — the app calculates the shopping list and the economics from your menu structure.

The planning side needs no server and never will: presets ship with the app, your customizations live in the browser, and it works offline. What a server buys you is the part that is inherently shared — a link your guests can open, a party two people can run, and your data on more than one device.

---

How to run it

	Browser	Hosted	Self-hosted
Price	free, forever	one payment	free
Account	none	Google sign-in	Google, or a local sign-in
Your data	this browser only	your account	your Cloudflare account
Menu, shopping list, budget	✅	✅	✅
Custom ingredients and cocktails	✅	✅	✅
Guest list you type yourself	✅	✅	✅
Signed QR tickets, one scanner	✅	✅	✅
Shareable invite link	—	✅	✅
RSVP funnel and spread view	—	✅	✅
Co-organisers on one party	—	✅	✅
Sync across devices	—	✅	✅
Several phones on the door	—	✅	✅

The free tier is not a trial: no expiry, no account, no card. If planning a party in one browser is all you need, that is the finished product.

Self-hosting is free because hosting is the thing being sold, not the software. Run the Worker yourself and there is nothing left to charge for — see Self-hosting.

---

Features

🍸 Drink Menu Engine

The menu is built around three category patterns:

• Spirits — 3-level structure: category → spirit → cocktail. Example: Vodka → 40% Vodka Lemon / 60% Vodka Redbull. Mixer quantities are derived automatically from cocktail recipes.
• Beer — 2-level structure: category → variety split. No cocktail layer, served as-is.
• Wine — 2-level structure like Beer, with percentage split across varieties.

Alcohol intensity presets still map to pure alcohol targets per person: 🌿 Soft · 🍹 Aperitivo · 🎉 Party · 🔥 Hardcore.

🛒 Smart Shopping List

• Calculates bottle counts from ABV, bottle volume, recipe ratios, and guest count.
• Supports min/max price ranges so you can estimate both best-case and shelf-price spend.
• Scales automatically as headcount or menu percentages change.
• Applies a configurable safety buffer to avoid underbuying.

📊 Party Economics

• Real-time revenue, estimated spend, and profit range.
• Break-even calculation based on fixed costs and average variable cost per person.
• Cost breakdowns and KPI-style summaries for fast planning.

🗂️ Catalog Management

• Preset ingredients and cocktails ship with the app as static data files.
• Users can extend the catalog with personal ingredients and cocktails stored locally in IndexedDB.
• Supports hiding presets, adding custom recipes, and overriding prices without touching the base catalog.

🎟️ Tickets & Validation

• Generate signed QR tickets in the browser.
• Validate tickets locally with HMAC verification and expiry checks. The signing key belongs to the party, so any organiser's phone can check any ticket — and it keeps working with no signal once fetched.
• Every ticket carries a five-character code as well. When a QR won't scan, the door types the code and the guest's name; both have to match.
• Several phones on one door share check-in state, so nobody is admitted twice. The server arbitrates, and a mistaken check-in can be undone.

📱 Offline-First Planning

• The planner runs entirely client-side and keeps working with no network.
• Browser storage keeps your custom catalog, settings, and tickets on-device.
• Export/import backup flow is recommended for portability and recovery.

---

This is the beginning of the README. Read the rest at the original. Read the full README ↗