*Hero image: delivery order preparation; Unsplash stock source.*
## Revenue is not the same as contribution
Two delivery channels can produce the same sales value and very different profit. One may charge a higher commission, require funded promotions and generate more refunds. Another may deliver a smaller basket but retain more revenue through direct ordering and lower fulfilment cost.
Many GCC operators still compare channels using gross sales, order count or average order value. Those measures are useful, but they do not answer the commercial question: after the costs caused by this order are removed, how much does the channel contribute to the business?
Contribution margin gives the operator a cleaner view without pretending that every fixed cost can be allocated perfectly to each ticket.
## Build a channel margin waterfall
Start with the order value actually paid by the guest. Then show the deductions in a fixed sequence:
1. customer-funded and restaurant-funded discounts;
2. aggregator commission or marketplace fee;
3. payment processing and settlement charges;
4. refunds, remakes and service-recovery credits;
5. packaging and order-specific consumables;
6. delivery cost, including rider, fleet or third-party fulfilment cost;
7. variable food and production cost.
The result is the contribution margin for the order. Report both the amount and the percentage. A high-value order with a low contribution percentage may need attention just as much as a small order with a negative contribution.
*Section image: channel performance review; Unsplash stock source.*
## Separate channel economics from customer behaviour
Do not blame the channel for every weak order. The same aggregator can contain profitable family bundles, low-margin single items, discount-led orders and distant deliveries. Segment the report by channel, branch, zone, daypart, basket type and promotion.
Then compare like with like. A direct order from a nearby customer should not be compared only with a marketplace order travelling across the city. Review delivery distance, promised time, basket composition and refund history alongside fees.
The operator should be able to answer practical questions: Which channel brings profitable first orders? Which one has the highest refund rate? Which zones become unattractive after delivery cost? Which promotions create extra contribution instead of moving orders that would have arrived anyway?
This builds on, but is different from, a simple [delivery zone profitability](https://unidiner.ai/delivery-zone-profitability-gcc-restaurants-order-growth/) review. The zone view explains where to deliver. The contribution waterfall explains what the order leaves behind after all variable deductions.
## Reconcile the report with settlement data
Marketplace dashboards and bank settlements do not always use the same dates or definitions. A refund may be recorded when approved but deducted later. A promotion may appear as a discount in one report and a marketing adjustment in another. Payment fees may be netted from the settlement rather than shown on the order.
Set a weekly reconciliation between order-level data, channel statements and bank receipts. Use the same controls covered in [restaurant cash and card settlement reconciliation in MENA](https://unidiner.ai/restaurant-cash-card-settlement-reconciliation-mena/), adapted for delivery marketplaces and direct payment providers.
Keep a reason code for each adjustment. “Refund”, “missing item”, “late delivery”, “duplicate charge” and “promotion funding” should not become one generic deduction. Clear reason codes help operations fix the cause and finance validate the settlement.
*Section image: payment and settlement control; Unsplash stock source.*
## Use the view to make channel decisions
Contribution reporting should lead to decisions, not just a prettier dashboard. An operator may reduce a promotion in a zone where it creates negative contribution, change the minimum basket, adjust a delivery radius, redesign packaging or move repeat customers towards direct ordering.
Do not remove a channel because one week is weak. Use a rolling view and identify whether the issue is structural or campaign-specific. Set thresholds for investigation, such as negative contribution after refunds or a sudden rise in settlement deductions. Let managers see the underlying orders so the response remains operationally realistic.
For multi-branch groups, central teams should set the definitions while branches explain exceptions. A connected platform can combine POS, online ordering, delivery and reporting data in one place. Start with [Unidiner online ordering](https://unidiner.ai/online-ordering/) and [reports and analytics](https://unidiner.ai/reports-analytics/). For implementation or wider systems advice, see [Tradify Services](https://tradifyservices.com/).
The strongest delivery strategy is not the one with the most orders. It is the one that creates repeatable contribution after the real costs of fulfilment are visible.