Property management that runs in Arabic and English at the same time. Made in Damascus and Riyadh for hotels of every size. ZATCA-ready, channel-synced, transparently priced.
Most independent hotels in Syria and Saudi Arabia run on a combination of spreadsheets, paper ledgers, and WhatsApp messages. 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 bookings. Channel icons per stay. Sticky chrome at front-desk pace, even on a twelve-year-old PC.
Dashboard managers actually open. Inverse-metric coloring done right — cancellations down is success-green, not just less red.
ZATCA Phase 2 simplified invoices, bilingual, with real TLV QR. Syrian tax engine ready. Auditor-ready out of the box.
Drag to create bookings. Sticky chrome. Channel icons per booking. Payment dots per stay. Today marker always anchored. Real CSS Grid — not table hacks. Eight statuses (Confirmed, In-house, Pending, Tentative, Maintenance, Cancelled, No-show, Checked-out) all distinguishable at a glance.
We borrowed the discipline of a calm operational interface, but built the architecture from scratch so it runs at front-desk pace on a twelve-year-old PC.
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 generated in Nozuly is a Phase 2 simplified e-invoice. 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.
For Syria, the tax engine swaps to the Syrian hospitality consumption tax. Same architecture, different rate.
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 independent hotels — 8 to 16 rooms typical, courtyard properties in Damascus, Aleppo and Latakia.
For Saudi independent hotels — 28 to 100 rooms, urban + heritage properties in Riyadh, Jeddah, AlUla and Khobar.
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 independent 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 independent hotels | EU / global mid-scale | Global independent | 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 independent 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. We've run independent hotels. We've paid $200/month for software designed for European hotels and hated every minute of it. We've written front-desk checklists by hand because the PMS we paid for couldn't render Arabic.
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 with 5 partner properties. 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 independent 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 30 days. No credit card required. At day 30 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. Servers in Frankfurt (EU) with optional pinning to Riyadh once the regional data centre comes online in 2026.
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.
Frankfurt today. Riyadh by Q3 2026.
Yes. We accept SYP via local bank transfer. Pricing is published in USD but billed at the prevailing rate. Reach out and we'll set you up — we work directly with Syrian banks to avoid friction.
Yes. We've integrated with two Syrian private banks for payment reconciliation. If your bank isn't supported yet, manual reconciliation via CSV upload is fully featured — most beta partners use that flow.
We're in private beta with 2 properties in Damascus and Aleppo today. Public availability for Syrian hotels in Q1 2026, full general availability in Q2.
Our e-invoicing implementation passes the ZATCA simplified-invoice validation suite. Formal solution-provider listing is in process; we expect listing in Q1 2026. 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.
