Services · Ecommerce development · Courier booking sites
Courier booking website development Saudi Arabia operators can scale on has to cope with more than one city. We build the website that quotes, schedules and takes payment for parcel and courier services across several regions: local deliveries inside each city, intercity transfers between hubs and business accounts that ship nationally. Pricing, collection windows, refunds and invoices follow national rules, while each city keeps its own zones and capacity. The result is one platform, in Arabic first, that your customers trust and your finance team can reconcile.
The scope here is the customer facing booking and payment website and the admin behind it. Driver and hub apps are separate products; this site is where paid demand is created and controlled. It is also the main source of data for your finance and planning teams.
200+ companies servedFrom a first store to an ADX listed developer
What the national platform covers
Running a courier brand in several Saudi cities creates a tension. Customers in Riyadh, Jeddah, Dammam, Makkah or Abha expect a site that feels local: their districts, their delivery times, their language. Your finance and compliance teams need the opposite: one set of tax rules, one gateway, one refund policy and one data protection regime. The courier online booking system development Saudi Arabia operators need resolves that by separating national settings from city settings. National rules cover VAT, invoicing, payment methods, privacy and terms. City settings cover zones, collection windows, cut off times and capacity. Intercity lanes connect the two. Every capability below is built on that split, so adding a new city becomes a configuration task rather than a new project.
Each city has its own zones, pricing bands, working hours, holiday rules and capacity per window, managed by a city lead in the admin. New cities are cloned from an existing template and adjusted, so launching in Tabuk or Abha uses the same booking engine as Riyadh. City leads can only change their own city.
Expansion is a configuration exercise, not a rebuild.
Customers sending between cities choose a lane, such as Riyadh to Dammam, and a service level. Prices come from a lane table by weight and size, transit times show realistic delivery days, and capacity per departure stops overselling when a hub is already full. Drop off at a hub or collection from the sender's door are offered as separate options.
Intercity promises match what your linehaul can deliver.
Addresses are captured using the Saudi National Address format, including the short address code, with a map pin as a fallback. Where you have access to address verification services, the site checks the address before payment so failed deliveries from bad data drop sharply.
Fewer parcels return to a hub undelivered.
Checkout supports mada, Visa, Mastercard, Apple Pay and STC Pay through a SAMA licensed gateway. Business customers paying larger invoices can use SADAD where your billing provider supports it. Tabby or Tamara instalments can be offered on bigger shipments, subject to provider approval.
Customers pay the way they already pay elsewhere in the Kingdom.
Every paid booking and account statement passes complete seller, buyer, VAT and line item data to your Fatoora compliant e-invoicing or ERP system. Simplified invoices for consumers and standard tax invoices for VAT registered businesses are handled as separate flows.
Invoices are correct first time across every city.
Companies shipping from several branches get one account with branch level bookers, address books, spending limits and a single consolidated statement. Account holders can be verified through company registration details, and through Nafath where your organisation is approved to use it.
National clients deal with one account, not one per city.
One refund policy applies nationally, with city level cut off times. Deposits can be required for bulky or high value jobs. Refunds go back through the gateway with approval levels, so a city manager can refund small amounts and larger ones go to finance.
Refunds are consistent and controlled across branches.
Online sellers using Salla, Zid, Shopify or WooCommerce book many shipments at once through spreadsheet upload or a store connection. Each booking draws from a prepaid wallet, and return or failed delivery charges post automatically to the merchant statement.
Merchant volume arrives in bulk, already paid.
Head office sees revenue, bookings, cancellations and refunds by city, lane and service, with capacity use per window. City teams see only their own figures. Data exports feed your BI tools for deeper analysis. Alerts flag cities where cancellations or refunds rise unusually.
Management can see which cities and lanes earn their keep.
Role based admin access per city, audit logs, data retention rules and a published privacy notice that reflects the PDPL. Hosting location and NCA control requirements that apply to your organisation are designed in, and card data stays with the gateway.
Compliance is part of the build, not a later audit finding.
Who this is for
Saudi courier companies reach a national footprint in different ways. Some grow city by city from a home base, some start national because a large merchant or corporate client demands it, and some are new licence holders building their first public site. The booking website has to suit the stage you are at and the shape of your network. These four situations are the ones we see most often across the Kingdom. Many operators move through several of them over a few years, and the platform is designed to follow.
You have a working operation in one city and are opening in others. The priority is a city template you can copy, with local pricing and capacity, and a national checkout and invoicing setup that does not change as you grow. We often launch in your home city first, then add each new city as its hub opens. Each new city inherits the national checkout, refund policy and invoice feed, so finance never has to learn a second process. City pages launch with local content written for search, not copied from the first city.
Rollout order is agreed city by city during discovery.
If your current booking site was built for one city and has been stretched to cover several, prices and rules drift between branches. We rebuild on a clean national and city split, migrate customer accounts and saved addresses, and redirect old booking pages so search traffic and repeat customers are not lost. Old booking references and account balances are carried across, and staff are trained city by city as each moves onto the new platform.
National clients want one account, branch level control, consolidated invoices and integration with their own systems. We build account features first, including bulk booking and store connections, and add public consumer checkout once account customers are settled on the new platform. Account features usually include approval rules, so a branch booker's order above a set value waits for a manager before it is accepted and charged.
Companies that have secured their licence from the Communications, Space and Technology Commission need a credible booking site from day one. We build a focused first release with quoting, booking, payment and invoicing, designed to accept more cities, lanes and account features later without starting over. The first release is designed with your licence conditions and service list in mind, so nothing is sold online that your licence does not cover.
A focused first release gets paying customers sooner.
How we work together
A fixed scope project suits the core platform and the pilot city. After that, many operators keep a retainer to configure new cities, lanes and services as the network grows. Larger groups sometimes take a dedicated team that stays with the platform for an extended programme. We can meet in person at our Riyadh office; teams elsewhere in the Kingdom work with us by video call. Codeeo has delivered 200+ projects across the UAE and the US with a team of 80+ across Dubai, Riyadh and Karachi, and holds a 4.7 rating from 23 Google reviews.
A defined build with a deadline
We agree what the product has to do, write it down with a price and a date, and build exactly that. Changes are priced before they are made, not discovered on the invoice.
A product that keeps evolving
Named engineers who work your hours, join your standups and stay on the codebase. You direct the backlog; we own the quality of what ships.
Something live that needs looking after
A monthly block of hours for improvements, fixes and the small requests that otherwise wait months. Unused hours carry for a quarter.
Technology
For a multi city network we usually recommend a headless front end over a custom booking and pricing service, connected to your dispatch, ERP and gateway through APIs. The admin lets city and head office teams manage their own settings without code. We favour tools your own developers or a future partner can maintain.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
City level booking, intercity lanes and national payment and tax rules.
Each city needs its own zones, windows and capacity. Lanes between cities need their own prices and transit times. Across all of them sit national rules: Saudi payment methods, ZATCA compliant invoicing, PDPL privacy and the disclosure expectations of the e-commerce law. A good platform keeps those layers separate so a change in one city never breaks another. Seasonal settings such as Ramadan hours or pilgrimage season limits in Makkah and Madinah are handled at city level.
Schedule a free consultation and get a written recommendation, with costs, before you commit to anything.
Get in touchPROVEN RESULTS
React
Next.js
TypeScript
Node.js
Laravel
WordPress
Shopify Plus
WooCommerce
BigCommerce
PostgreSQL
MySQL
MongoDB
AWS
Azure
Docker
GA4
Google Tag Manager
Search Console
Meta Pixel
Looker Studio