Coffee shop inventory management is the system a café uses to track ingredients, packaging, retail products, and operating supplies from delivery to sale. Done well, it helps you prevent stockouts, reduce waste, control costs, and order with confidence.
The challenge is that a coffee shop does not sell inventory in the same form it buys it. You buy beans by the bag, milk by the carton, and cups by the case—but sell lattes, cold brews, and pastries one order at a time. Every product moves at a different speed, expires on a different schedule, and may be stored across several locations.
This guide explains a practical inventory system for independent cafés and multi-location coffee businesses. It covers what to track, how often to count it, how sales should affect ingredient stock, which calculations matter, and when software becomes worth using.
Last reviewed: September 11, 2026.
The goal is not perfect inventory every second. It is knowing what you have, understanding why it changed, and acting before a shortage or excess order hurts the business.
A reliable inventory operation is a repeating loop:
Most inventory problems happen when one part of this loop is missing. A café may count accurately but fail to record waste. It may track sales but not recipe ingredients. It may create purchase orders but update stock before checking the delivery. Better software helps, but only when it supports the entire loop.
A latte sale should affect espresso beans, milk, a cup, and a lid. A flavored latte may also use syrup. If the system only subtracts one finished “latte,” the café still does not know how much of each ingredient remains.
Beans may be purchased by the bag, stored by weight, and consumed by the gram. Milk may be purchased by the case but counted by the carton. A missing conversion can make an otherwise accurate system misleading.
Milk, pastries, prepared food, and opened ingredients carry a different risk from cups or cleaning supplies. The right reorder quantity must balance availability with shelf life and storage space.
Morning rushes, weekends, weather, local events, promotions, and tourism can change demand quickly. A fixed par level that worked last month may create a stockout—or unnecessary waste—this month.
Start with the products that can stop service, tie up cash, create waste, or materially affect profit. Organize them into four groups.
Track coffee beans, milk, alternative milks, syrups, sauces, tea, chocolate, food ingredients, and anything else consumed when a menu item is prepared. These products directly affect availability, recipe cost, waste, and cost of goods sold.
Include cups, lids, sleeves, napkins, straws, bags, and takeaway containers. They may not appear in a recipe, but running out can still stop a sale.
Track bags of coffee, bottled drinks, merchandise, brewing equipment, and packaged food as sellable SKUs. These products are usually easier to connect directly to POS sales.
Cleaning products, sanitizer, paper goods, and back-of-house supplies do not always need daily precision. Track the items whose absence would disrupt service, safety, or compliance.
Do not start by tracking everything with the same level of detail. Begin with high-value, fast-moving, perishable, and operationally critical products. Add lower-risk items once the routine is working.
Before adding alerts or automation, give every item a consistent definition. Record:
Use one counting unit consistently. If oat milk is bought in cases of six but counted as cartons, record the case-to-carton conversion. If beans are bought in one-kilogram bags but consumed in grams, define that conversion before calculating recipe usage.
For a deeper setup, use the reorder point guide, safety stock guide, and inventory par-level guide.
Reports and alerts cannot correct a bad starting quantity. Perform a complete physical count before relying on the system.
For the complete process, see how to perform a physical inventory count.
Do not count every item every day. Count frequency should reflect sales velocity, value, shelf life, variance, and the damage caused by a stockout.
Assign each count to a role or shift and give the team a fixed route through the café. A repeatable count completed on schedule is more valuable than a perfect process that rarely happens. Cycle counting can reduce disruption by checking smaller groups more frequently.
A POS records what the customer bought. Your inventory process must translate that sale into the ingredients and packaging that left the business.
For a latte, define the expected quantity of espresso beans, milk, cup, and lid. Include modifiers when they materially change usage, such as an extra shot, alternative milk, or flavored syrup. The result is theoretical usage: what inventory should have been consumed according to sales.
Physical counts then show actual usage. The gap between theoretical and actual usage is the variance your team needs to explain.
Where Stash fits: Stash can connect supported POS sales with inventory and recipe usage, helping quantities stay current between physical counts. See how Stash tracks inventory.
If you use Square, see the dedicated Square inventory guide for coffee shops.
Expired milk, stale pastries, spills, remakes, samples, damaged products, and preparation waste should be recorded with a reason. Waste is not just a deduction—it is information about where the operation can improve.
Repeated waste may point to over-ordering, incorrect par levels, storage problems, inconsistent portions, or falling demand. Unexplained variance may point to recipe errors, missed deliveries, incorrect units, unrecorded transfers, counting mistakes, or loss.
When the shelf and the system disagree, do not simply overwrite the quantity. Work backward from the last reliable count and review:
The principle: correct the quantity, but preserve the reason. The reason is what prevents the same discrepancy next week.
Beginning Inventory + Purchases − Ending Inventory = Inventory Used
This shows how much stock was consumed during the period, whether through sales, waste, samples, or unexplained loss.
Beginning Inventory Value + Purchases − Ending Inventory Value = COGS
If beginning inventory is $2,000, purchases are $4,000, and ending inventory is $1,500, COGS is $4,500. Compare COGS with sales for the same period, but avoid treating one generic percentage as the correct target for every café.
Theoretical Usage − Actual Usage = Inventory Variance
Track variance by product and category. A total business-level number can hide a serious problem with milk, beans, pastries, or packaging.
(Average Daily Usage × Supplier Lead Time) + Safety Stock = Reorder Point
If a café uses 12 cartons of oat milk per day, delivery takes two days, and the café keeps 10 cartons as a buffer, the reorder point is 34 cartons.
Available Quantity ÷ Average Daily Usage = Days of Stock
If 60 cartons are available and average usage is 12 per day, the café has roughly five days of stock. Compare that with the next delivery date, shelf life, and expected demand—not in isolation.
A reorder point is a warning, not an automatic answer. Before buying, consider:
Review thresholds whenever demand or supplier performance changes. Static reorder levels become less useful when a café grows, opens a new location, changes its menu, or enters a different season.
Where Stash fits: demand forecasting can turn sales history and consumption patterns into earlier stockout warnings and more useful reorder guidance. Explore forecasting with Stash.
A purchase order should connect what you have, what you expect to use, what is already on order, and what the supplier can deliver.
When a delivery arrives:
This prevents a short shipment or substitution from becoming an invisible stock error. It also creates a reliable history of supplier pricing, lead times, order accuracy, and spend.
See purchase orders in Stash, or read how to create a purchase order.
A stockout and an overstock are often two versions of the same problem: buying without enough context.
Focus first on products that would stop service or disappoint customers, such as beans, milk, cups, and core menu ingredients. For each one, review usage, delivery frequency, lead-time variability, shelf life, and the cost of carrying extra stock.
Use a larger buffer when the supplier is unreliable or the product is essential and shelf-stable. Use a smaller, more frequently reviewed buffer for products that expire quickly. Forecasting should support these decisions, not remove operational judgment.
The most useful alert is not “quantity is low.” It is “this product is likely to run out before the next replenishment opportunity.”
Do not assume every café should hold the same quantity. Each location can have different traffic, menu mix, storage space, delivery schedules, events, and customer behavior.
Where Stash fits: owners can compare stock across locations and move products where they are needed without switching between separate accounts. See multi-location inventory.
The best system is not the one with the longest feature list. It is the one your team can maintain consistently while giving owners enough information to act.
Stash is designed for coffee shops that have outgrown disconnected counts, spreadsheets, supplier records, and purchasing workflows.
It brings inventory, supported POS sales, recipes, alerts, suppliers, purchase orders, forecasting, and locations into one system. That gives the team clearer answers to three daily questions:
Physical counts still matter. Stash makes the activity between counts visible, reduces manual double-entry, and turns the next count into better operational information.
See how Stash works for coffee shops or start a free trial.
Track ingredients, packaging, retail products, and operating supplies that affect service, cash, waste, or profit. Prioritize fast-moving, expensive, perishable, high-variance, and operationally critical products.
Count critical perishables and fast movers daily, broader ingredients and packaging weekly, and low-risk operating supplies monthly or as needed. Increase frequency when an item has high value, high variance, or serious stockout consequences.
Define a recipe for each menu item and modifier, including the expected quantity of beans, milk, syrup, cups, and other components. Multiply recipe quantities by POS sales to calculate theoretical ingredient usage, then compare it with physical counts.
Record waste by reason, use older stock first where appropriate, align order quantities with current demand, review portions and recipes, and investigate recurring variance instead of simply correcting quantities.
The standard starting formula is: average daily usage multiplied by supplier lead time, plus safety stock. Adjust the result for shelf life, delivery reliability, storage limits, seasonality, and upcoming demand.
No. Par levels and reorder points should reflect each location’s demand, menu mix, storage, delivery schedule, shelf life, and stockout risk.
A POS can track finished products and sales, but ingredient-level accuracy depends on recipe support and how inventory movements are configured. Cafés with complex recipes, purchasing, suppliers, or multiple locations may need a connected inventory system.
Yes. Stash connects with Square and adds inventory workflows around the sales data, including ingredient and recipe tracking, stock alerts, purchasing, forecasting, suppliers, and multi-location visibility.

Stash connects inventory tracking, forecasting, purchasing, suppliers, and multi-location visibility so growing physical businesses can act on the numbers with less manual work.