ForHosting KIT · Developer Utilities

Wine bottle calculator for a party

This wine bottle calculator turns a guest list into a practical shopping quantity.

● BetaFree · in your browser
Use it from WebAPIEmailTelegramApp soon

Enter how many guests will drink wine, the number of servings you expect each person to have, and the bottle volume in millilitres. The calculation uses a 150 mL serving, totals the wine required, and rounds up to a whole bottle so the plan does not run short. It also reports the planned serving total and any extra wine created by rounding.

Build the estimate from your actual guest list

Begin with the number of people who are likely to drink wine, rather than the total invitation count. Children, designated drivers, people who do not drink, and guests who prefer another beverage should not automatically be included. Next, choose an expected servings-per-guest figure that matches the event. A short toast, a seated dinner, and a long reception create very different demand. The calculator multiplies these two values to produce the total number of planned servings. Because the estimate accepts fractional servings, you can use a value such as 1.5 or 2.5 when a whole-number assumption feels too coarse. That does not imply that anyone receives half a glass; it represents an average across the group. The result is a planning quantity, not a recommendation for personal consumption. If attendance is uncertain, run a conservative case and a likely case separately. Comparing those outputs makes the cost of a small buffer visible and helps you choose deliberately instead of relying on an unexplained party-planning rule of thumb.

Understand the serving and bottle calculation

Every serving in this calculator is treated as 150 mL. The required wine volume is therefore the number of guests multiplied by servings per guest, then multiplied by 150 mL. That volume is divided by the bottle size you enter. Since shops sell whole bottles, the quotient is always rounded upward. For example, a requirement of slightly more than six bottles becomes seven bottles, never six. This upward rounding is the essential practical step: rounding to the nearest bottle could leave the final guests without the servings included in your plan. Bottle size is entered in millilitres so the same method works for half bottles, standard 750 mL bottles, magnums, or another clearly labelled format. The output includes the exact planned servings, required millilitres, whole bottles needed, and surplus millilitres caused by rounding. That surplus is capacity rather than guaranteed leftover wine; pouring variation, spills, and unfinished glasses can all change what is actually consumed during an event.

Turn the result into a sensible purchase plan

Use the calculated bottle count as the quantity required by the assumptions you entered, then review whether those assumptions cover the way wine will be served. A self-service table may produce less consistent pours than measured service. A meal with several courses may spread wine over more time, while a brief reception may concentrate demand near arrival. If you are offering red, white, rosé, or sparkling wine, the calculator gives the combined bottle total; divide that total among styles according to your menu, season, and guest preferences. Keep the combined quantity at or above the calculated requirement unless you intentionally reduce the service plan. For events where running out would be especially disruptive, compare the base result with another calculation using a modestly higher servings-per-guest estimate. The difference is a transparent contingency quantity. When automating repeated event quotes, the same deterministic calculation is available through the API for $0.002 per request. Identical inputs produce identical outputs, with no network lookup, randomness, or changing external data.

Plan wine for a wedding reception

Estimate a whole-bottle purchase quantity from the expected wine-drinking guests and the reception's planned average service.

Quote beverages for catered dinners

Apply the same transparent serving assumption to each guest count when preparing repeatable catering estimates.

Compare bottle formats

Run the plan with standard bottles, half bottles, or magnums to see how whole-bottle rounding changes the order.

How large is one serving in this calculation?

One serving is fixed at 150 mL. The result states this serving size so the assumption remains visible.

Why does the calculator round the bottle count up?

A fraction of a bottle cannot be purchased as a full sealed bottle. Rounding upward ensures the bottles contain at least the planned wine volume.

Can I enter a magnum or half bottle?

Yes. Enter its labelled volume in millilitres as bottle_size_ml, and the calculation will use that volume.

Can servings per guest include a decimal?

Yes. A decimal represents an average across all guests, which is useful when expected consumption is not a whole serving per person. It must be greater than zero.

Does the result split bottles into red and white wine?

No. It calculates the combined bottle requirement. You can divide that total among wine styles according to the menu and guest preferences.

What does the API calculation cost?

The API costs $0.002 per request. The browser calculation can also be used directly on this page.

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.

POSThttps://api.kit.forhosting.com/cook/wine-serving-count

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.

curl -X POST https://api.kit.forhosting.com/cook/wine-serving-count \
  -H "Authorization: Bearer $KIT_KEY" \
  -H "Content-Type: application/json" \
  -d '{"guests":24,"servings_per_guest":2.5,"bottle_size_ml":750}'
{
  "guests": 24,
  "servings_per_guest": 2.5,
  "bottle_size_ml": 750
}
{
  "task_id": "tsk_a1b2c3d4e5f6a1b2c3d4e5f6",
  "type": "cook.wine_serving_count",
  "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.

Per request$0.002

Published price — no tokens, no invented credits. A failed task is never charged.

HTTPCodeMeaning
401unauthorizedMissing or invalid API key.
402insufficient_balanceYour balance doesn't cover the task price.
404unknown_typeThat task type doesn't exist.
429rate_limitedToo many requests. Use the webhook instead of polling.

Read the full KIT documentation →