Custom Guestplan integration
Appfront builds integrations with Guestplan, the online reservation system for restaurants and other hospitality businesses. Guestplan has standard integrations with POS systems such as unTill and with Google Reservations. For hospitality groups and venues with their own app, loyalty programme, staff scheduling or reporting, we build the connection so that reservations and guest data are not transferred by hand.
What is a Guestplan integration?
Guestplan is an online reservation system for hospitality. Guests book through the venue's website, through Google or by phone, and the venue manages tables, times and guests in Guestplan, including in an app for iOS and Android. Guestplan has integrations with POS systems such as unTill, Nappkin and Bork, so that availability is accurate and POS data reaches the guest record.
Whatever is not covered by those standard integrations is often done by hand. A hospitality group wants to see reservations and covers per location side by side, and exports them venue by venue. Staff schedules are drawn up without knowing how many covers are coming. And a custom app or loyalty programme does not know the guest, because the reservation sits somewhere else.
We build custom because venues differ: a single restaurant or a group, which systems sit alongside Guestplan, and which data needs to go where. We look at which integration options Guestplan offers for your situation, and under what conditions, in the first step, together with you and with Guestplan. We only use guest data for what the guest has given consent for.
Reservations in one place
Covers and reservations in your own systems.
Planning around busy periods
Schedule staff based on expected covers.
Aligned with Guestplan
An integration via the route Guestplan offers you.
How we build your Guestplan integration
We start with your venue or group: which systems do you use alongside Guestplan, which data is currently handled by hand, who needs to see what, and which guest data is involved. Then we look with Guestplan at which route is available. We often start with covers and reservations per location for staff scheduling and reporting, because these don't need guests' names. A custom app or loyalty programme follows once the first integration is running well. After that, we maintain the integration when Guestplan or your own systems change.
Systems, data and who needs to see what.
What Guestplan offers for your situation.
Reservations both ways, with checks.
Go-live, monitoring, and maintenance when things change.
What a Guestplan integration actually does
The components below appear in almost every Guestplan integration. Which ones you need depends on your venue.
Reservations
Per location and part of the day.
Covers
For staff scheduling.
Guests
With consent, for loyalty.
Locations
All locations side by side.
No-shows
Visible per period.
Log
Every message recorded.
Who we build a Guestplan integration for
The integration is intended for hospitality businesses that use Guestplan alongside other systems. The more locations and systems, the more time an integration saves.
Hospitality groups
Multiple venues. Seeing figures side by side matters most.
Restaurants with an app
Guests in your own environment. Consent is key.
Hotels
Restaurant alongside accommodation. One guest counts.
Software suppliers
A product for hospitality. Connecting is the key.
Technology and integrations
This page is about integrations with Guestplan. For your own reservation system, see our page on reservation software; for the POS, see our pages on the unTill integration and POS software; and for your own hospitality app, see our page on hospitality apps. You can read about our approach on custom software development.
Why Appfront for your Guestplan integration?
Covers exported venue by venue, and rosters that don't know how busy it will be, cost a hospitality business time and money every week. That's what we build on: reservations in one place, rosters based on expected footfall, and an integration agreed with Guestplan.
No exports
Figures arrive automatically.
The right staffing
Rostering based on covers.
Careful
Only with the guest's consent.
Security and privacy for a Guestplan integration
The integration may process guest data such as names, contact details and preferences. We only use the data that is needed and for which consent has been given, access credentials are stored encrypted, and every message is logged.
The integration runs in a European data centre, with encrypted storage and daily backups. We record the processing in a data processing agreement.
Frequently asked questions about a Guestplan integration
Questions hospitality owners ask before they get started.
Guestplan is an online reservation system for restaurants and other hospitality businesses. Guests book through the website, via Google or by phone, and the venue manages tables, times and guests in Guestplan, including through an app.
Yes, including with till systems such as unTill, Nappkin and Bork, and with Google Reservations. If your system is on that list and the integration does what you need, custom work isn't necessary. A custom integration is for an app, rostering or reporting that isn't covered.
That depends on what Guestplan offers for your situation. Which data is available, how access is arranged and under what conditions, we look at in the first step, together with you and with Guestplan. Only then do we build, so you don't get stuck on a route that doesn't exist.
Yes. The expected number of covers per part of the day and per location goes into your rostering, so you can see where more or fewer people are needed. No guest names are required for this.
Yes. Reservations, covers and no-shows per location and per period come together in a single overview, without anyone having to export them venue by venue. That way you can see where it's getting busier and where no-shows are rising.
Carefully. We only use the data that is needed, and for loyalty or marketing only from guests who have given their consent. We record the processing in a data processing agreement.
The integration reports it and records what went wrong. The message is retried or queued for review, so no reservation is lost or arrives twice.
For hospitality groups with multiple locations, for restaurants with their own app or loyalty programme, for hotels with a restaurant, and for software suppliers who want to connect their product to Guestplan. If you run a single venue with the standard integrations, a custom integration is often not needed.
Guestplan connected to your own systems?
Tell us which systems you use alongside Guestplan and which data is currently transferred by hand. We'll show you which route is available and what the integration looks like.