INTEGRATION / BLUEPRINT
Muqeem | Odoo Integration
Visa and residency lifecycle data flowing from Muqeem into Odoo: how 4,000+ employees' iqama status became visible inside the HR system — with expiry alerting that killed last-minute surprises.
Overview
Connecting Odoo to Muqeem for visa and residency lifecycle data, so 4,000+ employees' legal status is always visible inside the HR system that manages them.
Residency and visa status lived in Muqeem while everything else about an employee lived in Odoo. HR teams switched between portals to answer basic questions — is this employee's iqama valid? — and expired documents were discovered late, sometimes after penalties. Legal status was the one piece of employee data the company couldn't see in its own system.
How the integration works
- Scheduled pull — Muqeem residency data lands in Odoo's employee records on a disciplined schedule: iqama validity, expiry dates, and status flags attached directly to the canonical employee profile.
- Expiry-driven alerting — thresholds trigger notifications to HR and the employee long before documents lapse. Threshold tuning mattered: too early and people ignore the noise, too late and it stops being a warning.
- Shared sync core — the engine reuses the idempotent, auditable core built for the Qiwa integration: same retry safety, same before/after logging.
Data flow
- Residency records are fetched from Muqeem per employee, on schedule.
- Each record is matched to the canonical Odoo employee profile and applied idempotently.
- Expiry dates are evaluated against alert thresholds; upcoming expirations notify HR and the employee.
- Freshness indicators show when each record was last synced — the design embraces eventual consistency honestly instead of pretending to be live.
Key decisions
- **Eventual consistency with visible freshness. ** Muqeem data is authoritative but not real-time; the interface shows how fresh each record is rather than implying it is live.
- Same batch philosophy as Qiwa. Scheduled, idempotent batches keep operational cost low and behavior predictable across both integrations.
Impact
4,000+ employees' residency status is now visible inside Odoo, where HR actually works. Expired-document surprises dropped to near zero thanks to proactive expiry alerts, and the company always knows its compliance posture at a glance.
Building something similar?
Let's talk architecture before you commit to it.
Integration work fails in the design phase, not the code phase. A consultation maps your systems, the data flow and the risks — before anything is built.
Request consultation