A café buyer needs enough coffee, milk, pastries and serving supplies for the planned service, with each order arriving before it is needed. Those items can have different suppliers, cutoffs, pack sizes and handling requirements. A busy sales day is only useful as a buying signal if the team can translate it into the right ingredient and packaging quantities.
This guide is for independent coffee-shop owners, managers and buyers coordinating café supplies. For green-coffee contracts and roast-input planning, use the separate bakery and roaster purchasing guide.
Quick answer: combine modeled demand with a usable-stock check
Map drink variants to their ingredient and packaging assumptions, then compare expected use with physical stock and confirmed incoming supply. Review the recommendation before the actual supplier cutoff. Keep supplier changes and accepted receipts visible to the person buying for the next service.
A useful software trial follows a milk reorder, a coffee price change and a short pastry delivery. Restaurant and café purchasing software should help the team inspect those exceptions as well as a clean order.
Start with drink variants and service type
A POS sale records a drink, but the purchasing model needs its ingredients and units. A milk substitution, extra shot, different size or reusable cup can change the inputs. Check how the actual POS connection represents those modifiers before relying on the calculation.
For an illustrative set of drinks, assume each uses 18 grams of coffee and 200 milliliters of the selected milk. These are planning examples, not drink specifications:
| Recorded sales | Coffee requirement | Milk requirement |
|---|---|---|
| 100 whole-milk drinks | 1,800 g | 20 L whole milk |
| 50 oat-milk drinks | 900 g | 10 L oat milk |
| Total | 2.7 kg | 30 L across two separate items |
If 120 of these drinks are takeaway orders using one cup and lid each, the modeled requirement is 120 cups and 120 compatible lids. Do not assign a disposable cup to every drink if the sales mix includes other service types.
The result is modeled use. It does not measure espresso dial-in, spills, remakes, staff drinks or leftover steamed milk unless the workflow records or explicitly estimates those uses. Keep their assumptions visible and avoid counting the same allowance twice. See consumption rate.
Turn dairy demand into a dated purchase quantity
Use each supplier's actual review cadence and usable delivery lead time. A target covering the interval between orders can still be too low if it ignores the wait after the order is placed.
Suppose an illustrative milk item has:
- Planned use of 20 liters per day.
- A two-day interval between order reviews.
- One day from order to usable delivery.
- A chosen six-liter planning buffer.
The order-up-to target is 20 × (2 + 1) + 6 = 66 liters. With 18 usable liters on hand and 24 confirmed incoming in time, net need is 66 − 18 − 24 = 24 liters, assuming no other commitments. At six one-liter cartons per case, that is four cases.
This is a simplified planning example, not a recommended buffer or guaranteed service level. Check timing separately: 18 liters cover less than one day at the assumed rate. An incoming delivery on day two leaves a potential gap even though it was included in inventory position.
Check storage capacity, labeled dates and the approved handling procedure before accepting the quantity. Do not add a generic daily “decay percentage” as though it establishes usability or predicts loss for every milk product. Separate items and product states where their instructions or demand differ.
The café PAR guide explains a worked stock-target example. The PAR calculator supports planning inputs; neither replaces a count or a product-release decision.
Check the difference between recipe use and stock movement
In a simplified daily record with no transfers, 30 liters opening stock plus 24 liters received minus 19 liters closing stock gives 35 liters of stock outflow.
If the drink model explains 30 liters and recorded disposal explains two, three liters remain unexplained. Review count timing, modifiers, remakes, unrecorded use and unit conversion before labeling that difference waste. Updating every recipe to absorb an unexplained difference can hide the underlying problem.
Use a consistent period and receipt cutoff. A delivery counted in closing stock but missing from the receipts creates a misleading result. Record corrections so the buyer can see what changed in the next recommendation.
Separate retail coffee sales from back-bar use
Retail bags and coffee used in drinks can draw on the same physical supply. Decide how the system represents each flow and reconcile them without creating or consuming stock twice.
For example, ten one-kilogram bags equal ten kilograms. Selling three bags retail and opening two for back-bar use leaves five sealed bags and two kilograms transferred to service stock before service consumption. The transfer is not itself a sale, and it should not also be counted as two kilograms of drink consumption.
Track the combined purchasing need while preserving the units and locations behind it. If the supplier allocates a particular coffee, record the agreement and remaining quantity separately. A normal reorder alert does not prove that the software manages allocation contracts.
For a new coffee or proposed substitute, the responsible team should approve the product and recipe changes. Confirm when the accepted cost becomes effective; do not silently apply a future price to older purchases.
Compare a supplier price change per drink
Suppose coffee cost rises from $20 to $22 per kilogram. At the illustrative 18-gram dose, modeled coffee cost per drink rises from $0.36 to $0.396, an increase of $0.036.
Across 1,000 such drinks, that is $36 of additional modeled coffee cost, holding the dose and mix constant. It is not the complete change in profit: milk, other ingredients, packaging, labor and other costs may also matter.
The food cost calculator helps compare the inputs you supply. Confirm which costs it includes before calling its output a complete drink margin. In a demonstration, show the supplier change, buyer review, effective cost and updated recipe estimate rather than assuming every received email automatically updates every menu item.
Receive pastries against the accepted order
Use this fictional bakery delivery as a workflow test:
- The café requests 40 plain pastries at $2 each: $80.
- The supplier offers 30 plain pastries at $2 and ten different pastries at $2.50: $85.
- The café reviews the proposed product and price change before accepting.
- The delivery contains 30 plain pastries and eight of the accepted substitutes: 38 items, with two still missing.
Keep the accepted substitution and the two-item shortfall distinct. If the supplier invoices the full $85, the missing items represent a $5 difference under these assumptions. Record the agreed delivery or credit resolution instead of marking the order complete because an invoice arrived.
A pastry substitution can affect product information and customer suitability. Have the responsible person review it under the café's procedures before sale. Purchasing approval alone is not a food-safety or allergen assessment.
Record unsold stock and its disposition under the approved handling process. A forecast determines a buying assumption; it does not set safe shelf life.
Treat cups and lids as a compatible set
A cup count does not establish that the shop can serve the planned takeaway drinks. Check size, lid compatibility and any other required packaging components.
For a planned 500 takeaway drinks, suppose the café has 300 suitable cups but only 180 compatible lids, with none incoming. Net needs are 200 cups and 320 lids. If both suppliers sell packs of 100, order two cup packs and four lid packs, subject to storage and the actual service plan.
Keep maintenance supplies on their own requirement schedule using the equipment instructions and observed stock. Do not assume a fixed monthly order or a particular replacement interval suits every machine and café.
Plan a seasonal item without turning revenue growth into ingredient growth
A prior seasonal promotion selling 40 bottles' worth of syrup is a useful reference, but a 15% rise in total café revenue does not establish a 15% increase in that syrup's demand. Price changes and a different sales mix could explain the revenue increase.
Use expected drink units, recipe quantities, existing usable stock and the launch period to construct scenarios. Check supplier lead time and pack rounding, then review actual sales as the promotion runs. Decide how to stop reordering near the end and what to do with remaining supply under the product's instructions.
What to demonstrate with LineNow
LineNow connects supported sales inputs, recipes, purchase orders, supplier replies and receiving. Test the actual POS connection, modifier mapping and refresh timing used by your café. Show how the buyer reviews quantities before the supplier cutoff and handles a confirmation received through the supplier's actual channel.
Use the milk, coffee and pastry examples above. Keep requested, accepted, received and invoiced quantities distinct, and assign an owner to any remaining difference. Confirm the implementation for specialty allocations, date controls and recipe-cost updates rather than inferring them from a general purchasing feature.
Start with a small set of real items across a complete ordering cycle. Measure corrections, emergency purchases, unresolved receiving differences and time spent preparing orders. Explore the café purchasing workflow with those examples before extending it across the menu or additional locations.