TableFlow integrates with partners we explicitly chose — not "we have a Zapier connection". Mollie for payments, Eitje for staffing, TheNextReview as sister product for guest feedback, and Google for the guest card and bookings from Search and Maps.
Embed on your own restaurant website — no redirect to OpenTable. Date, guests, moment in three fields. Lunch, dinner, breakfast, high wine — all configurable. Color accents match your brand. Hotel De Wolfsberg is one example.
No "check the integrations marketplace". Three partners TableFlow rests on, with flow we test end-to-end.
Payments stack. Deposits, payment links, refunds. iDEAL, Bancontact, card, PayPal, Apple Pay, Google Pay, SEPA. Webhook integration for real-time confirmation. TableFlow's own SaaS billing also runs via Mollie.
Roster + staffing. Eitje sends your roster to HorecaGPT — combined with your occupancy for advice. Read-only integration.
Sister product, native coupling. TableFlow sends feedback requests after every visit, TheNextReview collects scores internally, low scores hit you first — not Google.
Your guests keep their guest card and gift cards in Apple Wallet. The balance updates itself after every visit.
Your guests carry their points balance in Google Wallet. Walk past your place and their card appears on their screen.
Book a table straight from Google Search and Maps, with no detour via your website. The booking lands in your calendar.
Mollie payment links, Eitje roster sync, TheNextReview scores — all surfaced in the TableFlow mobile interface. The agenda mobile view shows a regular guest sidebar (with star detection), reservation list with status filtering, and instant access to walk-in modal.
Many "integrations" are marketing fluff. Here's literally what happens:
TableFlow ↔ Mollie
TableFlow → Mollie: deposit-link create, refund-request, payment-link create, subscription-mandate setup.
Mollie → TableFlow: webhook on payment success/failure, refund status, mandate events.
Eitje → HorecaGPT (one-way)
Eitje → HorecaGPT: roster data (per day, per shift, per staff member with role). HorecaGPT combines this with your occupancy for staffing advice. No reverse flow.
TableFlow + HorecaGPT ↔ TheNextReview
TableFlow → TheNextReview: feedback request after every visit (with guest email, reservation ID, restaurant name).
HorecaGPT → TheNextReview: broader review context for advice formation.
TheNextReview → TableFlow: guest feedback score (1-5) visible in guest profile + dashboard alerts on low scores.
