Careers page, applicant pipeline and interview scoring in Arabic and English, with hires converted straight into the Saudi employee record.

Saudi companies opening a new branch or a fulfilment shift need twenty hires in weeks, while CVs sit in email and WhatsApp groups, the Nitaqat band is at risk and nobody can say how many Saudi applicants reached the interview stage. Odoo Recruitment publishes jobs, captures applications and moves candidates through stages the hiring team shares, and Naqlah, Odoo partner in Saudi Arabia, configures stages, forms and data rules for Saudi hiring.
Applicant data is collected with a privacy notice on the form, access is limited to the hiring team for each position and retention rules remove data once the purpose ends, which is what the PDPL expects from employers. Offer letters capture basic salary, housing, transport and the probation period once, and those values carry into the contract that is documented on Qiwa, so what the candidate signed and what the system holds match. Saudi applicant and hire ratios are visible per role and branch for Nitaqat planning, and the hire flows into Odoo Employees for the document and contract setup, with Jisr or ZenHR connected where onboarding continues there, as listed on the integrations page.
PDPL ready from the first application
The application form carries the privacy notice, hiring managers see only candidates for their positions and a retention policy clears old applications. Candidate data no longer lives on personal laptops.
Saudization planning per position
Applicants and hires are tagged by nationality and reported per job and branch. HR sees whether a branch opening is on track for its Saudi headcount before the Nitaqat band moves.
Qiwa aligned offers
Salary, allowances and the probation period, up to the 180 day legal maximum, are captured on the offer and carried into the employee contract. No retyping between offer, contract and Qiwa.
1. Job published and shared
The position goes live on the bilingual careers page and the link is shared on LinkedIn, Bayt and WhatsApp, with the Jadarat or Taqat posting recorded as a source.
2. Applications land in the pipeline
Web form submissions and emails to the job alias create applicants with the CV attached, the source tagged and the nationality captured for reporting.
3. Interviews scheduled and scored
Interview slots are booked from the applicant card, the Survey form scores each interview and the hiring team compares candidates on the same criteria.
4. Hire converted to employee
The offer is signed through Sign, the applicant becomes an employee with one click, and documents for Qiwa, GOSI and Muqeem are attached to the record.
Timelines depend on scope and the number of positions and branches, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| Applications | Scattered across email and WhatsApp | One pipeline per job with the CV attached |
| Careers page | None, or a PDF on the website | Bilingual online form feeding the pipeline |
| Interviews | Ad hoc calls and unstructured notes | Scheduled from the card with scored forms |
| Saudization | Unknown until Qiwa shows the ratio | Applicants and hires tagged and reported per branch |
| Data privacy | CVs on personal laptops and phones | Role based access and a retention policy |
| Onboarding | Details retyped into HR and payroll | Converted to the employee record in one click |
Everything else, we cover in a free 30-minute consultation.
Free consultation. Meet the team and get a clear roadmap in one call.