What should I test when connecting my PMS to Booking.com?
A connection status is only the starting point. Use this acceptance protocol to check what reaches your property management system (PMS), what reaches Booking.com and who resolves a failed test.
Test a new Booking.com reservation, an amendment and a cancellation, then verify the matching dates, room type, rate, guest details and availability in both systems. Separately test prices, restrictions and payment information. Give every check a named owner, an expected result and timestamped evidence. Release the connection only when critical checks pass and staff know how to handle delayed or missing updates.
Agree the test scope before changing inventory
Record the property ID, connected room and rate IDs, occupancies, currency and which system controls each setting. Agree a processing window and escalation contact with the provider; do not assume a universal synchronisation time.
Ask your provider to arrange a suitable test environment. Booking.com’s test reservation tutorial is for connectivity developers, so it does not establish that your hotel has its own sandbox. Any live test needs an agreed booking, payment and cancellation procedure.
Separate platform capability from your implementation. Booking.com’s APIs support reservation and inventory workflows; that alone does not prove which actions your PMS, package or payment integration supports. Mark each requirement as demonstrated, manual or unsupported before signing off.
Your PMS–Booking.com acceptance protocol
Replace the roles below with names. For each row, record pass/fail, the actual result, timestamps with time zone, an evidence reference and any retest. Repeat relevant checks for every connected room/rate combination and occupancy you sell.
| Test and action | Expected result | Owner | Evidence |
|---|---|---|---|
| 1. Confirm connection scope | Both sides confirm the intended property, room and rate IDs; occupancy and GBP settings match. | Implementation lead | Approved mapping and connection record. |
| 2. Change a nightly price | The selected date and rate update. The guest-facing total reconciles with occupancy, meal plan, promotions and charges. | Revenue manager | Before/after PMS and extranet values; matching guest search. |
| 3. Add and remove a direct booking | Booking.com inventory changes for each affected night according to the agreed allocation; other dates remain correct. | Reservations lead | Inventory snapshots before, during and after. |
| 4. Apply and remove restrictions | A two-night minimum rejects a one-night search but permits an otherwise eligible two-night stay. A stop-sell blocks the selected product; reopening restores eligibility. | Revenue manager | Restriction settings and dated search results. |
| 5. Make a Booking.com booking | One PMS record appears with the channel reference, correct dates, guests, room, rate, total, inclusions and special request. Inventory reduces appropriately. | Reservations lead | Channel confirmation, PMS record and inventory. |
| 6. Amend through Booking.com | Supported date or occupancy changes update the existing booking; old and new nights reconcile without a duplicate. | Reservations lead | Original reference, amendment and inventory comparison. |
| 7. Cancel through Booking.com | The PMS records cancellation. Inventory matches the agreed replenishment settings, including a separate check with a stop-sell active. | Reservations lead | Cancellation confirmation and inventory on both sides. |
| 8. Check each payment route used | The collector, amount, currency, guest balance and applicable payment or payout status reconcile. Any manual step has an owner. | Finance lead | Redacted booking and payment records. |
| 9. Check a pre-switch reservation | An authorised channel amendment matches the imported booking rather than creating a second record. | Migration lead | Original channel ID and before/after PMS record. |
| 10. Rehearse delayed delivery | The provider demonstrates notification, recovery and duplicate prevention in a safe test environment; reception knows the fallback procedure. | Provider and duty manager | Test incident, recovery record and staff acknowledgement. |
Booking.com documents reservation fields and inventory and restriction controls. These define useful checks, not a guarantee of your supplier’s implementation.
Check cancellation behaviour explicitly. Booking.com has separate settings for replenishing inventory and reopening closed rooms after cancellation. Confirm the intended behaviour with your provider and test it; a previous closure is not sufficient evidence. See Booking.com’s property settings.
Illustrative example: follow the same booking
A fictional inn starts with three Double Rooms available on each night of 18–20 January 2027. Assume matching channel inventory, no other bookings, open sales and replenishment enabled. The guest rate is £120 per night, VAT-inclusive where applicable, with no extras or discounts; commission is not deducted from the guest total.
Book 18–20 January
Two nights total £240. Availability becomes two rooms on 18 and 19 January; 20 January stays at three.
Move to 19–21 January
At the same rate, the total remains £240. Availability is now three on 18 January and two on both 19 and 20 January.
Cancel the booking
With no other changes, all three nights return to three available rooms. The PMS retains one cancelled booking linked to the channel reference.
Capture each stage separately. A correct final inventory total can hide an amendment that briefly held both sets of nights.
Decide what blocks launch
- Hold launch for missing or duplicate bookings, incorrect prices or dates, unexplained inventory changes, failed restrictions or unclear payment responsibility.
- Retest failures with the same scenario after correction. Accept a manual workaround only when the manager approves its owner, instructions and review date.
- Remove test restrictions, reconcile test bookings and charges, restore intended inventory and assign someone to monitor the first live transactions.
A received reservation is not proof that payment has settled. Missing card data is also not automatically a connection failure: Booking.com describes several payment-data conditions. Verify the actual collection route without copying card numbers or security codes into test evidence.
Use the protocol in a RoomRaccoon demo
When assessing RoomRaccoon’s hotel channel manager, bring your room/rate list and the example above. Ask the team to demonstrate the booking–amendment–cancellation cycle and explain how staff identify a failed update.
Confirm which controls are available for your UK property, which package or partner services are required, and which tasks remain in Booking.com. Ask separately about payment handling and existing-reservation imports; the protocol is a requirement list, not a claim that every feature is included.
Bring one real operational scenario. Include your occupancies, restrictions and payment arrangement, then ask what evidence would support sign-off for your configuration.
Discuss your Booking.com connectionQuestions before sign-off
Is one successful booking enough?
No. It demonstrates one route and configuration. Test amendments, cancellations, inventory, restrictions and the payment arrangements you use, including any materially different room types or rates.
Can I test payments using only simulated reservations?
Do not assume so. Booking.com distinguishes test-property and real-property testing for different payment endpoints. Agree the supported method with your provider before creating charges; see its payment testing guidance.
What if reception receives a booking email but the PMS is empty?
Check the channel reference before entering anything manually. Notify the provider and follow the agreed fallback procedure. Booking.com documents fallback messages for missing updates; a later import must be reconciled to avoid a duplicate.
Sources and verification
Official Booking.com documentation checked on 10 November 2026. The protocol is an operational recommendation; confirm the supported workflow with your provider.












