Services · Ecommerce development · School course and enrolment sites
Codeeo delivers school course selling website development in Saudi Arabia for school groups, international school brands and education companies that sell programmes across several cities. Summer schools, exam preparation, language and Quran programmes, clubs and recorded courses sit in one catalogue with storefronts per region or campus. Checkout takes the payment methods Saudi parents use, invoices meet ZATCA rules, and learner data is handled under the Personal Data Protection Law from the first form onwards.
Selling courses nationally adds problems a single school never meets: several legal entities, campuses with different calendars, regional demand and national rules that apply to every sale. The platform is built to handle those once, centrally, so each campus can simply sell.
200+ companies servedFrom a first store to an ADX listed developer
What the platform includes
A group running campuses in Riyadh, Jeddah, the Eastern Province and smaller cities faces the same national requirements in every sale. Payments go through gateways licensed by SAMA. Tax invoices must follow ZATCA's e-invoicing rules through Fatoora. Personal data, especially children's data, falls under the PDPL enforced by SDAIA. Online selling falls under the e-commerce law administered by the Ministry of Commerce, and e-learning programmes that issue certificates may need a licence from the National eLearning Center.
Building these into each campus website separately leads to six different checkouts and six different interpretations of the rules. We build them once, at group level, and let each campus manage its own catalogue, teachers and timetable on top. Head office sees every enrolment in the Kingdom; a campus registrar sees only their own. These are the parts of the platform we usually deliver. Arabic leads every screen with right to left layouts, and English versions follow for international families and brands.
One platform serves several storefronts: by city, by campus or by brand where the group runs more than one. Parents see courses near them first, and shared programmes such as online exam preparation appear in every storefront with a single seat pool. Storefronts share one design system, so a new city launches quickly.
Each region sells locally while head office keeps one system.
mada, Apple Pay, credit cards and STC Bank (formerly STC Pay) through a SAMA licensed gateway, with Tabby and Tamara instalments where those providers accept course payments. Groups with several legal entities can route each campus's payments to its own merchant account. Failed payments release held seats after a short window, in every region.
Parents pay the way they already pay, and money lands in the right entity.
Every payment, refund and credit note produces an e-invoice that meets ZATCA's requirements, generated through Fatoora integration for each legal entity. The VAT treatment of each course type is configured with your tax adviser rather than assumed by the developer. Invoice numbering and archives are kept separately for each entity.
Tax records stay correct across every campus and every refund.
Guardian consent is captured per purpose and per child, with records the group can produce if SDAIA asks. Hosting is planned with you, inside the Kingdom where your policy requires, and any transfer of data abroad, for example to an overseas learning tool, is reviewed before launch.
Child data handling the group can explain and defend.
The e-commerce law expects clear seller identity, contact details, prices including tax, delivery of the service and cancellation terms. We build these into every course page and checkout, and plan the launch around registering the online store with the Ministry of Commerce where it applies.
Parents see the rules before paying, which keeps disputes rare.
Courses that carry a National eLearning Center licence can show it on the course page, so parents who check before enrolling can see it. Certificates are issued in Arabic and English only when completion rules are met, with a verification code that universities and other schools can check.
Certificates the group can stand behind, in every region.
Paid enrolments create or update learner access in the group's chosen learning system, whether Moodle, Microsoft Teams, Google Classroom or lessons hosted on the platform. One parent login covers children at different campuses, with access ending when each course closes. Teachers keep using the tools they already know at every campus.
No manual account creation after each intake.
Head office sets group rules such as sibling handling, staff children, scholarship codes and refund windows. Campuses add local rules for capacity, sections and prerequisites. Changes to group rules apply everywhere at once, with a record of who changed what. Campus staff cannot override a group rule without approval.
Consistent treatment of families wherever they enrol.
Each programme declares whether it is on site, live online or recorded, which adults may contact learners, whether sessions may be recorded and how long recordings are kept. The platform enforces those settings, and teacher messages stay inside logged channels. Your safeguarding lead approves each programme's settings before it goes on sale.
Safeguarding rules applied by the system, not by memory.
Owners see enrolments, fill rates, refunds and revenue by region, campus and programme. Finance reconciles settlements per merchant account, and registrars export rosters for their own campus only. Reports can be scheduled to arrive each week during enrolment periods, and the same figures are available on screen for principals who want to check a single campus or programme at any time.
Decisions about the next intake are based on real demand by region.
Who this is for
A national course platform only makes sense when a single school website cannot carry the load: several campuses, several entities, or learners who could be anywhere in the Kingdom. The four situations below are where groups usually start, and each points to a different first release. We say early if a simpler setup would serve you better for now. A group with two campuses in one city, for example, may be better served by a single school course site until a third campus or a new region makes the national platform worth it.
A group teaching in the Central, Western and Eastern regions needs one catalogue structure, regional storefronts and campus level control over timetables and teachers. The first release usually covers one shared programme, such as summer school, across every campus, so the group can compare demand by region from the first intake. Campus specific clubs and revision courses follow once registrars are comfortable with the admin, and the regional storefronts are already in place for them. Head office approves every storefront.
One shared programme first, then campus specific courses.
Companies that run exam preparation, language or enrichment courses online for learners anywhere in the country need strong course pages, national payment coverage, licence display and careful handling of children's data, because they never meet most of their learners, and the parent paying may live in a different region from the child learning. School online course platform development for this model puts the recorded library and live cohorts at the centre. Parent and learner accounts are kept separate, so the child sees only lessons.
Online first, with every learner potentially in a different city.
Owners who have bought several schools often inherit several ways of selling courses: one uses bank transfers, another a payment link, another a third party portal. We move them onto one platform in phases, keeping each school's brand while unifying payments, invoicing and data handling. Existing enrolment records and parent accounts are migrated with consent records intact, and old payment links are retired only after the new checkout has run a full intake. Reporting is unified from the first migrated school.
Phased migration so no school loses an intake.
A brand opening its first Saudi campuses needs Arabic first pages that match the global brand, local payment methods its home market may not use, Fatoora invoicing and PDPL compliant data handling from day one, plus a plan for adding campuses as the network grows. Global course content often needs adapting for Saudi curricula, calendars and sections, and the platform keeps local versions alongside the originals. We also help turn global policies into Saudi terms, consent wording and receipts.
Local rules built in before the second campus opens.
How we work together
Groups usually start with a fixed scope platform core and a first region, then move to a retainer as campuses join. Larger programmes take a dedicated team that stays with the platform across several terms. Discovery and workshops can take place in Riyadh in person; campuses in other cities join by video call. Cost depends on the number of legal entities and merchant accounts, storefronts and campuses, payment and instalment providers, the learning systems to connect, migration from existing portals and how many rules differ between regions. We set out the phases with an estimate for each, so the group can fund the core first and decide on later regions when the first results are in.
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
Platforms are typically built with Laravel or Next.js, SAMA licensed gateways, Fatoora integration per entity, hosting located to meet your data policy and connections to the group's learning, finance and student information systems. Every integration is documented so your own IT team can maintain it.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
Payments, e-invoicing, data protection, e-commerce and sometimes e-learning licensing.
Payments run through SAMA licensed providers, invoices follow ZATCA's e-invoicing rules, personal and children's data falls under the PDPL enforced by SDAIA, and online selling follows the e-commerce law under the Ministry of Commerce. Programmes that issue e-learning certificates may need a National eLearning Center licence. We build for all of these and work alongside your legal and tax advisers, who confirm how each applies to your entities. If a campus works with government bodies, the NCA's cybersecurity controls may also shape hosting and access decisions.
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