Sell one latte, deduct 18 g of beans and 220 ml of milk

Your stockroom has never held a latte; it holds beans, milk, syrup and cups. Until your POS thinks the same way, your inventory report is fiction with decimals.

Recipe level inventory starts from an awkward fact: you sell lattes, but you have never bought one. You bought a 1 kg bag of beans, a case of milk cartons, a bottle of syrup and a sleeve of cups. A POS that tracks "lattes in stock" is counting something that does not exist.

Why do finished item counts lie in a cafe?

Retail is sell a shirt, deduct a shirt. A cafe is different: one ingredient feeds many drinks, and one drink drains many ingredients. Milk flows into lattes, cappuccinos and hot chocolate, while beans flow into everything with a shot in it.

Count only finished drinks and your system knows nothing about the ₱40,000 of raw ingredients in your chiller and shelves. That is where the money is tied up, and where it leaks.

What does recipe deduction actually look like?

Each menu item carries a bill of materials. Ring one 16 oz latte and the system deducts, for example:

  • 18 g of espresso beans
  • 220 ml of fresh milk
  • 1 pc 16 oz cup, 1 lid, 1 stirrer
  • 10 ml of syrup, if a flavored variant was selected

Sell 60 lattes today and the system knows you consumed about 1.08 kg of beans and 13.2 liters of milk, with nobody counting anything. Modifiers must adjust too: oat milk swaps the milk line, an extra shot adds 9 g of beans, or your busiest drinks drift the most.

Theoretical vs actual: the gap that pays for the system

Deduction gives you theoretical stock, what should remain given what you sold. A weekly physical count gives you actual. The difference is variance, and variance is where cafes bleed: free poured milk, unrung staff drinks, unlogged spoilage, deliveries signed complete but received short.

Without a theoretical number, all of it hides inside "we probably used it." With one, a 4 liter milk gap is a visible, answerable question, and when the gap will not close, the transaction side of the story lives in your void and refund patterns.

How does it fix purchasing and the menu?

Once consumption is tracked per ingredient, ordering becomes arithmetic: you burn about 2.3 kg of beans a day, the roaster needs three days, so the reorder point writes itself. Fewer emergency milk runs at retail prices, less cash parked in syrups someone overbought in March.

Recipe costs also give you the peso margin of every item, the raw material for menu engineering with your own sales data. And the same recipe map is what lets one sold out ingredient flag every affected drink at the register.

Start with ten recipes, not a hundred

Build recipes for your top ten sellers; they likely cover 80 percent of consumption. Weigh what your baristas actually pour, not what the training manual says, and count your five priciest ingredients weekly.

The one prerequisite is deduction at the moment of sale, automatic, inside the register. A cafe doing ₱25,000 a day that trims even three percent of ingredient waste recovers the effort many times over, and the cashier never notices a thing.

Make the shelf match the report

We build cafe POS systems with recipe level deduction built in: sell the drink, deduct the grams, see the variance. No Sunday spreadsheet required.

See the POS We Built Tell Us About Your Counter