Services · Ecommerce development · Maintenance booking sites
Codeeo provides home maintenance booking website development in Saudi Arabia for repair, servicing and cleaning companies that sell in more than one city, or plan to. One platform sells your services, shows live availability in each city, takes payment through Saudi methods, issues ZATCA compliant invoices and handles cancellations and refunds under the rules of the Saudi e-commerce law. National requirements are solved once, so opening a new city is a matter of adding crews and areas, not building another website.
We focus on the commercial side of the business: selling the visit, collecting the money and keeping the promise of a time slot. Dispatch, stock and payroll tools stay where they are and receive clean, paid bookings from the site through their APIs.
200+ companies servedFrom a first store to an ADX listed developer
What the platform covers
A maintenance brand selling online in Saudi Arabia answers to the same set of national rules wherever its customers live. The Ministry of Commerce expects online sellers to identify themselves, describe what they sell, show full prices and explain cancellation and refund terms. ZATCA requires VAT invoices to follow the Fatoora e-invoicing rules. SDAIA enforces the Personal Data Protection Law, which became fully enforceable in September 2024. Payments run through SAMA regulated providers, and the NCA sets the cybersecurity controls many organisations are expected to follow.
Home maintenance online booking system development in Saudi Arabia means building those requirements into the core of the platform, then letting each city run its own crews, slots, services and seasonal patterns on top. The capabilities below are grouped that way: national foundations first, then the tools that let regional teams run their own diaries.
Business identity, commercial registration details, service descriptions, VAT inclusive prices, cancellation windows and refund timelines appear where the e-commerce law expects them. We also prepare the information you need for registering the online store with the Ministry of Commerce, which your company completes in its own name.
Customers in every city see the same clear terms before they pay.
Home maintenance online payment integration in Saudi Arabia starts with mada, then Apple Pay, Visa and Mastercard and STC Bank (formerly STC Pay), all through a SAMA licensed gateway. Tabby and Tamara cover instalments on installations, and SADAD suits corporate and landlord accounts that settle by bill payment.
One checkout that works for households and companies in every region.
Every booking, extra charge and refund produces the right VAT document, a tax invoice, a simplified invoice or a credit note, following ZATCA e-invoicing rules. Where your ERP is already integrated with ZATCA, the site passes transactions to it instead of issuing invoices itself.
Finance closes each month on one set of numbers for the whole country.
Customers enter a short National Address code or drop a map pin, and the platform resolves which city and service area the booking belongs to. Each region's team only sees bookings in its own areas, and technicians get a precise location rather than directions by phone.
Bookings land with the right regional team on the first attempt.
A coastal city may need corrosion checks and condensate cleaning, Riyadh may need dust season filter offers, and a newer city may only have servicing at launch. Each city has its own service list, prices and slot lengths, managed by its regional manager inside national rules.
Local teams adjust their offer without touching other cities.
Slots respect the Friday and Saturday weekend, prayer times by city, Ramadan evening schedules and public holidays. Dates can be shown in the Hijri and Gregorian calendars, and the schedule for each city updates without anyone editing slots by hand.
Customers are never offered a time your crews would not work.
Property managers, landlords and companies opening an account with credit terms can verify their identity through Nafath before their first booking. Their users, approval limits and VAT details are held on the account and apply in every city they book in.
Credit is extended to verified customers, not to anonymous forms.
Regional managers see their own bookings, capacity, cancellations and refunds; head office sees the whole country side by side, with revenue by city and service. Exports feed your accounting system and any reporting tools your management already uses.
Decisions about the next city are based on booking data, not guesses.
Where you cover a city through an approved local contractor, that partner receives bookings for its area through a limited portal, while payment is still taken centrally on your site. Commission and payouts are calculated per booking and visible to both sides.
Your brand reaches cities where you do not yet employ crews.
Cancellations and refunds follow one national policy published at checkout, whatever city the customer is in and whichever method they paid with. The platform returns money to the original card or wallet, handles instalment plan reversals with Tabby or Tamara, and issues the matching credit note without a regional team touching it.
Refunds are consistent across the country and easy for finance to reconcile.
Who it is for
A national booking platform is a larger commitment than a single city site, and not every business needs one on day one. We usually recommend it when a company already operates in two or more cities, has a firm plan to expand, or sells under a brand that customers recognise across the Kingdom. For a business serving one city only, we will say so and suggest a smaller first release that can grow later. The platform is planned so that a smaller start can become the national version without a rebuild.
Your systems were built for one city, and the second city is running on spreadsheets and a separate phone line. We move both onto one platform with per city services and capacity, a single checkout and national invoicing. When the third city opens, it is set up in the admin rather than in a new project. Customer accounts and history move across, so existing customers keep booking without noticing the change.
We usually launch the existing city first, then add the new ones in sequence.
You sell air conditioners, water heaters or filtration systems, and customers across the country want installation and servicing booked with the purchase. We build a booking site that sells visits by product model, routes each one to your own crews or authorised contractors, and records warranty details against the customer's address. Customers who bought from a retailer can register the product and book their first service from the same page.
You already maintain offices and compounds under contract and want to sell directly to households in the cities you cover. We build a consumer storefront with fixed price services and online payment that draws on the same crews, while your contract clients continue under their existing arrangements.
Keeping consumer and contract work apart in pricing, not in the calendar, avoids double booking.
Your brand is run by different operators in different cities. Each needs its own diary, its own payouts and its own reporting, while customers see one national brand and one checkout. We build franchise level access, central payments with per operator settlement and brand controls so the experience stays consistent everywhere. New operators are onboarded through the admin, with their areas, crews and payout details checked before they go live.
How we engage
National platforms usually begin as a fixed scope project covering the core and the first city, followed by rollout releases for each additional city. Many clients then keep a dedicated team, a stable group of designers and engineers who know the platform and handle new cities, services and integrations. Smaller operators preparing to expand often prefer a monthly retainer instead. In person workshops are available at our Riyadh office; teams in other cities join by video call. Scope, acceptance tests and sign off are agreed for each release before work begins.
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
We select technology for scale and for the systems you already run: a fast, multilingual front end, a booking and payments back end that can handle several cities and brands, and integrations with ERP, accounting and field tools through their APIs. Page speed is checked on typical mobile connections before launch, since most bookings start on a phone.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
We fix dates after discovery, usually with one launch city followed by staged rollouts.
The national foundations, payments, invoicing, compliance and the booking engine, take the most effort and are built once. The first city goes live with them. Each additional city is mostly configuration, training and testing, so it moves much faster. We write the plan with a date for the core release and a date per city, and adjust only with your agreement. Seasonal peaks also shape the order, since few teams want to learn a new system in the hottest weeks of the year.
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