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

The Data Silos Problem

WiFi session data knows when a guest was in your venue, how often they visit, and how long they typically stay. Your POS system knows what that same guest spent on each visit and what they ordered. These are complementary datasets — but in most hospitality operations, they are completely separate.

The WiFi CRM contact "Sara — first name, email, 14 sessions since March" and the POS transaction history "email receipts to sara@example.com, average bill €38, orders coffee and frequently adds lunch" are the same person. Combining them gives you a single customer view: a marketing-actionable profile that integrates behaviour (from WiFi) with purchase data (from POS).

Email as the Matching Key

The practical mechanism for matching WiFi data to POS data is email address. Both systems should have the guest's email — the WiFi portal collects it at login, and the POS system has it if the guest receives email receipts, participates in a digital loyalty programme, or makes reservations via a booking system that requests email.

1. Export email addresses from POS transaction data (anonymised to email only, no personal detail)
2. Match against VoqadoWiFi subscriber list
3. For matched contacts, append transaction-level data as custom merge fields in your email platform

Not every subscriber will have a POS match — guests who pay cash or do not receive email receipts will remain WiFi-only contacts. But the matched segment (typically 20–35% of the WiFi list for restaurants) is highly valuable because it has the most complete profile.

Which POS Systems Have APIs

For automated matching and ongoing sync, you need an API. Current POS systems with accessible APIs for independent hospitality venues:

Lightspeed Restaurant: Full REST API; connects to email platforms via Zapier or direct webhook. Relatively straightforward integration.

Square: Good API documentation, webhook support, Mailchimp native integration available. Best option for smaller venues.

Toast: Extensive API, designed for multi-location operators. More complex but comprehensive for larger operations.

Shopify POS (for retail): Native integration with most email marketing platforms. Simplest combined WiFi + POS view for retail.

Revel Systems: API available but requires developer work for custom integration. Not recommended for venues without in-house technical resources.

What the Combined Data Enables

With WiFi session data and POS transaction data matched at the contact level:

Spend-tier segmentation: Identify your high-spend vs low-spend subscribers regardless of visit frequency. A subscriber who visits twice per month but spends €80 per visit is more valuable than one who visits six times at €12. Email content for high-spend subscribers should reflect their profile — wine recommendations, tasting menus, private events — not generic promotions.

Menu preference signals: POS data at the category level (orders mostly beverages, orders mostly food, high dessert order rate) enables content-matched emails. "Your birthday month offer: our signature dessert tasting for two" resonates differently with a subscriber who regularly orders desserts versus one who orders drinks-only.

Churn by spend tier: A high-spend subscriber who has not been in for 25 days is a higher-priority re-engagement target than a low-spend subscriber at the same interval. Without POS matching, your WiFi CRM cannot make this distinction.

Privacy Considerations

Combining WiFi session data with POS transaction data creates a richer personal data profile and increases your obligations under GDPR. Specifically:

• Your privacy policy must reference the types of data combined and the purpose
• The legal basis for combining datasets should be reviewed (typically still consent for marketing purposes)
• Your data retention policy must apply to the combined dataset, not just the WiFi data in isolation

Document the data matching process in your Records of Processing Activities (ROPA) — a straightforward requirement under GDPR Article 30.