Loyalist × Toast

Connecting Toast puts what a guest actually spends onto their profile. Every closed check, the items on it, and the modifiers behind them attach to the person who ordered, so a restaurant can see lifetime spend per guest and target campaigns on buying history: the regulars who order heavily from the wine list, the guests whose checks run large.

How it works

A point-of-sale system knows what every table spent and nothing about who was sitting there. Toast sends each closed check to Loyalist line by line, and Loyalist attaches it to a guest, which is the step that turns last night’s revenue into one person’s history. What arrives is the spend, the items rung in, the modifier options on each one, any discounts, the table, the server, and the channel the order came through. Once a check belongs to a guest, the useful things follow: lifetime spend per person, what someone orders when they come in, and segments worth sending a campaign to. Loyalist is part of the Toast Partner Ecosystem.

Key benefits

  • All Toast check, item, and modifier details are brought into Loyalist. Spend, the items rung in, the modifier options on each one, discounts, the table, the server, and the order channel. Modifiers are the part most check feeds leave out, and they 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. Dine-in checks carry no name, so each is matched to the booking that held its table. From there spend belongs to a person rather than to a night, and a profile shows what a guest has spent across all of their visits rather than only the last one.
  • Campaigns and journeys can be built on what guests actually buy. Spend and item detail make the segment: the guests who order heavily from the wine list, the ones whose checks run large, the ones who have not been back in months. An email or a journey then goes to that group, so the guests worth bringing back are the ones being asked.
  • Some orders arrive with guest contact detail already attached. Where an order carries a name, email, or phone, that detail is used to find or create a profile directly. A dine-in check never carries it, in Toast or in any other point of sale, so those reach a guest through the reservation match instead.
  • The entire check history is imported at the beginning. History loads back to the earliest order on the Toast account rather than to the date of connection, so a guest’s lifetime spend is right from day one instead of starting at zero.

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.

How far back does Toast spend data go?

To the venue’s earliest order, not to the day Toast was connected. The whole account is walked during onboarding, and every check found is matched into guest records that already exist rather than filed in a separate Toast list, so a regular’s lifetime spend is right the first time anyone looks at it. New checks then arrive on a scheduled import rather than the moment one closes.

Why do some Toast 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.

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