Five systems, one customer: the integration problem every multi-venue business has

By Jason Fuller · Effulge

A multi-venue hospitality group (an inn, restaurants, a private-events arm, a retail shop) runs on five systems that work beautifully and refuse to speak to each other:

• Mews runs the hotel.
• OpenTable runs the dining room.
• Tripleseat runs private events and catering.
• Shopify runs the store.
• Klaviyo sends the email.

Now trace one guest. She books a weekend stay, has dinner twice, asks about hosting her company retreat, and buys a case of wine on the way out. To the business, that's one exceptional customer worth cultivating for a decade.

To the software, she's five strangers.

Mews knows her as a reservation. OpenTable as a party of two. Tripleseat as a lead. Shopify as an order. Klaviyo emails her a generic newsletter because it has no idea the other four relationships exist. Nobody did anything wrong. The category just works this way: every system of record is an island, and the guest is the water between them.

Why the obvious fixes fail

"We'll export CSVs." Someone does, monthly, for a while. The mappings rot, the intern leaves, and the spreadsheet becomes archaeology.

"Zapier it." Point-to-point zaps work for two systems. At five, you have ten possible connections, no shared source of truth, and silent failures nobody notices until a VIP gets a "welcome, first-time guest!" email during her sixth stay.

"Buy the all-in-one suite." The suite is mediocre at all five jobs. You chose best-of-breed tools for good reasons. Ripping them out to solve a plumbing problem is surgery to fix a leaky faucet.

The pattern that works: an event-driven hub

Don't connect tool A to tool B. Connect everything to a middle layer:

1. Events in. Every system already emits them: booking created, reservation seated, lead received, order placed. Webhooks catch them in real time.
2. Identity resolution in the middle. The genuinely hard part. Email is the join key, but it's messy: typos, shared addresses, the assistant who books for the boss. This is where engineering earns its keep: matching rules, confidence scores, and a human-review queue for the ambiguous 5%.
3. One guest record. Stays, covers, events, purchases, lifetime value, all in a unified profile each system can read.
4. Actions out. Klaviyo becomes the brain instead of a blaster: post-stay dinner invitations, retail offers to event bookers, VIP flags when a hotel guest crosses a spend threshold, win-backs for no-shows.

One caution from the field: not every platform plays equally. Some APIs are excellent (Shopify, Klaviyo), some are solid with quirks (Mews, Tripleseat, which just sunset its old authentication scheme and broke integrations that weren't watching), and some are partner-gated with weeks of approval lead time (OpenTable). Architect so the reluctant system is a nice-to-have feed, not a load-bearing wall.

What it's worth

The unified profile turns questions you couldn't ask into routine queries. Which dinner guests have never stayed overnight? Which event leads came from existing customers? What's the actual lifetime value of a wine-club member across all five systems? Every answer is a campaign, and every campaign runs against customers you already have: the cheapest revenue there is.

If your business runs on systems that don't share a customer, that's the exact shape of problem we build for. See how we scope it at effulge.ai.

---