Guest recognition above the property system.

The property management system is where reservations live, so teams treat its guest card as the house record. A repeat stay can be made without retyping the name. Sharing, where it is switched on, can show that card across properties on the same system.

That card is necessary. It is also attached to the product that holds the reservation. Recognition for the rest of the house is then assumed to follow from it.

The PMS card knows what that system was told. It does not automatically know the point-of-sale room charge, the spa booking with no room number, or the direct booking made on a work email while the OTA stay arrived on a proxy address. Those are other fragments, keyed for other jobs.

Identity is a second gap. The same person arrives as several records even inside one property system: a married name and a passport name, a personal email and a work email. A guest card stores what it was given. It does not decide which of those records are the same person.

Attachment is the third. Change the PMS and you are migrating cards, not pointing the same record at a new feed. Guest identity that lives inside the property system is rebuilt every time the property system is.

Recognition sits above the property system. The PMS stays. Casa Layer reads it as one feed among others and reconciles the fragments into one Master Profile per real guest. Guest identity should sit above every system that touches it, PMS included, not inside any one of them.

Casa Layer builds that record and holds it. We sell no applications on top of it, so there is nothing here for it to be locked into. Your own source systems stay the record throughout. The new PMS, if you switch, becomes one more feed into a stable record rather than the new permanent home for a decade of guest history.

You decide what Casa Layer can do in each system, under credentials you issue and can revoke. Every connection live today reads only. Nothing on this page asks you to rip out the PMS. The Switching PMS page is the longer version of that sequence, if a migration is already on the calendar.