HRMS Mobile

HRMS is employee self-service for organisations running HR on Odoo: a Flutter app and a Next.js dashboard over the oe_hr_ess_mobile_api REST module. Bearer sessions, portal-safe payloads, and records limited to what that employee is allowed to see. Home, Leaves, Pay, Attend, and a More hub cover the day-to-day; managers get approvals on top. Check-in is verified with DeepFace before the attendance record is trusted.

Employees were expected to live in Odoo for leave, payslips, attendance, loans, expenses, and letters. That is a desktop mental model. On a phone it becomes a maze of menus. HR still needed the system of record to stay Odoo — we could not fork the data.

We inventoried every ESS action people actually do on a phone: clock in, request time off, read a payslip, raise an expense, acknowledge a warning, open a help-desk ticket. Manager work (approvals) is a different permission set, not a different app. The constraint was portal-safe APIs — never expose another employee’s records — and a More menu that could grow without exploding the tab bar.

Branded sign-in, then a card-based ESS. Help desk, disciplinary, announcements, and 360 feedback use illustrated headers so dense HR modules still feel like products. Attendance combines clock-in with monthly stats. Disciplinary and warning letters expose EN/AR PDFs. 360 feedback is a completed questionnaire with matrix answers, not a dead thank-you screen.

Flutter client and a Next.js dashboard, both on Odoo via oe_hr_ess_mobile_api and bearer session tokens. DeepFace runs the face match at check-in; the verified record is what Odoo stores. Charts hit ESS analytics endpoints. Manager features (My Approvals) require approver rights in Odoo. Sessions persist until logout or expiry. Bilingual document export for letters and payslips. Push and an in-app notification inbox sit on the same record stream as announcements.

• Auth, session, and server configuration
• Home dashboard, insights charts, and alerts
• Time off: balances, requests, calendar
• Payslips with PDF export
• Attendance clock with DeepFace verification against the profile photo
• Next.js HR dashboard on the same Odoo session model
• More hub: profile, loans, custody, HR requests, expenses
• Announcements, notifications, directory, documents, policies, training
• Help desk tickets, appraisals, 360 feedback, disciplinary with EN/AR PDFs
• Manager approvals

We did not build a custom HRIS. Offline-first for every module would have fought Odoo’s permission model. The first product had to be a trustworthy phone for ESS — clock, leave, pay — with satellite modules complete enough that HR did not send people back to the browser for the long tail.

Shipped as HRMS Mobile against Odoo ESS. Versioned product documentation and a user manual were part of the release, not an afterthought — implementers and employees get the same module map.

Employees can clock, request leave, read pay, file expenses, and follow HR processes on a phone without leaving the Odoo permission model. Exact headcount and adoption sit with each deploying company.

Enterprise mobile fails when you wrap every desktop menu. It works when you pick the daily jobs, keep the system of record honest, and let the rest live one tap behind. I would pressure-test the More inventory with actual usage before treating every Odoo app as equally worthy of a custom screen.