Loyalist × SpotOn

How it works

A point-of-sale system knows what every table spent and nothing about who was sitting there. SpotOn sends its closed checks to Loyalist line by line rather than as nightly totals, and Loyalist attaches each one to a guest. What arrives is the spend, the items rung in, the modifier options on each one, any discounts applied, and the table. A dine-in check carries no name, so it is paired with whichever booking held that table that evening, and the spend then belongs to a person instead of to a service. Once it does, lifetime spend and what someone orders when they come in both become things a restaurant can act on.

Key benefits

• All SpotOn 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. Modifiers carry what reads as preference rather than as revenue: the substitution, the temperature, the allergy note repeated on every visit.
• Every check a guest has paid adds up on one profile. Nothing on a dine-in check says who ordered it, so each is paired with the booking holding that table. After that the money is attached to a person, and a profile carries the whole run of their visits rather than the most recent one.
• Campaigns and journeys can be built on what guests actually buy. A segment can be drawn from the money or from the menu: guests working steadily through the wine list, guests whose average check sits high, guests who have gone quiet since the spring. The message reaches them and nobody else.
• The entire check history is imported at the start. The load reaches back through the SpotOn account rather than beginning at the connection date, so a guest of several years arrives already counted.

Frequently asked questions

Does Loyalist see modifiers, or only the menu item?

Both. A check arrives with the items rung in and the modifier options attached to each one, which is the level most check feeds stop short of. That detail is what separates revenue from preference: two guests can order the same dish, and only the modifier records that one of them always asks for it without butter.

Why do some SpotOn checks never reach a guest?

Because a dine-in check has no name attached to it. Matching depends on a reservation covering the same table at the same time, so a check with nothing to pair against stays unmatched: a walk-in nobody logged, two tables combined mid-service, a booking made under someone else’s name. The share that does pair up is the venue’s match rate.

What happens to my SpotOn history?

All of it. Earlier checks are pulled in at setup and folded into guest records the guestbook already holds, so nobody starts at zero and a long-standing regular reads as one from the beginning.

Last updated August 23, 2026