Industry operations
Daily sales do not tell you what each menu item contributes
Separate sales, recipe cost, order-level expenses and whole-business profit through a transparent worked example.
Daily POS totals may still leave an owner unsure which menu item to sell through which channel. Menu names, recipes, purchase prices and fees may refer to different records.
The following numbers are hypothetical. All amounts use a consistent net basis; no tax calculation is included. They are not a restaurant’s results or market benchmarks.
Name the number you are trying to understand
Ingredient cost, contribution after variable order costs and whole-business profit answer different questions. Do not label them all profit without qualification.
For a menu decision, start with net item revenue less recipe cost and variable order expenses. What remains contributes to other costs; it is not automatically money the owner can withdraw.
One menu item, two illustrative channels
Assume net revenue of THB 200 and ingredients of THB 60. With no packaging or channel fee in the dine-in example, THB 140 remains. At the same delivery price, packaging of THB 10 and a channel cost of THB 30 leave 200 − 60 − 10 − 30 = THB 100.
The THB 40 difference follows these assumptions, not a universal preference for dine-in. Consider volume, capacity and additional expenses. Include order-dependent labour, restaurant-funded discounts or extra delivery costs where applicable.
Neither THB 140 nor THB 100 is net profit. Rent, fixed salaries, utilities, depreciation and other costs remain. Comparing figures at different cost levels without naming them can mislead.
Align purchase units with recipe units
Validate kilogram-to-gram conversions and distinguish bought weight from usable yield. Retain the recipe version, effective date and price source. Label estimates rather than silently substituting the latest purchase price for recorded costs.
ERPNext describes BOM costing as an approximate manufacturing cost based on materials or subassemblies and operation costs. A recipe in software does not automatically make estimated cost identical to actual cost.
References: [1]
Compare actual usage without rewriting the explanation
Multiply sales quantities by the recipe to estimate expected consumption, then compare with issues and counts over the same period. Record spoilage, staff meals, complimentary items and inventory adjustments separately.
Investigate unit errors, changed recipes, portion variation and incomplete receipts. Rewriting an old recipe only to make totals match can hide the reason for the difference.
Begin with five decision-relevant items
Choose high-volume or volatile-cost items. Confirm recipes, prices, units and channels together with the kitchen, purchasing and accounting teams before expanding.
Show cost dates, recipe versions, revenue basis and excluded expenses. Management can then decide whether to adjust a recipe, reconsider pricing or obtain missing information rather than treating every displayed balance as profit.
A practical starting checklist
- Distinguish ingredient cost, contribution and net profit.
- Validate purchase units, recipe units and usable yield.
- Map POS items to recipes and effective dates.
- Separate packaging, discounts and channel expenses.
- Investigate actual usage and explain differences.
Apply it to your business
Start with assumptions the team can confirm, then choose a tool that preserves them. A useful report explains what each number includes and excludes.
References
- Frappe. (n.d.). Bill of Materials. Retrieved October 1, 2026.
Numbered references support the attributed statements. Scenarios and recommendations are Linda’s examples, not verified client outcomes.
This article provides process-design guidance and illustrative examples, not an accounting, tax or legal determination or certification of every software module. Apply it with regard to your business, permissions and actual system scope.