Add bookings to your website, and Couverty to your tools.

Five ways to add bookings to your website, plus connections to Google, 3CX, Stripe and your screens.

Works on every platformOfficial WordPress pluginDocumented REST API

Which integration method should you choose?

If the website runs on WordPress, use the plugin. If the platform accepts custom HTML (Webflow, Wix, Squarespace, Framer, Shopify), use the iframe widget. If it accepts nothing at all, share the hosted page. The API only makes sense on a custom website whose code you control. All five methods feed the same calendar: you can combine several without duplicating anything.

Comparison of the five ways to integrate Couverty bookings
MethodBest forTechnical levelLimitations
Hosted pageAny website, social media, Google Business Profile, QR codeNone: a link to shareThe visitor leaves the restaurant's website
iframe widgetWebflow, Wix, Squarespace, Framer, Shopify, custom themeCopy and paste into an HTML blockRequires a plan that allows custom code
Floating buttonWebsites where booking must be within reach on every pageOne line of scriptTakes up a corner of the screen on every page
WordPress pluginWordPress websites, with or without a page builderInstalled from the WordPress adminWordPress 6.0+ and PHP 7.4+
REST APICustom websites, apps, in-house toolsDeveloperYou build the booking interface yourself

What syncs, and what does not

A useful integration is one whose limits you know. Here is what flows, in which direction, and what stays manual.

What goes out from Couverty

  • Every confirmed booking becomes a Google Calendar event. A change updates the event, a cancellation deletes it.
  • Your menu (dishes and drinks, with prices), your opening hours, your exceptional closures and the Menu and Website links go to your Google Business Profile.
  • The "Book" button on your Google Business Profile points to your Couverty booking page.
  • The menu, drinks and daily menu feed the website, the QR code, the dining room screens and the WordPress plugin all at once. You enter it only once.

What comes into Couverty

  • Google reviews appear in the dashboard; you reply there without switching tools.
  • An incoming call identified by 3CX shows the guest's record in the softphone and creates a Couverty notification.
  • Stripe payments (card guarantee or deposit) are linked to the booking they belong to.

What stays manual

  • Google Calendar sync goes from Couverty to Google, not the other way round: an event created by hand in Google does not take up a table in Couverty. To block a time slot, use closures.
  • Bookings taken on a third-party platform do not come into Couverty: you have to enter them, or make Couverty your single point of entry.
  • The Google, 3CX, Stripe and API integrations require the Épicurien plan; the WordPress plugin and the screens require the Gourmet plan.

FAQ

What webmasters, agencies and restaurant owners ask before connecting Couverty.

No. None of the five methods requires touching the structure of the website.

Yes. They all feed the same calendar, with no duplicates.

No: it lives in an isolated iframe, and its code never runs in your page.

The iframe widget, pasted into a custom code block.

No. Sync goes from Couverty to Google only.

A 3CX Standard licence or higher, admin access to the console, and a Couverty API key.

No. The booking widget is in every plan; WordPress and the screens from the Gourmet plan; Google, 3CX, Stripe and the API with the Épicurien plan.

Yes, and the partner programme pays you for the venues you bring in.

A question? Contact us

Integrating for a client?

The partner programme pays you for the restaurants you bring in, with direct contact with the team that builds the platform.

A question? contact@couverty.ch