Loyalist × Omnivore
Omnivore brings check and item detail into Loyalist from point-of-sale systems connected through an Omnivore terminal. Each check 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
Omnivore sits between a restaurant’s point-of-sale system and everything that wants to read it, which makes it a route into Loyalist for venues whose system has no direct connection. Checks arrive with the spend, the items rung in, the modifier options on each one, any discounts applied, and the table. A dine-in check carries no guest, so each is paired with whichever reservation covered that table that evening, and the spend then belongs to a person rather than to a service.
Key benefits
- All check, item, and modifier details available through Omnivore 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 lets a guest be understood by what they order rather than only by what they spend.
- Checks are matched to guests automatically. The check names nobody, so it is paired with the reservation covering that table. Spending then attaches to a person rather than a shift, letting a frequent modest guest read as clearly as an occasional large one.
- Campaigns and journeys can be built on what guests actually buy. Money and menu both work as filters, so a list can be the biggest spenders, the people who reorder one dish, or the guests who have drifted away since connection. Only that list gets the message.
- A venue whose point-of-sale system has no direct connection still gets item-level data. Omnivore reaches systems that would otherwise report nothing at all, and it carries the items and modifiers rather than only a check total.
Frequently asked questions
What can I do with Omnivore spend once it is on a guest?
Segment and message on it. Spend and item detail both become filters, so a campaign can go to the guests whose checks run largest or the ones who order a particular dish every visit, and a journey can trigger off a guest’s spending pattern rather than off a list somebody maintains.
How does an Omnivore check reach the right guest?
Through the reservation. No point-of-sale system records who was seated, so each check is paired with the booking covering that table at that hour. What cannot be paired stays unattached, which makes the book the thing that decides how much spend becomes guest history.
Does item detail come through Omnivore?
Yes. The items rung in arrive with the modifier options on each one and any discounts applied, which is more than a check total and enough to tag a guest on what they order rather than only on what they spend.
Last updated
