Get your mapping and parity right, and distribution will be the quietest part of go‑live.
Mapping and parity principles
-
Complete room/rate/add‑on mapping and validate parity with small push/pull tests. Keep the channel manager integration disabled until cutover; if the partner needs earlier connect, log the timestamp and re‑validate parity just before switching live.
-
For Booking.com: use Pull mapping for correct codes, confirm age/child settings, and only enable after tests pass; multi‑property setups require separate integrations per property.
Importing future bookings and handling stayovers (switching PMS)
-
Import future reservations into Mews before cutover; spot‑check rates, taxes, products, and agency links to avoid mispricing or missing charges.
-
For stayovers during a PMS switch: check out guests in your old PMS, recreate their reservations in Mews with the same room, and record already‑paid nights as external payments (cross‑settlement) to avoid double charges.
-
If you see OTA credential/permission errors (e.g., Booking.com 400 “access” errors), correct credentials in the integration and re‑run the download
Day‑of activation routine
- Apply a temporary stop‑sell during imports, then re‑check parity and activate the channel manager. Verify that new bookings created during cutover reach Mews and clear any queue errors you see.
If you need help reading a specific error, open a case via the Mews Digital Assistant and include screenshots of your parity tests (Mews ↔ CHM ↔ OTA) to speed up the fix.