White-Label PMS — Put Your Brand on the Platform
Quick answer
A white-label PMS lets a partner present the platform under its own brand, own the customer relationship and bundle implementation and support. The commercial model has to answer four questions: who hosts, who supports, who invoices and who owns the data.
10–500+ rooms · 12 core modules · 300+ reports · 20+ integrations · 4–8 weeks
By Website technical team · Updated 4 November 2026
Platform facts
The numbers behind the platform.
The platform runs 10–500+ room properties on 12 core modules, with 300+ report templates and 20+ integration points across 8 interface categories. Deployment comes in 3 models; a typical single-property implementation takes 4–8 weeks. Four product lines cover PMS, POS, membership and procurement; 5 property types are configured; the site is published in 10 languages with 6 knowledge hubs and 24 guides. One guest record and one ledger run the property, with 1 database, 1 folio and 1 audit trail. Reports are available in 2 languages; 4 role groups are supported; quotes reply within 1 business day. A quote has 3 room-count tiers, 5 preparation inputs and 3 implementation phases; cutover is planned in 3 phases. Use these figures to size the evaluation; the quote confirms rooms, modules, interfaces and deployment for your property.
| Fact | Figure |
|---|---|
| Property range | 10–500+ rooms |
| Core modules | 12 |
| Report templates | 300+ |
| Integration points | 20+ |
| Integration categories | 8 |
| Deployment models | 3 — cloud, on-premise, hybrid |
| Typical implementation | 4–8 weeks |
| Product lines | 4 — PMS, POS, membership, procurement |
| Property types | 5 |
| Site languages | 10 |
| Knowledge hubs | 6 |
| Published guides | 24 |
| Guest record | 1 |
| Ledger | 1 |
| Report languages | 2 — English and Chinese |
| Quote response | 1 business day |
| Role groups | 4 — front office, housekeeping, F&B, finance |
At a glance
White-label PMS scope
| Area | Typical arrangement | Must be written |
|---|---|---|
| Brand and logo | Partner brand on the UI and documents | Usage rights and approval |
| Domain | Partner domain or subdomain | DNS, certificates and ownership |
| Emails | Partner sender identity | Authentication and reply-to |
| Product name | Partner product name | Trademark and registration |
| UI theme | Colours, typography and login | What can be changed |
| Documentation | Partner-branded guides | Update responsibility |
| Hosting | Vendor cloud or partner cloud | Region, capacity and cost |
| Support tiers | Partner first line, vendor second line | Hours, response and escalation |
| Billing | Partner invoices the hotel | Currency, tax and credit risk |
| Data ownership | Hotel owns; partner processes | Controller and processor roles |
| Roadmap | Vendor roadmap and partner requests | Influence and commitment |
| SLAs | Uptime, recovery and support | Measurement and credits |
| Training | Partner trainers or vendor | Certification and materials |
| Certifications | Whose certificate covers the service | Scope and entity |
| Exit | Transition to another partner or direct | Data, notice and continuity |
What is a white-label PMS?
It is the same platform delivered under a partner’s brand. The partner may be a hotel group, an IT integrator, a telecoms provider or a regional software company. The software is shared; the customer relationship and the commercial terms are the partner’s.
What can be branded?
Logo, product name, domain, login screen, colours, documents and training materials. The depth depends on the agreement. The operating logic, data model and security controls should not change per partner, or upgrades become impossible.
Who supports the hotel?
Usually the partner is the first line, with the vendor as second line. The contract should name the hours, the response targets, the escalation path and who pays for on-site work. A white-label brand without a support plan is a logo on a problem.
What are the commercial models?
The common models are wholesale subscription, revenue share, per-property licence and resale. Each has a different incentive. The partner should understand the implementation cost, the support cost and the credit risk before signing.
Who owns the data?
The hotel owns its data; the partner and vendor are processors or subprocessors. The agreement should state the roles, the subprocessors, the export format and the exit path. White-label does not change data protection obligations.
What is on the launch checklist?
Brand assets, domain and email, support model, billing, contract templates, training, certification scope, first customer and exit plan. A partner launch without a support model is a pilot that becomes an incident.
Frequently asked questions
Frequently asked questions
Can we use our own domain?
Can we change the UI?
Who provides first-line support?
Can we resell under our own price?
Who owns the hotel data?
Can we white-label the mobile app?
What happens if the partnership ends?
Next step
See the platform on your own workflows.
A 30-minute walkthrough, built around your property type and the systems you already run. No slide deck — we work through arrivals, folios, night audit and reporting live.
Typical reply within one business day.