Services · Ecommerce development · QR ordering marketplaces

Table ordering platforms that let many Riyadh kitchens sell through one scan.

Codeeo provides QR menu ordering website development in Riyadh for destination operators, office campus food halls and founders building a table ordering marketplace. A guest scans the code at a shared table, orders from one counter or several, pays once with mada or Apple Pay, and every kitchen receives only its own ticket. Your side of the platform verifies each vendor, holds back your commission, settles payouts and resolves refunds, all in Arabic and English.

This is the paid platform where several sellers share one checkout. A single restaurant that only wants a readable menu without payment needs something simpler, and a separate page covers that. Here the work is the money: who collects it, who invoices it for ZATCA, and how each vendor gets paid correctly after a busy Thursday night.

Built for
Entertainment and leisure destination operators, tower and campus F&B managers, mall food hall owners and marketplace founders serving Riyadh venues.
Typical timeline
The payment model, vendor rules and pilot venue are fixed during discovery in Riyadh, then each phase gets a written date before work on it starts.
What you own
The platform code, the admin consoles, all vendor and order records, and the merchant account with your payment provider, held in your company's name.
Rated
4.7 / 5 from 23 Google reviews

200+ companies servedFrom a first store to an ADX listed developer

Modon
Majid Al Futtaim
HP
Belkin
Dulsco Group
OneClickDrive
Hanayen
HMS
Clocksprings
Ghezlan

What the platform handles

Everything between the scan at the table and the vendor's bank transfer.

Riyadh has a growing number of places where many food brands trade under one roof: leisure districts that fill up during Riyadh Season, food halls in new office towers around KAFD and Olaya, and family venues where groups order from four counters at once. The guest sees a menu and a pay button. The operator sees vendor contracts, commission rates, VAT, card fees, refunds and a payout file that must match the bank to the halala.

Restaurant ordering platform development in Riyadh is mostly back office work that guests never notice. We design the guest ordering pages, the vendor portal and the operator console as one platform, so a rule set in one place applies everywhere. Anything that moves money is agreed with your finance lead before it is built. The list below is what a multi vendor ordering platform in Riyadh usually needs at launch or soon after; discovery decides what ships first and what waits for a second release.

Explain your project
  • Zone and seat aware codes

    Each printed code knows the venue, the seating zone and the table, including family sections and outdoor terraces. Runners see exactly where to deliver, and the operator can move codes between zones when a layout changes for an event weekend without reprinting anything.

    Food reaches the right seat in a crowded hall.

  • Shared basket, split tickets

    Guests add a shawarma from one vendor and a specialty coffee from another into one basket and pay once. The platform splits the order into separate kitchen tickets, keeps each vendor's modifiers and preparation times, and issues a receipt that names every seller.

    One payment for the guest, clean sales records for each brand.

  • Checkout for Saudi wallets and cards

    mada debit cards, Apple Pay, STC Bank (formerly STC Pay) and international cards through a payment provider licensed by SAMA, with card details tokenised by the provider rather than stored by you. Venues that want it can keep a pay at counter option for guests who prefer cash.

    Payment in a few taps with the methods Riyadh guests carry.

  • Vendor verification

    Vendors apply online with their commercial registration, municipal licence from Balady, VAT number where they are registered, and an IBAN for payouts. Your team checks each file, requests anything missing and approves the vendor before a single dish appears on a menu.

    Only licensed kitchens can take orders through your platform.

  • Commission and settlement rules

    Commission by vendor, by category or by venue, with promotional rates for an opening month. The platform deducts commission and agreed fees, then produces a settlement statement per vendor and a payout file your finance team approves before transfer.

    Vendors see how every riyal of their payout was calculated.

  • Invoices that suit ZATCA

    Simplified tax invoices for guests and commission invoices to vendors, generated in the format your e-invoicing solution needs for Fatoora. Who issues which invoice depends on your marketplace model, so we build to the structure your tax adviser signs off.

    Invoicing that stands up when ZATCA asks questions.

  • Refunds and dispute desk

    A wrong item, a cold dish or a double charge becomes a case with the order, the vendor and the payment attached. Staff can refund one line or the whole order, and the cost lands on the vendor or the operator according to the rule you set.

    Complaints settled on the night instead of argued at month end.

  • Ratings and vendor scorecards

    Guests rate each vendor after the meal, and the operator sees preparation times, refund rates and ratings side by side. Reviews pass moderation before they appear, so one angry message does not sit on a vendor's page unchecked.

    Evidence for lease and contract conversations with vendors.

  • Peak night controls

    During a concert or a Riyadh Season weekend the operator can throttle a slow kitchen, hide items with long waits, cap orders per time slot and send ready alerts to the guest's phone so queues do not form at the counters.

    The platform stays calm when the venue is full.

  • Corporate and group billing

    Companies in a Riyadh tower can open an account, load a monthly allowance for staff meals and receive one consolidated invoice. Employees order with their work email, the allowance is drawn first, and anything above it goes to the employee's own card. HR sees usage without seeing what anyone ate.

    A steady weekday revenue stream for vendors near office districts.

