Waste tracking: a discipline separate from par-level inventory

Par levels, reorder points, and stock rotation answer one question: is the right amount of product on hand at the right time. They don't answer a different question that matters just as much: once a unit leaves inventory, did it actually become a sold drink, or did it disappear as spillage, an over-pour, expired stock thrown out, or a comped remake? That gap is what waste tracking exists to close, and it's a distinct discipline precisely because a venue can have flawless par levels and still bleed margin if nobody is recording where product actually goes after it leaves the shelf or fridge.

A simple waste log needs only a few fields to be useful: the item, the quantity, the cause, and when it happened — logged consistently rather than only when something dramatic happens. That log is what connects directly to true food cost percentage: theoretical cost, calculated purely from recipes, assumes every purchased unit converts cleanly into a sold drink, but actual cost of goods used — the number that should drive pricing and margin decisions — has to include everything logged as waste, which is why true food cost is always equal to or higher than the theoretical recipe cost, and a growing gap between the two is usually the first sign something in the waste column needs attention. A handful of causes account for most of it in practice: free-pouring syrup or milk past the recipe amount, incorrect dosing or a bad shot that gets dumped rather than fixed, dated stock like milk or prepared syrups that expires before it's used, drinks remade or comped for quality or service recovery, and spillage during steaming or transfer — each has a different fix, but none of them show up in a par-level report at all.