Loyalist × Oracle OPERA

OPERA runs the front desk at a large share of full-service hotels, holding the guest profile, the reservation and the folio. Connecting it puts a stay on the same record as that guest's restaurant visits, so the property sees one person rather than two.

How it works

OPERA is the system most full-service hotels run their front desk on, and it holds three things worth joining to a restaurant: the guest profile with its preferences and membership, the reservation, and the folio showing what the stay came to. Bringing those into Loyalist means a guest who checks in is the same record as the guest who books a table, rather than two profiles that happen to share a name. Preferences recorded by the front desk and preferences recorded by the floor stop living apart.

Key benefits

  • The profile the front desk keeps joins the one the restaurant keeps. Preferences, membership standing and history recorded at check-in sit alongside what the dining room knows, so recognition works in both directions.
  • Folio detail shows what a stay was actually worth. What was charged across the stay arrives with the reservation, so a guest’s value reflects the whole visit rather than the room rate.
  • Restaurant history is available before a guest arrives. Somebody whose preference was noted over dinner last spring is recognisable at check-in, which is where recognition matters most and usually travels least.
  • Guests can be segmented across the property. Frequent stayers who never eat in, and diners who have never stayed, are each a list worth treating differently.

Frequently asked questions

Does this suit large properties and groups?

That is where it earns its place. OPERA is normally run by full-service hotels and groups with several outlets, and the more places a guest can spend, the more a single record is worth.

What about membership and loyalty held in OPERA?

Membership standing is part of the guest profile rather than something derived from stays, so it travels with the guest and can be used the same way any other attribute is, in a segment or on a guest’s record before service.

Does a guest need to stay to be recognised?

No. Somebody who only ever eats in the restaurant is a guest record like any other. The connection matters for the people who do both, which is usually a larger group than either system shows on its own.

Last updated

More Integrations

See all integrations

Get started with Loyalist.

If your hospitality group is looking to supercharge your data, we’d love to chat.

Book a Demo