Services · Ecommerce development · School course enrolment sites
Codeeo offers school course selling website development UK schools, academy trusts and independent school groups use to sell paid courses across England, Scotland, Wales and Northern Ireland. That means holiday programmes, exam revision, summer schools, music tuition, online study and adult education, all on one platform with enrolment, payment and a paid learner area. Each nation has its own curriculum, exams, term dates and safeguarding checks, so a platform that sells across borders has to know which rules apply to which course.
The platform takes the money and records the place; your MIS and finance systems keep the official records. Codeeo has delivered 200+ projects across the UAE and the US, and we work with UK clients remotely by video call.
200+ companies servedFrom a first store to an ADX listed developer
Platform capabilities
A course that sells well in one school is often wanted elsewhere in the group. Scaling it is where most school course sites struggle. England and Wales use DBS checks while Scotland uses PVG and Northern Ireland uses AccessNI. England, Wales and Northern Ireland teach GCSEs and A levels, while Scotland has Nationals and Highers. Summer holidays start weeks apart. A Welsh school may need a bilingual site. Consumer law, VAT and data protection, on the other hand, apply across the whole UK.
Our school online course platform development UK groups commission separates those layers. National rules are set once. Regional rules attach to each school. School course payment integration UK finance teams can reconcile brings cards, wallets, Open Banking and Direct Debit into one ledger per school. School paid learning portal development UK learners use gives every paying learner one login, whichever school ran the course.
Each school is tagged with its nation and local authority. That setting decides the term calendar used for intakes, the qualification labels on study courses, the staff check type recorded for tutors and the language options shown. A trust adding a school in Wales or Scotland switches the setting rather than building a separate site.
New schools join without a new build.
Families search one catalogue by postcode, age and subject, and see courses from every school in reach. Behind it, each school manages its own intakes, prices, staff and refunds. Central teams can publish a course template, such as a revision programme, that schools adopt and adjust locally.
Consistent courses with local ownership.
Cards and wallets with Strong Customer Authentication, Open Banking payments and Direct Debit for termly plans all flow into a ledger split by school, course and intake. Finance exports match your accounting package, so each school's takings can be reconciled without manual matching of bank lines.
Group finance sees every payment in the right place.
Tutors are recorded with the right check for where they teach: DBS in England and Wales, PVG membership in Scotland, AccessNI in Northern Ireland. The admin will not assign a tutor to a children's course without a current record. Checks themselves stay in your HR process; the platform only records status and review dates.
Children's courses staffed only by cleared adults.
For schools in Wales, course pages, forms and emails can run in Welsh and English, with a language switch on every page and separate addresses for search engines. Staff edit both versions together. The same structure supports Gaelic for Scottish schools that teach it.
Welsh-medium families book in Welsh.
The Digital Markets, Competition and Consumers Act 2024 already requires mandatory charges in the headline price, and its rules on subscription contracts are expected in 2027. Course prices include every compulsory charge from the first page, and termly payment plans are built so cancellation and reminder steps can be added when the subscription rules take effect.
Pricing that holds up now and adapts later.
Private school education has been subject to VAT since January 2025, while many courses from state schools and eligible bodies are exempt, and trading subsidiaries may differ again. Finance teams set the treatment per course and per supplying entity, and receipts and reports follow it automatically across every school.
VAT applied consistently across the group.
A family that books a summer camp at one school and revision at another uses one account, with each child's bookings, forms and certificates in one place. Data stays partitioned so staff at one school see only their own learners, while the family sees everything they bought.
Repeat bookings across the group become easy.
Dashboards show bookings, revenue, fill rates and refunds by school, region and course type, with analytics cookies running only after consent under PECR. Leaders can see which programmes fill in which regions and plan the next term's catalogue from real booking data.
Course decisions based on bookings, not guesswork.
Schools in England answer to Ofsted, in Wales to Estyn and in Northern Ireland to the Education and Training Inspectorate, and holiday provision for young children can need childcare registration. The platform keeps registers, consent records, staff check status and incident notes for each course in a form leaders can export quickly when an inspector or the trust board asks.
Evidence for any course found in minutes.
Who this is for
A single school can sell a few courses with a simple shop. Organisations that run schools in several places need more: shared catalogues, separate finances, nation-specific rules and reporting that rolls up. These are the four groups we usually build for. Each starts with one region or a few schools, proves the model, then expands, so the platform is designed for growth from the first release. Rollout order is agreed with your leadership team, usually starting where demand is already proven.
Revision programmes, holiday provision and enrichment courses run at schools across different local authorities, each with its own office. The platform gives the trust one catalogue and one brand while every school keeps its own registers and takings. Funded places from local programmes are booked with codes and reported by authority, because each council runs its own scheme. Central staff can pause a course trust-wide if a policy changes, without logging into each school.
Report funded places by local authority.
Schools in England and Scotland selling summer schools, entrance preparation and music tuition to families who sometimes move between them. Parents keep one account, and the platform applies Scottish or English terms, qualifications and staff checks automatically. VAT treatment is set centrally for the whole group. Bursars at each school still see only their own takings and refunds.
One family account across every school.
A charity running paid and sponsored courses in partner schools across the four nations needs to sell places, record sponsorship and report to funders. Partner schools get limited admin access to their own sessions, and the charity keeps the learner relationship and the data. Sponsored places are recorded against the funder, so reports to each funder are produced from the platform rather than assembled by hand.
Partner schools see only their own sessions.
Training sold to staff from other schools works differently from pupil courses: buyers are schools paying by invoice or purchase order, often for several staff at once. The platform supports group bookings, invoice payment, attendance records and certificates for each participant. Purchase order numbers are captured at booking and printed on each invoice.
Schools pay by invoice, not just by card.
How we work together
Codeeo does not have a UK office. Our team of 80+ is based in Dubai, Riyadh and Karachi, and we work with UK trusts and school groups through video calls, shared documents and test environments every school can review. National platforms usually start with a fixed scope first release, then continue with a dedicated team or a retainer as further schools join. Codeeo is rated 4.7 from 23 Google reviews, and every stage is scoped in writing. Each school's office gets recorded training it can replay when staff change.
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
A multi-school platform usually runs on Laravel or Next.js with a headless content layer, so central teams and schools edit their own pages safely. We use UK payment providers supporting Strong Customer Authentication, Open Banking and Direct Debit, and host within the UK or the EU where your data protection assessment requires it. Code, data and accounts remain yours whichever supplier supports the platform later.
01Web
02Commerce
03Data and cloud
04Marketing and tracking
Nation-specific rules, separate finances per school and a shared catalogue.
A national platform has to apply different term dates, qualifications, staff check types and languages depending on where a course runs, while consumer law, VAT and data protection apply across the UK. It also needs one public catalogue with separate admin, takings and registers for each school, plus group reporting. We design these layers in discovery, so adding a school later is a settings change rather than a rebuild.
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