All articlesProduct Updates3 min read

PayOS connects your Square till to your guest profile

SStampede
PayOS connects your Square till to your guest profile (light cover)

Summary

PayOS runs on Square and puts orders, spend and visit frequency on the same guest profile as bookings, Wi-Fi sign-ins and reviews, with card-linked loyalty.

Square orders and payments on the same guest profile as your bookings, Wi-Fi sign-ins and reviews.

PayOS is the part of Stampede that connects the till to the guest profile. It runs on Square, and the idea is simple: the person serving a table can see what that guest has spent, how often they come in and what they usually order, and the marketing you send afterwards is built from the same record.

Most restaurants hold the payment data and the guest data in two different places. The POS knows what was sold and when. The marketing side knows who opted in and what they clicked. Neither knows that the guest who signed into the Wi-Fi in March is the same person who has been in six times since and orders the same bottle every time.

What the integration does

Square Restaurant POS orders and payments land on the guest profile alongside bookings, Wi-Fi sign-ins, reviews and loyalty activity. Purchases, values and visit frequency are visible during the visit and after it, and the same record is reachable from the terminal, so nobody has to switch between two screens to find out who is sitting at table nine.

That is the operational half. The marketing half is that a campaign can be built from what people actually bought last week rather than from a list somebody exported in the spring.

Loyalty without the scanning

Loyalty in PayOS is linked to the payment card. No app to open, no code to read out at the till, no stamp card left in another jacket. A guest pays, the points arrive, and an offer or discount applies from what they have bought before.

This matters more than it sounds. The schemes that fail are the ones where the guest has to remember to do something at the till and the person behind it has to remember to ask. Take both steps out and the loyalty numbers start being real.

What you can segment on

With spend on the profile, the obvious segments are there: spend level, purchase history, visit frequency, dietary preferences taken from the order, and review sentiment. A guest who came in twice a month and has not been for six weeks is a different conversation from a first-timer who left three stars.

Campaigns then run off live data rather than a third-party audience, so the offer goes to people who have already told you what they like by buying it.

Hardware

PayOS runs on Square hardware, from a compact device that suits a coffee shop counter to full terminals for multi-site operators. If you are already on Square, nothing changes at the till.

The honest caveat

An integration is only worth having if somebody reads the output. Wiring the POS to the guest profile gives you better data and better reporting, and neither of those pays for anything on its own. What pays is a manager who checks who is coming in tonight, and a campaign that goes out because a segment said so rather than because it is the first of the month.

Start with one of each. A pre-service look at the bookings with spend attached, and one win-back campaign to guests who have lapsed. Measure both against the previous month, then build the rest.

PayOS is live for Stampede venues running Square Restaurant POS. Book a demo to see it against your own menu, or if you are not on Square yet, sign up through the partner link.

See it running on your venues

One unified guest record across Wi-Fi, bookings, reviews and loyalty, and the marketing that acts on it.

Explore the platform