Casa Layer connects to Mews as a PMS source under your stack. The integration reads guest-related records from Mews into your Property Group so identity resolution can build Master Profiles across Mews and your other connected sources. Reservations and stay operations stay in Mews. Casa Layer does not replace your PMS.
What connects
When Mews is connected for your workspace, Casa Layer can read guest-related classes such as:
Guest profiles from Mews customers (name, contact details, and related attributes Mews exposes under the access you approve)
Reservations and stay context, including channel and rate-plan context when Mews provides it
Stay spend lines from order items linked to those reservations
Notes attached to guests or reservations where available
Marketing consent signals derived from Mews customer options when those options are present
Loyalty programmes and memberships when your Mews enterprise exposes them
Exact coverage depends on what your Mews enterprise shares under the credentials you issue. Every live connection reads only.
How setup works
Setup is handled with Casa Layer during onboarding. At a high level:
Your hotel issues Mews Connector API credentials (client token and access token) for the enterprise Casa Layer should reach. You can revoke those credentials at any time.
Casa Layer stores the connection for your Property Group and maps the Mews enterprise to the right Casa property.
A historical backfill brings relevant stay history into Casa Layer for identity resolution. Scope is agreed per hotel.
Ongoing reads keep guest fragments current. Staff keep working in Mews as the system of record.
Casa Layer does not ask you to paste secrets into a public form for general Help Center readers. Credentials stay under hotel control and Casa onboarding.
What staff see after connect
Once Mews data is in your Property Group:
Master Profiles resolve the same guest across Mews and other connected sources, with provenance so you can see which source contributed a field
Guest Lookup (where your workspace enables it) lets front-of-house search that resolved identity as a Chrome overlay beside existing tools
Partners and internal tools can read the same guest context through Casa Layer’s open API and agent tools (read-only today). Detail lives on docs.casa-layer.com
Source records from Mews remain source records. Resolution does not pretend one Mews row is the whole truth about a guest.
Limits and what this does not replace
Read only today. Casa Layer does not write reservations, folio changes, or guest edits back into Mews.
Not a rip-and-replace PMS. Check-in, inventory and stay operations stay in Mews.
Not a CRM or messaging product. Campaigns and inbox work stay in the tools that already own them.
Payment card data and other out-of-scope fields are not part of the read surface. You approve what each connection may share.
FAQs
Does connecting Mews change our front-desk workflow?
No. Staff keep working in Mews. Guest Lookup is optional context beside that workflow where your workspace enables it.
Who creates the Mews credentials?
Your hotel. Casa Layer connects under credentials you issue and can revoke. Exact steps are confirmed during onboarding with Casa Layer.
Will Casa Layer write back into Mews?
Not today. Live connections read only.