Food cost per customer: a clearer restaurant measure than one percentage

A total food-cost percentage can move because prices changed, because guests bought different items, because portions changed, because waste was recorded late, or because the denominator changed. A per-customer measure makes one part of that story easier to see. If the restaurant served more guests but sold a different mix, total cost and cost per customer may move in opposite directions. That is useful only when the report says what was counted and when it says whether the numerator is an accounting cost, a purchasing view, or a theoretical recipe view.

Build a comparable measure

Start with a written definition. For a dining-room report, you might use cost of food sold divided by completed covers, excluding tax and service charge from sales. For a mixed operation, you might produce separate measures for seated covers, takeaway orders, and delivery orders rather than forcing unlike transactions together. If you use purchases as the numerator, explain that the result is a purchasing-per-customer view and adjust for opening and closing stock when the purpose is consumption. If you include staff meals or waste, show them as named components so a manager can choose the right action.

• Numerator choices: cost of food sold, recipe-based theoretical food cost, or purchases adjusted for stock movement. Each answers a different question.
• Denominator choices: completed covers, guests, tickets, transactions, or channel-specific orders. Use a stable definition across the comparison.
• Bridge items: opening stock, closing stock, credits, transfers, waste, staff meals, complimentary items, and unrecorded usage can explain a gap.
• Sales context: keep discounts, refunds, taxes, service charges, and channel fees separate from ingredient cost so the result is not misread.
• Source trail: retain POS counts, inventory counts, invoices, recipe versions, waste records, and the period close used in the calculation.

Use the control cycle, not a single spreadsheet cell

Cornell’s food-cost control framework is useful operational framing because food cost is created across a chain. Ordering affects what arrives; pricing affects the sales mix; receiving affects quantity and specification; storage affects usable yield; issuing affects traceability; production and portioning affect the plate; cash collection affects whether recorded sales match the food that left the kitchen. A per-customer number is a signal inside that chain. It cannot identify the cause on its own, so pair it with a short explanation and the record that can test the explanation.

Illustrative worked example: two channels, one definition

A four-step process for a dependable report

1. 1Name the unit and question. Write whether the report is about a cover, person, ticket, or channel order. State whether you are measuring purchases, food consumed, or theoretical recipe cost, and specify the close dates.
2. 2Reconcile the inputs. Match POS counts to sales records, inventory movement to invoices, and credits or waste to their supporting documents. Separate tax, service charge, staff meals, comps, and channel fees when they answer different questions.
3. 3Calculate and annotate. Show the numerator, denominator, formula, and components. Add a short note when recipe changes, supplier continuity, portioning, or sales mix could explain movement. Keep illustrative user-entered figures visibly labelled.
4. 4Investigate one cause and review. Choose the next control point—ordering, receiving, storage, issuing, production, portioning, or cash collection—then assign an owner and a review date. Compare like-for-like periods before changing a menu or supplier.