1. Onboarding intake: The property provides its initial setup details through the onboarding dashboard in Mews Operations, including property information, users and the inputs needed to begin configuration. 

2. Configuration: The property configures its setup in Mews Operations, such as space categories, rate plans, services and products, taxes and accounting categories, payment and cancellation policies, and user accounts, working through the onboarding dashboard. The Mews Deployment & Adoption/ onboarding team provides guidance, validates progress and approves go-live readiness. For Custom-package onboardings, some configuration is completed hands-on by the onboarding team. 

3. Data migration: Reservations, guest profiles and, where agreed, historical data are migrated from the previous system. 

4. Integrations: Channel manager, OTA connections and any Marketplace integrations are connected and tested. 

5. Training and go-live: The property completes Mews University learning paths, runs a parallel test period where needed, and cuts over on the agreed go-live date. 

Simple, standalone properties can go live in as little as 10 business days from completed intake.  

Standard implementations typically take 6 to 12 weeks, depending on property complexity, integration requirements and data migration scope.  

Enterprise and multi-property deployments: Timeline as agreed in the SOW. 

• Completed onboarding intake, including property, space, rate, tax and accounting configuration inputs 

• Channel manager and OTA credentials for distribution connections 

• Historical reservation and guest data in the agreed migration format, where migration is in scope 

• Named property users and their permission levels 

For the full integration catalogue, see the Mews Marketplace: https://www.mews.com/en/hospitality-software-marketplace.  

Distribution connections such as channel managers, direct OTA connections to Booking.com and Expedia, and all other integrations are client-configured via the Marketplace. 

Web application embedded in the Mews operating system, accessed at app.mews.com from any modern browser.  

A companion mobile app, Mews Operations app for iOS and Android, supports housekeeping and in-room charge posting.  

A sandbox environment is available at app.mews-demo.com. 

1. Manage arrivals, departures and in-house guests from the timeline and reservation views 

2. Create and modify reservations, group blocks and rates 

3. Manage folios, routing, invoicing and payments through to the automated night audit 

4. Update housekeeping statuses and tasks 

5. Run operational reports and configure the property, including Marketplace integrations 

Continuous deployment. Changes are rolled out by Mews to all properties automatically; larger features may be released gradually behind feature flags or as controlled rollouts.  

There are no client-installed components to update for the web application; the mobile app updates via the public app stores. 

Feature releases: Continuous, multiple times per week.  

Major feature launches: Communicated via release notes and seasonal release announcements. 

Security patches: As required, applied by Mews without advance notice. 

No client action is required for standard updates. All changes to the web application are applied automatically by Mews.  

Mobile app updates are delivered through the Apple App Store and Google Play and should be kept current on property devices.  

Where a release introduces a setting that the property may want to adopt, this is flagged in the release notes; adoption is optional unless stated otherwise. 

Distribution: Direct connections to Booking.com and Expedia, plus certified channel managers via the Marketplace.  

All other integrations such as locks, guest messaging, upselling, accounting, RMS and more are client-configured via the Mews Marketplace: https://www.mews.com/en/hospitality-software-marketplace.