Connect every channel. Then make the money agree.

Salla and ZID for Saudi Arabia, Shopify, WooCommerce, Magento and BigCommerce internationally, plus Odoo's own eCommerce if you would rather not run a separate storefront. Marketplaces include Noon, Amazon.ae, Amazon.sa and Namshi.

This is the hardest problem in GCC e-commerce and the one most integrations ignore. The courier collects cash, holds it, deducts their fee, and remits days or weeks later in a lump sum covering hundreds of orders. We match each remittance line back to the originating order, post the courier fee separately, and flag anything uncollected or short-paid. Without that, COD revenue sits unreconciled for months.

Yes, and it matters more than people expect. Gateways settle net of fees, on their own cycle, batching many orders into one bank credit. We match the settlement to the underlying orders, post the fee to its own account, and surface discrepancies — chargebacks, refunds and failed captures — rather than letting them quietly distort your margin.

Aggregators pay in batches, net of commission and net of your share of any promotional discount, and they deduct cancellations from the next cycle rather than the current one. The payout therefore never matches the period's orders. We give each platform its own clearing account and analytic account, post commission and promotional share per order rather than as a period-end lump, and reconcile the settlement across cycles. The residual balance is the amount genuinely in dispute, and it is visible daily instead of at month end.

It gets logged, retried, and escalated to a person. An integration that fails silently is worse than no integration, because you carry on trusting numbers that stopped updating. Every connection we build has error handling and an alert path.

That is the point of doing it properly. One catalogue, one stock number, allocated across channels according to rules you set. It prevents the classic failure where the same last unit sells simultaneously on Salla, Noon and the shop floor.

Where the bank supports it. Several UAE and Saudi banks offer feeds that pull transactions automatically. Where they do not, we set up structured statement imports so reconciliation is still a review rather than re-keying.

A single storefront connection is usually two to three weeks. Payment gateway with settlement reconciliation, two to four. COD remittance matching, three to five, because the courier file formats vary and need mapping. Marketplaces depend on the platform's API maturity.

If it has an API, it can almost certainly be connected. We have built against documented APIs, undocumented ones, and in a few cases scheduled file exchanges where that was all the vendor offered.

Yes. Jahez, HungerStation, Talabat, Deliveroo, Careem, Noon Food, ToYou, Chefz and Marsool. Orders flow into Odoo with item-level detail, menus and pricing sync outward, and outlet availability updates in real time. For multi-brand cloud kitchens we map outlets and brands so reporting works by both.

Posted per order to its own account rather than netted off silently. Promotional discounts are split according to the campaign terms, cancellations and rider fees allocated separately. The result is that net margin by platform and by menu item is a report you run, not a reconstruction someone attempts at month end.

Yes. Brands map to analytic dimensions and outlets to locations, so a single kitchen producing for four brands across three aggregators still reports cleanly by brand, by platform and by outlet. This is a common GCC pattern and it works well once configured deliberately.

The provider pays you upfront and collects instalments from the customer, so settlement timing and the merchant fee behave differently. Revenue should be recognised at order approval, the fee posted separately, and the settlement matched as its own event. Getting this wrong overstates margin and distorts cash flow forecasting.