Who
A hotel management and marketing firm in Saudi Arabia.
It does not own hotels — it leases, operates and markets them on the owners' behalf. That distinction matters: each hotel in the portfolio runs its own hotel management system (Nazeel), and the portfolio is tracked in a PMS, but neither belongs to Masar el Daif and neither talks to the other.
The problem
Masar el Daif itself had no digital infrastructure. It worked through client Booking.com accounts and kept a central Excel dashboard.
A booking could take days to appear on that dashboard. Entries were mistyped, bookings were missed, and follow-up depended on someone noticing.
What we did
Sahla built the booking platform, then built a new Odoo module to sit behind it — central dashboards, live updates, and automatic notifications and alerts.
Four sources feed it through custom integration layers: the new booking platform, the portfolio PMS, each hotel's Nazeel HMS, and Booking.com. Sync runs on a ten-minute interval, which is why staff experience it as live.
Three engineering decisions carry the reliability: sync is bidirectional except for Booking.com, which permits fetch but not write through its API; alerts and logs report anything that drops; and failures retry on the next cycle rather than being lost.
What changed
Manual re-entry is gone. What remains is auditing — confirming a migration landed — rather than typing it again.
A booking now reaches the central system in at most ten minutes from any source, against days before. Two of the four reservation channels no longer need reconciling by hand at all.
The platform is live in production and in its third year of support, with a second release planned for the end of the year.
What we would say plainly
A consolidation layer is only as good as its weakest integration. Booking.com is read-only by API, so that channel is a one-way mirror — worth stating plainly rather than implying full two-way parity.