Restaurant for WooCommerce

1. Overview

Restaurant for WooCommerce turns your WooCommerce products into a one-page ordering menu. You put the shortcode [wxp_restaurant] on a page. Your product categories become the sections of the menu and your products become the dishes. Customers search, filter, add dishes, choose sizes or other variations in a popup, and go to the normal WooCommerce cart and checkout from a slide-in basket, without leaving the page.

The plugin keeps no menu of its own. Names, photos, prices (sale prices included), short descriptions, stock, categories and their order all come from your WooCommerce products. The only thing it adds to a product is one tick box, Is Non-Vegetarian. Orders are ordinary WooCommerce orders, so your payment methods, shipping methods (delivery or local pickup), coupons, taxes and order emails keep working as they do today.

It suits restaurants, cafés, takeaways, pizzerias, bakeries, food trucks and cloud kitchens that already sell through WooCommerce. A paid companion, Advanced Restaurant for WooCommerce, adds extras, opening hours and delivery slots; see How it relates to Advanced Restaurant for WooCommerce.

How it works

1. You put your dishes in WooCommerce product categories (for example Starters, Mains, Drinks).
2. You add [wxp_restaurant] to a page. When the page loads, the plugin lists the categories that have published products, in WooCommerce's category order, and the products of each category in WooCommerce's product order.
3. A customer taps Add on a simple dish, or opens the dish popup to choose a variation. The plugin sends the request to WooCommerce's own AJAX endpoint (?wc-ajax=rfw_add_to_cart), WooCommerce validates it like any add-to-cart, and the basket on the page is refreshed with the result.
4. The customer opens the basket and taps Checkout or View cart. From there everything is standard WooCommerce.

At a glance

What it does not do

• It has no settings. WooCommerce → Restaurant is a help screen, not a settings screen (see The WooCommerce → Restaurant screen).
• It does not offer extras, add-ons or kitchen notes, opening hours, an "Open now" or "Closed" status, or delivery day and time selection. Those are in the paid plugin.
• It does not stop customers ordering at any time of day. Orders are accepted whenever WooCommerce accepts them.
• It does not change the cart page, the checkout page or emails. Orders from the menu look exactly like any other order.
• It does not create order screens for a kitchen, table or QR ordering, printing, or order-status pages.
• It is a shortcode only. It has no block, widget, REST route or WP-CLI command.
• Search looks only in the dish name and the short description. It does not search the long description, categories, SKUs or tags.

How it relates to Advanced Restaurant for WooCommerce

Advanced Restaurant for WooCommerce is the paid companion. Its plugin header calls it "Restaurant for WooCommerce Pro". It replaces this plugin rather than extending it:

• Both can be activated, but only one works. WordPress lets you activate both. When the paid plugin is loaded, this plugin does not start. It registers no shortcode, no menu item and no scripts. The paid plugin provides the same [wxp_restaurant] shortcode, so your menu pages keep working.
• A notice tells you. On the Plugins screen, administrators who can activate plugins see: "Restaurant for WooCommerce Pro is active, so the free Restaurant for WooCommerce plugin is not used. You can deactivate it." You can then deactivate and delete this plugin.
• The check happens when plugins load. This plugin tests for the paid plugin's class or function after all plugins have loaded (plugins_loaded, priority 20), so the order in which the two are loaded does not matter. A network-activated paid plugin on a multisite network counts too.
• The menu changes when you switch. The paid plugin has its own page layout, templates and scripts. CSS variables and theme template overrides written for this plugin do not apply to it. Product data is shared: the Is Non-Vegetarian flag is stored under the same meta key in both.

The tables below compare what each plugin's code does. The paid plugin is described in full in its own documentation.

2. Requirements

3. Installation

1. Make sure WooCommerce is installed and active.
2. Open Plugins → Add Plugin, search for "Restaurant for WooCommerce", then click Install Now and Activate. The menu label is the one in WordPress 7.1.2; older versions word it slightly differently. You can also upload the plugin folder to wp-content/plugins/ and activate it on the Plugins screen.
3. Put your dishes in product categories and tick Is Non-Vegetarian on meat and fish dishes (see The Is Non-Vegetarian flag).
4. Add [wxp_restaurant] to a page with the Shortcode block and publish it.

