Cloud kitchen financial model: orders, costs and margin

A cloud kitchen financial model links completed orders and realized order value to food, packaging, platform fees, staffing and kitchen costs. Build the plan from the same business units used in the order and accounting exports. Compare actual results with supplied assumptions before deciding whether volume, food cost or channel mix needs attention.

Start with completed orders and settlement detail

Export one row per order with order ID, service date, location, channel, status, net food sales, discounts, refunds and platform charges. Add food inventory movements, packaging purchases, payroll including employer costs, rent, utilities and other kitchen expenses. Keep canceled orders separate from fulfilled orders.

Use one location and one month first. A shared kitchen running several brands needs a documented rule for assigning common payroll and property costs. Otherwise, moving an expense between brands can look like an improvement in operations.

Do not take a net platform payout as the sales number. Reconcile the settlement to orders and deductions, then follow the company's accounting policy for reported revenue. The IRS recordkeeping guidance says records should clearly show income and expenses; keeping order and settlement detail makes that possible here.

Food cost must reflect consumption rather than only deliveries. The IRS cost-of-goods-sold explanation connects goods available for sale with closing inventory. Your monthly operating schedule should also account explicitly for transfers, waste and count adjustments, using the same definition in plan and actual.

The finance lead owns the comparison and reconciliation. Kitchen operations owns portion assumptions and production capacity; the commercial owner supplies channel-mix assumptions. Keep the approved version rather than overwriting it with actuals. The broader FP&A process explains how those responsibilities fit together. Use the startup financial model for opening-stage funding and cash requirements.

Lay out the operating drivers

An illustrative US delivery kitchen has the following monthly plan and actual results. Column D tests a supplied shift toward direct pickup orders. Prices and costs are assumptions for this example, not market benchmarks or published platform rates. All money is USD.

Enter these Excel formulas in B11:B17, respectively, then copy across to C and D:

=B2*B3
=B2*B4
=B2*B5
=B11*B6*B7
=B11-SUM(B12:B14)
=B15-SUM(B8:B10)
=B15/B2

Microsoft documents SUM for adding a range. Covirage is not affiliated with Microsoft.

The platform-fee formula assumes equal order values across channels and a fee base matching the net revenue shown. If either differs in your contracts, calculate each channel separately and add the fees. Do not apply a percentage to all revenue when only part of the business incurs it.

Contribution excludes kitchen labor here because the supplied monthly staffing budget is fixed within the illustrated capacity. The operating result excludes depreciation, financing and income taxes. Use consistent labels; the separate gross, contribution and net margin guide explains why those subtotals answer different questions.

Prove the actual shortfall before changing assumptions

Actual operating profit is $15,200 against planned profit of $23,800, a shortfall of $8,600. Work the variance in a stated order: change order count at planned contribution, then food cost on actual orders, then labor.

The reconciliation is $23,800 − $5,400 − $2,200 − $1,000 = $15,200. Revenue also checks as 5,500 × $24 = $132,000. Food consumed checks as 5,500 × $7.60 = $41,800, and platform fees as $132,000 × 80% × 25% = $26,400. No unexplained profit balance remains.

Tie the order count to completed order IDs, revenue to the accounting export, food consumption to inventory records and labor to payroll. For variable order values, divide total net revenue by completed orders rather than averaging daily averages. Asking questions of an existing sales workbook covers that review without replacing the original files.

Test the supplied channel scenario

The scenario changes only platform share, from 80% to 60%, keeping actual orders, price and operating costs constant. Platform orders fall from 4,400 to 3,300, while direct pickup orders rise from 1,100 to 2,200. The shifted 1,100 orders avoid $24 × 25% = $6 of assumed platform fees each.

The calculated benefit is 1,100 × $6 = $6,600, matching the fee decrease from $26,400 to $19,800. Operating profit rises from $15,200 to $21,800. Per-order contribution rises from $10.40 to $11.60, with dollar figures displayed to two decimals.

This is a comparison of supplied assumptions. It requires direct orders to have no additional incremental cost in the example. Before approving it, add any payment, marketing or fulfillment costs that would change, and confirm that demand can move between channels. The capacity planning guide helps check whether a proposed order level fits available labor and equipment.

Where it goes wrong

• Gross orders mixed with completed orders. Cancellations inflate volume and understate cost per fulfilled order.
• Payouts used as revenue. Fees and refunds disappear inside a net bank receipt.
• Purchases substituted for food consumed. Inventory buildup becomes an apparent cost increase.
• Fee bases left undefined. Taxes, promotions and contract exclusions can change what a percentage applies to.
• Direct orders assumed costless. Extra acquisition or fulfillment spending can absorb the calculated fee saving.

Compare your kitchen files in Covirage

Bring your order export, settlement statements, cost records and workbook of approved assumptions. Covirage maps the columns, and its tools compute and check the comparisons; the external AI model explains the results with every figure traced to its rows. Create a free Covirage account and bring a sample of your own data.

See Covirage for hospitality teams for the supporting industry context.