The house remembers the same guest.

A general manager is judged on whether the house feels consistent. A guest who stayed last year should not be a stranger at check-in. The preference they mentioned at the bar should still be true at the desk. That is property-level recognition, not a group-wide programme.

The PMS is usually where that memory is assumed to live. The card is there. The notes are there. The returning reservation can be made without retyping the name.

A property-system guest card knows what that system was told. It does not automatically know the point-of-sale charge, the spa booking, or the OTA stay that arrived on a proxy address. Sister properties often do not share a database. A lot of the memory that makes service feel personal still lives in one person’s notes.

So the house remembers in pieces. The guest who comes back through a different channel, or who spent at an outlet the PMS never saw, is treated as new. Service consistency becomes a function of who is on shift and which system they opened.

Casa Layer assembles one record per real guest from the property system, the outlets and the other tools the hotel already runs. The Master Profile sits above those systems rather than inside the PMS, so a group can run one property system in the city and another at the resort and still read the same person.

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. Replace the PMS later and the resolved person is untouched, because the person never lived inside that product.

Nobody has to ask the guest questions they have already answered. The desk reads the profile from the interface it already uses. A first property is typically live in three weeks.