Connecting WiFi Guest Data to Your POS System: The Single Customer View

The Data Silos Problem

Your guest WiFi knows when a guest was in, how often they come and which location they used. Your POS knows what they ordered and what they spent. In most venues these two records never meet.

Illustrative example: the WiFi guest list shows "Sara, sara@example.com, in on 14 separate days since March". The POS has a customer profile for sara@example.com with an average ticket and a habit of adding lunch to her coffee. Same person. Put the two together and you have a single customer view: how often she comes and what she is worth.

Before going further, one thing to be clear about. VoqadoWiFi does not integrate with any POS system. What it does give you is your guest list, which you own, as a CSV export at any time. Everything below works from that export, or from whatever tools you already use.

Email as the Matching Key

Email address is the practical way to match the two. The WiFi login page collects it. The POS has it only where the guest gave it: a customer profile, a loyalty scheme, an online order or a booking.

A manual match, which is enough for most single site venues:

1. Export customers with email addresses from your POS (only the fields you need).
2. Export your guest list as CSV from VoqadoWiFi.
3. Clean both email columns the same way: lower case, spaces trimmed.
4. Match them in a spreadsheet with a lookup on the email column.
5. Keep only guests who agreed to marketing if you plan to use the result for emails.

Expect only part of the list to match. Guests who pay cash, never give an email at the till, or used a different address on each side will stay WiFi only. That is fine. The matched group is small but has the fullest picture.

Do it quarterly, not daily. A one off match tells you whether the combined view is worth building properly before you pay anyone to automate it.

Which POS Systems Have APIs

To keep the match up to date automatically you need API access to your POS, and someone (you, a developer or an integration tool) to connect it to your email platform. API access varies by vendor and sometimes by plan, so check with yours. Two examples from the vendors' own documentation:

Square. The Customers API lets developers create and manage customer profiles, which can include an email address (Square Developer).

Toast. API access is split by integration type. Standard API access is limited to read (GET) requests on APIs such as orders, menus and restaurants, while partner and custom integrations are granted wider access based on their requirements (Toast developer guide).

For other systems, ask the vendor three questions: can I export customers with email addresses, is there an API for customers and orders, and is it included in my plan?

If you use Mailchimp, VoqadoWiFi's Growth plan syncs guests there (name, phone and the tags "wifi-guest" and "location:" plus the venue name). Before emailing that audience, make sure your login page asks for marketing consent separately, with an unticked box; VoqadoWiFi's explicit consent mode does this. Some POS systems connect to Mailchimp as well: Mailchimp lists a Square integration that syncs customer contact and order details (Mailchimp). That lets the two records meet inside Mailchimp rather than in a spreadsheet, matched on email. Check what your POS offers before building anything custom.

What the Combined Data Enables

Once WiFi visits and POS spend sit against the same email address:

Spend tiers. You can separate frequent low spenders from occasional high spenders. For example, a guest who comes twice a month and spends €80 each time is worth more (€160 a month) than one who comes six times at €12 (€72 a month). The high spender probably wants to hear about a tasting menu or a private room, not a coffee voucher.

Menu preferences. POS categories (mostly drinks, mostly food, often orders dessert) let you match the offer to the person. A birthday dessert offer lands differently with someone who orders dessert every time.

Churn by value. A high spending regular who has not been in for 25 days deserves a personal note sooner than an occasional guest at the same gap. WiFi data alone shows the gap; POS data shows which gap matters more.

When not to bother: if you have one location and a few hundred known guests, you can probably name your best customers already. The single customer view earns its keep with more sites, more staff turnover, or a list too big to know by face.

Privacy Considerations

This is general information, not legal advice.

Combining WiFi data with purchase history builds a richer profile of each person, and under the GDPR that brings obligations:

• Purpose. Personal data must be collected for specified, explicit and legitimate purposes and not used in ways incompatible with them (GDPR Article 5(1)(b)). If guests were told their email was for WiFi access and marketing, matching it to their spending is a new use. Say so in your privacy notice before you start.
• Transparency. When you collect data you must tell people the purposes and the legal basis (Article 13). Update the notice on your login page and at the till. Our guest WiFi privacy notice template is a starting point.
• Retention. Apply your retention rules to the combined dataset, not just to the WiFi list. If you delete a guest from one, delete the match too.
• Records. Add the matching to your records of processing activities (Article 30). Organisations with fewer than 250 employees are exempt from Article 30 only in limited cases: not if the processing is likely to result in a risk to people's rights, is not occasional, or involves special category data. Regular marketing use of a guest list is not occasional, so most venues doing this should keep the record.

Only use matched data for marketing to guests who agreed to marketing. Accepting the WiFi terms is not marketing consent. Keep the two as separate choices on your login page (VoqadoWiFi's explicit consent mode does this) and use only the marketing choice to decide who gets emails.