Start with the money retained per order.

Model retained revenue, not just the menu price

A delivery-only kitchen can sell through channels with different charges, promotions and packaging requirements. The printed menu price is therefore only the beginning of an order contribution calculation. Work from the amount the business retains under the actual agreement.

This article uses labeled assumptions to demonstrate that calculation. It does not claim an industry-average commission, delivery-kitchen margin or occupancy cost. Channel contracts vary, and a public example should not be substituted for the terms that govern your orders.

Keep each channel separate at first. A blended average can hide a low-contribution order type or a promotion that costs more than expected. Combine channels only after their individual revenue and cost boundaries are clear.

Build the order cost in layers

Cost the complete food portion, including shared sauces and sides. Measure the finished batch yield and the amount used per order. Then add packaging and other direct components required by that channel. A delivery package can differ from a dine-in presentation even when the recipe itself is unchanged.

Apply any sales-linked fee to the correct contractual base. A fee on one definition of order value is not necessarily a fee on net food revenue after every adjustment. Confirm how discounts, tax, refunds and delivery charges are treated rather than guessing from a headline percentage.

Record responsibility for promotions and refunds. An advertised discount can be funded by different parties, and the kitchen's retained amount depends on the actual arrangement. The model should follow the settlement record you receive, not just the customer's receipt.

A transparent order scenario

Every value in this example is an assumption. The fee is calculated on the stated net menu price solely to illustrate the method.

The contribution is $20 less $4, $6, $1 and $0.50. It is not a profit margin because the kitchen's fixed commitments and any omitted costs remain to be covered. The chosen 20% fee is not a claim about a particular platform or a typical contract.

If the assumed fee were 25% on the same base, the fee would be $5 and contribution would fall to $7.50. The difference is $1 per order. At an assumed 200 orders, that difference totals $200 before considering any change in demand or other costs.

Compare channels without losing the mix

A direct order may avoid a particular marketplace fee while requiring other acquisition, payment or delivery work. It is not automatically costless. List those costs under the channel that incurs them and distinguish a variable order cost from a broader marketing commitment.

Use actual item counts and settlement values when reviewing an operating period. If one channel sells a different menu mix, average contribution can change even when its fee terms remain constant. Compare like items as well as the complete channel result.

A promotion can also change average order size and production demand. Keep the campaign period separate so the result can be interpreted. A higher gross order count is not sufficient evidence of a better financial outcome.

Calculate the volume needed to cover commitments

Assume the kitchen needs $17,000 of contribution in a period to meet the fixed commitments included in its model. At the illustrative $8.50 per order, the threshold is 2,000 orders. At $7.50, it becomes 2,267 orders after rounding up.

These results assume a stable average mix and contribution. They do not establish that demand exists or that the kitchen can produce the required volume. A planning model should show the volume assumption and the capacity check separately.

Keep the wider cost boundary visible. Removing a dining room does not remove occupancy, equipment, cleaning, supervision, administration or every other commitment. If the model omits a category, label the result as a subtotal rather than complete business profit.

Check the production constraint

Delivery demand can cluster into a short window. Consider how menu items share equipment, prep space and assembly steps. A product can look attractive per order while consuming the capacity needed for several other orders.

Measure the workflow using the intended packaging and handoff process. Food quality after the expected journey is an operating requirement, not a detail to check after pricing. A recipe change that lowers ingredient cost may create extra handling or reduce the product's suitability for delivery.

Use batch recipes where appropriate and keep their finished yields current. If a sauce is used by several virtual brands or menus, identify the shared component clearly. Otherwise a price update can reach one menu and leave another with an obsolete cost.

Keep waste and failed orders visible

Prepared stock that is not sold, remade orders and discarded components affect actual usage. They may not appear in the theoretical recipe cost multiplied by completed sales. Reconcile those records before concluding that an ingredient price is the cause of a margin change.

A refund is also not always the same event as wasted food. The product may have been produced and delivered, while the revenue adjustment occurs later. Align the operational event and the settlement record so the period report is understandable.

Record known causes without making an unsupported accusation. A variance can arise from count timing, pack changes, substitutions or incorrect recipe mapping as well as waste. Investigate the data path before assigning responsibility.

Make a change that can be evaluated

Choose a specific intervention, such as revising a packaging component, changing a shared recipe or testing a channel-specific price. State the expected effect on contribution and the demand assumption. Retain the old model so the comparison can be repeated.

After the test, inspect retained revenue, item mix, direct cost and production workload. Do not attribute every difference to the intervention if the service pattern changed. The result should tell you which assumption needs updating, not merely whether the headline sales number increased.

Use the contribution calculator for an ingredient-level check, but add channel costs in your wider operating model. The break-even calculator can model orders when all inputs use that basis. The browser ledger keeps the underlying recipes and shared components traceable.

Retain settlement evidence

Keep the channel settlement report beside the order counts used in the model. Timing differences, later refunds and adjustments can make a period’s cash receipt differ from the contribution expected from completed orders. Reconcile those differences instead of changing the recipe cost to force a match. The purpose is to identify which part of the data flow changed: the order, the channel charge, the payment timing or the ingredient usage. Each requires a different correction and should remain visible in the review.