Drinks per guest estimator
Twenty guests at a three-hour party need 90 drinks: the estimator multiplies guests by hours by 1.5 drinks per guest per hour, then rounds up to whole drinks for the shopping list. Free in your browser.
- Free
- Runs in your browser
- No sign-up
- Your data stays on your device
Run — free
Worked example
- Guests
- 20
- Duration hours
- 3
- Rate per guest per hour
- 1.5 drinks
- Total drinks exact
- 90
- Total drinks
- 90
Party hosts, wedding planners, catering managers, and event apps need a quick, repeatable answer to how many drinks to buy or pour when the guest list and the clock are known. Guessing low empties the bar mid-reception; guessing high wastes budget and cooler space. This drinks per guest estimator multiplies the number of guests by the event length in hours by a fixed catering rule of thumb—one and a half drinks per guest per hour—then rounds up to whole drinks so your shopping list and bar stock stay practical.
What the drinks-per-guest estimate means and how the fixed rate works
Beverage planning for social events is usually framed as drinks per person over time rather than as a single flat total. Catering guides and bar-service training materials commonly use a simple hourly rate so hosts can scale from a two-hour open house to a six-hour wedding reception without inventing a new spreadsheet each time. This capability freezes that idea into one constant: one and a half drinks per guest per hour.
The exact product is guests times duration in hours times one point five. The rate is intentionally fixed and documented: it is a planning rule of thumb, not a laboratory assay of thirst, not a medical recommendation, and not a claim about alcohol versus soft drinks. Real consumption varies with weather, meal service, age mix, and whether you serve open bar, cash bar, or non-alcoholic stations only.
When you need a more aggressive first-hour spike or a lower dry-wedding rate, scale the guest count or duration inputs in your own layer, or treat the returned total as a baseline and apply your house multiplier afterward.
Where a quick drinks estimate helps most
Wedding and party planning sites need a single source of truth when a couple enters headcount and reception length so the beverage package quote matches the free calculator on the marketing page. Corporate event desks and venue managers can convert RSVP counts and block times into cooler capacity and case counts without maintaining a private spreadsheet per client. Meal-kit and catering SaaS tools can attach a drinks line item next to food portions using the same guest and hour fields already in the booking form.
Failed validation does not consume balance. Document that results are fixed-rate planning estimates—not measured consumption—keep the rate visible in product copy, and you get reproducible bar math for hosts, CMS blocks, and edge workers without hosting your own beverage spreadsheet.
What you can do with it
Venue and corporate event desks
Convert block times and guest lists into cooler capacity and case counts without maintaining a private rate spreadsheet per client.
FAQ
What happens if guests or duration is zero or negative?
Non-positive guest count or event duration cannot produce a meaningful drink stock estimate and is not billed.
What rate does the calculator use?
A fixed catering rule of thumb: 1.5 drinks per guest per hour.
Is this a measured consumption forecast?
No. It is a deterministic fixed-rate planning estimate for stocking and quotes. Real intake varies with weather, menu, and service style; apply your own house multiplier if needed.
Why is the total rounded up to a whole number?
Because you stock whole bottles, cans or poured drinks. Ten guests for two and a half hours give 37.5 drinks exactly, so the estimator tells you to have 38 on hand rather than run short.
Does it split alcoholic and soft drinks?
No. The total covers every drink and makes no claim about alcohol versus soft drinks. Weather, meal service, the age mix and the kind of bar all change real consumption, so treat the figure as a baseline.
Related tools
For developers — API access
Everything on this page is available programmatically. This section is for teams who want to wire it into their own systems; everyone else can just use the tool above.
API endpoint
Prefer to automate it? One authenticated POST creates the task; the result comes back by webhook or a signed link. The same capability also runs here on the web, by email and from Telegram — and soon from our app too.
Call it from your stack
curl -X POST https://api.kit.forhosting.com/cook/drinks-per-guest \
-H "Authorization: Bearer $KIT_KEY" \
-H "Content-Type: application/json" \
-d '{"guests":20,"duration_hours":3}'const res = await fetch("https://api.kit.forhosting.com/cook/drinks-per-guest", {
method: "POST",
headers: {
"Authorization": `Bearer ${process.env.KIT_KEY}`,
"Content-Type": "application/json"
},
body: JSON.stringify({
"guests": 20,
"duration_hours": 3
})
});
const { task_id } = await res.json();import os, requests
res = requests.post(
"https://api.kit.forhosting.com/cook/drinks-per-guest",
headers={"Authorization": f"Bearer {os.environ['KIT_KEY']}"},
json={
"guests": 20,
"duration_hours": 3
},
)
task_id = res.json()["task_id"]<?php
$res = file_get_contents("https://api.kit.forhosting.com/cook/drinks-per-guest", false, stream_context_create([
"http" => [
"method" => "POST",
"header" => "Authorization: Bearer " . getenv("KIT_KEY") . "\r\nContent-Type: application/json",
"content" => '{"guests":20,"duration_hours":3}',
],
]));
$task = json_decode($res, true);body := bytes.NewBufferString(`{"guests":20,"duration_hours":3}`)
req, _ := http.NewRequest("POST", "https://api.kit.forhosting.com/cook/drinks-per-guest", body)
req.Header.Set("Authorization", "Bearer "+os.Getenv("KIT_KEY"))
req.Header.Set("Content-Type", "application/json")
res, _ := http.DefaultClient.Do(req)Example request
{
"guests": 20,
"duration_hours": 3
}Example response
{
"task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
"type": "cook.drinks_per_guest",
"status": "queued",
"_links": {
"result": "/tasks/tsk_…/result"
}
}The API is asynchronous: the call returns a task_id immediately and the result arrives by webhook. Polling is capped at 1 req/s per task.
Pricing
Published price — no tokens, no invented credits. A failed task is never charged.
Errors
| HTTP | Code | Meaning |
|---|---|---|
401 | unauthorized | Missing or invalid API key. |
402 | insufficient_balance | Your balance doesn't cover the task price. |
404 | unknown_type | That task type doesn't exist. |
429 | rate_limited | Too many requests. Use the webhook instead of polling. |
Technical notes
Non-positive guest counts and non-positive durations fail with invalid_input instead of inventing a zero-stock plan.
What the drinks-per-guest estimate means and how the fixed rate works
Because you stock whole bottles, cans, or poured units, the endpoint also returns a ceiling of that product as total_drinks—the number you should plan to have on hand. The API itself never changes the constant so goldens, SEO demos, and production automations stay aligned.
Input contract, response shape, and error behaviour
Example: ten guests for two and a half hours yields thirty-seven point five exact and thirty-eight drinks after the ceiling. Pin these deterministic products in tests so catering checklists and browser widgets stay byte-stable across releases. Extremely large magnitudes above the internal absolute cap are rejected so a bad automation cannot request absurd stock numbers. POST a JSON body with two required fields. guests is a finite positive number: how many people you are stocking for. Aliases such as guest_count, num_guests, people, attendees, and guest are accepted. duration_hours is a finite positive number of hours the event runs; aliases include hours, duration, event_hours, length_hours, and time_hours. Both fields may arrive as JSON numbers or as numeric strings. On success the body includes guests and duration_hours as echoed numbers, rate_per_guest_per_hour always one point five, total_drinks_exact as the raw product rounded for stable goldens, total_drinks as the ceiling whole-drink stock figure, unit always drinks, formula restating the multiply-and-ceil rule, and message for UI copy. Missing fields, non-numeric values, zero or negative guests, and zero or negative duration fail with invalid_input and are not billed. Example: twenty guests for three hours yields total_drinks_exact of ninety and total_drinks of ninety, because twenty times three times one point five equals ninety.
Integration use cases
Wedding and party planning sites
Turn RSVP headcount and reception hours into a stable total_drinks figure so beverage package pages match the free on-site estimator.
Catering SaaS and booking forms
Attach a drinks line item next to food portions using the same guests and duration_hours fields already captured at booking.
Technical questions
How does the drinks per guest estimator work?
Send guests (positive count) and duration_hours (positive hours). The API multiplies by a fixed 1.5 drinks per guest per hour and returns total_drinks_exact plus a ceiling total_drinks.
What does the drinks per guest estimator cost?
The browser tool is free. API requests use prepaid KIT balance at $0.002 per successful call; invalid input is not billed.