School ERP & Student Information System for Al F***** Education Group, UAECase Study

The fee structure proved far more intricate than any off-the-shelf product assumed. Fees varied by grade and by term, then by sibling discounts, staff discounts and a set of individually negotiated arrangements that existed only in the finance manager's spreadsheet and memory. Each term, generating fees for the whole student body was a multi-day exercise, with corrections continuing long after invoices had gone out.

Language was a genuine engineering problem rather than a translation task. Right-to-left layout affects form flow, table alignment, date pickers, report layouts and the direction of icons, and the old system's mirrored English screens left Arabic-reading parents disoriented. Report cards had to render correctly in both languages, including mixed passages where English subject names appear within Arabic text.

Administrative and timing pressures compounded this. Regulatory returns to the education authority had to be submitted in specific formats on a fixed schedule, and staff were exporting to Excel and reformatting by hand each cycle. Above everything sat the admissions season: if the new system was not ready for the next intake, the group would have to wait a full year.

PapaSiddhi built the student information system with React, Node.js and PostgreSQL, treating Arabic and English as equal first-class locales from the very first component. Layout direction, typography, Arabic and Western numerals and date handling are all driven by locale, and report card templates were designed separately for each language rather than produced by flipping one template, so mixed-language content renders cleanly.

The fee engine was implemented as a configurable rules layer instead of a fixed table. Grade, term, sibling and staff discounts and bespoke negotiated arrangements can all be expressed by finance staff without a developer, which allowed the finance manager to retire the spreadsheet. Payments run through a UAE payment gateway supporting the cards local families use, with bilingual fee statements. Admissions operate as a full pipeline from enquiry through assessment to enrolment, with the parent-facing journey designed mobile-first, and regulatory exports are generated directly in the formats the authority requires.

Access is scoped by campus and role, academic records carry retention rules, and SMS and email gateways handle bilingual parent notifications. Before launch, the team ran a bilingual usability round with Arabic-first parents, which revealed several form flows that were technically correct but felt wrong in sequence when read right-to-left. Resolving those before go-live took days; leaving them until afterwards would have cost adoption.