The purchase unit is the format in which the restaurant buys a product from the supplier; the usage unit is the actual measure the kitchen uses to cook, cost recipes, deduct stock or calculate costs.
The purchase unit and the usage unit are two basic concepts that make purchasing, inventory and recipe costing speak the same language. The purchase unit describes how the product arrives from the supplier: a case of 12 bottles, a 25 kg sack, a 5-litre container, a whole piece, a tray, a tin or a pack. The usage unit describes how it is used internally: grams, millilitres, units, portions or litres actually used in a recipe. In hospitality, confusing the two leads to very expensive mistakes.
If you buy cheese in 2.5 kg pieces but cost recipes in grams, you need to convert the price of the piece correctly into a cost per gram. If you buy beer by the case but sell individual bottles, the system has to know how many units each case contains. If you buy oil in containers but recipes use millilitres, every stock movement must convert litres into millilitres without losing precision. This relationship also affects the physical stocktake: the store may count 3 cases and 4 loose bottles, while the kitchen uses individual units.
Well-defined units prevent stock from looking right in purchasing but wrong in production, theoretical food cost from failing to match actual food cost, or the wrong quantities being ordered from the supplier. That is why every product should have a clearly defined purchase unit, base inventory unit and recipe usage unit. The key is not just recording unit names, but defining the conversion factor between them.
Cost per usage unit = Price of the purchase unit / Equivalent quantity in usage units
If a case costs €36 and contains 12 bottles, the cost per bottle is 36 / 12 = €3. If a 5-litre container costs €22, the cost per millilitre is 22 / 5,000 = €0.0044. If a recipe uses 80 ml, the cost allocated will be 80 × 0.0044 = €0.352. For products with waste, it is worth distinguishing gross and net quantity: if a 2 kg piece leaves 1.6 kg usable after trimming, the cost per net kilo is calculated by dividing the purchase price by 1.6 kg, not by 2 kg.
A restaurant buys mozzarella in cases of 6 × 1 kg bags for €48. The purchase unit is the case, but the kitchen uses grams on pizzas and salads. The cost per bag is 48 / 6 = €8. The cost per gram is 8 / 1,000 = €0.008.
If a pizza uses 120 g of mozzarella, the mozzarella cost in the recipe costing is €0.96. If the system recorded the case as a simple unit with no conversion, it might deduct a whole case for every pizza, or calculate an absurdly low cost per portion. Wine is another typical case: you buy a case of 6 bottles and sell both whole bottles and glasses. If a 750 ml bottle is served in 125 ml glasses, each bottle gives 6 theoretical glasses.
A case therefore contains 36 theoretical glasses. When selling by the glass, stock should go down in millilitres or fractions of a bottle, not just in cases.
It matters because it connects administrative data with operational reality. Purchasing negotiates cases, packs and formats; the kitchen works in grams, millilitres and portions; front of house sells units, glasses or set menus; management looks at costs and margins. If the conversion is not properly defined, you get inventory variances, misleading recipe costings, miscalculated supplier orders, unexpected stockouts and unreliable food cost. It also affects comparisons between suppliers: two suppliers may sell the same product in different formats, and only the cost per usage unit tells you which is really cheaper.
In multi-site businesses, badly configured units multiply the error because each site buys, counts and uses differently. Getting this foundation right makes every other metric, from theoretical usage to weighted average cost, defensible.
Zindra helps you manage purchase units, inventory units and usage units by linking suppliers, products, recipe costings, purchases and stock movements. The restaurant can buy by the case, produce by the gram, sell by the unit and analyse costs without manual conversion sheets. By keeping conversion factors consistent, Zindra improves food cost calculation, perpetual inventory, purchase forecasting and like-for-like price comparison between suppliers.
Tools and content to go deeper into this concept.
Food cost is the percentage of a dish's selling price that goes on the cost of its ingredients. It is the single most important indicator of how profitable your menu is.
A recipe costing sheet (escandallo in Spanish) is the technical document that breaks down every ingredient in a dish with its exact quantity, unit cost and total cost per portion. It is the foundation of cost control in a restaurant.
Recipe costing is the systematic process of calculating the exact cost of every dish by analysing all its ingredients, quantities, wastage and sub-recipes. It is the basis for setting profitable prices.
Perpetual inventory is a stock control system that updates stock levels in real time with every movement in and out, unlike periodic inventory, which is only checked at set points in time.
Theoretical usage is the amount of product a restaurant should have used according to its sales and recipe costings. Comparing it with actual usage reveals cost and inventory variances.
Inventory variance is the difference between the theoretical stock a restaurant should have according to purchases, sales and recipe costings, and the physical stock it actually finds when counting the stockroom or cold room.
Yield percentage is the usable share of an ingredient after cleaning, trimming, cooking or portioning. It tells you how much usable product you actually get from what you buy, and what it really costs.
Actual usage is the value or quantity of product a restaurant has really used during a period, calculated from opening inventory, purchases and closing inventory.
Weighted average cost is the average unit cost of a product, calculated according to the units bought at different prices. It is used to value inventory and usage without relying only on the last purchase price.
Every hospitality term with formulas, examples and benchmarks in a handy PDF.
Try Zindra free and keep food cost, staff, inventory and much more under control from a single platform.