Compare Restaurant Sales Reports by Order Channel

To compare a restaurant sales report by channel, start with the order date and the same sales definition for every source. Put counter, direct website, and marketplace orders into separate groups. Then show discounts, taxes, tips, fees, and deposits in their own fields. A deposit is cash received, not the same thing as sales earned.

That structure lets you answer two different questions: how much customers bought through each channel, and how much cash reached the restaurant after listed charges. It also exposes gaps before you use the numbers to change prices or marketing.

Set the channel and sales rules first

Choose one order source for each sale. A practical starting set is counter, restaurant website, and partner marketplace. Write down where phone orders, kiosks, QR orders, and orders entered manually belong. If the answer depends on who took payment or who submitted the order, make that rule explicit.

Keep the dining option in a separate field. Dine-in, takeout, and delivery describe how the guest receives the meal; they do not necessarily tell you where the order came from. A website order can be takeout, and a counter order can be dine-in or takeout. Combining those labels can count an order twice or hide a useful distinction.

Next, define the sales amounts. For the worksheet below, gross sales mean menu-item prices before discounts, tax, and tips. Net sales mean gross sales minus restaurant-funded discounts. Tax and tips are shown separately, not added to net sales. Fees are deducted later when calculating the expected deposit.

Decide how to handle refunds, voids, gift cards, service charges, and discounts funded by someone else. The right treatment can depend on the transaction and your accounting rules. Whatever definition you choose, apply it consistently and keep a record of exceptions. For example, distinguish the sale of a gift card from the later purchase paid with it so that the same spending is not counted twice.

Assign an order ID or another traceable reference to each row. If an order arrives through one source but is entered into another system for fulfillment, the source should remain clear. Check for a duplicate before adding both records to the channel total.

Map three orders to one worksheet

The following example is hypothetical. All three orders occur on Monday, November 2, in the restaurant's local time. Each has $100 in menu items, a $10 restaurant-funded discount, $9 in tax, and a $10 tip. There are no refunds or customer charges beyond the amounts listed. The assumed fees below are deducted from the deposits. The customer pays $109 per order: $100 minus $10 plus $9 plus $10.

The expected report shows $300 in gross menu sales and $270 in net sales across the three channels. Tax totals $27 and tips total $30. The $327 paid by customers, less $27 in listed fees, produces $300 in expected deposits. These deposits include the tax and tips in this example; they are not the restaurant's profit.

The worksheet also makes the comparison fairer. Each channel has $90 in net sales even though the expected deposits differ. Without separate columns, the marketplace order might look like an $89 sale while the counter order looks like a $106 sale. Neither figure uses the same definition as net sales.

When transferring your own data, map each source's field names to the worksheet rather than assuming that a field called “sales” means the same thing everywhere. One report might include tax in its total while another excludes it. Check a few individual receipts against the totals before relying on a channel summary.

Reconcile fees and deposits without guessing

Separate the charges you can identify. A marketplace commission, a card-processing charge, a delivery charge, an advertising charge, and a refund adjustment can affect cash in different ways. Do not call every deduction a commission, and do not assume that a charge appearing outside a payout has no economic cost.

In the example, the marketplace has an $18 commission and a $2 other fee. Its expected deposit is $109 minus $20, or $89. The counter and direct website deposits are $109 minus their respective $3 and $4 payment fees. These are assumed fees for the example, not quotes or claims about any provider.

For an actual reconciliation, connect the order record to the payment or settlement record where possible. Record the amount charged to the customer, each identified deduction, the expected payout, and the payout date. If a provider combines many orders in one deposit, compare the settlement's included orders and adjustments with the deposit rather than trying to match each order to a separate bank transaction.

A fee may be billed on a separate invoice instead of deducted from a payout. Add it to your channel cost review for the period, but do not subtract it twice from the deposit calculation. Likewise, a delivery fee charged to a guest is not automatically restaurant revenue or a restaurant expense. Ask who retains it and where it appears in the statements.

Net sales less listed fees still do not establish profit. Food, packaging, labor, rent, taxes owed, and other costs are outside the example. Use the channel report to spot differences worth investigating, then bring in the costs needed for a fuller margin decision. A bookkeeper or tax professional can help determine the proper treatment for your business.

Compare the same period and mark the gaps

Choose whether the report measures orders placed, orders completed, or cash deposited. For channel sales, an order-based period is often easier to compare; use a separate settlement view to track when money arrives. State the time zone and cutoff, especially if service runs past midnight.

Suppose the three example orders were placed on November 2, but their deposits arrived on November 3, November 4, and November 6. A November 2 order report should include all three orders. A November 2 bank-deposit report should not include those later deposits. Comparing one channel's order-day sales with another channel's deposit-day cash would produce a misleading result.

Late refunds and adjustments need a rule too. Keep the original order date visible and record the adjustment date and amount. Then decide whether a management report revises the original period or shows the adjustment in the later period. Either approach needs a clear label so that the report can be reconciled to settlement activity.

Document missing coverage instead of entering zero. If phone orders are not captured in the worksheet, label them “not included” and estimate their importance from available records before making a channel decision. Zero means the channel had no sales; missing means you do not know from this report. Also note partial days, a closed location, and any source whose data arrives later.

For a week-over-week comparison, use matching days and the same definitions. If you change how discounts or refunds are counted, restate the earlier period where practical or flag the break. A busy Friday compared with a quiet Monday tells you less about channel performance than two comparable Fridays.

Check a reporting workflow before you buy

Bring a small set of representative receipts and settlements to a vendor discussion. Ask how the workflow identifies the original order source, dining option, order date, discounts, tax, tips, and each fee. Ask which fields can be viewed together, which must be obtained elsewhere, and whether the detail can be exported for reconciliation. Do not assume a summary screen includes every field in the worksheet.

Fleksa's partner portal shows sales and order summaries for a selected period, alongside order-status views. Available views and configuration can vary. Compare that starting point with your required fields, and ask how it would work alongside your existing payment and partner reports. The restaurant management software and restaurant POS system pages can help frame the discussion; review integrations for the connections you need to investigate.

Use simulated records for a practice walkthrough. No real card payment, guest message, or courier dispatch is needed. If you later run a live service pilot, agree on its scope and review actual orders and settlements separately from the simulated check.

Use these observable criteria for the walkthrough:

• Pass: Each sample order has one source and a separate dining option. Fail: A delivery order is counted as both a source and a second sale.
• Pass: The three orders produce $270 in net sales under the stated definition. Fail: Tax, tips, or a deposit is mixed into that total without a clear adjustment.
• Pass: The worksheet shows $27 in fees and $300 in expected deposits. Fail: A fee is omitted, counted twice, or labeled without enough detail to reconcile it.
• Pass: The November 2 order report includes all three orders and notes later payouts. Fail: An order disappears merely because its deposit arrived later.
• Pass: Missing channels and unavailable fields are named. Fail: They appear as zero or are silently excluded from the comparison.

Before choosing a workflow, compare your requirements with Fleksa and confirm current availability. Bring your worksheet, a representative settlement, and the questions that matter to your operation.

Frequently asked questions

Should channel sales include tax and tips?

For the worksheet above, no. Show tax and tips separately from net sales so channels use the same definition. Follow the appropriate accounting and tax guidance for your business.

Why does a deposit differ from a channel's sales total?

A deposit can reflect taxes, tips, fees, refunds, adjustments, and settlement timing. Reconcile those items individually rather than treating the deposit as sales or profit.

What if a channel does not provide every field?

Mark the missing field and ask where the detail can be obtained. Use another reliable record where available, and avoid presenting an incomplete comparison as a complete one.