Skip to content
U-Dispatch

What it does today

A tour of what is built, surface by surface. Nothing on this page is a roadmap item.

Catalogue

Restaurants, categories and dishes, with the structure a real menu needs rather than a flat list.

  • Option sets and add-on groups, priced per choice
  • Two-level categories, so navigation matches the menu
  • Discounts that cascade dish → sub-category → category → restaurant
  • Bulk import and export of a menu as a spreadsheet
  • Everything named in Arabic and English at once

Ordering

From basket to delivered, including the paths that are not the happy one.

  • Guest baskets that survive signing in
  • A quote before the order — every fee and tax visible up front
  • Delivery, take-away and scheduled orders
  • Cancellations, refunds and offline payment proof
  • A counter POS for orders that never touched a phone

Delivery areas

Coverage is drawn, not typed. Zones are real polygons on a map, and an address either falls inside one or it does not.

  • Polygon editor on an open map — no map billing account
  • Active zones may share a border but never overlap
  • Delivery fees and rules per zone
  • A coverage check any client can call before checkout

Dispatch

Getting an order onto a rider, and knowing where it is afterwards.

  • Offers cascade by proximity and current load
  • A rider who declines is never offered the same order twice
  • Manual assignment from a live board when someone has to intervene
  • Live rider positions over websockets
  • Shifts, availability and delivery proof

Money

A double-entry ledger, not a set of totals — see the home page for what that buys.

  • Commission, delivery fee and tip settled per order
  • Rider cash on hand, collected per order or swept per day
  • Payout cycles with a statement behind every line
  • Customer wallets, top-ups and refunds
  • Expenses recorded against the same accounts

Integration

The platform is the system of record, and it can still speak to the ones you already run.

  • A signed, retried outbox — no fire-and-forget webhooks
  • Records synced from a provider are locked locally
  • A documented API for your own apps and partners

What is included, and what is granted

Most capabilities are switched on for every workspace. A few are granted per operator — the plans page lists exactly which.

See the plans →