Property management that runs in Arabic and English at the same time, for hotels in Syria and Saudi Arabia. Compliant with Syria's hospitality tax and Saudi ZATCA, with real channel sync and transparent pricing.
Many hotels in Syria run on a combination of spreadsheets, paper ledgers, and WhatsApp messages, while hotels in Saudi Arabia rely on booking systems of varying quality. It works, until it doesn't. Until a Booking.com sync fails silently. Until a tax audit asks for a year of ZATCA-compliant invoices. Until your front-desk staff calls in sick and nobody knows who's checking in at 2 PM.
Nozuly replaces the patchwork with one system. Designed to feel familiar from day one if you're coming from spreadsheets. Designed to feel like an upgrade if you're coming from Mews or Cloudbeds.
Operations, insight, compliance. Not feature checkboxes, the three surfaces front-desk and management actually open every day.
One tape chart for 28 rooms. Drag to create a booking, see each stay's channel at a glance, and work at front-desk pace even on an old computer.
Dashboard managers actually open. Inverse-metric coloring done right, cancellations down is success-green, not just less red.
Syrian tax engine ready out of the box. ZATCA Phase 2 simplified invoices for Saudi Arabia, bilingual, with real TLV QR. Auditor-ready.
Drag to create a booking. The header and dates stay in view as you scroll, each booking shows its channel and payment status, and a clear "today" line is always visible. All eight booking states — Confirmed, In-house, Pending, Tentative, Maintenance, Cancelled, No-show, Checked-out — are easy to tell apart at a glance.
We kept the interface calm and uncluttered, and built it to run fast even on an old front-desk computer.
Real KPIs. Occupancy 84% today, ▲6 points vs last Tuesday. Inverse-metric coloring done right: cancellation rate going down is success-green, not just "less red." A "needs attention" queue that prioritises by urgency.
Reports drill into channel breakdowns, occupancy forecasts, length-of-stay analysis and tax remittance, with proper period comparison and export to PDF, Excel or CSV.
Every invoice is fully compliant, the Syrian hospitality tax by default and ZATCA Phase 2 simplified e-invoices for Saudi Arabia: bilingual headers, real TLV-encoded QR codes, sequential numbering, cryptographic stamping. Auditor-ready out of the box.
Folios show source attribution for every charge (Front desk vs POS · Restaurant vs Channel · Auto vs Manual). The reconciliation view shows the four-step money flow: Guest pays → Channel deducts → Hotel receives → Taxes remitted → Effective revenue.
One architecture, both tax regimes, no separate module and no translation layer. Same folio, the correct rate for each market.
Two markets, one product. The architecture is dual-tax, dual-currency and bilingual from day one, not a translation layer bolted on after launch.
For Syrian hotels of every size, from small courtyard properties to larger city hotels.
For Saudi hotels, from boutique to larger urban and heritage properties.
Built to be cheaper than mid-scale PMS and clearer than the global SaaS players. Same tier whether you have 8 rooms or 80.
All plans include: ZATCA Phase 2 compliance · Bilingual UI · RTL support · GDPR/PDPL data handling · 99.5% uptime SLA · Encrypted backups · No setup fees.
Syrian pricing in SYP is available. For Syria-specific deployment, contact us directly. We'll work out terms that match the local banking system.
Compared to the PMS systems Syrian and Saudi hotels actually evaluate. We acknowledge what other systems do well, and where Nozuly is the right fit instead.
| Nozuly | Mews | Cloudbeds | Hotelogix | |
|---|---|---|---|---|
| Built for | GCC + MENA hotels | EU / global mid-scale | Global hotels | Generic global hospitality |
| Arabic-first UI | ✓ Native | ⚠ Translated | ⚠ Translated | ⚠ Translated |
| RTL support | ✓ Real | ⚠ Partial | ⚠ Partial | ⚠ Partial |
| ZATCA Phase 2 | ✓ Native | ⚠ Add-on | ⚠ Add-on | ⚠ Add-on |
| Syrian tax engine | ✓ Native | ✗ | ✗ | ✗ |
| Setup time | 30 min | 1–2 weeks | 1 week | 1–2 weeks |
| Starting price | USD 0 / mo | USD 350+ / mo | USD 200+ / mo | USD 150+ / mo |
| Channels supported | 4 (growing) | 100+ | 50+ | 50+ |
| Built by hospitality operators | ✓ Yes | ✓ Yes | ✓ Yes | ⚠ Unknown |
Mews, Cloudbeds, and Hotelogix are mature products. They're also built for global or generic markets. Nozuly exists because Syrian and Saudi hotels deserve a system that's Arabic-first by design, not by translation layer.
Nozuly is built by a small team in Damascus and Riyadh who have run hotels. We tried other hotel systems, but none fit the way we work or supported Arabic well.
So we built Nozuly. Bilingual from day one. Architecturally Arabic-first. Built to run at front-desk pace on the actual machines actual front-desk staff actually use.
We're in private beta, onboarding our first partner hotels. We're shipping v2 in Q3 2026. The roadmap is public, the pricing is on this page, and the founders answer their own email.
Most hotels are operational within 30 minutes. Setup is a guided onboarding: brand the property, add room types, paste channel API credentials, import an existing guest CSV if you have one. We help on a call if you'd rather, no extra cost.
No. Nozuly connects to your existing Booking.com, Expedia, Airbnb and Almosafer accounts via the official channel manager APIs. Existing future bookings sync in within a few minutes.
Yes. We support CSV imports for guests, room types, rate plans and historical bookings. If you're on a system with a public API, we'll write a one-off migration script for free during onboarding.
Yes, included in all plans. A 45-minute call, plus async chat support for two weeks. The Growth and Multi-property tiers come with priority response.
Yes, any time. Upgrades take effect immediately and are pro-rated. Downgrades take effect at the next billing cycle so you don't lose features mid-month.
Everything in Growth, for 90 days. No credit card required. At day 90 your data stays. You choose a plan, or export it and walk away. No lock-in.
No. One flat monthly fee, regardless of how many bookings you process. We don't take a cut of channel commissions either.
No.
Booking.com, Expedia, Airbnb, and Almosafer are live. Agoda and Hotelbeds are on the roadmap for Q2 2026. We integrate via the official channel APIs, no scraping.
Yes, on the Multi-property tier. You get a group-level dashboard, property switcher, consolidated reports and centralised team management.
The front-desk surfaces (tape chart, check-in/out) function offline for short interruptions and sync when the connection returns. ZATCA invoice generation requires connectivity at issue time (it's a regulatory requirement, not ours).
The web app is fully responsive and works on phone and tablet. A native iOS + Android app for managers is in beta. Sign up to the waitlist.
Encrypted at rest (AES-256) and in transit (TLS 1.3). Daily encrypted backups.
Yes. We're registered as a data controller in the EU, support DSAR within 30 days, and provide a signed DPA on request. The architecture treats guest PII as a first-class concern, not an afterthought.
Yes, PDPL-aligned. Once the KSA-region data centre is live, Saudi customer data will be pinned in-region by default. Until then, it's stored EU-region with full PDPL-compliant access controls.
Yes. We accept SYP via local bank transfer. Prices are in Syrian Pounds for Syrian customers. Reach out and we'll set you up. We work directly with Syrian banks to avoid friction.
Yes. Payments can be received via bank transfer or deposit in Syria, Sham Cash, Al-Haram, or bank cards.
We're in private beta today, onboarding our first partner hotels. Public availability for Syrian hotels is coming soon.
Our e-invoicing implementation passes the ZATCA simplified-invoice validation suite. Formal solution-provider listing is in process; we expect listing soon. Until then, invoices we generate are technically compliant and accepted by auditors.
Yes. You keep your existing Booking.com / Expedia / Almosafer accounts; we connect via the official APIs. No need to migrate accounts.
