Skip to content
Integrations

Everything that needs to talk to your till

Delivery platforms, accounting software, the payment gateway, the marketplace, and a partner API — into one order queue and one set of books.

The ten platforms connected today

  • Jahez
  • HungerStation
  • Keeta
  • Talabat
  • Noon Food
  • Mrsool
  • Ninja
  • The Chefz
  • ToYou
  • Carriage
  • Jahez
  • HungerStation
  • Keeta
  • Talabat
  • Noon Food
  • Mrsool
  • Ninja
  • The Chefz
  • ToYou
  • Carriage
Six directions

What comes in, and what goes out

Delivery platforms

Ten Saudi platforms pushing their menus out and landing their orders in one queue on your till — with no tablet-per-platform on the counter.

The detail

Accounting software

Qoyod, QuickBooks Online and Xero over OAuth2, with manual or scheduled export, account mapping and a full export history.

The detail

The payment gateway

EdfaPay with a merchant account per branch, signed webhooks, and full or partial refunds — settling into your own account.

The detail

The Thawani marketplace

Publish your catalogue onto an existing marketplace, take its orders in the same order screen, and reconcile its settlements.

The detail

The partner API

Per-store keys with a fixed ability catalogue, HMAC-signed webhooks, and an OpenAPI document with a reference rendered from it.

The detail

The app marketplace

Installing mints a partner key with exactly the abilities you consented to; uninstalling revokes it. There is no second permission system.

The detail
Delivery

Ten platforms, one queue

Each platform carries its own credentials per branch, receives the menu, availability and opening hours, and gets its status back in real time.

  • Jahez
  • HungerStation
  • Keeta
  • Talabat
  • Noon Food
  • Mrsool
  • Ninja
  • The Chefz
  • ToYou
  • Carriage
  • Ten platforms: Jahez, HungerStation, Keeta, Talabat, Noon Food, Mrsool, Ninja, The Chefz, ToYou and Carriage
  • Menu sync outbound — pushing the catalogue (Arabic and English names, prices, images, availability) to each platform through its merchant API
  • Stock availability sync — a product going out of stock is marked unavailable on every connected platform automatically
  • Order ingestion — new orders arrive by webhook or polling and are converted to a local order
  • Order status push — the status goes back to the platform as the order moves through preparation
  • Auto-accept or manual accept, configurable per platform
  • Per-platform, per-branch credentials — API keys, merchant IDs and webhook secrets
  • Operating-hours sync — pushing opening and closing times, with an automatic pause when the store closes
  • Order throttling — a cap on delivery orders accepted per time window, so the kitchen is not swamped
  • Commission tracking per order per platform, for financial reconciliation
  • A unified dashboard of every delivery order across every platform
  • Aggregator driver tracking inside the same order screen
Payments

Two rails, kept completely apart

Confusing them is the most expensive misunderstanding available, so it is written out here.

Your sales — EdfaPay

The customer pays into your own merchant account. Wameed never takes custody of the funds and is not a payment institution — its income is a published revenue share only.

Your subscription — PayTabs

You pay Wameed. This rail never touches your customers’ sales, and the two never meet at any point.

Need something not on this list?

The partner API is open, with webhooks and full documentation — or ask us to build it.