Contact
Start with a conversation.
Whether you are replacing a legacy PMS or standardising a group, the first step is the same: a short conversation about how your property actually runs. No slide deck required.
What happens next
Three steps, no pressure.
01
A short call
We ask about the property, the current systems and what is not working. You do not need a specification.
02
A tailored walkthrough
We show the flows that matter to your operation — arrivals, folios, night audit, reporting — using your scenarios.
03
A written scope
If it is a fit, we send a scope with modules, interfaces, deployment model and a realistic timeline.
Sales and new projects
New properties, groups, replacements and partnership enquiries.
sale@hotelpmssystem.com +86 13922702227 WhatsApp · +86 13922702227Office
Lodgcore Office, Room 312K, Huilange BLDG, No. 273, Huangpu Blvd W, Tianhe District, Guangzhou 510620, Guangdong, China
Existing customers
Operational issues, incidents and questions about a live deployment.
Tell us what you are working on
Share a little context and we will tailor the session to your operation — front office, F&B, finance or a multi-property group.
Request a quote
What to prepare for a quote.
A useful quote starts with five inputs: the property, the modules, the deployment model, the interfaces and the target date. Send them with the form and we reply within one business day with a written scope. Pricing separates subscription, implementation, training, interfaces and annual support, so you can compare the real cost rather than a single monthly number.
- Room count, property type and number of outlets
- Modules needed: PMS, POS, membership and procurement
- Deployment preference: cloud, on-premise or hybrid
- Interfaces: OTA, payments, door locks and accounting
- Target opening or migration date
No list price is published because scope changes with room count, modules, deployment and interfaces. The quote is written after a short call, not generated from a price table.
See the full quote process| Item | What it covers |
|---|---|
| Subscription | Modules, users and deployment for the agreed term |
| Implementation | Discovery, configuration, data migration and cutover |
| Training | Role-based sessions for the desk, outlets and finance |
| Interfaces | OTA, payments, locks and accounting, priced per connection |
| Annual support | Support hours, updates and the service boundary |
After the form, we usually ask two or three clarifying questions, then send a scope with modules, interfaces, deployment model and a realistic timeline. A short call is usually enough; you do not need a full specification to start.
For a group, tell us how many properties, which reporting standard applies and whether deployment is central or local. The same questions apply, with one extra decision: who owns the chart of accounts.
A single independent property usually takes four to eight weeks from kick-off to cutover, depending on interfaces, data quality and rate rules. Groups are phased property by property.
Hardware, third-party licences, travel and on-site work outside the agreed scope are listed separately. For a replacement project, bring the current report list and the interfaces you rely on; those two inputs usually decide the migration effort.
The written scope names what is included, what is excluded and who owns each decision. That is more useful than a single number, because it shows where the risk sits.
Frequently asked questions