A modular, AI-first Property Management System built on Odoo — engineered for South Asia and the GCC, deployable from one villa to a global chain.
Every LLM, embedding, transcription, or generative-AI call across all 35 apps flows through netex_ai, our single mandatory AI gateway. That means observability, cost control, PII scrubbing, and EU AI Act compliance enforced at one chokepoint — not bolted onto each feature.
67 AI features across 9 tiers. 10 hospitality-tuned services. August 2026 EU AI Act compliance enforced at the gateway.
Our Layer 1 modules embed dormant hotel-specific behaviour that activates only when the hotel core is installed. A standalone restaurant, spa, or gym can run the same code as a 300-room resort — and grow into the full platform without re-platforming.
9 product SKUs from Villa to Enterprise Chain. Edition bundles install the right subset in one click.
Most ERPs ship one reconciliation point: finance. We ship 13 — RoomNight, Folio, F&B Sales, Channel, Loyalty, USALI, GRNI, Inventory, FX, City Ledger, Group/BEO, Member Tier and Night Audit — because hospitality runs on them.
USALI 11th-edition accounting, HACCP-aware F&B, multi-property SaaS chain management — all standard.
Because hospitality isn't one customer profile — it's nine. From a single Villa to an Enterprise Chain, from a standalone bar to a flagship resort. Four layers let one codebase serve all nine SKUs without forks.
Authentication, approval, AI gateway, notifications, audit trail, API gateway. Every business module depends on it; users never navigate here directly.
Reusable business primitives that work without hotel modules through graceful degradation. Add the hotel core later and dormant hotel-specific behaviour activates automatically.
Hospitality-specific functionality — front office, central reservation, folio, housekeeping, banquets, distribution. Requires hotel_base.
Cross-cutting tooling: 300+ reports, the Integration Hub, and the BI Report Builder.
Seven clusters are shipping today; three more are designed, scoped, and on the roadmap. Select any cluster to see the apps it contains.
Netex-PMS doesn't add AI to features — AI is a platform contract. The netex_ai module is the single, mandatory gateway through which every LLM call, embedding, transcription, vision analysis, or generative-AI operation across the entire platform is executed. No other module — Platform, Generic, or Hotel — calls a provider directly.
This is enforced architecturally. Any module attempting a direct Anthropic, OpenAI, or Google call won't pass our internal Step 8 quality audit. The result: every AI call is observed for cost, scrubbed of PII, safety-filtered, evaluated for quality, and governed under the same EU AI Act compliance framework.
The gateway routes by capability ("summarize-long-text", "extract-id-document"), not model name. Callers request what they need; the gateway picks the best provider for the task, the tenant's budget tier, the region's data-residency rules, and current load.
August 2026 enforcement deadline. risk_tier='unacceptable' requests are blocked at AI-4001. risk_tier='high' requests require Human-in-the-Loop review. Every gateway call produces a tamper-evident audit log entry — SHA-256 hash chained with daily integrity verification.
| Layer | Function |
|---|---|
| Use Case Registry | EU AI Act risk classification (limited / high / unacceptable / minimal) |
| Consent Check | Per-partner, per-use-case consent ledger |
| PII Scrubbing | Regex catalog tuned for SEA (passport, NIC, Aadhaar, IC, NRIC, phone, email, IBAN, card PAN, DoB) |
| DLP | Block / redact / alert per tenant rules |
| Budget Enforcement | Per-tenant hard cap with 50/80/100% thresholds |
| Provider Routing | Anthropic Claude, OpenAI, Google Gemini — by capability + cost + region |
| Cost Meter | Token + USD aggregation per use case |
| Audit Log | SHA-256 hash chain, immutable, append-only |
| Quality Eval | LLM-judge framework with golden datasets |
| HITL Gate | Required for high-risk outputs |
Instant guest message + KB translation
Passport / IC / Aadhaar / licence → res.partner
Incoming review and chat triage
Long emails, contracts, BEO sheets
Promo copy, contract drafts, BEO narratives
Damage report + ID document quality
Guest call recordings → text
Guest-facing chat with Noor persona
Feedback → root-cause categorisation
Auto-routing reservations, complaints, queries
Every state change is logged in a tamper-evident, SHA-256 hash-chained audit trail (netex.audit.log + approval.audit.log). Every AI call passes through use-case registry, PII redaction, DLP, consent, budget, and HITL gates before reaching a provider. Every monetary action above tenant-defined thresholds requires multi-step approval with SoD enforcement and step-up MFA where appropriate.
For hotel finance, we implement USALI 11th edition Schedule 3+ revenue and expense classifications natively, with R6 reconciliation running monthly + year-end. For F&B operations, HACCP cold-chain controls drive minibar restock workflows and inventory adjustments. For multi-jurisdiction operations, per-market overlays cover Sri Lanka, UAE, Saudi Arabia, Malaysia, Maldives, Bangladesh, Singapore, Indonesia, and the Philippines.
Most PMSs ship one reconciliation point — finance. Netex-PMS ships thirteen, each queryable, auditable, and automated.
| ID | Reconciliation | Cluster | Cadence | What it does |
|---|---|---|---|---|
| R1 | Room Night | HOTEL-OPS | Daily | Night-audit room-nights ↔ folio postings |
| R2 | Folio | HOTEL-OPS + FINANCE | Continuous | Charges ↔ payments ↔ invoice ↔ city ledger |
| R3 | F&B Sales | F&B-RETAIL | End-of-shift + daily | POS sales ↔ inventory consumption ↔ revenue posting |
| R4 | Channel / OTA | EXTENDED-HOTEL-OPS | Continuous | PMS inventory ↔ OTA allocations ↔ commission |
| R5 | Loyalty Points | SUPPORT-OPS | Daily | Earned ↔ redeemed ↔ expired ↔ liability |
| R6 | USALI Schedule | FINANCE | Monthly + year-end | Revenue + expense per USALI Schedule 3+ |
| R7 | GRNI | F&B-RETAIL | Continuous | PO ↔ GRN ↔ invoice three-way match |
| R8 | Inventory | F&B-RETAIL | Cycle + monthly | Physical count ↔ system ↔ adjustments |
| R9 | Currency / FX | FINANCE | Daily + month-end | Multi-currency revaluation |
| R10 | City Ledger / A/R | FINANCE | Weekly + month-end | A/R aging |
| R11 | Group / BEO | F&B-RETAIL | Per event | BEO commitments ↔ delivered ↔ billed |
| R12 | Member Tier | SUPPORT-OPS | Quarterly + tier-period close | Tier qualification |
| R13 | Night Audit | HOTEL-OPS | Daily | End-of-day cutover integrity |
Each reconciliation is queryable, auditable, and automated. When a number is wrong, you know which reconciliation surfaced it — and which transaction caused it.
Nine product SKUs across the full hospitality spectrum. Each edition installs the right cluster set — nothing more.
| Edition | Rooms / Scale | Cluster Set | Best For |
|---|---|---|---|
| Villa | 1+ rooms | Foundation + HOTEL-OPS-lite + FINANCE-lite | Single villa, boutique guesthouse |
| Compact | 1–25 rooms | + F&B-RETAIL-lite | Small hotels, B&Bs |
| Compact+ | 26–50 rooms | + DISTRIBUTION | Boutique hotels |
| Professional | 51–150 rooms | + EXTENDED-HOTEL-OPS subset | Mid-size hotels |
| Professional+ | 151–300 rooms | + SUPPORT-OPS, ANALYTICS | Full-service hotels |
| Enterprise | 301+ rooms | All clusters | Flagship hotels, resorts |
| Enterprise Chain | Multi-property | + nop_integration | Hotel chains, holding companies |
| Restaurant | Layer 1 subset | netex_pos + netex_outlet_mgmt + inventory_mgmt + ntx_finance_core | Standalone restaurants |
| Bar | Layer 1 subset | netex_pos + netex_outlet_mgmt (bar) + inventory_mgmt | Standalone bars / nightlife |
Edition bundles — netex_restaurant_edition, netex_hotel_edition, netex_bar_edition — install the right subset in one click (on the roadmap, per ADR-004).
netex_approval — Multi-level approval, monetary thresholds, SoD.
netex_notify — Email, SMS, WhatsApp, Push, In-App.
netex_auth — Login, 2FA, session, RBAC, SSO.
netex_api — REST endpoints, webhooks, rate limiting.
netex_audit — Tamper-evident hash-chained log, GDPR DSAR.
netex_ai — Single mandatory AI gateway.
netex_help (Noor) — Floating AI help, position-based training.
netex_nop — Multi-property, cross-tenant management.
netex_uat — Automated Step 8 verification engine.
integration (L3) — OTA, payment gateways, IoT, fiscal printers.
hotel_reports (L3) — 300+ templates, KPI dashboards, USALI.
netex_core — Config, event bus, scale-adaptive UI.
Before, during, and after the stay. Mobile check-in, in-room control, IRD ordering, spa booking, folio review, loyalty engagement. 732 features. Available as React Native, Flutter, and PWA. Kiosk mode for self-service.
Workflows for housekeeping attendants, F&B stewards, managers, and supervisors. 356 features. Approval-on-the-go. Incident reporting. Live KPI dashboards. Same one-touch design as the guest app.
Both apps consume the F4 API Gateway exclusively. No direct database access. Same security model. Same audit trail. Same AI services.
PRDs locked. Pattern A discipline applied. Step 8 verification mandatory.
PRDs locked. Pattern A discipline applied. Step 8 verification mandatory.
PRDs locked. Pattern A discipline applied. Step 8 verification mandatory.
Book a 30-minute architecture walkthrough and live demo with our hospitality solutions team.