Comparing Profitability Across Channels
A fair channel comparison uses the same sales basis, time period and cost definitions. It also recognises that a marketplace, app, website and telephone line may perform different jobs for the business.

A fair channel comparison uses the same sales basis, time period and cost definitions. It also recognises that a marketplace, app, website and telephone line may perform different jobs for the business.
Standardise the data
- Define completed, cancelled and refunded orders.
- Use gross or net sales consistently.
- Separate VAT where appropriate.
- Record fees and promotions outside net payout.
- Match refunds and chargebacks to the original channel.
- Split collection and delivery.
Compare representative baskets
Use common basket types rather than only monthly averages. A marketplace may carry smaller new-customer orders, while the app may contain high-value loyal customers. Compare like-for-like baskets and then report the actual mix.
Include strategic and operational differences
| Dimension | Examples |
|---|---|
| Demand role | Discovery, repeat ordering, phone support or walk-in convenience |
| Control | Menu, pricing, customer journey and data access |
| Operational load | Tablets, manual entry, support and reconciliation |
| Resilience | Alternative route during a supplier or network failure |
| Contract risk | Commission, renewal, data export and exit |
Use sensitivity analysis
Test higher food cost, lower average basket, more refunds, a marketing incentive and an extra staff hour. Show when the channel ranking changes. A conclusion that disappears under a small assumption change should be treated cautiously.

Avoid simplistic decisions
Do not close a channel merely because its direct contribution is lower. First identify whether the business can move demand safely, whether another channel has capacity, and whether discovery or customer support value is being lost.
Practical next step
Select three comparable baskets and calculate contribution across website collection, website delivery and marketplace delivery. Then repeat using the actual monthly mix and explain the difference.
Control for customer and time mix
Compare weekday with weekday and peak with peak. A direct channel may appear stronger because established customers use it, while a marketplace bears the cost of discovery. Report new and repeat customers separately where identity can be matched lawfully and reliably. Do not force uncertain matches merely to improve attribution.
Reconcile the operational denominator
Use accepted and completed orders consistently. Show cancelled, refunded and failed-payment orders separately. For delivery, include journey and waiting time; for collection, include handover and no-show cost. If a channel requires manual re-entry or a dedicated tablet, record the labour and failure risk.
Document the decision
State whether the decision concerns pricing, promotion, capacity, supplier negotiation or channel closure. A profitability report should lead to a controlled action and review date, not a permanent ranking that ignores changes in commission, food cost or customer behaviour.
Include confidence and data quality
Rate each comparison as high, medium or low confidence based on matching, fee detail and cost evidence. A channel with incomplete refund or labour data should not be declared the winner. List the missing evidence and rerun the decision after it is obtained.
Present raw counts
Show order count, sales, refunds and contribution beside rates. Percentages from a small sample can create a false ranking, especially for a newly launched channel.
Related guides
- Payments — the main guide for the wider topic.
- Channel Profitability — the broader guide that frames this implementation.
- Pricing Strategy for Online Orders — a closely related operational control to review alongside this page.
- How to Calculate Contribution Margin by Ordering Channel — a closely related operational control to review alongside this page.
Sources and date checked
Guidance checked: 24 July 2026. Recheck official guidance, local requirements and supplier documentation before changing a live operation.
Operational, legal and platform requirements can change. Recheck official guidance and supplier documentation before altering a live service.
Related practical guides
PaymentsChoosing a Payment Gateway for Online OrdersThe cheapest quoted transaction rate is not necessarily the cheapest gateway for a takeaway. A payment service that creates duplicate charges, de…Read guide →
PaymentsChargeback Management for RestaurantsA chargeback is not the same as a customer asking the restaurant for a refund. It is a card-scheme dispute raised through the customer’s card iss…Read guide →
PaymentsHow to Reconcile Online Orders, Payments and RefundsReconciliation is the process of proving that the orders fulfilled by the takeaway agree with the payments taken, refunds issued, provider statem…Read guide →
PaymentsHow Marketplace Payments WorkA marketplace order can appear simple to the restaurant: a ticket arrives, food is prepared and a net payment arrives later. Behind that process …Read guide →
Restaurant AppsCustom-Built Restaurant AppsA custom app is justified when the business has a valuable requirement that available platforms cannot meet and can fund the product throughout i…Read guide →
Online OrderingHow to Handle Busy PeriodsA busy period becomes damaging when orders enter faster than the kitchen, packing area or delivery operation can complete them. The solution is n…Read guide →Connect customer ordering with operations and profit
Use the wider guide library to check the menu, kitchen, fulfilment, payment and financial implications of each decision.
Browse all practical guides