Loyalist × Agilysys
Agilysys runs the outlets across a whole property, so a guest's spend in the restaurant, the bar and by the pool arrives in Loyalist as one person's activity rather than three separate outlet reports. Room charges tie that spend back to the stay.
How it works
A resort guest eats in the restaurant, drinks at the bar and signs for lunch by the pool, and in most systems that is three unrelated transactions. Agilysys runs those outlets together, so checks arrive in Loyalist with the items rung in, the outlet they came from, and the way they were settled. Where a charge was posted to a room rather than paid at the table, the stay behind it is what identifies the guest. Everything else is paired with the reservation covering that table, the same as any dining room.
Key benefits
- Spend across every outlet lands on one guest. The restaurant, the bar, the pool and room service stop being separate reports and become one person’s activity across a stay, which is the number a property actually wants.
- A room charge carries its own identity. When a guest signs to their room rather than paying at the table, the stay is what names them, so that check reaches a profile without depending on a reservation match.
- Item detail travels with the check. What was ordered comes through alongside what it cost, so a guest can be understood by preference rather than only by total.
- Resort guests and restaurant regulars are the same list. A property that also serves locals can tell the two apart, or deliberately treat a returning guest as both, once their outlet spend and their bookings sit on one record.
Frequently asked questions
Does this work for a property with several outlets?
That is the case it fits best. Agilysys is normally deployed across a whole property rather than a single dining room, so the value is the consolidation: one guest, many outlets, one record, instead of a separate picture per venue.
How is a guest identified on a room charge?
By the stay it was posted against. That is the one case in a dining room where the check names somebody without a reservation behind it, and it is why property-wide systems tend to produce higher match rates than a standalone restaurant.
What happens to spend from guests who are not staying at the property?
It behaves like any restaurant check: no identity on the check itself, so it reaches a guest through the reservation that held the table. Properties serving a strong local trade get the most from keeping that book complete.
Last updated
