What should my reception team test during a hotel PMS demo?
Put everyday reception tasks at the centre of your hotel PMS demo checklist. Use this repeatable test script and weighted scorecard to check what happens when bookings, balances and staff responsibilities change.
Your reception team should create a booking, amend the stay, move rooms, settle and split the bill, process a partial refund, and test staff permissions. Use the same fictional booking with every supplier. Check saved records, balances and handover information, then score how independently the receptionist completes each task. Treat incorrect totals or unauthorised actions as unresolved blockers, regardless of the overall score.
Prepare one repeatable reception test
Ask for a test environment with fictional guests, provider-approved test payments and no live guest messages. Give every supplier the same brief in advance. Allow 45–60 minutes as a planning guide.
- Bring a receptionist to operate the system, a manager to test permissions and someone to record evidence.
- Confirm the demonstrated package, enabled upgrades, payment provider and connections. Use the same device and operator across demos where possible.
- For every task, record the score, elapsed time, prompts, workaround and evidence reference. Start timing at the instruction; stop when the saved result has been checked.
Run these six tasks in order
Illustrative example: a two-person direct booking arrives on 14 June 2027 and departs on 16 June. Two nights cost £120 each; breakfast totals £40. These fictional guest-facing amounts include any applicable VAT. Do not add VAT again; this exercise checks balances, not tax treatment.
| Task | Receptionist’s action | Evidence needed to pass | Weight |
|---|---|---|---|
| 1. Book | Create the stay in room 101, add breakfast and record a successful £100 test deposit. | Total £280; paid £100; outstanding £180. Correct dates, occupancy and confirmation preview; reopen the saved booking. | 2 |
| 2. Amend | Extend departure to 17 June. Add one night at £140 and breakfast at £20; preserve the original nights’ prices. | Total £440; deposit still £100; outstanding £340. No duplicate extras. Revised dates and amount appear in the guest-message preview. | 2 |
| 3. Move rooms | Before check-in, move the whole stay to available room 103 in the same category, without changing the price. | Room 103 holds the stay; 101 is released for those dates. Notes, extras and £340 balance remain. Attempt an occupied-room allocation and inspect the warning or block. | 1 |
| 4. Settle and invoice | Take a successful £340 test payment. Split accommodation and breakfast onto separate invoices for the same booker. | £380 accommodation + £60 breakfast = £440. Payments total £440, allocated once; total due £0. Both invoices retain the booking reference. | 3 |
| 5. Partially refund | Cancel the final £20 breakfast, record the billing correction and request a £20 refund against the original test payment. | Net charges £420. After successful refund, net payments £420 and due £0. Original payment, correction and refund remain traceable; inspect pending or failed status handling. | 3 |
| 6. Authorisations | On a separate test booking, attempt a refund and rate override as a restricted receptionist, then as an authorised manager. | Actions restricted by your agreed policy are blocked for reception and permitted for the manager. Completed changes identify the user and time; no shared administrator login. | 3 |
Scroll the table sideways on smaller screens. Record a score of 0–3 for each task using the rules below. The weights are suggested priorities, not an industry standard.
Score evidence, then apply decision gates
Use 0 for a failed or unsupported task; 1 for a vendor-only demonstration or manual workaround; 2 when reception completes it correctly with prompts; and 3 when reception completes it correctly without help. Mark untested tasks “Not tested” and arrange a retest before comparing totals. Score each task by its weakest required check.
Multiply each score by its weight. The maximum is 42 points: 3 × (2 + 2 + 1 + 3 + 3 + 3). Divide the points earned by 42 and multiply by 100.
Illustrative scoring: scores of 3, 2, 3, 3, 2 and 3 give 37/42, or 88.1%. This is a worked example, not a supplier assessment. A suggested shortlist threshold is 80%, with at least 2 on tasks 4–6. Any incorrect financial total or unauthorised action must be resolved and retested before selection.
Agree weights and gates before the first demo. Keep them unchanged across suppliers and compare task times only alongside accuracy and assistance.
Test the handover after a payment exception
After task 5, ask another receptionist to locate the booking without a verbal explanation. They should identify the room, revised charges, payment history, refund status and next action. Record who owns an unresolved refund and when they will check it.
A billing correction and a payment refund need separate evidence. For example, Stripe’s refund documentation distinguishes pending and failed refunds. That illustrates why a request is not proof of completion; it does not establish which provider or workflow your PMS uses.
Ask: “If the payment screen times out, how do I check whether the transaction succeeded before retrying?” Have the supplier demonstrate the supported recovery procedure. Mark unavailable exception tests for follow-up.
Bring your scorecard to a RoomRaccoon demo
RoomRaccoon’s UK hotel property management system page describes reservation management, payment-status visibility, invoice splitting and automated guest communication. Use those workflows as the starting point for your six tests, and ask to see the exact billing and refund arrangement your property needs.
The current hotel software plans and pricing comparison lists customisable user permissions from Essential upwards, with different user limits and upgrade allowances. Confirm your proposed package and payment setup before scoring authorisations; a demonstration with wider access may not represent your quote.
Bring this scorecard, your reception permission rules and one fictional booking. Ask the team to demonstrate each expected result and identify anything requiring another package or connection.
Book a demo around your reception tasksQuestions before your demo
What if reception cannot control the demo?
Have the receptionist direct every action, but record it as a vendor demonstration. Request a supervised hands-on session before awarding an independent-completion score.
Should we test OTA bookings too?
If they are essential to your operation, add a separate connected-channel test using the same booking pattern. Confirm which changes belong in the OTA and observe the actual exchange. A direct-booking demo does not verify an OTA connection.
Can we change the example to match our hotel?
Yes. Replace the amounts, extras and billing arrangement before approaching suppliers. Calculate the expected balances first and give everyone the same revised script.
Sources and checks
Product pages and supporting guidance checked on 10 November 2026. The test script, weights and thresholds are editorial suggestions.
- RoomRaccoon UK: PMS workflows — reservations, invoices and communication.
- RoomRaccoon UK: package comparison — permissions and plan limits.
- Stripe: refund and cancel payments — refund states; not evidence of a RoomRaccoon integration.












