Skip to content

Odoo ERP, website and accounting training

Kais Center

For an accounting training center we implemented Odoo with an Arabic chart of accounts, a site that reads cohort data from Odoo, and accounting training.

Year
2024–2025
Role
Odoo implementation, Laravel development and accounting training
Category
Odoo ERP, website and accounting training
Kais Center: Kais Center: Odoo ERP, website and accounting training

The challenge

An accounting training center wanted a working Odoo instance its students could actually log into, plus a public site that doubles as a sales surface for its cohorts.

The approach

Odoo 18 customization for an Arabic chart of accounts, a Laravel website that reads cohort data from Odoo, and a curriculum view that lets the head trainer reorder modules without writing code.

The outcome

Six modules taught across three live cohorts, and the center staff trained to maintain the system without the developer.

Under the hood

Field
Accounting Training · EdTech · SME Operations
Type
Odoo customisation + Laravel marketing site + live curriculum CMS
Team
Odoo engineer + Laravel dev + Arabic trainer

01

The real problem

Most Saudi accounting institutes either run on PowerPoint + WhatsApp or pay for closed-source LMS platforms that do not speak Arabic well and cannot model the actual accounting tools (debit/credit, chart-of-accounts, multi-currency) that students need to practise on. Kais wanted students to log into a real Odoo instance — the same ERP they would later configure for clients — not a sandboxed simulator. The public marketing site had to sell cohorts AND surface live availability without the staff updating two places.

02

Who did what

Customised the Odoo instance (Python + XML + PostgreSQL), built the Laravel marketing site, wired them together with a thin Odoo XML-RPC bridge, and trained their staff to maintain it.

Odoo engineer
Customised chart-of-accounts, invoice templates, and student-portal modules. Authored Python views + XML form definitions. Production data migration from the legacy spreadsheet workflow.
Laravel developer
Public marketing site reading cohort/seat/instructor data live from Odoo via XML-RPC. Bilingual content model, lead form pushing into Odoo CRM directly.
Trainer + curriculum designer
Taught two cohorts on accounting + Odoo basics. Wrote the curriculum and the staff handover playbook so the centre could maintain the platform alone after delivery.
Database + DevOps
PostgreSQL backups + restore drills. Odoo upgrade path documented. Domain + TLS + nginx vhost configured on the centre's VPS.

03

Architecture

01 — Public

Public marketing tier

  • Marketing site

    Laravel 10 + Blade

    Bilingual ar/en, cohort cards read live from Odoo

  • Lead form

    Laravel + Odoo XML-RPC

    Submits straight into Odoo CRM as qualified lead

02 — Internal

Internal app tier

  • Odoo 18

    Python · XML · PostgreSQL

    Customised accounting, student portal, instructor dashboard

  • XML-RPC bridge

    Laravel route + Redis cache

    60s TTL for cohort/seat reads to keep Odoo idle on public traffic

03 — Data

Data + backup tier

  • PostgreSQL 15

    Odoo schema

    Daily pg_dump, weekly off-site backup

  • Redis 7

    Cache · session

    Bridge cache + Laravel session store

04

Challenges

  1. 01

    Reading live Odoo cohort + seat data from the public Laravel marketing site without exposing the Odoo admin surface to the internet or duplicating data into a second DB.

  2. 02

    Arabic chart-of-accounts that matches what Saudi firms actually use — not a transliteration of the default English COA. Required collaboration with the head trainer + cross-checks against real client books.

  3. 03

    Single-source-of-truth for student-portal credentials: students must log into the same Odoo their instructors use, with restricted permissions, not a "training mirror".

  4. 04

    Lead form on the marketing site pushes directly into Odoo CRM as a qualified lead — no copy-paste between systems, no lost enquiries.

  5. 05

    Curriculum management UI that lets the head trainer reorder modules and adjust capacity without touching Python or PostgreSQL.

05

Hard problems

  • Live-read without exposing Odoo

    Built a thin Laravel proxy that hits Odoo XML-RPC over the internal network, caches results for 60 seconds in Redis, and serves them to the public site. Odoo never accepts a request from the open internet.

  • Arabic COA without breaking Odoo conventions

    Used Odoo's `code` field for stable English codes (used by reports and integrations) while overriding `name` with Arabic per the head trainer's draft. Reports render in Arabic; integrations stay safe.

  • Student-instructor role split

    Custom Odoo security group with row-level access controls so students see their own grades + their cohort's shared exercises, but not other students' work or instructor notes. Tested against horizontal privilege escalation.

06

Why these technologies

  • Odoo 18 (ERP core)

    • Real accounting ERP students will encounter in production — not a toy LMS that simulates accounting badly.
    • Open-source Python codebase the centre can audit + customise without vendor lock-in.
    • Native multi-company + multi-currency + Arabic support out of the box.
  • Laravel (marketing site)

    • Same stack as the centre's other tools so they can maintain it after handover.
    • Blade templating + Tailwind keeps the editing experience approachable for non-engineers on the team.
    • First-class XML-RPC client + Redis driver — the Odoo bridge is 80 lines, not 800.
  • PostgreSQL (Odoo-native)

    • Odoo standard — switching to MySQL means losing all the production-proven Odoo migrations.
    • Native JSONB columns used for translation overlays + per-cohort metadata.

07

What we learned

  1. 01

    When the goal is teaching a tool, students learn faster inside the real tool than inside a simulator.

  2. 02

    A 60-second Redis cache between a public site and an internal ERP is enough security + performance for SMB scale. Never expose Odoo directly.

  3. 03

    Arabic-first content model is not "translate the labels at the end" — it is a database design decision. Plan the COA in Arabic, then back-fill English codes.

Stack

  • Odoo 18
  • Python
  • PostgreSQL
  • Laravel
  • XML-RPC

Questions about Kais Center

Who built Kais Center?

Kais Center was built by Ali Yosef Software, a software company in Damascus. Our scope on the project: Odoo implementation, Laravel development and accounting training.

What is Kais Center?

For an accounting training center we implemented Odoo with an Arabic chart of accounts, a site that reads cohort data from Odoo, and accounting training.

What technology does Kais Center use?

Odoo 18, Python, PostgreSQL, Laravel, XML-RPC.

When was Kais Center built?

It was built during 2024–2025.

Can you build a system like Kais Center for my business?

Yes. We build ERP systems, point-of-sale systems, mobile apps and websites for clients in Syria, the neighbouring countries and the Gulf. Contact: info@aliyosef.online.