Understand the PMS as the shared operating foundation
The calendar matters. What happens everywhere else after a change matters more.A property management system should connect reservations, stays, guests, rooms, prices, charges, invoices and payments. This matters especially in small hotels where a few people cover several roles and cannot reconcile parallel lists all day.
Start with six moments from your operating day and define the expected result for each. A cancellation should release capacity; a housekeeping release should be visible at front desk without a call. One shared state is more valuable than isolated attractive screens.
| Hotel moment | Expected outcome | Not an acceptable substitute |
|---|---|---|
| New reservation | Guest, dates, price, category and status are connected. | Another entry in a side list |
| Room move | Occupancy and housekeeping follow the new room. | Verbal handover to the next shift |
| Early arrival | Priority and readiness are visible to both teams. | Calls between floors and front desk |
| Additional charge | The charge reaches the correct stay and invoice. | Handwritten note for departure |
| Partial payment | Payment and open balance remain traceable together. | Separate payment note without invoice context |
| Cancellation | Status, history and released capacity agree. | Delete the booking and risk later questions |
Keep reservations and occupancy as the reliable source of truth
Every shift should understand arrivals, stayovers, departures and blocks within seconds.Do not assess a calendar by colours alone. Change dates, category or room and verify conflicts, availability and the next shift’s understanding. Maintenance blocks must affect sellable capacity and cannot be treated like normal housekeeping work.
Hotel Nordlicht tests a two-night stay, a room move on night two and a parallel block. Front desk checks arrival and inventory, housekeeping checks the old room’s state, and management reviews the history.
Four-step reservation check
- 01Document the starting state
Record dates, category, room, price and status before the change.
- 02Make a real change
Extend the stay or move the room; do not use a prepared ideal case.
- 03Check the downstream effect
Compare availability, housekeeping state and price with the expected result.
- 04Review the history
A second person should understand what changed, when and why.
Know the guest once and support the whole stay
Guest data is not a separate address book. Profiles need booking context for communication, privacy, invoicing and return visits. Test duplicates, company versus private recipient, preferred language and consent.
Follow one message from trigger to reply. Arrival information belongs to the booking, uses the correct hotel data and remains visible for the next shift. The booking context determines the communication channel.
Organise rooms and housekeeping without a second source of truth
Room master data and the daily cleaning plan serve different purposes but must use the same occupancy. Categories describe what is sold; individual rooms show operational state. A departure, extension or room move must update the daily plan.
Define states precisely. “Ready” means an empty, cleaned room released for arrival. Completed stayover service concerns an occupied room. Maintenance and out-of-order states belong to room control because they block availability.
Test pricing and direct booking as one sales path
A price is shaped by category, base price, dates, rate plan, occupancy and conditions. Test a low-season weekday, a strong weekend and a multi-night stay. The team should explain each result and every automation needs understandable limits and approval.
Then complete a real mobile direct booking. Dates, price and extras must arrive in the PMS exactly as booked. Photos, capacities and descriptions should come from their responsible master data rather than being maintained in parallel.
Bring invoices, payments and control together
The financial workflow begins with the stay, not the PDF. Accommodation, extras, tax, recipient, payment and balance must agree. Test private and company invoices plus a partial payment, comparing preview, final file and list status.
Management needs more than a revenue tile. Ask which bookings, documents, payments and filters produce each number. Corrections and cancellations should remain visible instead of being overwritten in spreadsheets.
| Case | Verify | Passes when |
|---|---|---|
| Private invoice | Guest address, charges, tax, document date | Preview, PDF and list agree. |
| Company invoice | Company, address, optional company data, service context | The correct recipient was deliberately selected. |
| Partial payment | Amount, method, remaining balance, allocation | Payment and balance remain traceable together. |
Prove usability, personal access and support in daily work
“Easy to use” is proven when different roles complete real tasks without guidance. Give front desk, housekeeping, finance and management personal access and ask each person to perform three daily tasks while explaining the expected next step.
Test help and support before buying. Open one standard procedure, one exception and one troubleshooting guide. Each should state prerequisites, steps, visible result and common errors. STRYK includes all core apps at one clear price, offers 14 days free and charges no setup fee. STRYK Pricing Intelligence and STRYK Guest AI are clearly disclosed optional add-ons; external partners such as payment providers may charge separately.
Core PMS check before shortlisting
- A booking change correctly updates occupancy and follow-up work.
- Guest profile and stay remain connected but distinct.
- Housekeeping and front desk see the same room state.
- A mobile direct booking reaches the PMS completely.
- Invoice, payment and balance can be reviewed together.
- Personal roles, documentation and support pass real tasks.
