01
Reservations & Front Desk
Bookings, arrivals, departures, guest records, room allocation, stay changes and front-desk workflows.
Nestor Enterprise PMS · R15.7.3
One operating platform for hotels, residences and multi-property groups.
Reservations, front desk, housekeeping, maintenance, billing, accounting, long-stay operations, revenue intelligence, automation and integrations - without stitching together a dozen disconnected tools.
Independent hotelsBoutique groupsServiced apartmentsMixed short-stay + long-stay
Operations dashboard
Property-wide control
OperationalProperty-wide control
Occupancy
82%
Rooms ready
41 / 48
Arrivals
18
Tasks closed
94%
Reservation updatedFront Desk
Room marked readyHousekeeping
Workflow completedAutomation
Revenue signal refreshedIntelligence
Actual product
The live Nestor interface, not a concept render.
This is the current Nestor PMS operating interface. Demos and pilots are built around real property workflows rather than a canned slideshow.
Operations Dashboard · Nestor Enterprise PMS R15
Property overview with navigation for front desk, executive dashboard, command center, calendar, vacancy and wider PMS operations.
Property overview with navigation for front desk, executive dashboard, command center, calendar, vacancy and wider PMS operations.
See your workflowDemo the screens relevant to your property instead of sitting through every module.
Validate with a pilotUse a controlled 2-3 week evaluation with configuration, migration support and training.
Talk to the product teamDirect access during evaluation instead of a generic self-service trial.
Core platform
Everything your operating day depends on.
Nestor combines the core hotel PMS with the operational, financial and long-stay workflows that usually force properties into extra systems.
02
Rooms, Rates & Restrictions
Inventory, availability, rate plans, pricing controls and restrictions from one property model.
03
Housekeeping
Room status, cleaning tasks and tighter coordination between housekeeping and front desk.
04
Maintenance
Issues, assignments and maintenance progress linked directly to rooms and property operations.
05
Billing & Folios
Charges, invoices, payments, deposits and reconciliation controls built into the stay lifecycle.
06
Accounting & Reporting
Operational finance, trial balance, P&L, balance-sheet foundations, owner statements and reporting.
07
Revenue Intelligence
Forecasting, backtesting and recommendations to support pricing and occupancy decisions.
08
Workflow Automation
Rules and event-driven processes that reduce repetitive operational work and hand-offs.
09
CRM & Guest Profiles
Guest history and relationship data available to the teams serving the customer.
10
Multi-Property Control
Property-aware operations, reporting, role controls and group-level visibility.
11
Roles, Audit & Security
Role-based controls, audit visibility and operational accountability for real multi-user environments.
12
Thailand Workflows
TM30/passport-supporting workflows for properties operating in Thailand.
A genuine differentiator
Hotel PMS and long-stay residence operations in the same system.
Nestor is particularly strong where nightly accommodation, serviced apartments, longer stays, owners, tenants and utilities overlap.
Short-stay hotel operations
✓Reservations, arrivals, departures and room operations
✓Rates, availability and restrictions
✓Housekeeping, maintenance and guest service
✓Folios, payments, reconciliation and reporting
Residence & long-stay operations
✓Tenant ledgers and recurring charges
✓Arrears and longer-stay financial workflows
✓Utility billing support
✓Owner statements and property-level reporting
Open architecture
Designed to connect, not trap you in another silo.
Nestor includes API, webhook and distribution foundations for integration with the rest of the hospitality stack.
API
Public API foundations
Property-aware access patterns for controlled integrations and external applications.
WH
Signed webhooks
Event-driven integrations so connected systems can react to PMS activity without constant polling.
OTA
Channel distribution architecture
Inventory, rates and restrictions architecture designed for external channel connectivity.
PAY
Payments architecture
Payment integration foundations with provider onboarding treated as a separate production go-live gate.
SW
Nestor Switch
An integration-oriented switching layer designed to simplify connectivity between Nestor and external services.
GLB
Global foundations
Country, tax, timezone, locale and currency foundations designed for expansion beyond one operating market.
Connectivity status: Channex certification is under active review. Production OTA/channel connectivity is not represented as formally approved until external certification is completed. External payment-provider production approval is also handled as a separate go-live gate.
Why Nestor
Built for operators who need capability, not platform theatre.
| Requirement | Nestor approach | What it means operationally |
|---|---|---|
| Hotel + long-stay | One platform | Reduce duplicate guest, tenant, owner and financial workflows. |
| Multi-property | Property-aware controls | Operate groups without forcing every property into identical workflows. |
| Automation | Built into operations | Reduce repetitive work rather than layering automation on later. |
| Implementation | Direct support | Migration, configuration and training are part of the pilot/rollout approach. |
| Architecture | API/webhook foundations | Designed for a broader integration stack instead of closed-system dependency. |
| Commercial model | Tailored to property/group | Avoid paying for modules and complexity that do not fit the operation. |
Operational proof
Built from a working hotel operation, not just a slide deck.
Live-hotel operating history
Nestor has already been operated in a live hotel environment. The current R15.7.3 commercial build is now being prepared for wider deployment.
Hands-on implementation
Selected pilot properties work directly with the product team on configuration, migration, training and workflow validation instead of being handed a generic trial account.
2-3 week pilot
Test it against the way your property actually works.
A controlled pilot is the fastest way to establish whether Nestor fits your operation before a wider commitment.
01 · DISCOVERY
Map the operation
Property structure, room types, rates, workflows, reporting and integration requirements.
02 · CONFIGURE
Build the sandbox
Configure the evaluation around your actual operating model rather than a generic demo dataset.
03 · MIGRATE & TRAIN
Work with real workflows
Support evaluation data, implementation tasks and team onboarding.
04 · DECIDE
Evaluate the fit
Review operational fit, rollout scope, integrations, migration and commercial terms.
FAQ
Questions buyers normally ask.
Who is Nestor built for?
Independent and boutique hotels, small-to-mid hotel groups, serviced apartments, residences and mixed short-stay/long-stay properties that need more operational depth than a lightweight PMS without taking on unnecessary enterprise complexity.
Is Nestor already operating in a hotel?
Yes. Nestor has operating history in a live hotel environment. R15.7.3 is the current commercial build being prepared for broader deployment.
Does Nestor support multiple properties?
Yes. Multi-property and property-aware controls are part of the platform architecture.
Does Nestor include long-stay and residence workflows?
Yes. Tenant ledgers, recurring charges, arrears, utility billing support and owner reporting are core differentiators.
Is OTA connectivity certified?
Channex certification is under active review. We do not represent external channel connectivity as formally production-approved until that certification is completed.
How is pricing handled?
Pricing is scoped to the property or group based on size, operating model, deployment and integration requirements. Pilot and rollout terms are discussed directly rather than forcing every property into the same package.
See it on your operation
Start with a real workflow, not a sales presentation.
Tell us how your property operates. We will map the fit, show the relevant workflows and, where appropriate, set up a controlled 2-3 week pilot.