Cost of Goods Sold Is an Operating System

A food-cost or beverage-cost percentage can tell leadership that product cost moved. It cannot, by itself, explain what changed in the operating system that produced the number.

Product cost is created long before the P&L is reviewed. It begins with vendor terms and purchasing, continues through receiving and inventory, and is shaped by recipes, yields, portioning, waste, product mix, discounts, comps, and pricing.

That equation is necessary for accurate accounting. It is not yet an explanation. A useful review has to connect actual usage to what the business expected to use and then trace the variance to the operating drivers beneath it.

Theoretical cost provides a reference point

Theoretical cost estimates what product should have cost based on items sold, recipes, portions, yields, and current ingredient costs. Actual cost measures what the business actually consumed. The gap between them is not automatically theft, waste, or employee error. It is a signal that deserves diagnosis.

The variance may come from inaccurate recipes, changing purchase prices, poor yield assumptions, portion inconsistency, waste, receiving errors, unrecorded transfers, comps, inventory counting, or product-mix changes. Each explanation points to a different response.

Purchase price is only one driver

Vendor pricing matters, especially in volatile categories. But a purchase-price variance can be offset or amplified by other choices. A cheaper product that creates lower yield may cost more per usable portion. A higher-priced ingredient may improve consistency, reduce waste, or support a menu price that improves contribution margin.

Useful product-cost drivers include:

• Theoretical versus actual cost
• Purchase-price variance
• Product-mix variance
• Recipe-cost variance
• Yield variance
• Portion variance
• Waste and spoilage
• Comp and void activity
• Inventory turnover
• Receiving discrepancies
• Menu-item contribution margin

Menu design changes the cost story

A restaurant can execute every recipe correctly and still see cost percentage move because guests purchased a different mix of products. A shift toward higher-cost items can increase food-cost percentage while still improving contribution dollars. A lower percentage can look favorable while sales shift away from the items that produce the most cash contribution.

That is why percentage targets should be paired with contribution analysis and product mix. The objective is not to minimize ingredient cost in isolation. It is to understand whether the menu, pricing, and production system are creating healthy economics.

Variance review should create learning, not blame

When actual cost is unfavorable, kitchen employees are often the first place leadership looks. Sometimes execution is the issue. But vendor relationships, recipes, equipment, forecasting, prep systems, menu design, receiving controls, training, and leadership decisions all shape the result.

A productive review asks what the variance can teach the organization. Is the system asking for an unrealistic yield? Are pars driving overproduction? Are counts inconsistent? Has a vendor increase not yet reached menu pricing? Are portions difficult to execute during peak volume?

Inventory accuracy is part of operating clarity

Inventory is not only an accounting exercise. Poor count discipline weakens the reliability of cost percentages and makes every subsequent decision less certain. The count process, units of measure, transfers, cutoff, receiving, and item mapping all matter.

Before reacting to a cost percentage, confirm that the underlying information is trustworthy. Then separate price, usage, mix, and execution. The P&L shows where to look; the operating system explains what to do.

Next in the series, Why Labor Percentage Does Not Tell You What to Do applies the same approach to hours, rates, demand, productivity, and deployment.