Loyalist × Oracle Simphony
Connecting Simphony puts what a guest actually spends onto their profile. Checks arrive with the items rung in, the modifiers attached to them, and any discounts applied, and each is matched to the reservation that held its table, so spend becomes part of a guest's history rather than a nightly total.
How it works
Simphony records what a table spent, not who was sitting at it. Checks arrive in Loyalist with the spend, the items rung in, the modifier options on each one, any discounts applied, and the table. The check names nobody, as no point-of-sale system does for dine-in service, so each is paired with whichever reservation covered that table that evening. Once a check is attached to a person, the spend stops describing a night and starts describing a relationship, which is what makes lifetime value and campaign results countable.
Key benefits
- All Simphony check, item, and modifier details are brought into Loyalist. The spend, the items rung in, the modifier options on each one, any discounts applied, and the table. Item and modifier detail is what allows a guest to be understood by what they order rather than only by what they spend.
- Checks are matched to guests automatically. Nothing on the check identifies the diner, so it is paired with the reservation covering that table. Money then collects against a person rather than a service period, letting a modest but frequent guest stand alongside an occasional large one.
- Campaigns and journeys can be built on what guests actually buy. A group can be defined by check size, by a menu category someone buys from repeatedly, or by how long it has been since their last visit. Whatever defines it, the message goes only to that group.
- The entire check history is imported at the start. The load covers the Simphony account itself rather than beginning on the day of connection, so a regular’s spend is present from the first look instead of gathering afterwards.
Frequently asked questions
How does a Simphony check reach the right guest?
Through the reservation. Since the check itself names nobody, it is paired with the booking that covered that table at that hour. Anything with no booking behind it stays unattached, so how thoroughly the book is kept shapes a venue’s match rate as much as the connection does.
Does Loyalist see individual items from Simphony?
Yes, along with the modifier options on them and any discounts applied. That detail is what lets a tag rule read what a guest orders rather than only the size of the check, so a guest who works through the wine list is distinguishable from one who spends the same amount on a large table.
What happens to my Simphony history?
All of it. Earlier checks arrive at setup and merge into guest records the guestbook already holds instead of forming a parallel list, so totals read correctly from the outset.
Last updated