After activation, a Getting started link appears under the plugin name on the Plugins screen. It opens WooCommerce → Restaurant.

What activation creates

Nothing. The plugin creates no database table, option, user role, page, cron event or upload folder, and registers no activation hook. The only data it ever writes is a product meta value, _is_nonveg, when you save a product in the product editor.

Updating

There is nothing to migrate. Update from the Plugins screen as usual. Version 1.2 redesigned the menu, so if you wrote your own CSS against the markup of version 1.1, check your menu page after updating. The readme's upgrade notice says the same.

Deactivating and deleting

The plugin has no uninstall.php and no deactivation hook. Deactivating or deleting it removes no data. The _is_nonveg value stays on your products, so the flags are still there if you reinstall the plugin or switch to the paid plugin. A page that contains the shortcode shows it as plain text once the plugin is gone.

Multisite

The plugin has no multisite-specific code, apart from one check: it counts the paid plugin as active when that plugin is network-activated, and then stays idle. It stores no per-site or network options.

4. Quick start

1. Open Products → Categories and check that each menu section is a category, in the order you want (drag to reorder). Child categories are listed after their parent.
2. Edit each dish. Add a photo, a price and a short description. Tick Is Non-Vegetarian next to the product type for meat and fish.
3. Create a page, add a Shortcode block, type [wxp_restaurant] and publish. To show only some categories, use [wxp_restaurant categories="starters,mains,drinks"] with category slugs.
4. Open the page, add a dish and open the basket. Check that Checkout takes you to your WooCommerce checkout.
5. Open WooCommerce → Restaurant to see how many categories and dishes the menu lists and which pages contain the shortcode.

5. Features

The shortcode and which dishes it lists