Who this is for

Four kinds of Riyadh operator we build these platforms for.

A multi vendor ordering platform only makes sense when someone sits between the guest and several kitchens and needs to control the money. In Riyadh that is usually a destination owner, a building owner or a company whose product is the platform itself. If you run one restaurant with one kitchen, a simpler ordering site will serve you better, and we will say so in the first conversation. Good QR menu ordering website design in Riyadh also respects how people actually sit: family sections, mixed groups at long tables and guests who expect to pay separately.

01

Leisure and entertainment destinations

Districts and venues that host dozens of food brands, with crowds that peak on weekends and during seasonal events. The platform has to onboard pop up vendors quickly, cope with sudden spikes, and let the operator see sales per brand in real time. We plan for event nights from the first workshop, because a slow checkout in front of a full venue is remembered.

Temporary vendors can be given a start and end date.

02

Office towers and business campuses

Food halls serving people who work in the tower and have a short lunch window. Ordering from the desk or the lobby table, collection slots, and company accounts that let an employer subsidise meals all fit here. The guest is a regular, so saved preferences and quick reorder matter more than browsing.

Corporate billing can sit alongside personal card payments.

03

Founders building a table ordering marketplace

If the platform is your product and you sign up cafés and restaurants across Riyadh, you need vendor self onboarding, plan management, onboarding checks and payouts that scale before the sales team does. We build the first version so it can be sold to the tenth venue without a rebuild, with the admin tools your support staff will live in.

04

Hospitality groups with several concepts

A group running a café, a grill and a dessert counter in the same building, each with its own commercial registration, can let guests order across all three while keeping separate books. This is a marketplace in structure even when one owner sits behind every brand. The operator console still shows the group view, so the owner can compare brands, move a busy item between kitchens or close one counter early without affecting the others.

Six stages from a site walk in Riyadh to a platform paying vendors.

  1. 01Site walk and discoveryWe visit your venue in Riyadh, watch a service, map seating zones and kitchens, and agree who the vendors are, who collects payment and what the operator must control.
  2. 02Money flow designCommission, fees, refunds, VAT and payout timing are drawn as one diagram and agreed with finance and your tax adviser before any screen is designed.
  3. 03Arabic first designGuest pages, vendor portal and operator console are designed right to left first, then mirrored for English, and tested on phones in real venue lighting.
  4. 04Build and integrationsOrdering, checkout, payment provider, kitchen printers or screens, point of sale links and invoicing are built in short cycles you review every two weeks.
  5. 05Pilot with a few vendorsA small group of vendors trades on the platform on quieter days first, so settlement, refunds and kitchen flow are proven before the busy weekend.
  6. 06Rollout and supportThe remaining vendors are onboarded in batches, staff are trained, and we stay on support with monitoring for payments, printers and order delays.

Technology

What we build this with.

Guests use a fast web app that opens in the browser after the scan, so nobody installs anything. The platform runs on cloud hosting that can sit in a Saudi region if your data policy asks for it, with documented APIs for payments, kitchen hardware and accounting so another developer could maintain it later. Security controls follow the NCA Essential Cybersecurity Controls where your contracts require them.

01Web

  • React
  • Next.js
  • TypeScript
  • Node.js
  • Laravel
  • WordPress

02Commerce

  • Shopify Plus
  • WooCommerce
  • BigCommerce
  • Headless storefronts

03Data and cloud

  • PostgreSQL
  • MySQL
  • MongoDB
  • AWS
  • Azure
  • Docker

04Marketing and tracking

  • GA4
  • Google Tag Manager
  • Search Console
  • Meta Pixel
  • Looker Studio

Questions Riyadh operators ask before building table ordering.

It depends mostly on the payment model and how many integrations the first release needs.

A platform for one venue using a payment provider that already supports split settlement moves faster than one where you collect funds and pay vendors yourself. Point of sale links, kitchen hardware and invoicing integrations each add time. We agree the scope of the first release in discovery, break it into phases, and give each phase a date in writing before it starts, so you are never guessing.

Tell us what the business needs. We will tell you what to build first.

Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.

Get in touch

PROVEN RESULTS

4.7 / 5from 23 Google reviews