Introduction
The Mews integration covers most day-to-day guest communication needs, but there are things it does not do yet. Knowing them upfront is more useful than discovering them mid rollout. This article lists the current limitations of the two-way sync, online check-out, and reservation time updates, along with the technical and operational points worth planning around.
Writing data back to Mews
Email updates can fail on a duplicate. If the email a guest submits already exists on another profile in Mews, the update may fail.
Manual edits in Bookboost do not sync back. Only updates submitted through a form are written to Mews. Editing a profile directly in Bookboost does not change the Mews record.
Notes are one way. Reservation notes flow from Mews to Bookboost only. Notes added or changed in Bookboost are not written back.
Products and upsells are not written back. Bookboost cannot add inventory or add-on products, for example a room upgrade, breakfast, or a bike hire, to a Mews reservation today. Booked upsells must be entered in Mews. Reservation charges already in Mews are still readable through tokens; it is only the writing back of new products that is not supported.
Online check-out
Mews supports only two guest links today: online check-in and the property homepage. There is no online check-out link, so Bookboost cannot send a check-out deep link the way it does for check-in. In addition, the automatic communication Mews sends for online check-out cannot be turned off on its own; the only way to stop it is to disable the entire Mews online check-out feature. Online check-in and online check-out are separate features in Mews and behave differently.
Reservation time updates
Only the time is editable through a form. The date stays anchored to the reservation's original arrival or departure day.
Only the Mews integration supports this. Other PMS connectors are not affected.
If Mews rejects the requested time, for example a time outside the allowed window, the guest sees a generic submission failure rather than a specific message.
Technical considerations
Multi-property. Each Mews property needs its own integration and app in Bookboost.
API rate limits. Mews enforces API rate limits. Bookboost manages these internally, but syncing delays can occur.
Sync timing. Mews webhooks can be delayed, so Bookboost also polls Mews for consistency. Data syncs about every five minutes.
Operational best practices
Reservation notes. Add helpful guest information to Mews notes. Bookboost imports them, but does not write them back, so Mews stays the master copy.
Front desk awareness. Bookboost handles guest communication, but bookings must be modified in Mews. Make sure front-desk staff know where each action belongs.
Configuration and Setup
These limitations apply once the Mews integration is active. There is nothing to configure to encounter them. To connect a property, see Setting up the Mews integration; for how the integration works, see What the Mews integration does.
Support
Please contact us through the 'Talk to Us' option on the left menu in the platform, or through the Bookboost Support email at support@bookboost.io if you have questions or need additional support.