Put the shortcode in the content of a page or post. It prints the menu where it stands. You can use it more than once on a page; each menu gets its own element ID (wxp-menu-1, wxp-menu-2, ...) and all menus on the page share one basket. In the admin area (for example in some page builders' editors) the shortcode prints nothing.

The shortcode also accepts a menu attribute (default lunch). It changes nothing on the page. It is only passed on to the wxp_restaurant_menu_category_args filter as its $menu argument.

Which categories are listed

• Without the categories attribute, the plugin asks WordPress for product categories that are not empty. In WooCommerce 11.1.2, product categories come back in the order you set under Products → Categories. The plugin then arranges them parent first, then that parent's children, and so on. In the wide layout (see below) child categories are indented in the category list, with three indent levels at most.
• With the attribute, categories appear in the order you list them, all at the same level, whether or not they are parents or children.
• A category appears only if at least one of its products can be listed (see below). A section without any listed dish is dropped.
• The number beside each category name and section title is the number of dishes listed in that section. It changes while the customer searches or filters.
• If the category has a description, it is shown under the section title.

Which dishes are listed

• Only products with the status Published. Drafts, private and scheduled products are not listed.
• A product whose catalog visibility is Hidden is not listed. Products set to "Shop only" or "Search results only" are listed. The code excludes only the value hidden.
• If WooCommerce → Settings → Products → Inventory → Hide out of stock items from the catalog is on, out-of-stock products are not listed. Products that are in stock or on backorder are listed. With the setting off, out-of-stock dishes stay on the menu and are marked Sold out.
• A dish in a child category is listed in the child's section only, not repeated in its parent's section.
• Dishes follow the manual order you set with the Sorting link above the product list (Products → All Products → Sorting; WooCommerce's menu_order), then alphabetically by title. There is no limit on the number of dishes per section.
• If nothing can be listed, the page shows: "There is nothing on the menu yet. Please check back soon."

The menu page

The menu has a toolbar (search and Veg filter), a category list, and one section per category.

Category list

• Narrow menus (below 760px wide): a sticky bar of swipeable category chips at the top of the menu. The chip of the section in view is highlighted and scrolled into view.
• Wide menus (760px and above): a sticky column on the left, 180 to 230px wide, with each category and its count. The width that counts is the width of the menu's own container, not of the browser window, so the same page can use either layout depending on your theme's content width.
• Clicking a category scrolls smoothly to its section (jumps at once if the visitor has asked for reduced motion). While scrolling, the active category follows the section in view. At the very bottom of the page the last section is active.
• While a search or filter is active, categories with no matching dish disappear from the list.
• The sticky bar sits at the top of the window, or below the WordPress toolbar when it shows (32px, or 46px up to 782px wide, and 0 up to 600px wide).

Dish rows

Each dish shows a diet mark (green for vegetarian, red for non-vegetarian), the name, the price as WooCommerce prints it (sale prices and variable-price ranges included), the short description, the product photo if it has one, and the order control. On menus 1,180px wide or more, dishes are laid out in two columns.

• Clicking the name or the photo opens the dish popup.
• Simple and variable dishes that can be bought show Add. Variable dishes also show the note Customizable.
• External products, grouped products and other product types (for example subscriptions or bundles) are not ordered from the menu. They show a button instead. External products use the product's own button text, link to the product's external address (the "Product URL" of the product) and open it in a new tab (noopener noreferrer nofollow). Other types use the product's add-to-cart text and link to the product page.
• A dish that is out of stock shows the badge Sold out. A dish that is in stock but cannot be bought (for example a simple product without a price) shows Unavailable. A variable product with no buyable variation shows Sold out.

Search and Veg filter

• The search box filters as you type. It matches the dish name and the short description, ignoring case and accents. Pressing Esc in the box clears it; so does the clear button.
• Veg only and Non-veg only are two tick boxes that work like radio buttons: ticking one unticks the other. Search and filter combine.
• Sections and category entries with no match are hidden. If nothing matches, the page shows "No dishes match your search." and a button, Show the whole menu, that clears the search and the filter.
• The browser may restore text typed before a reload. The script re-applies it when the page loads.

There is no setting to switch the search or the filter off in this plugin. You can hide them with your own CSS (for example .wxp-search { display: none; } and .wxp-diet-filter { display: none; }), or use the paid plugin, which has settings for both.

The Is Non-Vegetarian flag

Edit a product and tick Is Non-Vegetarian in the row of tick boxes next to the product type (where Virtual and Downloadable are). Its help text is "Check if item is Non-Vegetarian." The tick box shows for simple and variable products only. Every product that is not ticked is shown with the vegetarian mark, including product types that do not show the tick box.

• The value is stored in the product meta _is_nonveg as yes or no.
• The plugin saves it only when you save a product from the classic product editor (it hooks woocommerce_admin_process_product_object). Quick edit, bulk edit, the REST API and imports leave the value as it is. Before 1.2, those saves reset it to "no".
• To set it in an import or a script, write the meta key _is_nonveg with the value yes.

Adding dishes: Add button and quantity stepper

On a simple dish, Add adds one to the basket without leaving the page. Once the dish is in the basket, the button turns into a stepper (a minus button, the quantity, a plus button).

• Plus adds one more. It is disabled when the product allows only one per order ("Sold individually") or when the quantity in the basket reached the product's maximum purchasable quantity.
• Minus removes one. At a quantity of 1 the minus button becomes a bin icon, and tapping it removes the dish from the basket.
• The quantity shown on a dish is the total of that product in the basket, including all its variations. If the same dish is in the basket on several lines (for example two sizes), the minus button does not guess which line to reduce. It shows "This item is in your basket more than once. Change the quantity in the basket." and opens the basket.
• Tapping Add (or plus) on a variable dish opens the popup, because a variation has to be chosen.
• Requests from the menu run one after another, so quick repeated taps are handled in order. While a request runs, the control shows a busy state.
• After a successful add, a message appears at the bottom of the screen ("Added to your basket.") with a View basket button. Failures show the reason in a red message for about five seconds.

The dish popup

The popup is a native dialog element, so Esc closes it and focus returns to the control that opened it. Clicking outside the panel or the close button also closes it. On narrow screens it opens as a sheet from the bottom.

• It shows the photo (the product's single-product image), the diet mark, name, price and the short description (the same text as in the dish row; the long description is not shown).
• For a variable dish, each attribute is a group of option buttons (radio buttons) labelled with the attribute name. Values that are the product's default attributes are preselected, and an attribute with a single value is preselected.
• While the customer chooses, option buttons that would lead to a combination that cannot be bought (out of stock, not purchasable, or not existing) are disabled, and the selection is cleared if it becomes invalid. When all attributes are chosen, the price shows the variation's price and the photo switches to the variation's photo if it has one. If the chosen combination is unavailable, the popup says "Sorry, this combination is unavailable. Please choose another one."
• A quantity stepper (minimum 1, maximum the variation's or product's purchasable maximum) sits in the footer next to the button Add to basket, which shows the line total (unit price times quantity, formatted with your WooCommerce currency settings). If options are missing, tapping the button shows "Please choose an option for each choice."
• On success the popup closes and the "Added to your basket." message appears. On failure the message appears inside the popup.
• For external, grouped and other linked products, the popup footer shows the link button; for sold-out and unavailable dishes it shows the badge.

The basket

The basket is printed once, in the page footer, whenever a menu is on the page. It has two parts.

Floating basket button

• Empty basket: a round button with the basket icon (on wide screens it reads "Your basket").
• With items: the item count (total quantity), the subtotal and "View basket". On screens up to 640px wide it becomes a full-width bar at the bottom of the screen.
• On screens up to 767px wide, if the page has Storefront's handheld footer bar, the button is lifted 69px so it does not cover the bar. For other fixed footer bars, set --wxp-basket-lift (see Customising colours and layout).

Basket drawer

• Each line shows the thumbnail, the name, the cart item data (for example the chosen variation), the unit price, a quantity stepper and the line total. The plus button is disabled for "Sold individually" products and when the maximum is reached.
• The footer shows the Subtotal (WooCommerce's cart subtotal, with your tax display setting), the note "Delivery and any discounts are calculated at checkout.", and the buttons Checkout and View cart. They go to the WooCommerce checkout and cart pages.
• An empty basket shows "Your basket is empty" and "Add something tasty from the menu."
• Changing a quantity to 0 removes the line. Errors (for example not enough stock) appear as a message at the bottom of the screen.
• The drawer is a modal dialog: the page behind it does not scroll while it is open.

After every cart change the script refreshes the basket button and drawer from the server's response, then asks the theme to refresh its own mini cart. It triggers the jQuery event wc_fragment_refresh on the page body (if jQuery is on the page) and dispatches the wc-blocks_added_to_cart event on the body. WooCommerce's block scripts listen for that event (found in the WooCommerce 11.1.2 block scripts, including the one used by the Mini-Cart block).

What WooCommerce still checks

The menu is a front end for WooCommerce's cart. Every change goes through the server, where:

• The product must exist and be published, and must be a simple product, or a variable product with a valid variation that belongs to it. Otherwise the customer sees "This item is not available." or "Please choose an option for each choice."
• For "Any ..." attributes (the variation accepts any value), the value the customer chose is sent along and WooCommerce validates it against the product.
• Other plugins' checks on woocommerce_add_to_cart_validation (minimum and maximum quantity plugins, bookings, and so on) run before the item is added, with the same arguments as on a product page. Checks on woocommerce_update_cart_validation run when a quantity changes. Messages those plugins add as WooCommerce error notices are shown to the customer, with WooCommerce's "View cart" button removed.
• WooCommerce's own cart checks run when the item is added: purchasable, in stock, enough stock, sold individually.
• When a quantity is raised in the basket, the plugin checks "Sold individually" ("You can only have 1 %s in your basket.") and stock for products that manage stock without backorders ("Sorry, only N of X are available."). The count includes other basket lines that draw on the same stock.
• Prices are recalculated by WooCommerce on every change, so coupons and tax rules apply as on the cart page.

Security token and page caching

Requests from the menu carry a WordPress nonce (action wooexperts-menu, sent as the check parameter) that is printed into the page. A WordPress nonce is valid for between 12 and 24 hours by default (the nonce_life filter; checked in WordPress 7.1.2). If a page served from a cache carries an expired token, the server answers with the message "Your session has expired. Please reload the page and try again." and a fresh token, and the script repeats the request once with the new token. The customer normally sees nothing.

The cart state on the page (the basket button, the drawer and the quantities on the dish rows) is printed when the page is generated. The script does not ask the server for the cart when the page loads; it updates the state after the first change. A cache that serves one stored copy to visitors who already have items in their basket therefore shows the cached state until they change something. See Troubleshooting.

Customising colours and layout

Colours, radii and shadows are CSS custom properties on the .wxp-root class. The menu, the popup, the basket button, the basket drawer and the message all carry that class, so one rule changes them all. Add your rule under Appearance → Customize → Additional CSS (or Appearance → Editor → Styles → Additional CSS with a block theme):

.wxp-root {
  --wxp-accent: #0f766e;
  --wxp-accent-hover: #115e59;
  --wxp-accent-soft: #e6f4f2;
}

Template overrides

Since 1.2, you can copy templates/menu.php or templates/basket.php from the plugin folder to your-theme/restaurant-for-woocommerce/ and edit the copy. WooCommerce looks for your-theme/restaurant-for-woocommerce/menu.php and, as a fallback, your-theme/menu.php (child theme first, then parent theme; checked in WooCommerce 11.1.2). A file called menu.php or basket.php in the root of your theme therefore replaces the plugin's template too.

• menu.php prints the menu. It receives $items (products per category slug), $cats (per slug: id, name, count, description, depth), $instance (1 for the first menu on the page) and $cart (the cart state).
• basket.php prints the floating button and the drawer. It receives no variables.
• dashboard.php (the admin screen) is included directly and cannot be overridden.
• The bundled script looks for the class names and data attributes used by the templates (data-wxp-menu, data-product, .wxp-item, .wxp-add, .wxp-drawer and so on). Keep them when you edit a copy.

Sticky positioning in themes

Sticky elements stop working inside a parent that has overflow: hidden, which several themes use. To keep the category list sticky, the menu script looks at the menu's ancestors and, for any that hide overflow, sets the inline style overflow: clip (which clips the same way without breaking sticky). It does this in the visitor's browser on every page with a menu. If a theme element misbehaves, that is the first place to look.

The WooCommerce → Restaurant screen

Open WooCommerce → Restaurant (menu slug wxp-restaurant, for users who can manage_woocommerce). The screen, titled "Restaurant for WooCommerce" with the version number, has no form and saves nothing.

The screen's own stylesheet and script load only on this screen.

Options from the paid plugin in the cart

If a cart contains items that were added by the paid plugin with options (cart item data under the key wxp-menu), this plugin still shows those options on the cart item, adds the options' prices to the item price, and copies the options to the order line item as item meta. This covers customers whose cart was created while the paid plugin was active. This plugin never creates such options itself.

• The cart shows each option group as a name and value list. Options with a price show "(+price)" after the name.
• The price is added to the item every time WooCommerce loads the cart from the session and again before totals are calculated. The code guards against adding it twice to the same product object.
• The plugin also removes any cart item data row whose name is empty and whose value (or display text) is empty, for every cart item, whichever plugin added it (it filters woocommerce_get_item_data).

Accessibility and translation

• Controls are real buttons and links. The popup and the basket are modal dialogs with labels. Stepper quantities are announced as they change. Keyboard users keep focus in the right place when the basket is redrawn.
• Animations are switched off for visitors who prefer reduced motion.
• Text is translatable with the text domain restaurant-for-woocommerce. The plugin folder contains no translation files. Strings that the scripts show are passed in from PHP, so they translate too.

6. Developer reference

Shortcode

Filters

The plugin fires three filters of its own. It fires no actions.

Exclude two products from every section:

add_filter( 'wxp_restaurant_menu_product_args', function ( $args, $slug, $atts ) {
    $args['exclude'] = array( 123, 456 ); // product IDs
    return $args;
}, 10, 3 );

Leave one category out of every menu (term ID 15):

add_filter( 'wxp_restaurant_menu_category_args', function ( $args, $menu, $atts ) {
    $args['exclude'] = array( 15 ); // term ID
    return $args;
}, 10, 3 );

Mark dishes tagged "fish" as non-vegetarian without touching the product. Both the row and the popup read the diet, so set it in both places:

add_filter( 'wxp_restaurant_menu_item_data', function ( $data, $product ) {
    if ( has_term( 'fish', 'product_tag', $product->get_id() ) ) {
        $data['diet']         = 'non-veg';
        $data['json']['diet'] = 'non-veg';
    }
    return $data;
}, 10, 2 );

AJAX endpoints

Requests go to WooCommerce's AJAX endpoint, ?wc-ajax=rfw_<action>, as POST. They are available to logged-out visitors. Every handler verifies the nonce (action wooexperts-menu, POST parameter check) before it changes the cart.

Every response is JSON with these keys:

• res: true or false.
• message: the text to show the customer.
• fragments: div.wxp-drawer-content (the drawer's HTML) and button.wxp-basket-btn (the floating button). The script replaces the elements that match each selector.
• cart: count, subtotal (plain text) and products (product ID to qty and keys, the cart item keys).
• On a nonce failure: code = nonce and a new nonce.

The older endpoint ?wexperts-ajax=add_to_cart (or remove_item, update_item) still works, for pages cached with the version 1.1 script. It runs on template_redirect at priority 0, defines DOING_AJAX and sends no-cache headers.

An example from a page that has a menu (the script's wxpmenu object exists only there):

fetch( wxpmenu.ajax_url.replace( '%%endpoint%%', 'rfw_add_to_cart' ), {
  method: 'POST',
  credentials: 'same-origin',
  headers: { 'Content-Type': 'application/x-www-form-urlencoded; charset=UTF-8' },
  body: new URLSearchParams( { data: 'product=123&quantity=1', check: wxpmenu.nonce } ).toString()
} ).then( function ( r ) { return r.json(); } ).then( console.log );

JavaScript configuration and events

The script assets/js/menu.js (handle restaurant-script, loaded in the footer with defer, no dependencies) receives a global object wxpmenu printed by wp_localize_script(). The style handle is restaurant-style. Both are registered on every front page and enqueued only when the shortcode is rendered.

After each cart change the script triggers wc_fragment_refresh on document.body (jQuery event, only if jQuery exists) and dispatches the DOM event wc-blocks_added_to_cart on document.body.

PHP classes and functions

The plugin does not declare a public PHP API. These are the helpers its own templates call.

• wxp_restaurant() returns the main object (class WooExperts_Restaurant). Its get_options( $product ) returns the variation data for the popup.
• WooExperts_Load_Restaurant (in classes/load-restaurant.php) registers the shortcode and the product tick box. get_menu_categories(), get_menu_items(), get_item_data() and esc_data() build the data for menu.php.
• RFW_WExperts_AJAX (in classes/ajax.php) handles the endpoints and builds the basket HTML: get_cart_state(), get_basket_button_html(), get_sidecart_html(), stepper_html() and icon().
• wxp_restaurant_pro_is_active() returns true when the paid plugin's class WooExperts_Restaurant_Pro or function wxp_restaurant_pro() exists.
• Constants: WXP_RESTAURANT_FILE (the plugin's main file) and WXP_RESTAURANT_VER (1.2).

WordPress and WooCommerce hooks the plugin uses

The plugin calls these WooCommerce filters and actions itself, so other plugins' callbacks run: woocommerce_add_to_cart_validation, woocommerce_update_cart_validation, woocommerce_ajax_added_to_cart, woocommerce_cart_item_product, woocommerce_widget_cart_item_visible, woocommerce_cart_item_name, woocommerce_cart_item_thumbnail, woocommerce_cart_item_price and woocommerce_cart_item_subtotal.

Data the plugin reads and writes

The plugin has no options of its own, no custom tables, no user meta, no transients, no cron events, no roles, no custom capabilities and no REST routes. The only capability it checks is manage_woocommerce for the admin screen.

File layout

• restaurant-for-woocommerce.php: header, bootstrap, the free/paid check, admin menu, variation data.
• classes/load-restaurant.php: shortcode, categories, products, item data, script registration, cart-item handling.
• classes/ajax.php: AJAX handlers and basket HTML.
• templates/menu.php, templates/basket.php, templates/dashboard.php.
• assets/js/menu.js, assets/js/admin.js, assets/css/front.css, assets/css/admin.css.
• readme.txt.

7. Privacy

8. Troubleshooting

9. FAQ

10. Changelog

1.2 - 29/09/2026

• New - Redesigned menu: dish rows with photos, one-tap Add buttons that become quantity steppers, category chips on phones, sticky category list on desktop, live search in names and descriptions.
• New - Dish popup (native dialog, no jQuery plugins) with option buttons for variations, disabled out-of-stock combinations, default attributes, variation photo and price, quantity and live total.
• New - Basket drawer with quantity steppers, line totals, subtotal, Checkout and View cart; floating basket button with item count and total (bar at the bottom on phones).
• New - Shortcode attribute categories="slug1,slug2".
• New - Nested categories are listed parent first, then their children; dishes of a child category are no longer repeated in the parent's section.
• New - Dishes follow the product sort order, and products hidden from the catalog or out of stock (with "Hide out of stock items") are not listed.
• New - External, grouped and other product types link to their product page; sold-out and unavailable dishes are marked.
• New - Templates can be overridden in your-theme/restaurant-for-woocommerce/; colours can be changed with CSS variables.
• New - WooCommerce > Restaurant screen with getting started steps, copyable shortcodes, pages using the menu and FAQ.
• New - Declared compatibility with HPOS and Cart/Checkout blocks; header mini carts refresh after changes from the menu.
• Fix - Only 10 items per category were shown (default query limit); all published dishes are now listed.
• Fix - "Any" variations with custom attributes of more than one word (for example "Extra Hot") could not be added to the basket.
• Fix - Stock limits, "Sold individually" and other plugins' add-to-cart validation are applied to menu orders and quantity changes; WooCommerce error messages are shown to the customer.
• Fix - Pages served from a full-page cache with an expired security token now retry automatically instead of failing.
• Fix - Menu styles and scripts were not loaded with block themes.
• Fix - Fatal error when the add-to-cart request contained a missing or invalid product.
• Fix - "Is Non-Vegetarian" flag was reset to "no" whenever a product was saved outside the product editor (quick edit, REST API, imports).
• Fix - Add-to-cart failures (out of stock, expired session, network error) left the menu blocked.
• Fix - The plugin also loaded next to the Pro version on multisite when WooCommerce was network-activated.
• Fix - The plugin screen hid all admin notices.
• Fix - PHP 8.2+ deprecations; all output escaped; Plugin Check clean.
• Tweak - Removed fancybox, the icon font and the BlockUI dependency (smaller, faster pages).
• Tweak - AJAX requests use the WooCommerce AJAX endpoint (the old endpoint still works).
• Tweak - Text domain changed to restaurant-for-woocommerce; tested with WordPress 7.1, WooCommerce 11.1 and PHP 8.2 - 8.5.

1.1 - 30/07/2022

• Tweak - Minor fix and compatibility check.

1.0 - 04/05/2021

• Initial release.

11. Support

For help, see WooCommerce → Restaurant in your dashboard, open a topic in the WordPress.org support forum, or email support@wpexpertshub.com.

When you write, include:

• The plugin version (1.2 or the version you run), your WordPress version and your PHP version.
• Your WooCommerce version and the name of your theme.
• The address of the page with the menu, and the exact shortcode you used.
• What you expected, what happened, and what you already tried. A screenshot of any message and the browser console output help.