Zenchef widget integration
This plugin allows you to integrate your restaurant's Zenchef reservation widget directly on all pages of your website.
Solid choice
Zenchef widget integration is a solid plugin choice in 2026, with a few things worth checking first. It runs on 2K+ sites and was last updated 3 days ago, and scores 71/100 on our health check.
- Actively developed — last update 3 days ago
- Tested with the latest WordPress (7.1)
- Momentum — downloads up 185.5% vs the previous 30 days
- Very few reviews so far
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Zenchef widget integration stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| food | #82 |
| reservation | #97 |
| restaurant | >100 |
Version adoption
Share of active sites per release.
About Zenchef widget integration
From the official readme · v1.5.0Description
This plugin allows you to integrate your restaurant’s Zenchef reservation widget directly on all pages of your website, allowing your customers to take reservations directly without having to switch page.
You can also customize the integration according to your needs.
The widget is set up with your restaurant’s public ID, which starts with rpid_ (for example rpid_AB12CD34). Restaurants that set the plugin up with a numeric restaurant ID can keep it for now, but should switch to the public ID: the settings page shows a reminder until they do.
Usage
Default (global) widget
Once your restaurant’s ID is set, the widget is added automatically to every page of your website, with a floating booking button positioned according to the settings.
Shortcode
You can also place the widget inline on a specific page or post using the [zenchef_widget] shortcode. With no attributes, it uses the same settings as the global widget:
[zenchef_widget]
You can override any of the settings per-page (useful for sites managing several restaurants):
[zenchef_widget restaurant_id="rpid_AB12CD34" open_delay="0" position="center"]
All of the settings from the admin page can be overridden as shortcode attributes:
[zenchef_widget restaurant_id="rpid_AB12CD34" language="fr" primary_color="#cc0000" hide_button="1" auto_open="0" disable_gtm="1" disable_ga4="1"]
When the shortcode is used on a page, the floating global widget is not also injected, so there is never a duplicate.
Tip for the Gutenberg editor: Insert the shortcode using a Shortcode block (Add Block / Shortcode), not a Paragraph block — Paragraph blocks can auto-format quotes and break the attributes. The widget only renders on the front-end of your site; Gutenberg does not preview shortcodes inside the editor.
Support
For plugin support, please visit the support center.
Privacy policy
Our reservation widget plugin relies on the Zenchef service to enable restaurants to manage table reservations directly from their website. It requires a subscription to Zenchef.
Purpose
The Zenchef service is integrated into our plugin to provide a reservation widget on the restaurant’s website, allowing customers to reserve tables online seamlessly.
Data Transmission
User data is transmitted to Zenchef when a customer makes a reservation or updates their reservation details through the widget.
What is stored on the visitor’s device
The plugin itself sets no cookies and uses no local storage. However, it loads the Zenchef SDK from https://sdk.zenchef.com/v1/sdk.min.js, which embeds the booking widget in an iframe served from bookings.zenchef.com. That iframe writes to the visitor’s device as soon as the page loads, before the visitor interacts with the widget:
aws-waf-token(cookie) – distinguishes visitors from automated trafficawswaf_session_storage,awswaf_token_refresh_timestamp(local storage) – distinguishes visitors from automated trafficunleash:repository:sessionId,unleash:repository:repo(local storage) – keeps feature rollouts consistent across visitsbugsnag-anonymous-id(local storage) – groups error reports from the same device
Note that local storage counts as storage on terminal equipment under ePrivacy Article 5(3) (and §25 TDDDG in Germany), just as cookies do.
The rest is written only once the visitor does something:
formDataFromCookies(cookie) – written when the guest ticks “Save the information for my next reservations” and books. Holds their name, email, phone, country and postcode so the form can be pre-filled next time. Cleared when the browser closes, and deleted if the box is unticked.zc_popup_*(local storage, on your own domain) – written when the visitor dismisses a widget popup, so it is not shown again for 14 days.adyen-checkout__checkout-attempt-id(local storage) – written at a payment step, at restaurants that take payment through Adyen.__stripe_mid,__stripe_sid(cookies) – written at a payment step, at restaurants that take payment through Stripe.
If your restaurant takes prepayments or card imprints, the payment step also loads your payment provider’s own scripts, and Adyen’s checkout includes a Google Pay button loaded from pay.google.com. That does not happen anywhere else in the flow.
Your own analytics are separate. If you enter a Google Analytics, Google Tag Manager or Meta Pixel ID under Guest analytics in Zenchef OS, those load inside the widget too, using your own tracking properties, and set their usual cookies (_ga, _fbp, and so on). The plugin cannot tell whether you have configured them, so it does not declare them to your consent plugin – treat them the same way you treat the analytics on the rest of your site.
Depending on your jurisdiction and how you use the widget, you may need to obtain the visitor’s consent before this happens. The plugin is built to make that possible:
- The SDK is loaded by its real URL, so consent platforms that block third-party scripts by URL can detect and block it without any configuration from us.
- The plugin registers with the WP Consent API (https://wordpress.org/plugins/wp-consent-api/) and declares the storage above, so compatible consent plugins can list it accurately.
- The filters documented under Hooks let you suppress loading or add whatever attributes your consent banner blocks on.
Because the SDK is an external script, WordPress also emits a dns-prefetch hint for sdk.zenchef.com. That resolves the domain ahead of time but transfers no data and stores nothing on the visitor’s device. It is removed automatically when zenchef_widget_should_load returns false; note that it is not removed when a consent platform blocks the script by URL, since the hint is a separate element the platform does not touch.
This is a matter for your own legal assessment; the above is a description of the plugin’s behaviour, not legal advice.
Hooks
zenchef_widget_should_load(bool) – return false to suppress the SDK, the widget configuration element and the DNS prefetch hint entirely, for instance until consent has been given.zenchef_widget_script_attributes(array) – attributes of the SDK script tag. Add whatever your consent banner blocks on. Passed $attributes, $handle, $src. Theidattribute is re-applied afterwards and cannot be changed – the SDK locates its own script element by that id and will not start without it.zenchef_widget_consent_category(string) – the WP Consent API category the widget’s non-essential storage is declared under. Defaults tostatistics.
Suppress the widget until your own code decides otherwise:
add_filter( 'zenchef_widget_should_load', function () {
return my_visitor_has_consented();
} );
Mark the script for a banner that blocks by attribute:
add_filter( 'zenchef_widget_script_attributes', function ( $attributes ) {
$attributes['type'] = 'text/plain';
$attributes['data-cookieconsent'] = 'statistics';
return $attributes;
} );
Read more
Installation
- Upload the plugin to your WordPress plugins directory, or install the plugin through your website dashboard, under Plugins / Add new page.
- Activate the plugin through your website dashboard, under Plugins.
- Set your restaurant’s public ID (it starts with
rpid_) on the new settings page that have been added to your dashboard, under Settings / Zenchef widget.
Changelog
1.5.0
- The restaurant ID setting now asks for your restaurant’s public ID, which starts with
rpid_and is shown in your Zenchef dashboard under Settings > Widget > Embed. - Numeric restaurant IDs keep working for now. The settings page shows a reminder inviting you to switch to your public ID.
- Public IDs are now checked for their exact format:
rpid_followed by 8 capital letters and digits. A public ID typed in lowercase is rejected with an explicit message instead of being saved and loading a widget that cannot find the restaurant. The[zenchef_widget]shortcode applies the same check.
1.4.0
- The settings page is now fully translated into French, Dutch, German and Spanish, and those translations ship inside the plugin. Sites set to a regional variant of these languages, such as Belgian French, Swiss German or Mexican Spanish, get the closest one rather than English.
- Fixed: the plugin’s bundled French translation never loaded, because WordPress was pointed at a languages directory that does not exist. French sites only saw the strings translated on translate.wordpress.org.
- For French, Dutch, German and Spanish, the bundled translations now take precedence over translate.wordpress.org, where these languages covered only a handful of the settings-page strings. Every other language is still served from translate.wordpress.org as before.
1.3.0
- Tested with WordPress 7.1 (release candidate 3) and 7.0.3.
- The declared PHP requirement was wrong. The readme claimed PHP 5.6, but the plugin has used PHP 7.0 syntax since 1.2.0 and would fail to load with a parse error on anything older. It now declares PHP 7.4 (what WordPress itself requires from 6.0 onward), and declares it in the plugin header as well, so WordPress refuses activation with a clear message instead of breaking the site. Sites on PHP older than 7.4 will no longer be offered plugin updates.
- All settings-page strings are now available to translators on translate.wordpress.org. Previously 19 of them — the whole per-page shortcode reference — sat in
.phtmltemplates that the WordPress string extractor skips, so they could not be translated in any language. The translation template now covers 59 strings instead of 16. Translating them is a separate, ongoing effort. - The Zenchef SDK is now loaded by its real URL instead of through a local loader script. Cookie consent platforms that block third-party scripts by URL can now detect and block it, which previously was not possible.
- Registers with the WP Consent API (https://wordpress.org/plugins/wp-consent-api/) and declares the storage the booking widget writes, so compatible consent plugins can list it accurately.
- New filters for consent integration:
zenchef_widget_should_load,zenchef_widget_script_attributesandzenchef_widget_consent_category. - The privacy section of the documentation now describes what the booking widget stores on the visitor’s device, and when.
- Existing installs are unaffected — the widget behaves exactly as before unless one of the new filters is used.
1.2.0
- Tested with WordPress 7.0.
- Settings page expanded with language, custom brand colour (with “use the colour set in Zenchef OS” mode and a colour picker), hide-floating-button, explicit auto-open toggle, and disable-GTM / disable-GA4 options. Reorganised into four sections (Restaurant, Appearance, Behaviour, Analytics).
- All new settings can be overridden per-page through the
[zenchef_widget]shortcode. - In-admin shortcode reference card with the full attribute list added below the settings form.
- Existing installs are unaffected — defaults preserve the previous behaviour.
1.1.0
- Restaurant ID is now trimmed and validated on save, so a stray space copy-pasted from the Zenchef dashboard no longer silently breaks the widget. Invalid values are rejected with a clear error notice instead of being saved.
- New
[zenchef_widget]shortcode for inline embedding and per-page configuration overrides (useful for multi-restaurant sites). - Documented how to trigger the booking widget from a custom button in Elementor, Gutenberg, or any other page builder.
1.0
- Initial release of the plugin.
- Basic widget integration and admin settings.
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Zenchef widget integration alternatives
All food plugins →FAQ
Zenchef widget integration: quick answers
Straight answers, pulled from live WordPress.org data.
Source: WordPress.org
Is Zenchef widget integration free?
Yes. Zenchef widget integration is free to download and use from the official WordPress.org plugin directory.
Is Zenchef widget integration safe to use in 2026?
Zenchef widget integration is a solid plugin choice in 2026, with a few things worth checking first. It runs on 2K+ sites and was last updated 3 days ago, and scores 71/100 on our health check.
How many websites use Zenchef widget integration?
Zenchef widget integration is active on 2K+ WordPress websites and has been downloaded 13,012 times since it launched in July 2024. It was downloaded 1,810 times in the last 30 days.
Does Zenchef widget integration work with WordPress 7.1?
Yes. The developer has tested Zenchef widget integration up to WordPress 7.1.5, the latest release. It requires WordPress 4.6 or newer.
What PHP version does Zenchef widget integration need?
Zenchef widget integration requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Zenchef widget integration last updated?
The latest version, 1.5.0, was released on November 16, 2026 (3 days ago).
Who makes Zenchef widget integration?
Zenchef widget integration is developed and maintained by Zenchef.
What are the best alternatives to Zenchef widget integration?
The most popular alternatives to Zenchef widget integration are WP Recipe Maker (50K+ installs), WP Delicious (4K+ installs) and Restaurant & Cafe Addon for… (1K+ installs).
Powered by PageForge
One template and a spreadsheet. A real page for every search.
PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.
- CSV and XLSX, plus Google Sheets on Professional and Enterprise
- Its own title, URL, SEO fields and schema for every page
- Works with the block editor, Elementor, Divi and Avada
- Free on WordPress.org, no credit card


